Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Unity 2018.3 is now released.
    Dismiss Notice
  6. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Daydream rendering issue with Skinned Mesh Renderer.

Discussion in 'Daydream' started by Imbazephyr, Jan 25, 2019.

  1. Imbazephyr

    Imbazephyr

    Joined:
    Jul 2, 2015
    Posts:
    5
    Hi all,

    This is a strange issue I'm running into. I have a model which uses the skinned mesh renderer component, which seems to cause some seizure-inducing flashing when built and deployed onto the Mirage Solo headset.

    I have conducted some testing on my own behalf:
    1. I have built the exact same project onto a Oculus Go, and this issue is not present.
    2. I have replaced the skinned mesh renderer component with mesh filter + mesh renderer, and they seem to work fine on daydream as well.

    I'm developing on Mac, and my Unity version is 2018.3.1f1.
    I have attached some screenshots:
    This is what my game looks like in the editor compare to how it looks in the headset
    Screen Shot 2019-01-24 at 11.09.13 PM.png troubleshoot.JPG

    Here is a screenshot for my skinned mesh renderer component:
    Screen Shot 2019-01-24 at 11.18.42 PM.png
    If anyone else has encountered this, please feel free to share some thoughts.

    Thank you.
     
  2. Xarbrough

    Xarbrough

    Joined:
    Dec 11, 2014
    Posts:
    311
    Could it be the same issue as detailed in my thread here? If so, the bug was reported and reproduced by Unity.

    In the meantime I found that it’s possible to change to an earlier Unity version if no other issues prevent it. Or, you can implement custom skinning, e.g. search for “DualQuaternionSkinning for Unity” online. We actually used said community code to work around our issues.