Observer․: If they are going that route, they should change the options to Dynamic, Dynamic (override world), and rename forced to Extreme Mode or something. And again, make them accessible.

Dynamic Mode cannot break any world in a way that isn't easily fixed by the creator (allowing them to force dynamic off is completely unnecessary tbh). Only forced mode (0.001 nearclip) can cause unsolvable graphical bugs.

GenesisAria: You wouldn't be overriding anything the world creator has set. Just like you can't jump in a world with jump disabled. The toggles that were teased are a way of forcing some things or instance creators to turn certain features on or off as well.

The idea here is world creators need to understand how the camera works, and if they choose to force a specific viewing frustum they can do so.

I'm all for dynamic being on by default, that's what I use to not break the world I'm in while retaining the view I want in VR.

Observer․: Yes but then we're going to get multiple obnoxious creators that will force a specific settings because they don't realize that their issue is easily fixed via other means (or just want to be a stick in the mud). I never approve of world creator authority, they are the minority, their customers are the masses, and the customer is always right. Forced authority at the hand of world creators has never ended up well for the majority users in vrchat. If creators want people to use their worlds more, they should strop trying to control everyone. Replayability comes with freedom.

ps: nobody wants to stay for long in worlds that don't have jump; also jump was never "disabled", it was just not added in the default sdk2 world prefab, so you had to manually add it.

GenesisAria: As a developer you very much need control over the camera in many scenarios, from framing all the way to optimisation.

With the system teased, if it ever gets into any form of development (because I don't know what stage it is in), then I believe the players will need to be notified of what is enabled or disabled when they load into the world.

It's not as if you would not know your settings is being forced off, and you can leave. If suddenly every world creator is forcing it off then something else is wrong entirely.

Observer․: You only need control over the farplane for optimization (though even that is largely unnecessary if you have good occlusion culling and/or occlusion portals set up). As a casual developer and researcher on topics such as these, i know the nuances of how and why. And framing is very easily worked within >=0.01 nearplane. Dynamic Mode is a non-issue, it needs to stop being made into one.

My point still stands about the control precedent. They are the primary reason we were never allowed to properly fly (amongst numerous other things), was because of a select few world creators that couldn't stop complaining about stuff like flying avatar colliders (they'd even keep jump off to prevent people from flying up even in worlds without games). It's to the point it just gets silly. I suppose they'll find out the hard way that people won't like their control schemes.

The onus should be on the world creator to fix their buggy/bad design, not give them a lazy 1-click solution that causes problems for users.

Observer․: I can see a reason for blocking forced mode (due to issues with rendering, or needing a long view distance), however, dynamic mode I feel should always be available.

It is worth noting that players who use very small avatars may run into issues (or for those that phantom sense, physical discomfort) if the near clip plan is forced to far. A world that forces a too distant near clip plane would be preventing those players form exploring the world in their preferred avatar when they otherwise would have been fine.

AirGamer: People using exceedingly tiny avatars are minority, and this topic was more used as an accessibility excuse to get more clip plane options. If you want to go to something like test pilots, don't expect to be in a tiny avatar, that's just a technical limitation of the engine in it's current state. That or the world creator would have to employ fancy game dev tricks to skirt around this by doing stuff such as illusory perspective (in shaders) and make stuff closer than they seem.

AirGamer: The issues of dynamic mode are extremely rare. I've only seen a couple worlds have any noticeable skybox issues, and that's including back in context of the mod forcing it to always be 0.01 in every world. It's impact is dramatically overstated, and also very easily fixed by the world creator (tested and proven). ps: i world hop a lot so i see many many worlds.

GenesisAria: I was thinking more for those using forced mode, I always normally use dynamic myself.

It's worth noting that forced can cause more than just skybox/fog issues, I recall back in the modded days someone encountered a world where the lighting was broken with the near clip plane mod active, although an exceedingly rare issue I believe.

It does however serve as another reason to move it back to the quick menu, beyond just quick access.

AirGamer: Yeah i've seen plenty of lighting/shadow issues, as well as floating point exacerbating as pointed out here, caused by forced mode or setting clip to 0.001 with mods:

I'm well aware of the issues it can cause. Hence they should be separated as settings, because they are completely different animals. If dynamic mode is causing these issues, it is folly on the part of the world creator as they set things up in a delicate or incorrect way.