Starcraft I broodwar dying on mouse click.

simak · Post by **simak** » Mon Jan 23, 2012 9:11 am

Hello.
I have Fedora 16 and wine-1.3.36.
I installed starcraft broodwar with out problems.
Then i started game and created local network game it was ok.
When the game starts i can go in menu and click with mouse everywhere changing options and preferences, but when i make any click on the map or the unit the game just go out...
So any click in game after it starts - cause to starcraft die.

John Drescher · Post by **John Drescher** » Mon Jan 23, 2012 10:14 am

I have Fedora 16 and wine-1.3.36.
I installed starcraft broodwar with out problems.
Then i started game and created local network game it was ok.
When the game starts i can go in menu and click with mouse everywhere changing options and preferences, but when i make any click on the map or the unit the game just go out...
So any click in game after it starts - cause to starcraft die.

How about posting on pastebin the terminal output during the crash?

http://wiki.winehq.org/FAQ#get_log

Also graphics cards and drivers can effect this. nVidia with nVidia
proprietary drivers still represents the best chance of success with
Intel gpus and drivers having the most problems.

John

simak · Post by **simak** » Tue Jan 24, 2012 2:14 am

John Drescher wrote: How about posting on pastebin the terminal output during the crash?

Here is the whole output after starting StarCraft.exe

Code: Select all

fixme:advapi:SetSecurityInfo stub                                                                                                                                                                    
fixme:win:EnumDisplayDevicesW ((null),0,0x33f2fc,0x00000000), stub!                                                                                                                                  
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 32 channels, pretending there's only 2 channels                                                                                       
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels                                                                                    
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels                                                                                    
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels                                                                                    
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels                                                                                    
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels                                                                                    
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 32 channels, pretending there's only 2 channels                                                                                       
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels                                                                                    
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub                                                                                                                                                     
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub                                                                                                                                                     
err:seh:setup_exception_record stack overflow 1200 bytes in thread 0027 eip 681d4634 esp 00240e80 stack 0x240000-0x241000-0x340000

John Drescher wrote: http://wiki.winehq.org/FAQ#get_log

Thanks. RTFM forever

.

John Drescher wrote: Also graphics cards and drivers can effect this. nVidia with nVidia
proprietary drivers still represents the best chance of success with
Intel gpus and drivers having the most problems.
John

Code: Select all

lspci | grep -i nv 
04:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce 9400 GT] (rev a1)

Code: Select all

lsmod | grep nv
nvidia              12122373  30 
i2c_core               28203  2 nvidia,i2c_i801

Code: Select all

nvidia-settings -v
nvidia-settings:  version 290.10

Yesterday i found that if i run it in window mode - all is great, but if it is full screen all ruins after any click in created game.

simak · Post by **simak** » Tue Jan 24, 2012 2:16 am

But it is not very fun to play in window size of which is 800x600, when size of my linux desktop is 1600:900 .

jjmckenzie · Post by **jjmckenzie** » Tue Jan 24, 2012 10:17 am

On Tue, Jan 24, 2012 at 12:16 AM, simak <[email protected]> wrote:

But it is not very fun to play in window size of which is 800x600, when size of my linux desktop is
1600:900 .

You should be able to change the size of the virtual window to match
your desktop size and run it that way. Does this not work?

James

simak · Post by **simak** » Tue Jan 24, 2012 10:50 am

jjmckenzie wrote:On Tue, Jan 24, 2012 at 12:16 AM, simak <[email protected]> wrote:
But it is not very fun to play in window size of which is 800x600, when size of my linux desktop is
1600:900 .
You should be able to change the size of the virtual window to match
your desktop size and run it that way. Does this not work?

James

No, starcraft l has it's own resolution - 800x600 or even 640x480, so when it starts - the size of picture comes to this little resolution.
So i need to fix fullscreen mode...

jjmckenzie · Post by **jjmckenzie** » Tue Jan 24, 2012 11:11 am

On Tue, Jan 24, 2012 at 8:50 AM, simak <[email protected]> wrote:

jjmckenzie wrote:
On Tue, Jan 24, 2012 at 12:16 AM, simak <[email protected]> wrote:

But it is not very fun to play in window size of which is 800x600, when size of my linux desktop is
1600:900 .

You should be able to change the size of the virtual window to match
your desktop size and run it that way. Does this not work?

James
No, starcraft l has it's own resolution - 800x600 or even 640x480, so when it starts - the size of picture comes to
this little resolution.
So i need to fix fullscreen mode...

Thank you for this piece of information. I'll read through this topic
again and see if I have any ideas to help. Others may also provide
additional information as well.

James

L. Rahyen · Post by **L. Rahyen** » Tue Jan 24, 2012 11:37 am

But it is not very fun to play in window size of which is 800x600, when size
of my linux desktop is 1600:900

Why not use xrandr to switch resolution to 800x600 before running the game
and back to 1600x900 after you're done playing? It can be easily automated: you
can create shell script for that. First, run "xrandr" to make sure that you
have 800x600 available, then run "man xrandr" for relatively short manual how
to use it.
For example, if your favorite editor is nano, run:
sudo nano /usr/local/bin/starcraft
...and put the following into it:

