The primary culprit for Wolfenstein II’s launch issues is the way it handles high-performance features like Async Compute and Image Streaming. If the game detects an outdated driver or a secondary display adapter (like Intel HD Graphics), it may crash before the menu appears. Modifying the configuration file allows you to strip away these taxing features and hard-code your native resolution, which is the most reliable way to fix the “Black Screen” and “Console Dump” errors.
Hardware Compatibility & Expectations
- Async Compute Conflict: While designed for AMD GCN and newer NVIDIA architectures, it is a common point of failure on older drivers. Disabling it via config is the #1 fix.
- Integrated Graphics Bug: The game often tries to launch using your CPU’s integrated GPU instead of your dedicated card. Disabling the iGPU in Device Manager is recommended alongside these tweaks.
- Vulkan Support: Ensure your GPU supports Vulkan 1.1+. If your card is older than the GTX 600 or HD 7000 series, the game may not launch regardless of config edits.
Backup and Preparation
Editing the .local file is safe, but the game may overwrite your changes if the Steam Cloud is active.
- Completely exit Wolfenstein II and the Steam/GOG launcher.
- Navigate to the saved games directory (path below).
- Right-click Wolfenstein II The New ColossusConfig.local, select Copy, and save a backup to your desktop.
- Open the original file with Notepad++.
File Location
The configuration file is tucked away in your user’s “Saved Games” folder: C:\Users\%USERNAME%\Saved Games\MachineGames\Wolfenstein II The New Colossus\base\Wolfenstein II The New ColossusConfig.local
Best Config Settings to Prevent Crashes
Search for these parameters or add them at the bottom of the file if they are missing:
r_enableAsyncCompute "0"
is_poolsize "4096"
r_mode "19"
r_fullscreen "2"
r_windowWidth "1920"
r_windowHeight "1080"
r_initialModeWidth "1920"
r_initialModeHeight "1080"Pro Tip: If you cannot find the file because the game has never successfully launched, you can create a new text file, paste the commands above, and rename it to
Wolfenstein II The New ColossusConfig.local.
Key Parameters Explained
| Parameter | Recommended Value | Impact |
| r_enableAsyncCompute | 0 | Disables a high-risk Vulkan feature; fixes most startup crashes. |
| is_poolsize | 4096 (or 8192) | Increases the texture streaming budget to prevent “out of memory” errors. |
| r_fullscreen | 2 | Forces Borderless Windowed mode, which is more stable for Vulkan startup. |
| r_mode | 19 | Corresponds to the internal resolution index. 19 is standard for 1080p. |
| r_windowWidth/Height | [Your Res] | Manually sets the window size to prevent the engine from guessing incorrectly. |
Alternative Launch Options
If editing the config doesn’t work, Steam users can force-disable certain overlays that conflict with Vulkan:
- Right-click the game in Steam and select Properties.
- In the General tab, find the Launch Options box.
- Paste:
+r_disableSteamOverlay 1 +jobs_numthreads 4 - This reduces the CPU thread complexity during the initial load, which can prevent “hanging.”
Troubleshooting & Common Fixes
- Fatal Error: vkEnumeratePhysicalDevices: This means the game is seeing your Integrated Graphics. Disable the “Intel HD/UHD Graphics” adapter in Windows Device Manager before launching.
- Steam Cloud Overwrite: If your settings reset every time you launch, right-click the file, select Properties, and check Read-only.
- Black Screen on Intro: Press
Alt + Enterimmediately when the screen goes black to force the game into Windowed mode.
Frequently Asked Questions (FAQ)
Why does deleting the config file sometimes help?
Deleting the file forces the engine to re-scan your hardware. If you’ve recently updated your drivers, a stale config file might still be trying to use old memory addresses.
Is “is_poolsize” dangerous?
No. It simply tells the engine how much VRAM it can use for texture streaming. For an 8GB card, setting this to 4096 or 8192 ensures the game doesn’t “muddy” the textures to save space.
Does disabling Async Compute lower FPS?
Slightly. Async Compute can provide a 5-10% boost on compatible hardware, but in Wolfenstein II, it is better to have a stable game at 60 FPS than a crashing one at 66 FPS.
Conclusion and Expected Results
By manually refining your Wolfenstein II The New ColossusConfig.local, you are bypassing the unstable auto-detection routines of the id Tech 6 engine. You can expect the game to launch directly to the main menu, stable transition into cutscenes, and consistent resolution mapping on modern displays.