WineHQ

Wolfenstein: The New Order

No Screenshot

Submit Screenshot
Steam version

Application Details:

Version: Steam
License: Retail
URL: http://www.wolfenstein.com
Votes: 0
Latest Rating: Platinum
Latest Wine Version Tested: 1.9.14

Maintainers: About Maintainership

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

Everything

What does not

N/A

Workarounds

What was not tested

Multiplayer

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

== My system == PC | ASUS Laptop (K55VD) CPU | Intel i7 Ivy CPU (2.3 GHz, 4 cores) RAM | 8Gb DDR3 Memory GPU1 | Intel HD Graphics 4000 GPU2 | Nvidia GeForce 610M (2Gb DDR3) DISK | SSD ADATA Premier Pro SP550 (240 Gb @ R:560/W:510 MB/s) OS | Arch Linux 64bit (Linux kernel 4.6.3) DE | GNOME Shell 3.20.3 Wine | 1.9.14 USED GPU: In this test I used GPU2 to run the game

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentArch Linux x86_64Jul 09 20161.9.14Yes Yes PlatinumHorațiu Mlendea 
ShowUbuntu 15.10 "Wily" amd64 (+ variants like Kubuntu)Mar 05 20161.8.1Yes Yes PlatinumJavier Garcia 
ShowLinux Mint 17.2 "Rafaela" x86-64Sep 08 20151.7.50Yes Yes PlatinumLiam Stevens 
ShowUbuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)Jun 19 20151.7.44Yes Yes Goldan anonymous user 
ShowUbuntu 14.10 "Utopic" amd64 (+ variants like Kubuntu)Feb 24 20151.7.37Yes Yes PlatinumKonrad Materka 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

A few issues and solutions
by William on Saturday August 19th 2017, 9:37
1. Audio (in the main menu at least) seems to 'crackle'
Solved by starting Steam process with `PULSE_LATENCY_MSEC=60` as an environment variable
E.g.

PULSE_LATENCY_MSEC=60 Steam.exe

Source: psyq123.wordpress.com/2017/04/07/fix

2. When the game window loses focus, swapping back to it results in a black screen with a texture in the top-left corner
I experienced this while in the i3 window manager. It was fixed by reloading i3.
On other desktop environments swapping to another virtual desktop and back might be good enough.
I had to wait a couple of seconds after the window showed again, it froze for a second, but then I can hit 'continue' on the main menu.
Continuing before the freeze results in a black screen, which can be corrected by repeating the process.

3. Steam does not allow you to run the game unless you are using a 64bit Wine prefix
Solution is obvious enough, but it'd be nice if this info were added to the page
Crash-on-start when using Intel HD graphics
by Horațiu Mlendea on Wednesday September 21st 2016, 6:01
Hello. Has anyone found a solution for the "wglCreateContextAttribsARB" crash when trying to run this game using Intel HD Graphics (integrated graphics)?

It used to run fine on my laptop using the Nvidia GPU (610M) but not on it's integrated gpu (Intel HD 4000). Now I have a desktop PC with only integrated graphics (Intel HD 530) and no dedicated GPU (I'll get one but later).

I would be interested in playing this game since I haven't finished the campaign when I started playing it on my laptop which is now broken, and it looks to me like I can't. I'd really much rather play this in WINE than moving it to the Windows partition and having to reboot every time I want to play it...
RE: Crash-on-start when using Intel HD graphics
by Liam Stevens on Wednesday September 21st 2016, 14:31
After a bit of quick research, it appears this game requires OpenGL 3.3 to be able to get past this problem. Make sure that your iGPU supports that feature set and that your Mesa is up to date enough to run OpenGL 3.3.
RE: Crash-on-start when using Intel HD graphics
by Horațiu Mlendea on Friday September 23rd 2016, 4:04
Hi. I think I too found the threads discussing your suggestion but I thank you for reminding me because I took a second look and this was exactly the issue. You see, I used to have a laptop before and when I build my desktop a few days ago I just took the SSD from the laptop and put it in. I did uninstall Nvidia drivers and bumblebee but I forgot to reinstall the Intel drivers. This was what was causing it on Windows as well. I moved the game to a newly created partition for Windows+WINE games and when I tried to start it on Windows 10 the same issue came up, but it worked fine after reinstalling the latest Intel HD Graphics driver.

I am still trying to do the same on Arch Linux. I tried it with 'yaourt -S mesa' and the 'xf86-video-intel as well, I even tried removing the package cache to force a redownload and use the --force parameter, but the issue persists. I'm not sure how should I proceed in order to get rid of the old drivers and get the proper ones for the new processor.
RE: Crash-on-start when using Intel HD graphics
by GloriousEggroll on Saturday October 28th 2017, 22:23
found a fix for this on mesa, worked on amd/ati, not sure if it works on intel. This was on the old gearsongallium site, intended for RAGE but never worked properly without a shader dump. Luckily it works fine for Wolfenstein.

Two parts to the fix:

1. you'll need to patch wine (NOT wine-staging. does not work with staging for some reason).

patch:
github.com/lutris/buildbot/commit/e09b7a55d76e7e3c2d7f9cfbc4075462532e7376

2. You'll also need to use MESA_GL_VERSION_OVERRIDE=4.5COMPAT environment variable
Back