Here is a link to fire SDL demo which outputs number of fps.

http://aminet.net/demo/intro/fire-0.3b-m68k.lha

I see that people here have a different hardware, so maybe we can get results from P2/A1/060@50MHz/060@75Mhz for comparison.

Please run fire on the 32bit Workbench:

"fire -verbose"

and close the window after about 10 secs.

Wawa, maybe you can run the benchmark under OS 3.9 and OS 4.0? It would be very interesting to see the results.

Under WinUAE I get 250fps.

Link broken if press on it (if copy+paster - works)
On os4.1/peg2 binary itself works if run without params. With -verbose have Grim.

@amistuff
under 3.9: 18 fps (060/50/voodoo3)
under os4.0 it doesnt want to open with -verbose. otherwise it seems to run 2 to 3 times slower than on 3.9. my ppc runs with 150mhz.

i tried it on 3.9/060/picasso4 too. i do not have a 32bit mode there. results are: on 24bit-7fps, on 16bit-16fps
i noticed it causes hits. on my p4 setup it actually even crashes after some time.

@wawa:

Hmm, that's strange because I get no hits/crashes under WinUAE with 8bit/16bit/32bit modes. Anyone else notice crashes under a real Amiga?

BTW. P4 24bit mode seems to be very slow. Could you run again Fire on the 060+Voodoo 3 with 16bit screenmode, so we will see how much Voodoo machine is faster compared to P4?

>i noticed it causes hits. on my p4 setup it actually even crashes >after some time.

what hits you get ?

@bernd_afa:

I reproduced it, but it's not so easy to reproduce.

When you run Fire for some time, next quit it, change screenmode from 32bit to 16bit, run again Fire and quit, change screenmode from 16bit to 8bit, run Fire etc., after some time you will probably get hits too.

the hits only appear when using argument -verbose.
here an example:

and further (quote was too long):

strangely on voodoo on all color depths i always get around 17fps except for 24bit where it is 8fps.
btw. i get always the same hits on all resolutions.

When you get these hits - when you start the demo, while it's playing, at the exit?



Do you see any speed different?


Try this:

"fire_old -verbose"

http://www.filejumbo.com/Download/E99E9DBCDEE47667/


You will get incorrect fps counter.

I got 221 fps here with MorphOS 2.2 on Pegasos II G4.

the first few lines (data:,addr:) appear just from the start, then clicking on sashimi window there eventually appear some lines of stck:
it has just crashed on me as i was going to save the log. the whole rest arrives when closing the demo. i will test the other one in a minute.

edit: fire_old also throws hits in similar manner.

you mean if the slowdown is visible? yes it is. the framerate on 24bit is positively lower. the counter does not lie.

@wawa

What about 16bit vs 32bit speed on the Voodoo? Do you see any visible speed different? Maybe 060 CPU is just too slow to process demo's effects faster.

http://www.filejumbo.com/Download/951C0918FD9031C9/


Here you have 3 binaries which uses software surfaces. Please run them with "-verbose". If it don't work correctly, I don't know where is a problem.

I get no hits as long as I don't change screenmode, but I'm not so sure it is related to Fire demo. I must investigate it longer.

@itix

Thanks for the results. Not bad ;)

BTW. Anyone can confirm hits/crashes/anything under a real Amiga?

difficult to say since all the demos seem to block my cpu load counter or even break them sometimes. all the versions, also the three in fire_test archive, work correctly except for when given -verbose attribute all of them throw the same hits as far i was able to judge. fire_swsurface is the fastest of the test set with ca 13 fps. maybe there is still some underlaying failure in the sdl?

Reproduced.

I see hits ONLY when I disable JIT.

Here is (hopefully) a fixed version. Please test:

http://www.filejumbo.com/Download/D01AF8822BE87605/


You can try to run it under AOS 4.0 if it works correctly with "-verbose" option and after that maybe kas1e will try to run it again.

Good thing is that HWSURFACE speed-ups a bit demo under a real hardware, but this 24bit speed is very slow. This is libSDL-related, so maybe Bernd will try to see why it is so slow (byteswap is need for 24bit=slowdown? I don't know).

i will try in a minute. meanwhile i wanted to correct my previous statement. fire was so slow on os4 probably due to workbench set to 24bit what i have overseen.

edit: working fine with os4. 21fps on 32bit. (604/150mhz)

edit2: working fine under 3.9 17-18fps, no hits. (60/50mhz)

wrong colors under 32bit bgra, but it is related to sld, bernd is already informed and looking into it i suppose. argb is all fine. i suspect 24bit slowdown might be due to sdl too. lets hand it over to bernd.;P

Ok, thanks wawa.

I see fire morphos version on the Aminet ("new" folder). Itix is that you? ;) Don't forget to post results. I want to know how much native version is faster.

