https://bugs.winehq.org/show_bug.cgi?id=40233
Bug ID: 40233 Summary: Devil Daggers Refuses to Start Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: tristanlshockley@gmail.com Distribution: ---
Created attachment 53778 --> https://bugs.winehq.org/attachment.cgi?id=53778 Devil Dagger Force Close Output
I created a thread in the forums (https://forum.winehq.org/viewtopic.php?f=8&t=26228) where I was recommended to create a bug report. To get to this point I needed lib32-openal. After installing samba a winbind error was removed (see the forum link) but this doesn't appear to change anything. The game will not start through terminal because of DRM, you need to run the game through Steam in WINE. When you do so you will see a black box which will autoclose in about five seconds. Attached is the text Steam spits out during this time, and if I can figure out how to post another I will provide an image of the black box.
https://bugs.winehq.org/show_bug.cgi?id=40233
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net --- Not a blocker.
https://bugs.winehq.org/show_bug.cgi?id=40233
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz@gmail.com
--- Comment #2 from fjfrackiewicz@gmail.com --- (In reply to tristanlshockley from comment #0)
Created attachment 53778 [details] Devil Dagger Force Close Output
I created a thread in the forums (https://forum.winehq.org/viewtopic.php?f=8&t=26228) where I was recommended to create a bug report. To get to this point I needed lib32-openal. After installing samba a winbind error was removed (see the forum link) but this doesn't appear to change anything. The game will not start through terminal because of DRM, you need to run the game through Steam in WINE. When you do so you will see a black box which will autoclose in about five seconds. Attached is the text Steam spits out during this time, and if I can figure out how to post another I will provide an image of the black box.
The thing I found with Steam games that it's easier to navigate to a game's executable and open a terminal and type "wine <game name>.exe".
I've found that launching games' executables directly from their directory works better than when Steam tries to do it.
Also, keep in mind that launching a game via Steam also runs the risk of Steam installing runtimes or redistributable files into God knows where.
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #3 from fjfrackiewicz@gmail.com --- (In reply to tristanlshockley from comment #0)
Created attachment 53778 [details] Devil Dagger Force Close Output
I created a thread in the forums (https://forum.winehq.org/viewtopic.php?f=8&t=26228) where I was recommended to create a bug report. To get to this point I needed lib32-openal. After installing samba a winbind error was removed (see the forum link) but this doesn't appear to change anything. The game will not start through terminal because of DRM, you need to run the game through Steam in WINE. When you do so you will see a black box which will autoclose in about five seconds. Attached is the text Steam spits out during this time, and if I can figure out how to post another I will provide an image of the black box.
I see you are using wine-staging from Arch's repos from your forum post.
I would recommend you try wine from their multilib repo as wine-staging is highly experimental and then report back with any bugs you find :)
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #4 from fjfrackiewicz@gmail.com --- I just finished a 2 hour session with Devil Daggers and the game runs fine on wine from either the multilb repo ( https://www.archlinux.org/packages/multilib/x86_64/wine/ ) or the community repo ( https://www.archlinux.org/packages/community/i686/wine/ )
You need to uninstall wine-staging and install one of the versions of Wine I linked above.
If you install the multilib version, make sure to create a 32-bit prefix.
If you use the i686 version then all you need to do is make a clean prefix, run "winetricks vcrun2012", download the game via Steam and hit "Play" so that Steam installs OpenAL for you and you should be playing in no time.
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #5 from tristanlshockley@gmail.com --- (In reply to fjfrackiewicz from comment #2)
The thing I found with Steam games that it's easier to navigate to a game's executable and open a terminal and type "wine <game name>.exe".
I agree it is easier, however when I try doing this, the game spits out an error claiming that "Steam must be running to play Devil Daggers" and then it autoclosed. I don't know how you managed beyond this but that is what I am getting.
(In reply to fjfrackiewicz from comment #3)
I would recommend you try wine from their multilib repo as wine-staging is highly experimental and then report back with any bugs you find :)
I have removed wine-staging and installed wine with no differences. Wine by default is a multilib package so is what I have installed. I tried the community wine 1.9.5 (one you linked) and it too spit out the error "Steam must be running to play Devil Daggers". So I installed steam onto a new 32bit wineprefix AFTER installing vcrun2012 and even going so far as to install Devil Daggers onto the prefix (as opposed to using the already installed game) and still, black box and an autoclose.
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #6 from fjfrackiewicz@gmail.com --- (In reply to tristanlshockley from comment #5)
(In reply to fjfrackiewicz from comment #2)
The thing I found with Steam games that it's easier to navigate to a game's executable and open a terminal and type "wine <game name>.exe".
I agree it is easier, however when I try doing this, the game spits out an error claiming that "Steam must be running to play Devil Daggers" and then it autoclosed. I don't know how you managed beyond this but that is what I am getting.
(In reply to fjfrackiewicz from comment #3)
I would recommend you try wine from their multilib repo as wine-staging is highly experimental and then report back with any bugs you find :)
I have removed wine-staging and installed wine with no differences. Wine by default is a multilib package so is what I have installed. I tried the community wine 1.9.5 (one you linked) and it too spit out the error "Steam must be running to play Devil Daggers". So I installed steam onto a new 32bit wineprefix AFTER installing vcrun2012 and even going so far as to install Devil Daggers onto the prefix (as opposed to using the already installed game) and still, black box and an autoclose.
Could you post the terminal output that you get when Devil Daggers auto closes?
Also, can you try using an override in Winecfg for openal to "native, built-in" and playing the game in Windows XP mode?
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #7 from tristanlshockley@gmail.com --- Sorry it took me so long to reply.
Could you post the terminal output that you get when Devil Daggers auto closes?
You can find the output on the forum post (https://forum.winehq.org/viewtopic.php?f=8&t=26228)
Also, can you try using an override in Winecfg for openal to "native, built-in" and playing the game in Windows XP mode?
I will give this a try as soon as I am back on Linux, sometime within the next three days
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #8 from tristanlshockley@gmail.com --- Created attachment 54022 --> https://bugs.winehq.org/attachment.cgi?id=54022 Full Steam Log Post OpenAL Override
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #9 from tristanlshockley@gmail.com --- I just tried the OpenAL override but it did not work. I have attached another file to the OP, the full steam log (i believe you were asking for this and not just the part where devil daggers crashes, i apologize)
https://bugs.winehq.org/show_bug.cgi?id=40233
--- Comment #10 from tristanlshockley@gmail.com ---
I have attached another file to the OP, the full steam log (i believe you were asking for this and not just the part where devil daggers crashes, i apologize)
I will stop spamming after this, I see now you didn't ask for this but its attached anyways. I haven't compared the two files yet but it looks like it might have different output.
https://bugs.winehq.org/show_bug.cgi?id=40233
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #11 from winetest@luukku.com --- (In reply to tristanlshockley from comment #10)
I have attached another file to the OP, the full steam log (i believe you were asking for this and not just the part where devil daggers crashes, i apologize)
I will stop spamming after this, I see now you didn't ask for this but its attached anyways. I haven't compared the two files yet but it looks like it might have different output.
Could you retest with more recent wine? Your log was done with
fixme:winediag:start_process Wine Staging 1.9.5 is a testing version containing experimental patches.
And we are currently using 2.0 series. 2.8 being the latest development version. Staging has not yet released 2.8, but it should come anytime soon.
https://bugs.winehq.org/show_bug.cgi?id=40233
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #12 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-5.21?
-
wine-bugs＠winehq.org -
WineHQ Bugzilla