Control issue in the registered version

Talk about your ideas, rants, raves, technical issues, and problems.

Moderator: Forum Moderators

Post Reply
Elamaton (edit)

Control issue in the registered version

Post by Elamaton (edit) » Fri Dec 03, 2004 8:10 am

I just registered TS 1.00 and eagerly started playing. I chose 5 random tracks, picked The Slider, and started the practice mode.

When coming to the first curve after just starting the race, the car veered off into a random direction when I pressed the turn key, and the keyboard stopped responding. I took my hands off the keyboard and the car kept turning in place, movin slightly forward or back. Using the direction keys had no effect.

On the first time I tried hitting the esc key, and that did nothing. Then I tried alt+tab and ctrl+esc, nothing. Ctrl-alt-del, nothing. I almost reset the computer, when the ctrl-alt-del finally took effect and threw me to the Windows desktop. I shut down the game from Task Manager.

After that I tried shutting down some background programs, restarted the game, tried racing with the same settings, and got the same result. This time, though, the esc key returned me to the menu, albeit with a significant multi-second delay. The menus work without a hitch, the arrow keys do exactly what they are supposed to.

This is really weird. I downloaded the demo just yesterday, and it worked just great, both in practice mode and internet play. Only after entering the license did this phenomenon start.

I'm running a standard (workplace ;-)) desktop, with Windows XP Pro, admin rights, with no keyboard-afflicting background programs that I can think of (I played the demo with more stuff in the background than I had with the licensed version). 1280x1024, integrated Intel 82845Gx -series display controller. Active background programs: Moz Firefox and Thunderbird, a couple of PuTTYs, Total Commander, jEdit. The Java Virtual Machine is active in the background due to jEdit.

After writing this I'm going to try rebooting the machine altogether, and if that doesn't help, removing the license, and it THAT doesn't help, re-installing and relicensing the game. I'll post the results here after I'm done testing.

Elamaton

Resolved!

Post by Elamaton » Fri Dec 03, 2004 8:20 am

:oops: Boy, is my face red.

It turned out that just turning off ALL background programs was enough. Now, of course, this is a recommended practice for all games, but since I had no problems like this with the demo with all the stuff in the background, I automagically assumed it would be a bug.

Note to self: test assumed bug thoroughly before hitting the forums :?

Odd, though; with the list of background progs running, what could possibly be causing this? I'll keep on testing further, if I can identify the offending program.

Elamaton
Posts: 2
Joined: Fri Dec 03, 2004 8:26 am

Final notes

Post by Elamaton » Fri Dec 03, 2004 8:55 am

Well, I was unable to reproduce the situation with any reasonable amount of background programs. It remains a mystery why this occurred. My machine has been on the whole night between yesterday when I got the demo and today when I registered it, and the Java Virtual Machine was consuming over 80 megs of memory (still plenty left, though - 768 megs doesn't run out easily). Then again, it's been on for 24x7 for a good while before I even got the demo, which worked fine, and after shutting the JVM down and restarting it through jEdit, it's already using over 50 megs with no problems in the game.

I think this case can be closed, then. Too bad I can't edit the topic of the original post into something less alarming (maybe an admin can do that, perhaps edit out the FATAL BUG thingy :oops: ).

Enough with this, now I'll just have to choose between working and driving...

User avatar
Ande
Game Developer
Game Developer
Posts: 487
Joined: Thu Oct 14, 2004 9:43 pm

Re: Final notes

Post by Ande » Fri Dec 03, 2004 11:45 pm

Thank you for your information in any case! Actually, I have experienced something like that once when I was running Fraps (screen capture program) in the background. It may also have had something to do with having double buffering on (did you have it on?) or having a bigger-than-default screen resolution.

So there may really be some kind of bug in SDL event handling system. If you can find out the offending program or any other information on the issue, please keep us informed!

Post Reply