Wolfenstein II: The New Colossus

Wolfenstein II: The New Colossus

View Stats:
jasonBethesda  [developer] Oct 28, 2017 @ 12:59pm
Update 10/30: Patch Now Live (Steam Overlay, Async Compute, JP Fixes)
Update: Hey guys,

This patch is now out of beta and is being pushed live to all users. Continue to let us know if you're experiencing any issues. Thank you!

--

Hey all,

The team is pushing through a hotfix patch to the beta branch of Steam for Wolfenstein II: The New Colossus. This includes the following fixes:

Patch notes:

- Resolved an issue affecting the deployment of full game files in Japan, Bahrain, Kuwait, Lebanon, Oman, Qatar, and Saudi Arabia

- Re-enabled Async compute for AMD users (requires AMD driver version 17.10.3, linked below)

http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-17.10.3-Release-Notes.aspx

- Temporarily disabled Async compute on 1080ti until driver fix is in

- Re-enabled Steam Overlay

- Added driver version detection and dialog


In order to install a patch on the Steam public beta branch, right click the game in your Steam library. Go to properties, then the "Betas" tab. In the dropdown, choose public beta as your branch.
Last edited by jasonBethesda; Oct 30, 2017 @ 3:16pm
< >
Showing 451-465 of 510 comments
ryaz Nov 1, 2017 @ 6:57pm 
Originally posted by DaveBot:
Originally posted by That one fox:
When is this going live? and will it fix the effing crash dump error?

The crash dump error seems to occur if your display drivers are not up to date. Go to the official source of the company which produced your GPU (Nvidia, AMD etc.) and download the latest display driver for your card there. I do not recommend performing this process with third-party software, as it may not give you THE most recent drivers. For example, I tried with Driver Booster the first time around, but apparently the driver I downloaded was not 100% the latest version and so it didn't fix the problem. I went to Nvidia's site, found my card generation there, got the driver and bam, problem solved.

If you're unsure exactly what hardware specs you have, I recommend using CPU-Z to see it all in detail and make sure you get the drivers for the appropriate card.

Hope this helps!
- Dave
Its a ♥♥♥♥♥♥♥t - exact on LATEST driver dor nvidia (388.13) - mostly ALL in this topic have the crush problem (same as me) - on 385 drivers - i have no problem!
Still getting crash dump error
zenghui551 Nov 1, 2017 @ 7:43pm 
Why is the game updated and cannot be entered?
Originally posted by rogermorse:
Originally posted by VolkNasty:
Energy Weapons VS Wooden Crates:

Has anyone else noticed that those same energy weapons that can melt steel crates, and decapitate a mech nazi with ease doesn't stand a chance against a wooden crate?
At first I thought maybe the crate was "out of play" and not useable, but soon after I used up all the energy ammo, I simply went up to it and used my tomahawk, SMASH! Energy weapons can burn anything in the game except wood. Strange don't you think? Bug?


strange of what? wood is not a conductor, what's there to find strange? It's an energy weapon, I am sure it would react with conductive materials. It's like putting your hand on an induction cooking plate and complaining that you don't get burnt.

Laser USES energy but it is a laser beam, not ELECTRICITY!

It should be able to burn a wood crate (and create a fire through heat) just like a lightsaber in Star Wars or a laser shot.
mcfly666 Nov 2, 2017 @ 2:22am 
Originally posted by ANZACMonash-AAPG Daniel:
Originally posted by rogermorse:


strange of what? wood is not a conductor, what's there to find strange? It's an energy weapon, I am sure it would react with conductive materials. It's like putting your hand on an induction cooking plate and complaining that you don't get burnt.

Laser USES energy but it is a laser beam, not ELECTRICITY!

It should be able to burn a wood crate (and create a fire through heat) just like a lightsaber in Star Wars or a laser shot.

I agree with you and the other guy, energy is energy. An energy weapon capable of killing a man in less than a second would destroy a little wooden box lol
Christsnatcher Nov 2, 2017 @ 3:57am 
For those getting the infamous crash dump error, as far as I could find out via debugging is it "SteamOverlayVulkanLayer64.dll" which causes a memory leak after having been loaded and eventually the final exception that brings up the error message. The graphics driver used may have an impact on this issue, but it's not a crucial one.

There're basically two options to resolve the actual problem: The first would be to make sure the aforementioned "SteamOverlayVulkanLayer64.dll" does NOT exist in your base Steam folder, e.g. by renaming the file to something else. The second option is to edit the configuration file the .dlll uses, namely "SteamOverlayVulkanLayer64.json". Just open it in any good text editor and change the very last "1" character to "0", so that the last line with actual text reads:

"enable_environment": { "ENABLE_VK_LAYER_VALVE_steam_overlay_1": "0" }

Save the file and the issue should be gone. Btw, en- or disabling the steam overlay doesn't make any difference in this particular case, as the Vulkan Layer isn't affected by the overlay setting and instead always gets loaded and executed if the original .json config file is present.

