Possible bug in Shooter demo

#1 Actually, I believe this is a "bug" in your keyboard. A keyboard can only send so many signals and certain key combinations conflict. On my keyboard here I was able to move diagonally up and left while shooting. This underscores the importance of configurable keys for shipping games.

#2 Its just strange that I can hold space, right and down... space, up and right.. space down and left, everything EXCEPT up and left... If its a bug with my keyboard, it would have to be a bug with the up and left keys specifically. And they appear to be working fine, in other applications..

It would be troubling to think that some people will be unable to move diagonally while pressing another button as well, 3 buttons really shouldnt be too much for the keyboard, and i can use the Up, Left, Space combination in any other application without problems. I'm going to try and put together a more focused experiment to see if I have any other combinations which act flakey, this might be useful to anyone else with similar issues..

#3 3 buttons CAN be too much for a keyboard. It's called keyboard masking... another effect you get is keyboard ghosting where pressing two keys together will result in a third key press event being triggered for a key you didn't press.

This is a common problem for Arcade Emulators that use the keyboard input to hook Joystick and buttons up to.

#4 Ahhh! I see... Do you have any reccomendations for dealing with these sorts of problems? I guess the first thing I should try is remapping 'fire' to something other than space..

Edit:
Ok, I mapped 'Z' to fire as well, and using the up and left arrow keys in combination with the Z key didn't produce the problem for me that Up + Left + Space did. I can also use W + A + Space, as well as W + A + Z. No big deal, Ken's point about the importance of having configurable controls is spot on!

#5 Gamepad support is really handy in these situations. :)

#6 No one else has a thruster particle effect in the middle of the screen the whole time?? Maybe I screwed something up in doing the Basic Tutorial? This is after using the .bat file to run the game.

#7 @Corey: I'll have to dig out the resource but configurable controls would work in an identical manner as TGE being as it uses the same system. Yes, this kind of stuff only becomes a problem with twitch-style games with lots of keys.

@Drew: Well each object defaults to position (0,0) and the default coord for the middle of the screen is (0,) but if it had been mounted to an object and wasn't destroyed (which it will be automatically if it's mounted unless you specifically turn this off), it would be left where it was, not the middle of the screen.

It looks like, for some reason, the thruster is not being mounted to the parent object correctly. I'd recommend double-checking the console (tilde ~ key or check "console.log" file next to the T2D executable) and if you don't see any T2D errors, check the calls you're making to "attachThruster()". Just double-check you're passing "%parentObject, %mountPosition, %angle", something like "attachThruster( $player, "-0.12 -0.33", 0 );".

- Melv.

#8 @Drew: I had this happen too in the Shooter demo after completing the basic tutorial. I got rid of the problem by reverting the client.cs in the example/T2D/client directory back to the default one.


EDIT: Upon checking the console, there is an error message being displayed stating:

"Object '1649' is not in the same SceneGraph!"

This error message continually repeats with the object number increasing on every iteration.

I'm not 100% sure why this could be happening - Unfortunately I've not had the chance to investigate more fully.

#9 Thx Dave, I figured it was something I did in the Basic Tutorial, but I was too tired to look into it at that point last night. Stayed up way late playing with T2D :)