Yes I wanted to see what that demo does and ported it to MorphOS ;) I get 375 fps natively. That is roughly 50% increase (the best I got with fire 68k was 245 fps).

24bit packed true colour modes are always slower than 32bit or 16bit modes. It is due to way pixels are processed. 16 or 32 bit datatypes are more efficient than 24 bit ones.

firenew2 test. 68060@75MHz, AmigaOS 3.9 & P96 2.x, Mediator with Voodoo4, 800x600...

32bit BGRA 23 fps
32bit ARGB 22 fps, colors messed up
24bit BGR 10 fps
16bit PC 26 fps
16bit BE 23 fps, colors messed up
15bit PC 24 fps
15bit BE 23 fps, colors messed up
8bit chunky 23 fps, colors messed up

PC=little endian, BE=big endian
Big endian modes are messed up because of a bug in the Mediator Voodoo drivers.
No crashes but I didn't run MuForce as it may slow the results.

>Under WinUAE I get 250fps.

thats slow, i get on a AMD64 3000+ (real 1,8 GHZ) and a gforce 6600 PCIe

what CPU and gfx card you have ?

430 upto 439 fps

I use a 32bit bgra screenmode.

when i use a rgb16 PC screenmode i get 480 upto 485 fps

but the demo use always 8 bit calculation and convert it to your screen resolution.

if you use routines that draw correct in the screendepth, speed can increase more.

with 24 bit i have problem, to test on winuae.i look whats wrong in your mode 11 the video use

but best is for classic systems use not more as 16 bit.

Tested firenew2 -verbose on 32 bit screens:

morphos2.2 / 1ghz / peg2- 225fps
aos4.1 / 1ghz / peg2 - 216fps

@bernd_afa:

I have an older hardware here (Athlon XP 2600+/GeForce 6200), but I don't feel any need for upgrade.

@matthey & kas1e:

Thanks for the results.

@matthey: where are the mediator drivers exactly buggy? if you can nail it, it would be best to forward this info to elbox themselves in order to fix them. i expect they would do it. from my experience they are still quite supprotive despite what the general opinion is. i dont know for what reason, maybe they respect compatriots a little more ;-)

@wawa

I believe the Mediator Voodoo (Voodoo.card?) drivers are buggy. If I remember correctly, the big endian modes used to work until the upgrade before last. I haven't e-mailed Elbox but I did post a message to the Amiga Mediator user group...

http://tech.groups.yahoo.com/group/Amiga-Mediator/

all modes are working correctly on my setup. or do you mean under os4? there i get partly wrong colors on wb, using elbox driver and some glitches sometimes. but then most people use hyperion ones and they work well afair. one day i will revert this too when tweaking my os4 install. i have not given it much attention lately.

>I have an older hardware here (Athlon XP 2600+/GeForce 6200), >but I don't feel any need for upgrade.

my hardwarte is too very old, and from 2600 to 3000 is not much.so i wonder wy your values are much fewer.but it seem AGP or onboard graphic is the reason, but anyway 250fps are too enough.I like the demo run slower.with 60 fps and WAITTOF look nicer ;-)

@bernd_afa:

You can change -width and -height values to bigger, for example 640x480 to slowdown the demo ;)

@bernd_afa & wawa:

Check your mails :)

@wawa

I'm talking about under AmigaOS 3.9. I only have a CSMK3 so no PPC. That's interesting that you don't have the problem. Others on the Mediator user group have the problem as well. Maybe the problem is some kind of software conflict with or outside of the drivers. I'll have to do some experimenting when I have some time.

@matthey: ibrowse has partly wrong colors on32argb but i always thought it a failure of ibrowse. on workbench it is not visible very much, only one pen in the palette seems to be little mispaced. but it is one that is least used, maybe thats why it went unnoticed. i ve only red the thread you pointed to very briefly. you have voodoo4 i understand, which is known for broken support.
i have really to leave for my plane now. we will see into that in 2 weeks. take care

I get 364 fps under WinUAE.
I have Sempron 2600+ / Radeon 9550.

I will run also on Amithlon later, should be nice result.