Re: [Super-tux-devel] today's CVS commit
Brought to you by:
wkendrick
From: Ricardo C. <ri...@ae...> - 2004-01-23 14:13:48
|
Em Sexta, 23 de Janeiro de 2004 18:08, o Tobias Gl=C3=A4=C3=9Fer escreveu: > Am Do, den 22.01.2004 schrieb Ricardo Cruz um 20:16: > > Well, I can't still play the game in my laptop. It is a bit slow > > (Pentium Celeron), so the Tux isn't updated too often and takes off the > > screen... > > Hmm, I can't test the game on low-end machines currently. (AMD 2500+ , > NVIDIA GF4200TI, 256DDR) > > :( > > The game is currently optimized to "produce" as many frames per second > as possible. (up to 100) In the old code 40 were the absolute maximum > and probably never reached. > I'll introduce an option (CLI and menu) to tune SuperTux for old > machines. Stay tuned. :) > i have made 3 snapshots to see what's the situation: http://rpmcruz.planetaclix.pt/trash/supertux1.png http://rpmcruz.planetaclix.pt/trash/supertux2.png http://rpmcruz.planetaclix.pt/trash/supertux3.png Tux collision with bricks is not even tested, because it just "moves" way = too=20 fast. Since the framerate is so low, the game makes Tux to move without=20 updating all positions. And many ppl still use Pentium 2. > > I am not sure if these kind of code is making the slowness: > > while (issolid(pplayer->base.x, pplayer->base.y + 31)) > > { > > if (pplayer->base.ym < 0) > > pplayer->base.y++; > > else if (pplayer->base.ym > 0) > > pplayer->base.y--; > > } > > this code had been in the "old" SuperTux, too. > Didn't notice, the old gameloop was so huge :) Anyway, then it's the timer's fault. Ricardo Cruz =2D-=20 Help a swallow land at Capistrano. |