#!/bin/bash
xrandr -s 800x600 -r 60
cd /to/the/directory/where/StarCraft.exe/is/located
WINEDEBUG=-all wine StarCraft.exe
xrandr -s 1600x900 -r 60

Of course, edit the path appropriately. Than run:

sudo chmod +x /usr/local/bin/starcraft

Now you can run your game just by running "starcraft". Of course, you need
to set your window manager to position virtual desktop window at 0,0 (top left
corner of the screen) and show it without border. In KDE you can do this by
running your game in virtual desktop and then in its Window Menu click
Advanced -> Special Window Settings. I do not know how to do this in non-KDE
environment.

simak · Post by **simak** » Wed Jan 25, 2012 1:19 am

L. Rahyen wrote:
But it is not very fun to play in window size of which is 800x600, when size
of my linux desktop is 1600:900
Why not use xrandr to switch resolution to 800x600 before running the game
and back to 1600x900 after you're done playing? It can be easily automated: you
can create shell script for that. First, run "xrandr" to make sure that you
have 800x600 available, then run "man xrandr" for relatively short manual how
to use it.
For example, if your favorite editor is nano, run:
sudo nano /usr/local/bin/starcraft
...and put the following into it:

#!/bin/bash
xrandr -s 800x600 -r 60
cd /to/the/directory/where/StarCraft.exe/is/located
WINEDEBUG=-all wine StarCraft.exe
xrandr -s 1600x900 -r 60

Of course, edit the path appropriately. Than run:

sudo chmod +x /usr/local/bin/starcraft

Now you can run your game just by running "starcraft". Of course, you need
to set your window manager to position virtual desktop window at 0,0 (top left
corner of the screen) and show it without border. In KDE you can do this by
running your game in virtual desktop and then in its Window Menu click
Advanced -> Special Window Settings. I do not know how to do this in non-KDE
environment.

I had already try that, but it is not solution for the starcraft, when you need to scroll the map with mouse. You move your mouse to bottom off the screen so the map must scroll down but it is not, because you are out of full screen.

Ohh cmon do not we really can make the full-screen work?

Nobody knows what can this means?

Code: Select all

err:seh:setup_exception_record stack overflow 1200 bytes in thread 0027 eip 681d4634 esp 00240e80 stack 0x240000-0x241000-0x340000

L. Rahyen · Post by **L. Rahyen** » Wed Jan 25, 2012 2:12 am

Ohh cmon do not we really can make the full-screen work?

Only somebody who is willing to run regression test can help to "make it
work" in (hopefully) near future. Anybody who have the game can run regression
test including you, its very simple and straightforward process
http://wiki.winehq.org/RegressionTesting . Please read
http://bugs.winehq.org/show_bug.cgi?id=29544 for more information about this
bug. If nobody will run the regression test then it is unlikely to be fixed,
its your responsibility as a user to report the regression properly (by posting
regression test result).

I had already try that, but it is not solution for the starcraft, when you
need to scroll the map with mouse. You move your mouse to bottom off the
screen so the map must scroll down but it is not, because you are out of full
screen.

How can you be "out of full screen" if you ARE in full screen? Assuming of
course your game uses 800x600 resolution and it is supported by X, and you have
removed the border and positioned the window correctly, and you have used
script given in my example and not something else. Solution I have provided is
equivalent of "real" full screen mode IF you did everything properly and your
game runs in foreground (so you are not switched back to native resolution
until you exit it). If it does not work for you, then either there is a bug
somewhere, or your game runs in background (then you have to remove "xrandr -s
1600x900 -r 60" to make it work as expected and run xrandr manually after
exiting the game) or you (or your window manager) did something wrong.
But if you really cannot use this workaround for some reason (for example
because your window manager cannot do what's necessary for this workaround to
work), you can try downgrading Wine. If this is what you want, read the bug
report to know to what version you need to downgrade.

simak · Post by **simak** » Wed Jan 25, 2012 2:53 am

L. Rahyen wrote: Please read
http://bugs.winehq.org/show_bug.cgi?id=29544 for more information about this
bug.

I confirm, that there is no such bug with starcraft l - all works fine.

simak · Post by **simak** » Wed Jan 25, 2012 2:54 am

simak wrote:
L. Rahyen wrote: Please read
http://bugs.winehq.org/show_bug.cgi?id=29544 for more information about this
bug.
I confirm, that there is no such bug with starcraft l - all works fine.

Ohhh. I mean with wine version 1.3.24

P.S. Why can`t i edit my message...

L. Rahyen · Post by **L. Rahyen** » Wed Jan 25, 2012 3:27 am

I confirm, that there is no such bug with starcraft l - all works fine.
Ohhh. I mean with wine version 1.3.24

Please say this in the bug report (not here in the forum) to confirm the
regression. Most developers do not read this forum; also it is important to
keep information about bugs organized.

If you find the time to perform regression test then it would be very
helpful for Wine Project, it will not take too much of your time and will help
to fix the bug.

P.S. Why can`t i edit my message...

Read the sticky topic "Editing is disabled"
http://forum.winehq.org/viewtopic.php?t=5710 , the reason is given there.