About Timer

you may use another timer-component,
the TTimer-component is not very accurate in its intervall

I get from your question that your problem is not with the timer, its about how fast a computer can run your simulation program.

You can run a short part of your simulation on program startup and measure how much time does it take to run. Then you can adjust your timer interval based on that value. As there are indefinite number of computers out there in an indefinite number of configurations, you should not expect an exact value. So:

>> Is there anyway I can use constant speed Timer for all machine ?

no, there is not.

You can give user the option to adjust timer interval as he/she wishes.

To measure the times of diffrerent functions I use the following code, It can time down to a millionth of a second or so! If you can find out which procedures are taking too long then you can try to speed them up.  If you set your programs timer quite slow for everyone then there should be less of a difference when going between computers

The code is

function getStartSecs:extended;
var
  freq,start:int64;
begin
  QueryPerformanceFrequency(freq); {Get counts/second}
  queryperformanceCounter(start);
  result:=start/freq;
end;

function getElapsedSecs(const start:extended):extended;
var
  freq, count:int64;
begin
  QueryPerformanceFrequency(freq); {Get counts/second}
  queryperformanceCounter(count);
  result:=(count/freq-start);
end;

procedure TForm1.Button2Click(Sender: TObject);
 var
  start,stop1,stop2,freq:int64;
  i,j:integer;
  Times: integer;
  TotalTicks,NumASec: int64;
  Ticksfor1,Timefor1: real;
  x:extended;
begin
  Times:= {ENTER NUMBER OF TIME TO RUN THE PROGRAM 100+ RECOMENDED}

  screen.cursor:=crHourGlass;
  QueryPerformanceFrequency(freq); {Get counts/second}
  QueryPerformanceCounter(start); {Get string count}
  x:=0;
  for i:=1 to Times do ;
  QueryPerformanceCounter(stop1);  {Get end of loop1 count}

  for i:=1 to Times do  {TEST PROCEDURE GOES IN HERE}

   QueryPerformanceCounter(stop2); {Get end of loop2 count}
  screen.cursor:=crDefault;
  {calculate net counts per million processmessage calls and
   if we divide by freq (counts/sec), we get secs per million calls
  (i.e. microsecs per call)
 }

  TotalTicks:= (stop2-stop1)-(stop1-start);
  Ticksfor1:= TotalTicks/Times;
  Timefor1:= Ticksfor1 / freq;
  NumASec:= Trunc(1{second} / Timefor1);

  If freq>0 then
     showmessage('x='+floattostr(x)
     +#13+'Ticks taken to call the procedure '+inttostr(Times)+' times:= '+
     inttostr(TotalTicks)+
     #13+'      Ticks for 1 Call:= '+FloatToStrF(Ticksfor1,ffNumber, 4,2)+
     #13+'      Ticks per second:= '+inttostr(freq)+
     #13+'      Time in micro seconds for 1 call:= '+FloatToStrF(1e6*Timefor1,ffNumber, 4,8)+
     #13+'      Therefore you can call this procedure '+floattostr(NumASec)+' times a second')
  else showmessage('No hardware timer available');

end;

You will need to add Msystem and Maths to your uses.  The source has been modified from www.delphiforfun.org

hope that helps

DAvid

timer interval is totally dependant on the system clocking, so interval 1000 miliseconds is 1000 physical milliseconds, no matter what computer you running it on, 286 or P4 or AMD64. You may have a problem with running procedure inside timer, on P4 i may takes less time to process and AMD64 a little longer, then timer starts slipping. Look at the procedure/function execution