SceneContentAdjuster doesn't work on device
See original GitHub issueSceneContentAdjuster
only seems to work in Play mode. When I build and deploy to an immersive HMD, the object stays at the preset height.
SceneContentAdjuster
also overwrites the X and Z values (to 0) instead of just the height, which doesn’t seem ideal.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Troubleshoot scenes and 3D data—Portal for ArcGIS
Issues you may encounter when working with scenes, hosted scene layers, or 3D data in the portal and their suggested solutions are listed....
Read more >Troubleshooting - Bakery GPU Lightmapper: Wiki - geom.io
Using a version control system I copied the scene to another PC and it doesn't look right. Make sure you followed version control...
Read more >Detect edit points using Scene Edit Detection
Using scene detection helps you to automatically get the cut points without having to go through the footage manually.
Read more >Troubleshooting issues related to playback and performance
Sometimes you may face issues where the playback doesn't work after hitting the play button. Usually, such issues occur due to Audio ......
Read more >Light/Exposure Adjusting Automatically - SOLVED
I understood 90% of the work and now I can adjust the exposure of the scene based on the physical settings in HDRP...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The more I look at
SceneContentAdjuster
, to more I’m not sure I understand how it works. It looks like it “worked” in the Editor because that was special cased inAwake
to be 1 meter high.On device, the
Update
loop was putting it at (0, 0, 0), due to a bug inTryGetDimensions
.What we should be getting is the offset between the floor and the head at app launch, right?
Off-topic, but I don’t think we’re using
TryGetDimensions
right there even without the Unity bug. It looks like it gives us the bounds dimensions, which means the Y value would be the height of the bounds itself, not the Y value of the floor.Looks like GitHub didn’t automatically close these issues when merged into master. I’ll close these manually and look into why.