Search Unity

  1. Unity 2020.1 has been released.
    Dismiss Notice
  2. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice

[SOLVED] Issue with rendering. Looks good in editor, lots of artifact in build.

Discussion in 'Daydream' started by mat9054, Jun 22, 2018.

  1. mat9054

    mat9054

    Joined:
    Nov 14, 2015
    Posts:
    42
    Hi, Im bringing a game I did for Windows mixed reality. I want to bake lights and shadows in each scene so it runs better, but I'm having issues with baked GI. I am using subtractive lighting mode with mixed directional light. In the editor everything looks good, when I build the apk, there is a lot of artifact that moves when camera (head) is moving. I also enabled generate lightmap uv on each model I am using in that scene.

    This is what I see when I run the apk.
    https://imgur.com/a/avXnbtZ

    This is in the same view in the editor.
    https://imgur.com/a/Zq6rre5

    This is my lighting settings.
    https://imgur.com/a/8suoEUL
    https://imgur.com/a/ooAtfXZ

    This is my player settings.
    https://imgur.com/a/xD03EQI

    Here's project quality setting.
    https://imgur.com/a/swY8MKs


    Any help would be highly appreciate.
     
  2. mat9054

    mat9054

    Joined:
    Nov 14, 2015
    Posts:
    42
    After hours playing around with my lighting and rendering, I saw this post from unityinhance in Best Practice thread.

    "Also, enable 24-Bit Depth Buffer under Project Settings -> Player -> Other Settings -> Daydream VR SDK. This will get rid of shimmering "zig-zag" edges and provide a more consistent framerate. "

    And SiliconDroid also gave a good explanation,

    "Yeah if the difference between the magnitudes of your cameras near and far clip planes is too great then 16 bits simply isn't enough to sort triangle pixel depths and so you get ambiguous triangle edge interfaces. Or if you put two surfaces too close you'll get z-fighting as both surfaces dance around the same depth value.

    In VR we need quite a good clip plane range, so 24 bits recommended.

    A ratio of 500:1 or below for 16 bit... so you'll get away with 16 bits if you had say near of 10cm and far of 50m.

    16 bit depth is a little faster though, more so on older devices. "
     
unityunity