Bounded Volume Camera Window Resizing Limit Not Working?

[psyabcd]

I’m testing out the volume camera resizing functions using play to device on a vision pro device. I found out that all properties under “Output Dimensions Options” (the “Window Resizing Limits” as well as the min&max window size) are not taking effect.

I’m using basically the same scene in the post here. The only difference is that I removed the unbounded volume camera.

Content scale when ScaleContentWithWindow property is disabled

For the scale - yes, that’s correct. That would be the scale of the gameObject the VolumeCamera component is attached to. I’ve mocked up a small scene showing what I mean with creating an unbounded volume camera in the scene and setting the transform.Scale to 0.5x0.5x0.5. You can see that the two cubes, although in different volume windows (one is in a bounded and one is in an unbounded), are roughly the same size (I tried my best to position them next to each other, but the bounded one is slig…

If I set the “Window Resizing Limits” to “Fixed Size”, I can still resize the volume on device.

If I set the “Window Resizing Limits” to “Limit Minimum And Maximum Size” and change the min&max size limits, those limits don’t seem to work.

[vcheung-unity]

Hi,

Couple of quick points here, which may or may not apply to your scene:

• Modifying WindowResizingLimits during runtime is not supported.
• WindowResizingLimits will not work during P2D connections - P2D has a fixed set of window output configurations and tries its best to match your scene’s requested volume with that list.
• Ensure that there’s only one unique volume window output configuration per OutputDimension (only applies to Bounded volumes) in your scene, otherwise on run-time, it may be a toss up on which output configuration actually gets used.

That being said, once you build an Xcode project, there should be a file called UnityVisionOSSettings.swift in the project. Can you post a snippet or copy+paste the contents of that, especially the stuff in mainScenePart0? That should show what the output configurations are actually being defined as in RealityKit.