After MOD4 update NW crashes on wine/linux

dark666wulf · August 2014

Sadly i don't get any error messages and a fresh wine prefix dose not help :-(

iambecks1 · August 2014

Yeah somebody asked panderus about this and all he could tell them was that they don't support it and to try asking on the STO and CO forums :<

charononus · August 2014

If anyone uses codeweavers (pay for wine) could they let us know if that works?

jay7n · August 2014

I have same problem on fresh ArchLinux (

sheronis · August 2014

charononus wrote: »

If anyone uses codeweavers (pay for wine) could they let us know if that works?

Doesn't work. I'm using CrossOver Mac.

failedsomuch · August 2014

according to the posts it seems to crash on many (all ?) wine configuration, both linux & mac.

I understand the point of dev, but please keep in mind neverwinter was working fine on wine before mod4. And that brought to neverwinter many players who wouldn't have come otherwise.

Wine & logs give quite no information, everything seems to be trapped by the cryptic error handler. So without some help from dev / support tech, diagnostic is like bingo.

catsofulthar · August 2014

Ubuntu 14.04, Wine 1.7.22 here, was working before the new module, I logged in fine before yesterday's downtime/patch, not since

charononus · August 2014

sheronis wrote: »

Doesn't work. I'm using CrossOver Mac.

Too bad, I know that it's just slightly different than the wine release so I was hoping it did something just different enough to work.

two30 · August 2014

It's still possible to launch Owlbear (NW.15.20140707a.17) through Wine, so you can do comparisons of "+relay" logs.

Having done so, a big difference that leaps out is:

0041:Call KERNEL32.MultiByteToWideChar(0000fde9,00000000,11021ebd "2014-08-15 13:22:57 PROGRAM ASSERT OCCURRED! Unknown video card vendor!\n",00000048,00337ce2,00000049) ret=011de202

My theory is that Module 4 is using a slightly different method of identifying the video card, and fails. However, the failures aren't vendor-specific (people are crashing with both NVIDIA and ATI).

stretch611 · August 2014

This is affecting me as well. I have tried on two separate installs (which were both working in the past.) I even attempted to run with virtualbox. However nothing seems to work.

panderus · August 2014

One of our graphics programmers is also a Linux guy, he took a look during his lunch and is trying to track down a cause. No promises, but we are looking into it.

two30 · August 2014

panderus wrote: »

One of our graphics programmers is also a Linux guy, he took a look during his lunch and is trying to track down a cause. No promises, but we are looking into it.

This is greatly appreciated.

charononus · August 2014

panderus wrote: »

One of our graphics programmers is also a Linux guy, he took a look during his lunch and is trying to track down a cause. No promises, but we are looking into it.

Great news, if he needs any details or error reports let us know we'll be happy to send them in.

dark666wulf · August 2014

panderus wrote: »

One of our graphics programmers is also a Linux guy, he took a look during his lunch and is trying to track down a cause. No promises, but we are looking into it.

I did some debugging but all i could find was the same thing two30 found, i hope your Linux guy will fix it :-) it would not be nice to have the money me and some other linux users spend would be lost ;-)

crypticcliff · August 2014

Sorry, guys. We changed up a bunch of stuff about how we compile shaders since the last release, and the WINE stuff never got tested. Mostly because our "Linux testing" setup consists of my (personal) old laptop and we've all been pretty busy the last few months so I haven't booted up the game on it in a while.

