Joe#

I'm now embarrassed that I suggested this bad idea: when the next beta version is released this game's server owners and players/beta testers will want it to fix this map change crash bug not to instead add debug statements to the log to make the cause of this crash bug easier to find.

Hi guys, Firstly, I would like to thank everyone who has given up some of their free time to contribute to the development of this great free game. I played my first online Renegade X game today on the "Gold Rush" map and after 21 mins my game crashed on this map. After the crash I didn't write down any info about the state of the server and my game when this crash occurred. My PC: * OS: Windows 8.1 * Processor: 2.6 Ghz Dual Core Intel Celeron G1610 * RAM: 8 GB DDR3 with dual channel bandwidth enabled * Graphics Card: HD 7750 with 1GB GDDR5 * Hard drive: SATA 3, 7200 RPM, 930GB with 64 MB of cache I was playing as Nod and my team was winning, I don't know if my team had won just before the crash occurred because I was in my base defending it while my team mates were attacking the enemy base with flame tanks. I was at a terminal inside a building which I think I recall was the Obelisk of light. Because they don't have error call stack traces to work with, I personally think this game's programmers should consider releasing a beta version which can print debug statements to the log at the different stages of the map change process. Some of these statements will be printed before this process fails showing the programmers which statements in this process have been successfully executed before the crash. Log.zip