Test build results

[Argh]

Hmm, just tried the latest build (3008):

1. Good stability with KAI, no more random crashes! I actually got to finish a game with a new build, with an AI, for the first time in a month! Since I have made use of a lot of features that only work in 0.75b, I'm very happy about this- it makes testing game-balance of the use of new features much easier

2. Better framerate! Like, wow! At least 10 FPS gain, and no changes in my settings! I have shadows on 2048, and have no FPS below 40 unless something extreme is going on!

Now, I haven't beaten this thing to death, looking at specific bugs yet... but thus far, I'm pretty darn impressed. This is finally coming together into a very good build of Spring, I think.

[AF]

mingw32 or VS2003/5?

[Argh]

I dunno. From the size of the build, I'd say Mingw32.

Found one thing that's buggy- the fix for the weapon textures is borked, again I don't understand- this has been fixed in SVN builds for quite awhile, now it's borked again. Any good ideas why? It's extremely irritating that using a null texture as the "end" of a laser doesn't work properly...

[rattle]

Try to use an undefined tag (i.e. remove null from resource.tdf) and not a texture at all. This is the only workaround I found so far.

[Argh]

That doesn't cause a crash, or otherwise damage performance, and fails silently? If so, no biggie, I'll just take that out, problem solved...

<tested>

Works just fine. Glad you found that and thanks for sharing! Now I can just ignore this problem, and if I have another instance where I want to not see a given texture, I can just reference a foo.

I would've thought that Spring would crash if it couldn't find the texture reference, like it used to do- guess they made it fail-soft... good for modders, and it totally solves this problem

[rattle]

I think it crashed in the past if a tag refered to an undefined resource tag.