This was discussed in the IRC channel last night. Something about how the process actually closes is interpreted by Vista as a crash, though it is a successful close.
For now the fix appears to be to just tell Vista to close it.
Intrestingly, Windows XP doesn't produce such behavior.
But yes... I do use abort() instead of exit() in the specific instance to guarantee a close of the interpreter once the game dies. Ruby tends to be uncooperative when exit() is called.
I'll produce a new rubyintersect.dll version that works around this.
Edit:
I've fixed this by switching abort() to ExitProcess() in the terminator thread. We'll release an RC2a shortly to fix this and the other bug found in RC2.
Comments
I am also getting this error. I run Windows Vista 32 bit Home Edition Premium.
For now the fix appears to be to just tell Vista to close it.
But yes... I do use abort() instead of exit() in the specific instance to guarantee a close of the interpreter once the game dies. Ruby tends to be uncooperative when exit() is called.
I'll produce a new rubyintersect.dll version that works around this.
Edit:
I've fixed this by switching abort() to ExitProcess() in the terminator thread. We'll release an RC2a shortly to fix this and the other bug found in RC2.
Patch RC2a was live as of... saturday? yeah, saturday.
That would be neat.
Maybe we can get some type of e-mail newsletter thing set up or something...
Yeay, or if theres a new un-read article, the TribesNext tab could highlight, or flash, or something badass like that.
there are plans for an autoupdater in the future.