World: r3wp

How many RHz do you get with: http://www.rebol.com/speed.r

The snapshot may have been done with a slightly different version. 
I play with the colours.

Console:   0:00:12.979 - 39 KC/S
Processor: 0:00:00.801 - 1078 RHz (REBOL-Hertz)
Memory:    0:00:02.023 - 23 MB/S
Disk/File: 0:00:00.991 - 30 MB/S

I get around 760 RHz

which terminal program do you use?

So, makes sence.

I get 345 on the mac

The standard Terminal incl. in MacOSX

same here

but...

Maybe you have some background program running on the mac stealing 
CPU?

I get 222 kc/s in the OSX console, where the Windows console only 
gives 39 kc/s

Computers are strange and difficult to compare. :)

there is something that massively slows down the console under windows. 
I get the same slowness under View with most programs.

testing the same programs under slower PC's yield better results 
than this one

strangly it seems I'm the only one with this problem. I've talked 
a lot about how slow SHOW is, but it seems to be unique to this PC

I use SHOW in the voxel program.

it's not really visible on small windows, but fullscreen stuff is 
at least 10-25 times slower

Maybe some bottleneck somewhere.

I get 13-15 fps on the mac

what graphics card does your mac have?

ATI 32MB AGP, chipset: ATY,RV280M9+ (It's an iBook).

mac mini here... seems to be close to the same specs

ATI Mobility Radeon 9200

same

it's probably the modem. for some reason it constantly eats 25% cpu

Hey, that's cool. I get 33.3 FPS.

Console:   0:00:01.082 - 467 KC/S
Processor: 0:00:00.501 - 1724 RHz (REBOL-Hertz)
Memory:    0:00:01.091 - 43 MB/S
Disk/File: 0:00:00.471 - 64 MB/S

:-)

To new readers:

We're testing this Voxel Landscape script, I've made in rebcode: 
http://home.tiscali.dk/john.niclasen/voxel/NicomVoxel.r

Too see what it is, screengrab is here: http://home.tiscali.dk/john.niclasen/voxel/snapshot.png

You need View 1.3.50 to run it:
Windows: http://www.rebol.net/builds/031/rebview1350031.exe
Mac OSX: http://www.rebol.net/builds/024/rebview1350024.tar.gz
Linux: http://www.rebol.net/builds/042/rebview1350042.tar.gz

Use w, s, a and d to move around.

Q to quit and F1 to save snapshot.png

Nice job, John!


I have played with it a bit : the keys were not friendly for Azerty 
keyboards ;-)
And I wanted it to fly without "Control".


So the same things, but use Arrows to increase/decrease speed in 
both directions.
do http://membres.lycos.fr/didec/rebol/NicomVoxel.r


You can also try page up/down to change the view altitude, but rebcode 
part is not fully ready for that (can give error if you go too far).

:-) Unfortunately it doesn't work in MacOS, because of missing timers 
(rate).

DideC, I just tried your version on my PC. It's cool! :-) Ok flying 
experience, and the elevation is fun too. But code is not completely 
ready for that, as you point out.

Not bad. I got around 22 fps on P3  933MHz

I've got 22fps too on P4/2GHz

:-) strange, on so much powerfull machine ... maybe it is because 
of View slow refresh ....

I get 25fps on my 1Ghz PIII, but the script use "rate 30" so don't 
expect it to go to high in frame rate ;-)

To clarify: my original script only update the window, when moving 
around, so fps can only be measured when holding a move key. DideC's 
version use RATE, so it continuously update the window. Using RATE 
doesn't work with View 1.3.50 under MacOS (I don't know about the 
Linux version).

note that rate doesn't go past around 20/s on windows.

I can get up to 48Hz on WinXP.

Anton, with my original version or DideC's version using RATE?

I think there's confusion there between face/rate and the fps reported 
by your program. I think I have switched to talking about face/rate 
while everybody else is still talking about your program. I thought 
that Gabriele was probably talking about face/rate. Now I'm not so 
sure :)

Anton, I read it the same way as you did then. If Gabriele mean, 
using face/rate can only produce 20 ticks pr. second, then you've 
proven him wrong, yes. :-)

I think Gabriele might be remembering the number 20 milliseconds, 
which is close to the time interval given by 48Hz.

i remember not going much past 20 ticks per second on my machines, 
but i don't recall if i was measuring rate alone (probably not)

i also think others had similar results... but, if it's 48hz, then 
that's better :)

btw, Gabriele - I hope rebcode is part of rebol 3 big picture?

What about some security issues Brian pointed to earlier?

it will certainly be if the security issues are solved in time (i 
think we can do it for beta, but it might be delayed to final)