Spring RTS Engine

(sorry if it seems like all I do is complain )

I installed Spring on Ubuntu Jaunty, and it worked without any major problems. I upgraded to Karmic, and suddenly the game wouldn't start from the Lobby over half the time; no error messages or anything, just nothing. Pushing the button several times would start it, but afterwards there would still be a "spring" process running that I would have to kill in the system monitor in order to start another game.

I thought it might be because it was originally installed in Jaunty, so I removed the pacakages and deleted the .spring and .springlobby directories in my home directory, and then reinstalled. Got the same problem, except I get an error message saying the game has crashed. Again, it will still launch sometimes, but there is still a process running that I have to kill (killing it gives me the same error message).

Also, this happened in single player. Haven't tried multi yet.

Is this a problem with Spring or with Karmic? Should I post the infolog file?

And for more fun, units in-game often have white boxes appear above them, and the idle builders widget doesn't work. Almost makes me want to find my OTA disc

wombatron wrote: Is this a problem with Spring or with Karmic? Should I post the infolog file?

It would help a bit if you would, yeah. Just paste it on pastebin or something like that.

wombatron wrote: And for more fun, units in-game often have white boxes appear above them, and the idle builders widget doesn't work. Almost makes me want to find my OTA disc

Wasn't this already a known bug? Or was that with the 3d trees?
In case you have an ATI graphics card: check if you have ATI hacs turned on. That often solves things for many people.

Ok, here it is. Also, I installed from the official Karmic repos, and I've purged the packages and deleted all files associated with Spring and then reinstalled multiple times, so I don't think it was just a 1-time buggy install.

Pretty sure it's a Karmic problem, because the error didn't occur in Jaunty, but just in case:

Ubuntu 9.10 Karmic Koala
NVIDIA GeForce 6150 SE (integrated; using recommended NVIDIA accelerated graphics driver Version 185)
AMD Athlon 64 X2 4000+ 2.1 GHz
2GB DDR2 SDRAM

Yeah, I know it sucks

Have you tried reverting spring settings to defaults (there's an option in the file menu of the SpringSettings app)?

.springrc

MidKnight wrote:Have you tried reverting spring settings to defaults (there's an option in the file menu of the SpringSettings app)?

Just tried it. Still have the problem.

aegis wrote:.springrc

What do you mean?

Post your springrc

(.springrc attached)

I get this error message after make:

Error: Could not find 7z.
make[2]: *** [CMakeFiles/gamedata] Error 1
make[1]: *** [CMakeFiles/gamedata.dir/all] Error 2
make: *** [all] Error 2

Well, I decided to try the binary installer. It worked, and the game isn't crashing almost every time. I do get a dialog saying that "You cannot start a spring instance while another is already running" whenever I try and start a single player game after playing one, but there isn't a ghost process and I just have to close out of the lobby.

EDIT: Never mind, there is still a process left over after a game. Ugh. At least it isn't crashing any more.

ur nick sounds familiar, hmmmm...

Wombat wrote:ur nick sounds familiar, hmmmm...

Hail, fellow burrowing marsupial!

f u

wombatron wrote:I get this error message after make:

Error: Could not find 7z.
make[2]: *** [CMakeFiles/gamedata] Error 1
make[1]: *** [CMakeFiles/gamedata.dir/all] Error 2
make: *** [all] Error 2

install package p7zip-full

Thanks hoijui! Ok, I uninstalled the binary, built spring from the link posted above, and it doesn't crash anymore. However, there are still several processes running after I close out of a single-player game, called "spring" and "sh". I guess this is a different bug, so does anyone know what to do about this? I have to manually end the processes in the system monitor, and doing that after every time I play a game just strikes me as being a bad idea.

could it be that this only happens when using Java AIs?
that would explain it at least, cause... because the JVM can not be created, deleted, and created again in a single native process (eg running spring once), and because of the current way AI Interfaces are loaded, i can not kill the JVM, and hugh already reported that he has problems wiht that.
it might help if you disable the debug agent in the jvm.properties file under AI/Interfaces/Java/0.1 (will not change anything if you odnt use Java AIs).

No, I haven't been using the Java AIs. Just NullAI 0.1 and RAI 0.601.

ok.. then i have no idea :/