Many thanks to all for the answers!
I'm making some test for understand the 'speed' of different CPU so I can 'calibrate' the game speed better.
The only certain result is that float calc on Celeron are very slow.
For the gfx I just discovered that on some *very old ATI cards* all is gone to the hell...I'm looking for more information about this card.
@Flameduck
2. Are Timers/Millisecs() EVER correct on different machines?
Define 'correct'? You should note that there seems to be an arbitrary limit as to how many consecutive timers you can have (on Windows?).
I express bad myself. I'm using something like this
With timers I refer to the 'internal' clock of CPU/computer, not with the 'timers()' of BlitzMax/Windows.
On the Celeron (and on a Pentium II) 'seems' that Millisecs() runs in a different way...
I'm making some test for understand the 'speed' of different CPU so I can 'calibrate' the game speed better.
The only certain result is that float calc on Celeron are very slow.
For the gfx I just discovered that on some *very old ATI cards* all is gone to the hell...I'm looking for more information about this card.
@Flameduck
2. Are Timers/Millisecs() EVER correct on different machines?
Define 'correct'? You should note that there seems to be an arbitrary limit as to how many consecutive timers you can have (on Windows?).
I express bad myself. I'm using something like this
IF millisecs()>Timer+Duration ...do something Timer=Millisecs() End IF
With timers I refer to the 'internal' clock of CPU/computer, not with the 'timers()' of BlitzMax/Windows.
On the Celeron (and on a Pentium II) 'seems' that Millisecs() runs in a different way...