[Bug 39655] New: Enemy Front crashes almost immediately after launch
https://bugs.winehq.org/show_bug.cgi?id=39655 Bug ID: 39655 Summary: Enemy Front crashes almost immediately after launch Product: Wine Version: 1.8-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Created attachment 52859 --> https://bugs.winehq.org/attachment.cgi?id=52859 enemy_front-1.8-rc1-output.log Debian Jessie amd64 in a 32-bit wineprefix (clean install) under wine 1.8-rc1. The first intro movie to play crashes after about two seconds, when my monitor is set to the native resolution of 2560x1440. Console output attached. Interestingly, if I set the monitor to 1920x1080, the cut scenes don't crash at all and I can make it all the way to the main menu (which also doesn't work, but we can make that another bug). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://store.steampowered.c | |om/app/256190/ Distribution|--- |Debian -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte(a)systemsaviour.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 Anthony Jagers <noonetinone(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noonetinone(a)gmail.com --- Comment #1 from Anthony Jagers <noonetinone(a)gmail.com> --- I have it working. Since I was unable to duplicate my success in other distro's, I'm not sure why. My feeling is that it has something to do with the native resolutions of the coded cut scenes vs the resolution you are trying to run the game in. I would try to remove the intro movies pak. Rename or move Game2/_FastLoad/IntroMovies.pak. There is another pak you should experiment with, Game2/Videos.pak. This would disable cut scenes altogether. Try to hand edit your config file. The steam forum has been helpful for me. I got in ...common/Enemy Front/System.cfg the lines. r_Driver=DX9 r_Fullscreen=0 r_Width=1280 r_Height=720 r_PostProcessHUD3DShadowAmount=0.3 Delete the $HOME/Enemy Front folder everytime you try to restart. If it works you'll have low detail, which you can turn back on when you start playing. I'll try be of further help if I can. I was unable to get it working in two other distros with almost similar setups( wine versions and prefixes). My working setup is Ubuntu 15.10 with Lackner's Wine-staging ppa. The configs in the file Game2/_FastLoad/startup.pak maybe worth editing. It's a 7-zip file. This I learned from the steam forum. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 --- Comment #2 from Adam Bolte <abolte(a)systemsaviour.com> --- (In reply to Anthony Jagers from comment #1)
I have it working. Since I was unable to duplicate my success in other distro's, I'm not sure why. My feeling is that it has something to do with the native resolutions of the coded cut scenes vs the resolution you are trying to run the game in.
I ran: $ xrandr --output DP-1 --mode 1920x1080 (which reduced my resolution down from 2560x1440 to 1920x1080) and tried re-launching the game. No effect. This is odd, since it worked for me in 1.8-rc1 as per my previous entry. I reverted to 1.8-rc1 and confirmed it does work, so suspected there may be a regression. Tried 1.8-rc2, and that was crashing. Went back to 1.8-rc1 again, and now that was crashing! So in conclusion,. it's nothing to do with resolutions and all just completely random. :)
I would try to remove the intro movies pak. Rename or move Game2/_FastLoad/IntroMovies.pak. There is another pak you should experiment with, Game2/Videos.pak. This would disable cut scenes altogether.
This is interesting. If I rename Game2/_FastLoad/IntroMovies.pak, I get the blank screen with cursor, which I believe is supposed to be the main menu... but then after about two seconds I get the same crash. So perhaps another background thread independent of the video being played is the issue here.
Try to hand edit your config file. The steam forum has been helpful for me.
I got in ...common/Enemy Front/System.cfg the lines.
r_Driver=DX9 r_Fullscreen=0 r_Width=1280 r_Height=720 r_PostProcessHUD3DShadowAmount=0.3
Even though winecfg says my prefix is set to Windows XP, r_Driver was set to DX11. It must be related to being a fresh installation and all that new DX11 code added as of late. I tried changing the setting to DX9 and setting r_Width=2560 and r_Height=1440, and it actually worked right up until the menu (which still doesn't load but shows a black screen and a custom mouse cursor). However when I tried to run the game a second time, the crash during the cut-scene returned. As I hypothesised above, probably changing system.cfg had no effect at all and the crashing is entirely related to chance.
Delete the $HOME/Enemy Front folder everytime you try to restart. If it works you'll have low detail, which you can turn back on when you start playing.
I tried all the above system.cfg values, removed the EnemyFront folder, ran `wineserver -k`, ran `xrandr --output DP-1 --mode 1920x1080`... and crash.
The configs in the file Game2/_FastLoad/startup.pak maybe worth editing. It's a 7-zip file. This I learned from the steam forum.
Just a regular zip file by the look of it. But I'd rather find the root cause of the problems I'm observing than find a work-around. I know this game used to work for me (and I played it for an hour or so), but that was some time ago - and I had to patch wine to avoid flicking (the Crysis engine bug which has since been fixed). I don't like patching my Wine install, so I ignored this game for about a year. During that time, I reinstalled using the latest version of Wine (which seems to have changed the defaults in the config since it had DX11 in system.cfg and you had DX9 - unfortunately I didn't keep my old wineprefix around), I have upgraded from Debian Wheezy to Debian Jessie, I have a new monitor with a bigger default resolution, I have made slight changes to my system hardware configuration, and there have been a ton of changes in Wine too (which is hard to regression test since you need patches to work around other bugs such as the flickering), I have updated my Wine build scripts to enable CFLAGS="-g -O0"... There are so many things that could potentially be related, but Wine should be able to deal with whatever the root cause is. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 --- Comment #3 from Anthony Jagers <noonetinone(a)gmail.com> --- Your hypothesis is correct. It doesn't matter which resolution you try. The crashes occur. I do believe that 1280x720 in the config & disabling cut scenes would help in getting the game at least started that way someone can get the debugger working. Like I mention in my other setups I couldn't get it to work. But I wouldn't describe the problem as a crash. It's a freeze and the accompanying background music is playing repeatedly nonstop. I have to kill the process. However, I now have a another problem with the so-called working setup. Whenever I die, the prompt to 'press enter to try again' appears and then the game freezes with the music still playing . This maybe a lost cause. Windows users are have many of the same problems. In fact things have gotten worse since the last patch. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 --- Comment #4 from Adam Bolte <abolte(a)systemsaviour.com> --- For me it's definitely a crash. An epic crash! It doesn't show a Wine crash dialog box, and it even takes out Steam! I have to run `wineserver -k` and launch Steam again every time it happens. There's no Enemy Front background process left running to continue to play audio. I've never had any other crash take out Steam that I can immediately recall. FWIW, I had the Steam in-game community option disabled when I was testing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 --- Comment #5 from Anthony Jagers <noonetinone(a)gmail.com> --- Created attachment 53096 --> https://bugs.winehq.org/attachment.cgi?id=53096 a normal log with a clean shutdown I am using the staged patches. I also deleted Game2/_FastLoad/IntroMovies.pak. The game freezes if the file is there. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 --- Comment #6 from Anthony Jagers <noonetinone(a)gmail.com> --- Adam, I have been looking at your logs. The staging patches for me have fixed a few things that your wine doesn't have. Look for Lackner's wine-staging ppa or compile wine-staging yourself. The two files processpipe_any.cpp & pipes.cpp do not exist in the wine sources. They're a part of steam. Searching for the keyword "CCrossProcessPipe::" I found that it is an old problem with steam that didn't get fixed in linux. it seems. The lines of assertion failures in yours log gets several hits. The solution was to remove your Xbox 360 controller. The game isn't dumping those lines in your log, neither is wine, steam is. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #7 from winetest(a)luukku.com --- I have few interesting news. The game is currently -90% discount at steam and for me it would cost 2.99€. There is appdb entry for this game and it is reported working with 1.8 series of wine. https://appdb.winehq.org/objectManager.php?sClass=version&iId=33009 Care to retest this game? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 --- Comment #8 from Anthony Jagers <noonetinone(a)gmail.com> --- I wrote that entry. I just tried it with wine-2.0-rc2. It worked. I'm not sure about the cut scenes. When starting a new game at the main menu the screen went black and piano music was playing. If that happens try pressing 'Enter' after about 10 secs. Also rename you cutscenes paks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 --- Comment #9 from Adam Bolte <abolte(a)systemsaviour.com> --- Just tested the game without any cracks or overrides in a Windows XP prefix using an unpatched Wine 2.1. Everything seemed to work great - menus, cut scenes and gamplay. After about 30 minutes of gameplay, once I returned to the tunnels after completing the second mission, I did come across some minor graphics corruption - the lighting(?) made everything in that area shaded with large white and purple tiles. However that could be an issue with Mesa 17.0.0-rc2 - I didn't investigate since it's unrelated. I do believe this bug can be closed. Thanks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox_xerox2000(a)yahoo.co.uk Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> ---
I do believe this bug can be closed. Thanks.
Well, you are the owner of this bug so you can close it yourself ;) Anyway, I assume we can close this as fixed then -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39655 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 2.2. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org