User overrides for platform settings #643
Conversation
|
So the plan is to get the user-friendly version of this out there so we can encourage people to try different settings and decide on better defaults. Once we have a good default we should move that settings into an in-app editable dialog. However - I suspect most of these settings aren't terribly interesting or useful. So some can just live in the config file in perpetuity. |
|
Should we revisit #108 in this context? :-) Otherwise, looks good! |
|
I've realised that most of the interesting performance stuff happens in AppQualitySettingLevels. I think you can already override this to some degree in the config but I need to investigate properly. |
The full PR had multiple commits but the only one that had any effect was the change to "QualityLevels Mobile.asset" which has issues in any case.
This reverts commit f2451db.
|
Undecided what to do with this. It's not amazingly useful unless we also investigate the auto-quality switching and undo the problems caused by #5 which disabled bloom but didn't remove or adjust the associated quality levels. Therefore the quality level switching is behaving erratically. We should either reinstate/fix mobile bloom or remove the last two quality levels. |
|
Thinking about this some more... Some of differences between PC and Quest are where there's a separate mobile panel. It would be good to maybe bring some of these across where it's technically possible, initially hidden behind a config setting. "Select All/Invert Selection" springs to mind but I'm sure there's a list somewhere in the docs. The only places we can't do this is where the required libraries are PC only. e.g. video rendering, fbx export, "export selected strokes" (which relies on USD). |
No description provided.