I'll try to look into it, assuming they let me take the time to do it, but there probably won't be a solution this weekend. :[

zomd · August 2014

crypticcliff wrote: »

Sorry, guys. We changed up a bunch of stuff about how we compile shaders since the last release, and the WINE stuff never got tested. Mostly because our "Linux testing" setup consists of my (personal) old laptop and we've all been pretty busy the last few months so I haven't booted up the game on it in a while.

I'll try to look into it, assuming they let me take the time to do it, but there probably won't be a solution this weekend. :[

Unrelated to linux, but related to graphics. Any idea why the eight core fix for AMD processors resulted in jittery looking framerates for some of us? I disable 4 cores and it runs smoothly. It's weird.

crypticcliff · August 2014

Update: I think I have a fix for this, but there's still no way it's getting in before the weekend. I will beg and plead to get it in ASAP starting Monday.

Sorry for you guys who can't play over the new content over the weekend. I'll try to get this fix pushed through soon.

hustin1 · August 2014

Does the fix involve any changes to getting mouse and keyboard input? I've verified that if I force user32.RegisterRawInputDevices() to return 1 instead of 0 then loading completes without a crash, but then the game won't respond to any mouse or keyboard events (because I don't have any raw input devices for it to use). Is there a way to get the game to use DirectInput8 *without* always using raw inputs from user32?

crypticcliff · August 2014

hustin1 wrote: »

Does the fix involve any changes to getting mouse and keyboard input? I've verified that if I force user32.RegisterRawInputDevices() to return 1 instead of 0 then loading completes without a crash, but then the game won't respond to any mouse or keyboard events (because I don't have any raw input devices for it to use). Is there a way to get the game to use DirectInput8 *without* always using raw inputs from user32?

Try with this command line parameter: "-enableRawInputSupport 0"

Alternatively, you can force it to think it's running under a different WINE version. The game disables raw input support for versions of WINE early enough to not support it (earlier than 1.5.13, I think). So you can try this command line parameter: "-fakeWineVersion 1.5.12"

(Without the quotes, of course.)

Right now raw input is the only thing that it makes any decision based on version for, so the only difference is whether something is before or after 1.5.13.

kiffehz278 · August 2014

I shall remain faithful to the developers, hopefully this issue gets resolved. I am quite new to the game and am enjoying the game. One of the firsts games where i can play for 8 hours straight without getting bored.

two30 · August 2014

crypticcliff wrote: »

Update: I think I have a fix for this, but there's still no way it's getting in before the weekend. I will beg and plead to get it in ASAP starting Monday.

Sorry for you guys who can't play over the new content over the weekend. I'll try to get this fix pushed through soon.

You are wonderful.

hustin1 · August 2014

crypticcliff wrote: »

Try with this command line parameter: "-enableRawInputSupport 0"

Alternatively, you can force it to think it's running under a different WINE version. The game disables raw input support for versions of WINE early enough to not support it (earlier than 1.5.13, I think). So you can try this command line parameter: "-fakeWineVersion 1.5.12"

(Without the quotes, of course.)

Right now raw input is the only thing that it makes any decision based on version for, so the only difference is whether something is before or after 1.5.13.

Trying it. Do I run "GameClient -enableRawInputSupport 0" or "Neverwinter -enableRawInputSupport 0"? I'm actually trying this on Windows 2000 (a version that I've patched myself and always worked before last night). I have the raw input API's present as stubs in user32 as adding the "real" versions from XP would involve a ton of additions to win32k.sys, which would not be an easy task (especially since I'd have to expand its internal dispatch table, which is a nightmare).

pointsman · August 2014

crypticcliff wrote: »

Update: I think I have a fix for this, but there's still no way it's getting in before the weekend. I will beg and plead to get it in ASAP starting Monday.

Sorry for you guys who can't play over the new content over the weekend. I'll try to get this fix pushed through soon.

Thank you very much! It is greatly appreciated.

charononus · August 2014

crypticcliff wrote: »

Update: I think I have a fix for this, but there's still no way it's getting in before the weekend. I will beg and plead to get it in ASAP starting Monday.

Sorry for you guys who can't play over the new content over the weekend. I'll try to get this fix pushed through soon.

Give that man a raise.

stretch611 · August 2014

charononus wrote: »

Give that man a raise.

I'd buy you a beer, but my guess is that you are on the opposite coast. (Im EST).

I appreciate the effort, and I look forward to not using the 8yr old XP machine again.

kn1ghtscross · August 2014

crypticcliff wrote: »

Try with this command line parameter: "-enableRawInputSupport 0"

Alternatively, you can force it to think it's running under a different WINE version. The game disables raw input support for versions of WINE early enough to not support it (earlier than 1.5.13, I think). So you can try this command line parameter: "-fakeWineVersion 1.5.12"

(Without the quotes, of course.)

Right now raw input is the only thing that it makes any decision based on version for, so the only difference is whether something is before or after 1.5.13.

Please Help
For those of us that are not computer literate

where do we put what ?

I've never done more than turn on pc, play, fall asleep, play some more

the more detail the better, like your training a dog lol

thx for your time

charononus · August 2014

kn1ghtscross wrote: »

Please Help
For those of us that are not computer literate

where do we put what ?

I've never done more than turn on pc, play, fall asleep, play some more

the more detail the better, like your training a dog lol

thx for your time

Mac user? If not I recommend taking your system to the guy who set it up for you as going from scratch like that on a linux system is a long lesson on computers.

aderonz · August 2014

hustin1 wrote: »

Trying it. Do I run "GameClient -enableRawInputSupport 0" or "Neverwinter -enableRawInputSupport 0"? I'm actually trying this on Windows 2000 (a version that I've patched myself and always worked before last night). I have the raw input API's present as stubs in user32 as adding the "real" versions from XP would involve a ton of additions to win32k.sys, which would not be an easy task (especially since I'd have to expand its internal dispatch table, which is a nightmare).

i think he's refering to the command line in the launcher's option.

charononus · August 2014

aderonz wrote: »

i think he's refering to the command line in the launcher's option.

using the command line it the launcher is the same as launching gameclient from command line with those options. At least it was last time I needed to mess with it back in CB.

hustin1 · August 2014

Sorry. I was referring to the command line in the OS (cmd.exe). I didn't even know that the launcher had a command line option, but I'll try that now. I've also started investigating porting XP's raw device API to 2k, but that won't be easy. I've ported a ton of things to 2k already (which is why I can run Neverwinter at all), but expanding win32k.sys is never an easy task.

kn1ghtscross · August 2014

kn1ghtscross wrote: »

Please Help
For those of us that are not computer literate

where do we put what ?

I've never done more than turn on pc, play, fall asleep, play some more

the more detail the better, like your training a dog lol

thx for your time

sry for wasting your time, I think I'm in the wrong thread as I'm running Win 7
my problem is game freeze ( although the game is still running ), black screen
and game crash, since the new session update

After MOD4 update NW crashes on wine/linux

Comments