Mesa OpenGL 68k RTG

[NovaCoder]

Originally Posted by arti

Nice, looking forward for it.

If you would enable fps counter in gears demo using your Mesa code we could compare performance.

Yep okay, should be easy to do.

Update:

Here you go, please compare this to the old 68k Mesa and your GLUT approach.

The attached it as optimized as I can get it without introducing glitches, it runs at 12 fps for me on WinUAE (old laptop), with glitches I can get that up to 17 fps.

For a fair comparison, make sure that you use 640x480 and 16 bit color depth (full screen).

I've attached the source code that made the demo (basically standard Gears code without GLUT).

Actually, let me try and get those optermization flags working without causing the glitches...

okay, now uploaded an optermized version without glitches.

[arti]

I can't get fullscreen in glut so I compiled SDL version.

Your code 97 fps,
SDL version 367 fps.

Tested on WinUAE with Wazp.

I assume that AmigaMesa is optimised a lot for 68k.

sdlgears.lha

[alexh]

I was of the understanding that Wazp in WinUAE will render outside the emulated 68k environment?

[NovaCoder]

Originally Posted by alexh

I was of the understanding that Wazp in WinUAE will render outside the emulated 68k environment?

Yep you have to be careful and compare like to like, mine is pure software rendering (no hardware acceleration in winuae including Wazp3D)

[arti]

Yeah, I forgot that you are testing Mesa 4.1 in software.
Maybe someone can test as I'll be home later in the evening today.

It would be interesting if it works with Wipeout. I've already tried TinyGL and PortableGL software renders without luck.

[jeff b00toNic]

Interesting, I also get 120 frames in 9.630 seconds at 12.461 FPS on my Amiga.
Could it be that your laptop is as fast as a PiStorm with an RPi 4 at standard clock speed, or is the speed perhaps limited?

[NovaCoder]

Originally Posted by jeff b00toNic

Interesting, I also get 120 frames in 9.630 seconds at 12.461 FPS on my Amiga.
Could it be that your laptop is as fast as a PiStorm with an RPi 4 at standard clock speed, or is the speed perhaps limited?

Yep interesting, I think that's just a coincidence though. It shouldn't be limited (only by the refresh rate)

[NovaCoder]

Originally Posted by arti

Yeah, I forgot that you are testing Mesa 4.1 in software.
Maybe someone can test as I'll be home later in the evening today.

It would be interesting if it works with Wipeout. I've already tried TinyGL and PortableGL software renders without luck.

No worries, thanks for trying

[jeff b00toNic]

Originally Posted by arti

Maybe someone can test as I'll be home later in the evening today.

With your version, I get 158 frames in 5.015 seconds, at 31.5055 FPS.

[klx300r]

with my PiStorm32-3A+

@ NovaCoder

120 frames in 14.476 seconds=8.290 FPS

@ arti

103 frames in 5.018 seconds=20.5261 FPS

[arti]

Originally Posted by klx300r

with my PiStorm32-3A+

@ NovaCoder

120 frames in 14.476 seconds=8.290 FPS

@ arti

103 frames in 5.018 seconds=20.5261 FPS

Is that with paraj warp3d.library? If so my version will be faster because it's partially accelerated by Pi's GPU.

[klx300r]

Originally Posted by arti

Is that with paraj warp3d.library? If so my version will be faster because it's partially accelerated by Pi's GPU.

ah cool where can I get your warp3d.library

[arti]

It was made by paraj from Pistorm discord channel.

Warp3D.zip

Tested this time on Pistorm with Wazp
Nova 8fps
SDL 12fps (with paraj library = 34 fps)

It needs 32bit depth in code.

sdlgears-32bit.zip

[NovaCoder]

Originally Posted by arti

It was made by paraj from Pistorm discord channel.

Attachment 82632

Tested this time on Pistorm with Wazp
Nova 8fps
SDL 12fps (with paraj library = 34 fps)

It needs 32bit depth in code.

Attachment 82633

I didn't know that piStorm already had hardware acceleration available, that means there isn't much point in a pure software implementation of Mesa I guess.

[arti]

Originally Posted by NovaCoder

I didn't know that piStorm already had hardware acceleration available, that means there isn't much point in a pure software implementation of Mesa.

That's not even full hardware acceleration. Game still runs in software mode but uses Pi GPU at some point.

It's interesting that the old Mesa you used for SDL is faster than mine, maybe it's using assembler (mine is just standard C code).

Yeah, most likely. Enhancing Amiga Mesa code with newer versions of Mesa would make more sense I guess.

BTW PortableGL which is OpenGL 3.3 ish gives also 8 fps.

[klx300r]

@ arti

with warpd3d.library and sdlgears-32bit

88 frames in 5.026 seconds=17.509 FPS

[tomcat666]

Pistorm32 CM4 2.2Ghz (no HW accel whatsoever, so Wazp3d I guess):

Nova 17.693 fps (runs full screen)
sdlgears 42.8458 fps (runs full screen)
sdlgears-32bit 40.3274 fps (runs in a window)

All have correct colours

[arti]

Originally Posted by klx300r

@ arti

with warp3d.library and sdlgears-32bit

88 frames in 5.026 seconds=17.509 FPS

Should be faster not slower. Have you renamed it to warp3d.library?

[Dunny]

Originally Posted by NovaCoder

I didn't know that piStorm already had hardware acceleration available, that means there isn't much point in a pure software implementation of Mesa I guess.

PiStorm doesn't have hardware acceleration. That's a test that only runs on a specific model of Pi, intended to see if it can be done and uses the Pi's shader processor to hand off some of the load from the 68k.

It's not being developed further and is a dead end tech-wise. There is currently no full Pi OpenGL (or otherwise) hardware solution actively in development.

[klx300r]

Originally Posted by arti

Should be faster not slower. Have you renamed it to warp3d.library?

Yes I did. Is the lib specific to the Pi4B models maybe?