#WOLFENSTEIN THE NEW ORDER WON'T START PLUS#

You start the mission in what we shall call 'the torpedo chamber'.

That means small corridors & tight spaces. This mission is a prime opportunity for you to work on challenges that require you to play guns blazing. The next mission is relatively short, but it's an action packed adventure with explosions and lots of bullets. (At least the unique one will require more than a 4 GB GPU from what I've noticed and the VMTR one seems to affect weapons and other items but setting that to 16384 with the two above compressions disabled causes severe stuttering but the game won't hang like it will with the unique one which affects most everything else in the game using textures.There won't be a safehouse mission this time. Or 16384 but that needs a very high end machine if you have these two set. If you set those to 512 instead and then use vt_restart most of the game should be blurry but as you walk forward and then back (Like pressing right up to a wall for instance.) you should notice texture clarity increase and decrease when you are very close to objects whereas if you use 8192 they use high quality for a much larger area. Vt_pageImageSizeUniqueDiffuseOnly2 '8192' but I don't know if it works as actual resolution or if it's more like LOD like the texture settings. Yeah that's the shadow buffer, kinda works as a resolution for shadows (They're kinda pre-baked instead of fully dynamic - unless you use the slowmap command which will force a level to load with fully dynamic but highly unoptimized lighting, crashes in Wolfenstein though and needs the ењ†4 version of Rage.) - though character shadows might be different. Image_LODBias is a oddity, you can use the console prompt to exec a configuration but you won't see a visual difference unless you enter it manually though even then no matter what you set it to it won't make a visual difference, that is until you next start the game. (VT_LODBias takes effect without restarting the game or without even having to use vt_restart and can be set from -2 up to 8 or so although positive values will greatly decrease texture quality of course, I'd set it to -2 for quality reasons since it won't have the strong sharpening effect that image_lodbias has.) Load a level and you should immediately notice severe sharpening, of course you can enter the command without restarting the game but it won't have any effect then. I'd post some comparison screenshots but it's easy enough to test, start the game and at the main menu bring down the consome prompt (Ctrl+Shift+Tilde or ~ as the symbol for it is.) enter 'image_lodbias -2' minus the quotes and press enter to input it, now quit the game and start it back up and again bring down the console prompt and write 'image_lodbias' again (Press enter to confirm.) and it should display as -2 already which means it's set correctly.

#WOLFENSTEIN THE NEW ORDER WON'T START PLUS#

That's because the command only takes effect on start so you have to enter it manually into the console (exec *.cfg files will not write it into wolfconfig.cfg where it needs to be to load that early during startup process.) and the value should be within 0 to -0.5 in value although the max range is 2 to -2 but you don't want to use -2 it'll oversharpen the entire image (Even 0.1 which I'm currently using is a bit too sharp in some areas.) plus it will cause visual glitches and can also destabilize the game. Click to expand.Image_LODBias is a oddity, you can use the console prompt to exec a configuration but you won't see a visual difference unless you enter it manually though even then no matter what you set it to it won't make a visual difference, that is until you next start the game.

Wolfenstein the new order won't start