S.T.A.L.K.E.R.: Call of Pripyat Forum

I have used the command line switches: -nosound -i to start the game.
Without the first switch game is stopped with blak blank screen (the intro must be shown here).
Without the second switch the mouse is locked at the middle of the screen.

could you please explain how you set the command line parameters.
i could not figure it out how this work.
the game runs fine but i have this f**king bug with the fixed mousepointer.

EDIT:

strange...it works to use the mouse but the graphic screwed up then.
reinstall it to another bottle. mouse works only on 1200x1024px window mode.
in fullscreen mode or other resolutions the mouse is fixed.
d3d9.dll and dinput.dll override making the game crash.
also trying to use the regedit DirectInput method lets the game crash.
console command "input_exclusive_mode 1" was also no solution for this problem.
for now im fine with the window mode. :D

I installed the game, and I have the following issues:
-Mouse fixed at the center of the screen. This without any comand line.
Now, the saddest part: whenever I try using ANY comand line on the launch options, the game just won't run.
If anyone could help with this issue, it would be most apreciated.

Running on a MacBook Pro, latest Cross Over version (Demo, though) and through Steam.

EDIT: I forgot to add: keyboard didn't work in the menus also, until I deactivated the Steam Community Option. (ALT+TAB thing)
So yeah, seems like Steam itself is causing the issue....

Hi,

That actually sounds like ...can you assert for me that you're
running the demo version of Crossover Games 9.1? There was an issue
like that with the previous crossover games version that was fixed
in 9.1 so I'm just making sure we're both on the same page here....

...however, I have the Steam version of Stalker:SoC and the latest
Steam update has seemingly broken this title. Another user in the
Stalker:SoC forum also reported that Stalker:CoP has been broken
as well...I submitted a support ticket on this over the weekend, so
the problem is known....but at present, you might not have any joy
with this title due to something Steam has done which crossover games
hasn't (yet) been optimized to handle...

@Anyone else in this forum with the Steam version of Stalker:CoP --
can anyone confirm or not the latest Steam update has caused issues
with this title?

Cheers!

Yep.... CrossOver Games 9.1.0

And I think you are RIGHT, I checked the Steam Forums, and some people seems to be having issues with the game, also, after the latest client update.
I guess that must be the cause....
Anyway, if you guys can fix it or do something about it, it would be great.
I convinced a friend of buying his own CrossOver Games License (Even before mine, hehehe...) and I would love to see how the game runs in his i7 iMac :P

Thanks Don!!

EDIT: I forgot to add: keyboard didn't work in the game main menu, until I deactivated the Steam Community Option. (ALT+TAB thing)
So yeah, seems like Steam itself is causing the issue....

ultramalakian wrote:

Yep.... CrossOver Games 9.1.0

And I think you are RIGHT, I checked the Steam Forums, and some
people seems to be having issues with the game, also, after the
latest client update.
I guess that must be the cause....
Anyway, if you guys can fix it or do something about it, it would be
great.
I convinced a friend of buying his own CrossOver Games License (Even
before mine, hehehe...) and I would love to see how the game runs in
his i7 iMac :P

Thanks Don!!

EDIT: I forgot to add: keyboard didn't work in the game main menu,
until I deactivated the Steam Community Option. (ALT+TAB thing)
So yeah, seems like Steam itself is causing the issue....

Hi,

Yeah, it's a little unfortunate when a change in Steam does something like this...not only to
Crossover users either, but to windows users as well 8) Typically speaking in cases like this, it's
sometimes 'sit on your hands' time and wait for Steam to redress the issue 8)

Cheers!

We have confirmed that a number of recent bugs in Steam games are due to changes in the in-game community overlay DLL. For some games, disabling the in-game community feature via Steam's settings is good enough to fix the problem. For other games, that's not enough.

For those, you can go into the Wine Configuration (winecfg) tool via Manage Bottles -> select bottle with Steam -> Control Panel. On winecfg's Applications tab, click Add Application. Select the executable of the Steam game that's having the problem (or just type its filename, like foobar.exe) and click Open. Select the Libraries tab of winecfg. Type GameOverlayRenderer in the "New override for library" edit field, click the Add button, click the Edit button, select Disable, click OK, and click OK. That prevents the in-game community overlay from even being loaded for that game.

If you don't use the in-game community, you might find it simpler to just disable it for the whole bottle. To do that, just skip the above steps involving the Applications tab of winecfg. Just leave it with Default Settings selected, which is how it starts, and go straight to the Libraries tab and proceed from there.

Tried that Ken, word by word, and it didn't work...
Seems like we'll have to wait for a Steam fix after all.... :(