I currently have an issue that I am unable to resolve myself.
I have a problem with my Quality Settings where a build running on different computers utilizes different quality settings.
It appears that when run on my high end home PC and on my work PC, the build seems to drop its quality to the very low setting.
But on other PCs running the very same build, this does not occur. It has even been tested on a standard laptop and shows no loss of quality as what occurs on my PCs.
I am unsure what could have changed in my project to cause such a discrepancy of quality between multiple computers and am now reaching out to the community.
I currently use Unity 2019.4.12 and 2019.4.7
The Quality Settings are defaulted on PC Standalone to use Unity’s Ultra Quality profile.
It was confirmed with testing involving Realtime Reflection Probes that the quality was dropping to Very Low Quality profile in standalone builds on certain PCs.
I’ve had this happen before - but I will have to do some digging to provide the exact answer. It’s something with the registry settings however. Try changing the company name in your publish settings - it will write new reg info that way…
1 Like
Thanks daveMennenoh, that worked.
I altered my company name in Player Settings to Test, and for good extra measure also changed the product name to Test and created a new build.
Once the build launched, the lighting issues I have been having were no longer visible.
I will need to assess further whether I should alter my Windows Registry to fix the previous Company name or discuss with my team about changing the Company name to something new.
1 Like
When you run a build for the first time, it uses the default quality setting you’ve chosen. At some point before your build exits it saves that setting (along with screen resolution and other settings) to a location near where playerprefs are also stored. In the case of Windows this is in the registry. Every subsequent time you launch your build it will ignore the defaults in the build and use the previously saved settings.
This is a problem if you change those defaults and never intend for the previous defaults to be accessible, but it is done because once you ship your game it would really piss people off if every time your players get an update it resets all their resolution and quality settings making them have to go to your game settings window and fix them again.
I had read there was some changes to this behavior coming in some either recent or near future version of Unity, but I don’t recall exactly what those changes were.
I would expect changing the company name in your project will change the location of where those registry settings are stored, so yeah that is a kind of weird work around, but it should think it is a first time run when it doesn’t find the previously saved settings in the new location. What I’d do if you are having trouble finding this in the registry, is just save a pretty unique string to playerprefs, exit your build, and then search the registry for it. Then just delete the entire folder (or whatever name they use for folders in the registry) with your company name. Should be back to the way a first run is with all defaults.