i'll make this quick, as it was something discovered during the "demo" 3 months ago.

step 0: set up your graphics settings before doing all this. you wont be able to change anything after. put texture quality to low for the biggest vram gains, of course!

step 1: open file explorer and navigate to this directory:
C:\Users\*your username*\Documents\My Games\Test Drive Unlimited Solar Crown
alternatively: just click on documents, ^ then follow what's written above this section ^

step 2: open UserSettings.cfg (if windows asks you what program to use, select notepad)

step 3: press ctrl+f and type maxfps into the "find what" section. press find next and you'll see a blue highlight on Engine.Device.MaxFPS and should look something like this:


step 4: change the value to something thats lower than 200 (i personally set it to 60 because i use lossless scaling with this game)

step 5: save the file (NOT AS A NEW FILE!) then right click UserSettings.cfg and click Properties (usually at the bottom)

step 6: at the bottom of the properties tab, click on "Read-Only" next to the Attributes section. it should look something like this:


step 7: launch the game and you'll see that your vram usage has been lowered significantly!

step 8 (not recommended, only try if you know what you're doing!): revert Engine.Device.MaxFPS to 200, and uncheck read-only in the properties tab. it (probably) won't change the vram usage back to 11+gb, but more testing should be done with this.

here's the before and after shots: (fun fact: setting texture quality to low makes the game think it only needs around 4gb of vram! it still uses at least 5gb, though.)

this is just a section to compile solar crown's vram issue. it's unconfirmed whether this method is guaranteed to work for you, so your mileage may vary!

https://psteamcommunity.yuanyoumao.com/app/1249970/discussions/0/7404569601242750734/ - there's a 50/50 on if this method works or not

https://psteamcommunity.yuanyoumao.com/app/1249970/discussions/0/7404569601241679515/ - updating drivers apparently fixes the bug?