Update 10/30: Patch Now Live (Steam Overlay, Async Compute, JP Fixes)

[jasonBethesda]

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.

[Gashapon]

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.

[The Grongle]

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

[Mikko]

Nvidia 388.13 update works fine little bit pixel

[lordjyw]

Still unplayable...... NVDIA 970m 388.13 Driver

[Mikko]

what m? it is GTX and i have 970GTX and i update 388.13 driver i can play it now

[lordjyw]

NVIDIA GeForce GTX 970M laptop GPU

[iRock]

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.

[ANZACMonash-AAPG Daniel]

iRock M.D. の投稿を引用：

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!

[DirtyDan]

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.

[Mikko]

i dont have any problem :D

[cezzary22]

Is there anybody from the developer, any sight of progress reparing this THING??

[GameAddict411]

Your patch broke the game for me. From worse performance to corrupted skybox, so thanks for nothing. It's shocking to me that in this day and age we shouldn't expect games to function on day one. Take your time, or don't release a broken game. It's not that complicated.

[The Crazy Gringo]

I had a weird artefact coming out from Caroline Becker's head, like a long line, but that's gone now for obvious reasons.
The rest of the game plays flawlessly on my GTX970.

[Rebel]

cezzary22 の投稿を引用：

Is there anybody from the developer, any sight of progress reparing this THING??

I also would like to hear any news. unfortunately buying PC games at launch is a risky business for us consumers. I had no problem with the game before the patch. Had to stop playing for now, so I don't get mad with the artifacts in the skybox.

[hasher------>A++]

The first patch for Wolfenstein II is won achieve as Great Failure Of The Year:

1) head bobbing fix doesn't work for new patch - why Bethesda/MachineGames even think that motion sickness is a good idea?? They walk like that in real life or just bullying us? It's unplayable killer-feature.

2) I cannot use old NVidia driver 387.92 (which there was no any problems!), because the game now requires at least 388.00 driver and just crashing with error 'Could not write crash dump';

3) 'Could not write crash dump' error appears periodically in the random places of levels (before new patch there was no one crash!);

3) After installing latest NVidia driver, the game is crashed when I try to switch to the desktop by Alt-Tab;

4) Annoying bug when mouse cursor is appears when call console by '~' button is NOT fixed!

5) And finally, the artefacts are appears! Developers, thanks!

*facepalm*

--
P.S. 1080 / win7x64