This might be a known issue, but I haven’t seen it mentioned in the recent beta patch notes. Speedtree lods are going haywire when playing with the HTC Vive. (Playing in editor without VR everything is fine)
Scales for different lods seem to be off
Transitions seem to snap back and forth a few times before settling
This happens no matter how the lod transition is configured; none, fade, animated, doesn’t make a difference.
I’m on beta 11, SteamVR plugin is up-to-date. I’m not using single-pass stereo rendering. I’ve reimported the speedtree asset and let it regenerate materials, no dice.
Still trying to figure out what makes it go from working to broken state. Funny thing is I can break them in entirely different ways just by varying parameters of the TreeInstances in the terrain data. Now the billboards are actually OK, but the hero-lod-level explodes:
Still appears this only happens in builds, but this at least is presenting itself in both VR and non-VR builds.
Actually, Unity’s LOD selection seems to change completely when I switch VR support on and off. Without VR a tree is only culled at several kilometers away from the camera, but with VR support they’ll be culled way closer the camera.
Is that a bug or some secret automatic LOD bias being applied?
Had the same problem. Then I realized LODs are based on their size in screenspace. With VR its actual size in screenspace is based on the one screen that is rendered (the double image), rather then it’s relative size to one eye. Bump up the LOD bias in the quality settings. I just detect if a vr device is present and have it adjust the bias so they’re about the same wether I’m testing with vr on or off.
I was contacted by support, they were not able to reproduce it. After my comment what I believe they were doing wrong. No response after that for nearly 2 months.
In meantime, scene specific trick wasn’t working for me after some change, so I must have reverted through source control. Otherwise whole project would be …
Starting to be hopeless. Showstopper with exact repro project although big. And no fix for months.
I do not like to say it but in fact it’s there at least from 10.12.2015 I have created same bug case 752862 for different Unity version. I’m not sure why speedtree bugs are not solved with highest priority. It was an showpiece of Unity 5 release. Something that represents AAA quality inside of Unity…
Both case open. 752862 without reaction. 781150 was at least noticed… Maybe I’m little sad but I need to notice that I’m pro user
