C# OpenGL game. Help on incrementing a score..

[XA04]

Anybody here know C# well?

Basically I'm using OpenGL and the TAO framework to create a game and I'm trying to increment a score simply by one. I'm making space invaders and when the bullet hits the enemy the score needs to go up by one. Now I simply can't increment the variable by 1 as the display method updates however many times a second and so the score ends up getting incremented 30 odd times mores instead of once.

I've had a play about using booleans to create some kind of switch but this doesn't seem like the right thing to do. I have a feeling that using the system clock to only allow 1 to be incremented if a variable is used to measure a gap of 2 seconds between incrementing. This would stop it right?

Just can't get my head around doing it.. anybody got an example for me?


Thanks!

[kalniel]

No specific knowledge of c#, but why not only increment the score by one once, until some other condition like the bullet is no longer hitting the enemy or a new bullet is fired?

eg (psuedo logic/code)

BulletHitsEnemy {
  if !alreadyHit { 
    score++;
    alreadyHit =1;
  }
}
BulletFired {
  alreadyHit =0;
}

Yes, I know you said you played with it, but why did it not seem like the way to go exactly?

[Lucio]

The flaw to kalniel's pseudo-code is it assumes only one bullet will be in play at any one time.

To my mind the logical point to put your scoring code is in the response to the bullet's impact. Presumably a shot hits an enemy, and it either takes damage or is destroyed outright. In either case, those are the points to tag on the scoring system. Since the damage/destroyed response can only occur once, your score should only increment once.

[kalniel]

The flaw to kalniel's pseudo-code is it assumes only one bullet will be in play at any one time.

Just like early space invaders

But it was just an example. There are other other conditions you could check like damage/destroyed, or start being fancy and assigning an ID from a pool of IDs equal to the number of bullets you can have in play at a time to each bullet such that each bullet can only score once.

Or you could speed up your response so that in the same cycle that a bullet hit is detected the bullet is removed, and/or the invader object is removed and relaced with a non-interactive dying animation etc.

Or take your hit calculation out of the display stuff.

[XA04]

Cheers guys will have another play about with it. I will only be shooting one bullet at a time, just like the original.

The bullet travels through the enemy at the moment and once that is detected I will be running another method to set the score, reset the start positions etc. I think where I'm going wrong is the bullet keeps travelling through the enemy so keeps on incrementing the score. If I make the bullet disappear as soon as it detects the collision then hopefully it should only increment once... so I'll take your ideas into account and have a play about with it and let you know how I get on

Cheers!

Edit: Yep, sorted already.. obviously was at it too long yesterday and got my mind all confuddled.

        static public void ResetPlayers()
        {
            bulletY = 0;
            bulletShot = false;
            playerScore++;
        }

This is just very basic sample code, not looking for criticism