http://bugs.winehq.org/show_bug.cgi?id=11125
Summary: s.t.a.l.k.e.r does not start Product: Wine Version: 0.9.52. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: asdmin@gmail.com
Created an attachment (id=10163) --> (http://bugs.winehq.org/attachment.cgi?id=10163) printout
Is there anybody who has a clue on this error message? This appears whenever i want to start stalker, installed and started as the appdb howto spefifies.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2008-01-10 16:40:48 --- What is the exact command you used to run it? Also how and where did you installed the game?
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #2 from Dániel Vásárhelyi asdmin@gmail.com 2008-01-10 18:22:21 --- Hi,
I have installed the game just as it is provided in the howto: - export WINEPREFIX=/the/path/the/game/is - started the installer. Installer never ever failed. - grabbed and installed patch (stk-ww-10005.exe) without problem - wine regedit, Set "OffscreenRenderingMode" to "fbo" - cd game's installation dir; wine XR_3DA.exe -dsound -nodistort
A black screen occurs and the game later exits, leaving the wine running, producing the errors continously.
My laptop is equipped by a Radeon Mobility X1600, I've tried the exactly same installation on an nVidia, and the game actually started.
http://bugs.winehq.org/show_bug.cgi?id=11125
Jeff Zaroyko jeffzaroyko@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffzaroyko@gmail.com
--- Comment #3 from Jeff Zaroyko jeffzaroyko@gmail.com 2008-01-10 18:40:53 --- wine-0.9.52, Ubuntu 7.04, nVidia 8800GTS, NVIDIA 169.04
started from the installed directory with the -dsound -nodistort parameters, lastest game patchlevel, recognises game disc without issue.
works for me.
http://bugs.winehq.org/show_bug.cgi?id=11125
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P5 Summary|s.t.a.l.k.e.r does not start|s.t.a.l.k.e.r does not start | |[ATi]
--- Comment #4 from Vitaliy Margolen vitaliy@kievinfo.com 2008-01-10 19:27:05 --- Don't set fbo - ATI [drivers] does not support it. Like most other features required by this game. You will be lucky if you get anything 3d working on your disabled hardware.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #5 from Dániel Vásárhelyi asdmin@gmail.com 2008-01-11 02:36:02 --- (In reply to comment #4)
You will be lucky if you get anything 3d working on your disabled hardware.
You mean the failure of starting this game is the fault of the ATI driver?
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #6 from Vitaliy Margolen vitaliy@kievinfo.com 2008-01-13 13:08:20 --- Yes, ATi drivers known to have lots of bugs and deficiencies with more sophisticated features - the ones Wine use all the time.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #7 from Austin English austinenglish@gmail.com 2008-01-13 21:34:06 --- Can any d3d guys comment on if this is fixable? Or is this going to be another ATI driver bug?
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #8 from Dániel Vásárhelyi asdmin@gmail.com 2008-01-16 04:00:14 --- (In reply to comment #4)
Don't set fbo - ATI [drivers] does not support it. Like most other features required by this game. You will be lucky if you get anything 3d working on your disabled hardware.
I have shut down fbo but the game produces the same symptoms. :(
http://bugs.winehq.org/show_bug.cgi?id=11125
James Andrewartha trs80@ucc.asn.au changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |trs80@ucc.asn.au
--- Comment #9 from James Andrewartha trs80@ucc.asn.au 2008-04-06 10:20:03 --- I'm seeing this as well, with an nvidia card. The game used to work, but I hadn't tried it recently and now it doesn't work (with wine 0.9.58~winehq0~debian~4.0). I created a new wineprefix but it gave the same error.
http://bugs.winehq.org/show_bug.cgi?id=11125
Alexander Dorofeyev alexd4@inbox.lv changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexd4@inbox.lv
--- Comment #10 from Alexander Dorofeyev alexd4@inbox.lv 2008-04-06 10:34:43 --- James Andrewartha: Can you run a regression test? http://wiki.winehq.org/RegressionTesting
(In reply to comment #9)
I'm seeing this as well, with an nvidia card. The game used to work, but I hadn't tried it recently and now it doesn't work (with wine 0.9.58~winehq0~debian~4.0). I created a new wineprefix but it gave the same error.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #11 from James Andrewartha trs80@ucc.asn.au 2008-04-06 11:04:47 --- I just tried 0.9.36 and 0.9.37 which both worked, and then 0.9.38 again which also worked. So I can't reproduce it any more, maybe it's some sort of race condition? :-/
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #12 from Alexander Dorofeyev alexd4@inbox.lv 2008-04-06 11:39:31 --- Did you mean 0.9.58 or 0.9.38?
(In reply to comment #11)
and then 0.9.38 again which also worked.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #13 from James Andrewartha trs80@ucc.asn.au 2008-04-06 11:51:28 --- (In reply to comment #12)
Did you mean 0.9.58 or 0.9.38?
Err, 0.9.58. And it was 0.9.56 and 0.9.57.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #14 from Alexander Dorofeyev alexd4@inbox.lv 2008-04-06 12:13:32 --- (In reply to comment #13)
(In reply to comment #12)
Did you mean 0.9.58 or 0.9.38?
Err, 0.9.58. And it was 0.9.56 and 0.9.57.
You mentioned you re-created your wineprefix. Perhaps, this problem only occurs with certain d3d settings (those wine Direct3D registry keys), and maybe you don't have these settings in your new profile? This does happen sometimes. If you did have some non-default settings for d3d in registry, try to isolate the one which created problems by changing them one by one and post here if you find anything, that info can be useful.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #15 from James Andrewartha trs80@ucc.asn.au 2008-04-06 12:28:13 --- (In reply to comment #14)
(In reply to comment #13)
(In reply to comment #12)
Did you mean 0.9.58 or 0.9.38?
Err, 0.9.58. And it was 0.9.56 and 0.9.57.
You mentioned you re-created your wineprefix. Perhaps, this problem only occurs with certain d3d settings (those wine Direct3D registry keys), and maybe you don't have these settings in your new profile? This does happen sometimes. If you did have some non-default settings for d3d in registry, try to isolate the one which created problems by changing them one by one and post here if you find anything, that info can be useful.
No, it was a once-off wineprefix that I then deleted, my recent testing was with the prefix I used some months ago, and haven't changed between it working, it not working and it working again. The D3D keys I have set in the prefix are OffScreenRenderingMode: fbo, PixelShaderMode: enabled and UseGLSL: disabled.
Oh here we go - starting without "-dsound" causes the hang for me. But the original reporter was running with -dsound, so this isn't related, apologies for the bugspam.
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #16 from Alexander Dorofeyev alexd4@inbox.lv 2008-04-06 13:25:24 --- Hmm. There are sometimes sound-related hangs at the start of the program in case wine crashed or was killed in the middle of operation - then there's a semaphore left in system apparently in some non-sane state, and wine hangs at start. This can be verified by running 'ipcs' command, there should be something like
------ Semaphore Arrays -------- key semid owner perms nsems 0x0056a4d5 ..........
it can be cured by removing this semaphore(ipcrm) or rebooting. I don't know if that's your case, but I get this problem all the time when killing games.
No, it was a once-off wineprefix that I then deleted, my recent testing was with the prefix I used some months ago, and haven't changed between it working, it not working and it working again. The D3D keys I have set in the prefix are OffScreenRenderingMode: fbo, PixelShaderMode: enabled and UseGLSL: disabled.
Oh here we go - starting without "-dsound" causes the hang for me. But the original reporter was running with -dsound, so this isn't related, apologies for the bugspam.
http://bugs.winehq.org/show_bug.cgi?id=11125
Zhenya Zenitur@yandex.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Zenitur@yandex.ru
--- Comment #17 from Zhenya Zenitur@yandex.ru 2008-07-22 23:33:40 --- Maybe, this is dublicate of 12929? Or 12929 is a dublicate?
http://bugs.winehq.org/show_bug.cgi?id=11125
--- Comment #18 from Austin English austinenglish@gmail.com 2009-01-21 10:48:39 --- Is this still an issue in current (1.1.13 or newer) wine? Are you sure it's not a dupe of bug 12929?
http://bugs.winehq.org/show_bug.cgi?id=11125
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #19 from Austin English austinenglish@gmail.com 2009-07-21 14:47:41 --- Abandoned. If you still have a problem in current (1.1.26 or newer) wine, and can provide the needed information, feel free to reopen.
http://bugs.winehq.org/show_bug.cgi?id=11125
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #20 from Austin English austinenglish@gmail.com 2009-07-21 15:08:58 --- Closing.