Spring RTS Engine

Hi there!

I wanted to try Chilli UI (i.e. copypasted the needed files and 1 example) for my own project and on game start, my whole system frooze. Since that time, all spring games and mods freeze everything in finalizing-phase.
Last time spring was so powerful was in 2008 or '07.

I went for a new make install, some files were "up to date" and some were renewed, but still the same problem.

Infolog from THIS attached, there are some errors, but nothig special, its the same with BA/CA/Whatever

So there must have been a permanent change to something

Edit: now with BA-Infolog too

pretty sure ba/ca doesn't have an invalid main.lua

smoth wrote:pretty sure ba/ca doesn't have an invalid main.lua

As I wrote, the basic mod-related errors don't matter. But now theres a BA-Log aswell. I could also create one with gundam.

smoth wrote:pretty sure ba/ca doesn't have an invalid main.lua

Do you mean to say he has corrupted or changed his main.lua file and it needs to be replaced?

Dunno, yet again attachments are not working.

He had an error about allow unsafe changes that was crashing his main.lua.
*edits* they are working now:

[f=0000000] Lua LoadCode pcall error = 2, LuaRules/main.lua, [string "LuaRules/main.lua"]:3: attempt to call global 'AllowUnsafeChanges' (a nil value)

anyway. what does this have to do with chili? ba doesn't use it. you are still getting the freeze at finalize?

smoth wrote:Dunno, yet again attachments are not working.

He had an error about allow unsafe changes that was crashing his main.lua.
*edits* they are working now:

[f=0000000] Lua LoadCode pcall error = 2, LuaRules/main.lua, [string "LuaRules/main.lua"]:3: attempt to call global 'AllowUnsafeChanges' (a nil value)

anyway. what does this have to do with chili? ba doesn't use it. you are still getting the freeze at finalize?

He said the problem started after he "wanted to try Chilli UI (i.e. copypasted the needed files and 1 example) for my own project" so I'm thinking corrupted preferences, widget scripts or he has altered his base files in some way... it would have had to be something that didn't get reverted when he uninstalled and re-installed but I don't know enough about what is cleaned up on Linux on uninstall to make informed suggestions on how to resolve that type of issue.

Edit:
Just noticed he didn't uninstall and re-install, assuming "make" refers to building a new version/updating.

@OP: back-up all of your spring folders (so you don't lose any work you've done on your personal projects etc.) and then completely uninstall spring and clean out all of it's folders... then make a brand-fresh install of spring.

If spring hasn't worked for you since 2009 then you may be having a problem completely unrelated to your experiments with chilli... cleaning everything out and starting from scratch will eliminate whatever you may have done wrong as a factor... so if it still doesn't work at that point at least me know to look elsewhere for issues.

Hi. The reference to 2009 was meant the other way round: Crashes of course happen sometimes, but a complete system-freeze due to spring happend last time 2-3 years ago, so there must be something serious.

I only ran "make install", so didn't completely purge spring before. Hoped, it could correct some basic stuff. I will go for a complete cleanup tomorrow. I will backup ~/.spring/ for obvious reasons, is anything else needed to track down the problem later on?

@smoth: It was something about THIS, its an old version, where you still had to call AllowUnsafeChanges for some effects. It's not in the BA-Log.

Your problem has absolute nothing to do with chili.
It isn't even loaded!

You enabled something in your (spring) settings that is incompatible with your graphics drivers!

PS: You are running an Intel GPU under linux -> you got MesaGL + a few hw optimizations = crap. So you have to deactivate all (esp. shader based) fancy thingies.

Spring should simply outright close when an Intel integrated card is detected. This is fucking ridiculous. Us gamedevs end up spending hours chasing phantom bugs because of this crap.

jK wrote:Your problem has absolute nothing to do with chili.
It isn't even loaded!

You enabled something in your (spring) settings that is incompatible with your graphics drivers!

PS: You are running an Intel GPU under linux -> you got MesaGL + a few hw optimizations = crap. So you have to deactivate all (esp. shader based) fancy thingies.

most likely false
true
false
true

Fact is: While HW and some other stuff might be crap, things went fine until that point today. As I could not remember just downgrading my board / manually changing settings, it's not related. All games went fine. I don't expect LUPS to work or to see units in Evo atm. Settings are all off/down anyway.

camo wrote:As I could not remember just downgrading my board / manually changing settings, it's not related.

If I would would get a penny each time I hear this

Actually, Evo functions quite well on asscrappy settings. It looks awful, but otherwise works just fine.

Integrated Intel gfx cards are a scourge and should be stamped out.