LODGroup in DayDream

LODGroup behaves very differently in Daydream on device than in the editor. It seems to select *far* lower LOD levels at the same distance on device than in editor. I've seen some whispers of this for Gear VR, where people are simply doing things like setting their QualitySettings.lodBias = 3.8 when they're not in the editor.

What's the correct answer here, though? Is this a bug? Or is this expected since the display is in stereo and the screen size of objects is actually smaller on each display, even though it would be larger if the entire display were a single eye?

Thanks!

 

Bump - anybody know anything about this? @joejo ?

 

But the work flow for using lodgroup is to drag the dividers between the levels of detail, which causes the scene view camera to visibility zoom out until you've reached the desired size/distance for that lod level. This is the scene view, not the game view, so no stereo, etc at this stage. This then translate really well to similar size/distance at runtime across various screen resolutions and mobile/desktop/web platforms, but falls completely apart in vr. Why is that?

And whatever the reason, how are we to properly use this component for platforms or daydream, where what we see during the work flow described above at authoring time bears no resemblance whatsoever to the results at runtime? How does one know what parameters to select at authoring time when the visual controls for this thing simply lie in the editor? By trial and error? Or is there some lod bias number that should simply correct it for daydream?

Thanks!

 

I will create a simple repro project and file a bug report, then post it here and in 5.6. Thanks for offering to help, joejo!

 

It's submitted as bug case number 879100 and it has a very simple repro project attached, including an already-built APK of the project to try on Daydream. The bug report includes all of the details about what to observe in editor vs daydream headset.