Okay, the first time I tried running this under Linux on my
machine, I had a similar problem. However, it managed to run
after a second attempt, and I just ran it again and it
worked fine, with Indianapolis as my selection.
Hopefully I can figure out what's behind this bevahiour
soon. Sorry about that. Most of the development up until now
has been under Windows, so there might be a fair number of
little annoyances like this under Linux that need addressing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found a work around for the bug. I start an instance from
an xterm window. Then I get to the select team screen and
select a team. Then when it crashes I press ctrl-z in the
terminal window to put the program in a stopped state.
Then I start another instance in the same xterm without
kiling the previous process.
Maybe the program is crashing because some resource is
causing the crash and when you start a second instance the
crashing resource is busy and doesn't get invoked or
something. Just a guess.
I found a work around for the bug. I start an instance from
an xterm window. Then I get to the select team screen and
select a team. Then when it crashes I press ctrl-z in the
terminal window to put the program in a stopped state.
Then I start another instance in the same xterm without
kiling the previous process.
Maybe the program is crashing because some resource is
causing the crash and when you start a second instance the
crashing resource is busy and doesn't get invoked or
something. Just a guess.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1127463
Okay, the first time I tried running this under Linux on my
machine, I had a similar problem. However, it managed to run
after a second attempt, and I just ran it again and it
worked fine, with Indianapolis as my selection.
Hopefully I can figure out what's behind this bevahiour
soon. Sorry about that. Most of the development up until now
has been under Windows, so there might be a fair number of
little annoyances like this under Linux that need addressing.
Logged In: YES
user_id=196943
update: update:
I found a work around for the bug. I start an instance from
an xterm window. Then I get to the select team screen and
select a team. Then when it crashes I press ctrl-z in the
terminal window to put the program in a stopped state.
Then I start another instance in the same xterm without
kiling the previous process.
Maybe the program is crashing because some resource is
causing the crash and when you start a second instance the
crashing resource is busy and doesn't get invoked or
something. Just a guess.
I found a work around for the bug. I start an instance from
an xterm window. Then I get to the select team screen and
select a team. Then when it crashes I press ctrl-z in the
terminal window to put the program in a stopped state.
Then I start another instance in the same xterm without
kiling the previous process.
Maybe the program is crashing because some resource is
causing the crash and when you start a second instance the
crashing resource is busy and doesn't get invoked or
something. Just a guess.
Logged In: YES
user_id=196943
It may be my alsa lib.
Logged In: YES
user_id=1127463
Might be mine too. I just ran the game again and experienced
the crash, and this time didn't get any music to go along
with it.
I'll try including a --nosound option for the command line
in the next version.