TimeDemo on iPAQ VS. @migo

[Matt Keys]

Ok I just got my @migo and I ran the time demo on it overclocked to 236MHZ. I got 969frames in 113 seconds, 8.7fps. Could someone run the timedemo on their overclocked iPaq for comparison?

[Moose or Chuck]

how do u run timedemo, and i'll tell u what it runs on a 200 mhz e-125

[randall]

come on Chuck... what are you? New?

[Moose or Chuck]

have i ever run timedemo, or turned on the thingy to figure out FPS, no. I just always guesstimated the speed.

[Moose or Chuck]

mwuahahahahaha, since i don't have that level installed, i was getting 969 frames in 18.8 seconds and 51.5 fps thats cause it didn't process the frames

[Moose or Chuck]

whats the command to see the fps during normal play?? cause i wanna see how much speed i got from this bump too 200hmz

[randall]

There isn't a command to see FPS, that wasn't implemented until Quake 2.<br><br>A quick calculation with r_speeds can be done though. The first number is the number of milliseconds it takes to render a frame. The higher that number is, the lower the FPS will be. Divide that number into 1000 and you should get an approximate FPS.<br><br>If you have around 100ms, that's a little choppy, but not too bad. 400ms is is absolutely horrible.<br><br>Dan, how hard would it be to change r_speeds to reflect FPS instead of "milliseconds to render each frame"? I can estimate FPS by looking at the ms, but FPS would be much more useful to most people.

[Matt Keys]

type: timedemo "demo1.dem" into your console, letter for letter. please soemone on a iPAQ overclocked to 236. and make sure no programs are running in the background.

[Moose or Chuck]

i told u i did that, but it gives a bad reading cause i deleted that level.

[Dan East]

Randall, that's a good idea, and I'll add it to the list of enhancements for the next version.<br><br>For you guys timing the demos, make sure you use a blank autoexec.cfg (like one that only contains the timedemo command) or no autoexec.cfg at all. That's the only way to get the "true" benchmark.<br><br>Dan East

[Matt Keys]

I will try it again today without a autexec and post the results later on.

[Moose or Chuck]

But uhm, the first time the autoexec.cfg was run it automatically placed all those commands in the config.cfg, so you'd have to delete that too so it runs all the default settings. But run it once so that it creates the config, then close out and run it a second time this time with the time demo, so the created of the config.cfg file doesn't affect the timedemo.

[Matt Keys]

OK i ran the test again this time with no config file or autoexec. the results:<br><br>206MHz: 7.4FPS<br>236MHz: 8.6FPS<br><br>Now, anyone with a casio please run the same test so I can compare the two. and if your machine can go to 236MHZ please try that as well.

[999]

I'm interested to see how fast I can get it with an Autoexec file <br><br>Let's face it, True benchmarks aside, noone really plays with settings that basic do they?(with the exception of Moose ofcourse )<br>

[Matt Keys]

I would be interested to see that too 999, feel free to send me a nice custom autoexec. The @migo has four buttons on the front unlike the casio's three. their "aux" values starting at the top of the four bottons and working counter-clockwise are, aux2, aux3, aux4, and aux5.