I hope this helps some of you guys, cheers!

EDIT:

Here's the modified .json file for those of you who can't do the edit themselves for whatever reason:

https://openload.co/f/3mNkPs2pFRo
Last edited by Christsnatcher; Nov 2, 2017 @ 4:06am
Shamus Young Nov 2, 2017 @ 4:29am 
Originally posted by Christsnatcher:
For those getting the infamous crash dump error, as far as I could find out via debugging is it "SteamOverlayVulkanLayer64.dll" which causes a memory leak after having been loaded and eventually the final exception that brings up the error message. The graphics driver used may have an impact on this issue, but it's not a crucial one.

I can confirm this works. The game was giving me the crash dump error on startup, and after following this advice the game will launch again.

It runs like garbage now, but other people have suggested the latest drivers are responsible for this. I might roll back and see if that helps.
Boocheus Nov 2, 2017 @ 4:40am 
Originally posted by Odyssey:
Massive screen tearing going on here. Does not happen with other games.
It's a tear in the middle of the screen.
Updated all drivers.
Check your frame rate. Cap it at 62, 92 or 125
Mikko091 Nov 2, 2017 @ 4:40am 
Nvidia 388.13 update works fine little bit pixel
lordjyw Nov 2, 2017 @ 4:59am 
Still unplayable...... NVDIA 970m 388.13 Driver
Last edited by lordjyw; Nov 2, 2017 @ 5:00am
Mikko091 Nov 2, 2017 @ 5:45am 
what m? it is GTX and i have 970GTX and i update 388.13 driver i can play it now
lordjyw Nov 2, 2017 @ 5:56am 
NVIDIA GeForce GTX 970M laptop GPU
iRock Nov 2, 2017 @ 6:33am 
Originally posted by Christsnatcher:
For those getting the infamous crash dump error, as far as I could find out via debugging is it "SteamOverlayVulkanLayer64.dll" which causes a memory leak after having been loaded and eventually the final exception that brings up the error message. The graphics driver used may have an impact on this issue, but it's not a crucial one.

There're basically two options to resolve the actual problem: The first would be to make sure the aforementioned "SteamOverlayVulkanLayer64.dll" does NOT exist in your base Steam folder, e.g. by renaming the file to something else. The second option is to edit the configuration file the .dlll uses, namely "SteamOverlayVulkanLayer64.json". Just open it in any good text editor and change the very last "1" character to "0", so that the last line with actual text reads:

"enable_environment": { "ENABLE_VK_LAYER_VALVE_steam_overlay_1": "0" }

Save the file and the issue should be gone. Btw, en- or disabling the steam overlay doesn't make any difference in this particular case, as the Vulkan Layer isn't affected by the overlay setting and instead always gets loaded and executed if the original .json config file is present.

I hope this helps some of you guys, cheers!

EDIT:

Here's the modified .json file for those of you who can't do the edit themselves for whatever reason:

https://openload.co/f/3mNkPs2pFRo
That's the issue! Hope devs read this and fix it asap.
Originally posted by iRock M.D.:
Originally posted by Christsnatcher:
For those getting the infamous crash dump error, as far as I could find out via debugging is it "SteamOverlayVulkanLayer64.dll" which causes a memory leak after having been loaded and eventually the final exception that brings up the error message. The graphics driver used may have an impact on this issue, but it's not a crucial one.

There're basically two options to resolve the actual problem: The first would be to make sure the aforementioned "SteamOverlayVulkanLayer64.dll" does NOT exist in your base Steam folder, e.g. by renaming the file to something else. The second option is to edit the configuration file the .dlll uses, namely "SteamOverlayVulkanLayer64.json". Just open it in any good text editor and change the very last "1" character to "0", so that the last line with actual text reads:

"enable_environment": { "ENABLE_VK_LAYER_VALVE_steam_overlay_1": "0" }

Save the file and the issue should be gone. Btw, en- or disabling the steam overlay doesn't make any difference in this particular case, as the Vulkan Layer isn't affected by the overlay setting and instead always gets loaded and executed if the original .json config file is present.

I hope this helps some of you guys, cheers!

EDIT:

Here's the modified .json file for those of you who can't do the edit themselves for whatever reason:

https://openload.co/f/3mNkPs2pFRo
That's the issue! Hope devs read this and fix it asap.

They'll fix it. Just go to their support section at Bethseda and upload your dxdiag.txt file and description of problem/s.

Like, before the patch, everything was HEAVENLY PERFECT!
DirtyDan0311 Nov 2, 2017 @ 8:13am 
Are we going to get a new patch soon? All of these graphic glitches make the game extremely unenjoyable. I have the game running maxed out in 4k and had zero problems. New patch, new drivers, get to NO level and boom game turns to sh*t.
< >
Showing 451-465 of 510 comments
Per page: 15 30 50

Date Posted: Oct 28, 2017 @ 12:59pm
Posts: 510