Although game is running smoothly, stable 60 FPS, the camera shakes, moves like it would have less FPS. Like scene would be 60 FPS, but camera 10 FPS. What’s the thing? It makes the gameplay not as fun…
@Adrians: Could be the dampning on the camera? I played around with it for a bit, though at my 8fps I couldnt see a difference.
@SmokingMirror: That’s very possible, my test session was very brief, haven’t tried doing all 3 laps (used the cube on layer 2 and moved the lap counter plane to test it)
Also, haven 't mentioned it before, but there IS a monster easter egg… well, actually there are two. See if you can find em!
runs very fine on dual core 2.3 ghz low end pc, 2.74 ubuntu. feels like good old nintendo days. camera is weird feels somewhat broken mechanics. jumpramps need texture or at least some wood normals. one of the best games so far.
edit: i have placed the camera behind the player and parented it at the jetski. activated slow parent with an offset of 65. works much better.
Really cool game. It runs well on my Asus Republic of gamers. Will try it later on my pentium P6-100. I didn’t find anything wrong with the controls or camera.
Ok, I see the camera shaking but not a big problem for me.
But, apparently “I lose” even though I came first… Maybe a bug there. Do you have to go over every ramp? I skipped a few.
You all probably know this, but to get the “win” scene to work, just select the lap counter plane,(lapcounter.001) and change AI property “laps” to equal player property “laps”. Both should equal 4.
I also ended the object (lapcounter.001) if AI property collided with the lapcounter plane first and property “laps” equal 4.
Nope, quite a complicated method, I used integers, if if you’re on the last lap it sets the property to 3, if they cross the line on 3, it assigns it to 4. If you cross at 4, you get the lose overlay.
Not sure what’s going on… it’s majorly flawed, I know.