3D looks slower on my Sam440 with OS41FE

Hello

I have updated my Sam440 to OS41FE
But now when I try some of my 3D progs CoW3D or Microbe3D they seems to be slower

Typically my Aminet/Cow3D-ppc
was giving me 41 fps on my old OS411 and
now it give me 38 fps on OS41FE
so something like 7% slower

I have copied my old envarc to remove all OS411's "nice wb effects" that may use the cpu
Then I have used TaskList to compare the active tasks OS41FE
vs OS411 ==> Removed some stuffs in devs/dosdrivers to be the same

I have desactivated all in wbstartup
I have put back the old Warp3D in libs:
(So warp3D is NOT the slowing thing)
I have compared the startup-sequence

BUUUT whatever I do : on OS41FE i have 38 fps not 41 anymore

Can someone with a dual boot confirm this ???

Alain Thellier

Edit: I have also maded deeper tests with Microbe3D that confirm the same (typically drawing the partygirl.obj was done in 52ms versus 55ms now so 6% slower. This happen in the W3D_DrawArray part)
Edit2: All the tests are maded with the Compositing effect OFF

@thellier

On my x1000 too the Cow is slower on FE than on 4.1.6 (tested on a dual boot system) of around 15% (hum... from 8 fps to 7 fps ) .

@thellier

If you're using Picasso96 functions in your Wasp3D, rewrite your code to use graphics.library direct.
Picasso96 is wrapper for graphics.library, same issue with cybergraphics.
BitmapLocks are slow, use WritePixelArray, and double buffers instead (RAM,VRAM).

@LiveForIt

I think the idea here is to compare the same program on both versions of the OS; increased speed by changing the program is nice but then both OS version would need to be tested with the changed program.

Graphics aren't the only things that have slowed down. It takes twice as long to compile Dopus5 (and other large programs) on FE as it does with OS4Update6.

Just Quick test with IoQuake 3 (Huno R3 version)

AmigaOS 4.1 Update 6

HunoPPC R3 version of IoQuake3 1.36 (Sam440ep Flex 800 Mhz + ATI Radeon 9250, 128 MB, 64 Bit)
640x480 - 21,5/21,9 FPS

AmigaOS 4.1 Final

HunoPPC R3 version of IoQuake3 1.36 (Sam440ep Flex 800 Mhz + ATI Radeon 9250, 128 MB, 64 Bit)
640x480 - 21,1/21,3 FPS

So yes seems a bit slower but acceptable, so just a bit in this specific game, however the entire system are slower for sure, you can see the difference even just moving a normal window around the WB .. not to mention the various freeze in WB (expecially when compositing are enabled)

Probably the new graphics system need some more optimizations, testing and bugfix, atleast to reach again the same results we had before with Update 6 ..

@all
Thanks for answers

@LiveForIt
>If you're using Picasso96 functions in your Wasp3D
I wasnt talking about my WaZp3D but about real WaRp3D usage

In Microbe3D I have made deeper tests: the slowdown dont seems to be in BltBitMapRastPort() or other Picasso96/graphics stuff but rather in the part that call W3D_DrawArray()

@samo79
Did you tested Cow3D too ? because IoQuake3 certainly do lots of things not related to 3D drawing (sound,gameplay, transformations,etc...)

Alain Thellier

@thellier



In Microbe3D I have made deeper tests:

Quote:

Yes thats is a graphics.library funtion so that should not be slow, so thats good.

Picasso96 functions normaly starts with prefix p96#?

Quote:

Should be some new True color functions for Graphics.library.

Like RectFillColor() works simular to p96RectFillColor().

@xenic

Quote:

That might not be possible, there are new stuff that only exists in AmigaOS4.1 Final.

I don't think a new SDK for AmigaOS4.1 fianl has been released yet for general public, maybe I was too fast.

W3D_DrawArray() is a WaRp3D function it draw several 3D triangles that are stored in an array : it is a kind of "Draw a whole 3D mesh" function
(This function rely on gpu bus : Cow object contain 5813 triangles so at 41 fps it need 238 000 triangles/seconde)

Microbe3d use W3D_DrawArray()
Cow3D use W3D_DrawElements() that is a similar function but use indexed triangles

I have also tested to start Cow3D in the Startup-Sequence (after Iprefs) so without the Workbench : It is the same 38 fps

So it is not the Workbench the problem...

Alain Thellier