ok i got the default game loop
speed_counter is incremented 100 times per second.

while (!key[KEY_ESC])
{
   while (speed_counter>0)
   {
      game();
      speed_counter--;
   }
   draw_game();
   //while (speed_counter==0) rest(1);
}

this way i get 100+ FPS.
if i uncomment the rest(1)-line my FPS-counter stays at 64.
so shouldn't i get here FPS around 100, too?

Are you using vsync or tripple-buffering?

no just double buffering.
the strange thing is that i uncommented this line once before and then it worked fine...
this was with an older compiler but this shouldn't matter!

Resting isn't accurate. Resting for 1ms will cause you to rest closer to 10ms (giving you 100 FPS max). Then add in the time to do the logic and render each frame, and possible background tasks in the system, and you'll get less than 100 FPS. What's your speed if you use rest(0) instead of rest(1)?

for rest(0) it's the same thing.
and i know that the timer isn't that accurate but when i did this before the FPS were around 100 (+- 5) but not constant 64...

Maybe something has turned on your vid card vsync. Just a week ago my favorite old DOS editor could use the extended keys again for no reason that I could see.

"I hate computers, they're so nasty and complex. I could just pinch them" Marvin the Martian

in this case is there any way to disable vsync or do i have to reintstall the older version of mingw?

I doubt its your compiler. There should be an option in your video card settings to force vsync on or off, or leave it application defined.

I doubt it's a vsync issue though. What version of Allegro do you have?

Calling rest(1) forces the OS to put the process on the queue and hence reschedule it. 10ms time slices isn't too uncommon. Quick guess, you using windows?

ps: This is why its not a "real-time" os.

yes its in windows (and linux) and newest allegro
even if rest(1) would delay more than 10 ms there would be only a few frames less but not that much

Tasks/Threads get 10ms slices, its more than possible to loose 100ms after doing your slice, it all depends on the system load, and the priorities all threads are running at.

edit, You CANNOT depend on the scheduler doing anything in a non real time OS.

ok i reinstalled the older verision of the compiler with no success.
i said my timer runs 100 times per second and with rest(1) i get 64FPS.
i have tested timers that runs 50 and 40 times per second and here i get the 50 and 40+-1 FPS.
so whats the difference betwenn a 50 and a 100 BPS timer

edit: Eh nevermind, not entirely sure what you're getting at

About twice as many tics (meaning more logic calls, and more attempted frames drawn). If your system is just barely keeping up at 100FPS with no resting, it can lose several frames if you try to rest any.

i know that 100 is twice as fast as a 50 BPS timer...
i meant what makes the difference in the FPS?

and without rest(1) i get around 150 FPS so this shouldn't be the problem.

[edit]
even this code doesn't work - test it yourself !

Both rest(0) and rest(1) give me 55~60 FPS with that. Granted though, X isn't the best at getting the fastest speed.

yes someone try it in windows!