*sam* Posted Apr 2, 2009, 4:08 pm	This was a server-only patch, fixing some more DW:T bugs (including, hopefully, the one that was stopping playbacks of DW:T events working- but note that any events run before now will still be broken as the playback was being written incorrectly). Also, you now get a notification in a race/deathrace when your car is slipstreaming. If the driver has the slipstreamer specialism, you will get this info. as a percentage. I have put some extra game-logging in when you create DW:T events, to help me figure out why some vehicles are not getting created in your 'personal DW:T collection' when you make them. I intended to test this out right now but I'm outta time... gotta brave the Galway traffic once again...
The Paranoid Tourist Posted Apr 2, 2009, 4:13 pm	Ooh. I love the slipstreaming notification. . . if only I had a racer who was a slipstreamer. . .
*sam* Posted Apr 3, 2009, 3:09 pm	We just had a test-run (3v3) of my "Ragtag Attack" DW:T template. Quite a few usablity issues noted down... Also, playbacks are still not working for DW:T events, sorry about that. I will temporarily disable any playback events whose IDs are less than 300, to stop this being a problem. (The DW:T playbacks are still sending the server into an infinite loop which isn't good for CPU useage...)
Kime Dennory Posted Apr 3, 2009, 3:59 pm	On the other hand, this probably explains the serious slowness we were seeing the first or second day after these were implemented. A couple of tight infinite loops on the server can ruin your whole day. -KD
*Grograt* gary.r.horder@gmail.com Posted Apr 3, 2009, 5:06 pm	and a bad haircut
*sam* Posted Apr 3, 2009, 6:51 pm	Quote: On the other hand, this probably explains the serious slowness we were seeing the first or second day after these were implemented. A couple of tight infinite loops on the server can ruin your whole day. That's right, if there's one you notice a slowdown but at one stage we had two running so both CPUs were essentially loaded down.