WinUAE Voodoo 3 emulation testing

[Mad-Matt]

There is the Variable "Mediator/VoodooMemOS" to enable/disable mapping vram as system memory. I prefer it off for the sake of potentially better compatibility. Not to mention that it must be slower in the real world to have vram over Z2 as apposed to directly on the cpu card.

[AC/DC HACKER!]

When I load WinUAE, select Quickstart A4000 + CSPPC.. Set config, then go to RAM/Memory Settings & and I see Chip is at 2 MB but advanced memory settings shows Chip RAM at 1 MB. If I move either slider attempting to go to 8 MB..let say, and let go, neither will stay at 8.

[Toni Wilen]

Experimental feature: allow direct VRAM access if current graphics mode is little-endian compatible. 8-bit mode and any mode that includes "PC" or "BGR" or "BGRA".

Should increase speed especially in m68k JIT/PPC modes but it might also break 3D support.

Checkbox option in Expansion panel (Graphics boards -> Voodoo. Ignore ROM setting, it does nothing). Log also shows when VRAM mode is indirect vs direct. Most likely only works with Mediator in Z3 mode because it has 1:1 Amiga/PCI side mapping.

[White]

currently with voodoo driver some artifacts remain when moving windows.
this does not happen with the picassoIV driver even having only 4mb of memory with the 4.1.
Will it be corrected later?
Thanks

[Mad-Matt]

It's important to note that the same random corruption happens on real hardware as well (odd random squares appearing, icons vanishing and sometimes text doubling) using med/voodoo3 combo so in that sense the emulation is accurate.

[White]

then I really have no words
but who bought this card kept the amiga computer in this way?

"only amiga makes its possible"

[White]

If it can be useful, the problem is solved by using themes that use datatypes and the problem disappears.
the menus remain slightly delayed, but I have to see better
this is an important aspect if used with 4.1 otherwise it becomes impossible to work with a default workbench

[Zarnal]

Has anyone managed to run Warp 3d demo "Engine" as well as Wipeout (in 68K hardware mode) with a 3.1 workbench / kickstart.

Here are the problems :

"No mode ID" issue with "Engine".

For WipeOut, I click on "Select mode ID" and nothing happens.

An idea ? Thank you.

Original Mediator + update 2.6
Warpos 3D elbox version 4.2.
Voodoo.card 4.35.
PCI.library v 13.10.
Picasso96API v 2.34 (I also tried with P96 aminet version ).
Rtg.library 41.38 ( I also tried with P96 aminet version ).

[Toni Wilen]

It expects some specific resolution/depth combination and you don't have it configured? (Picasso96Mode)

[Mad-Matt]

Engine doesnt like Voodoo for unknown reasons and doesnt work on my real Amiga either (med/voodoo3). On Permedia2 Engine normaly asks what mode you want to use 15/16/24 and runs on whatever is selected. It works on an emulated CVision3D 15bit screen as well. Not working on Emulated Voodoo with cgx or p96.

My thoughts are that it does something very specific for Warp3D v2/v3 and there is no v3 HW driver for Voodoo. Likely similar reason why early StormMesa demos dont run on Voodoo either. with Permedia2 you can force Warp3D v4 to fall back on Warp3Dv3 compatability (although sometimes you really need to drop the v3 hardware driver back in).

Wipeout Wont work in 68k as its a ppc game!!

[Zarnal]

Originally Posted by Toni Wilen

It expects some specific resolution/depth combination and you don't have it configured? (Picasso96Mode)

I'll recheck all my P96 modes and read the documentation again. Thanks.

[Zarnal]

Originally Posted by Mad-Matt

Engine doesnt like Voodoo for unknown reasons and doesnt work on my real Amiga either (med/voodoo3). On Permedia2 Engine normaly asks what mode you want to use 15/16/24 and runs on whatever is selected. It works on an emulated CVision3D 15bit screen as well. Not working on Emulated Voodoo with cgx or p96.

My thoughts are that it does something very specific for Warp3D v2/v3 and there is no v3 HW driver for Voodoo. Likely similar reason why early StormMesa demos dont run on Voodoo either. with Permedia2 you can force Warp3D v4 to fall back on Warp3Dv3 compatability (although sometimes you really need to drop the v3 hardware driver back in).

Wipeout Wont work in 68k as its a ppc game!!

Thank you very much for these detailed explanations. Yes, for WipeOut I made an unfortunate mistake talking about 68K. But the question remains the same (but in PPC).



Did you successfully launch Wipeout with OS 3.1 in PPC mode and full screen ?

[Mad-Matt]

Wipeout works fine in 3.1 and fullscreen using A4000/Grex/Voodo combination.

A4000/Mediator/Voodoo works in fullscreen, but it runs too slowly to enjoy. (Likely due to issue with gfx base address and ppc - causing huge slowdown)

EDIT: A1200/Grex/Voodoo is working fullscreen but speed is erratic. 603ppc emulation is notably slower in general though.
A1200/Mediator/Voodoo3 is a little better, but not by much. (although winuae could hardcrash after the title screen)

[Zarnal]

Originally Posted by Mad-Matt

Wipeout works fine in 3.1 and fullscreen using A4000/Grex/Voodo combination.

A4000/Mediator/Voodoo works in fullscreen, but it runs too slowly to enjoy. (Likely due to issue with gfx base address and ppc - causing huge slowdown)

EDIT: A1200/Grex/Voodoo is working fullscreen but speed is erratic. 603ppc emulation is notably slower in general though.
A1200/Mediator/Voodoo3 is a little better, but not by much. (although winuae could hardcrash after the title screen)

Same thing with a real machine or it's emulation related ?


I did some tests and it is indeed very slow ( my actual PC is too old ).

I have found what was wrong with my full screen issue.

It's in fact an environment variable which was not present in Prefs / Env-Archive / Mediator : Warp3D = YES.

I will be doing some tests later with Grex and OS3.1. For now, I'm going back to do some tests on OS4.

[Zarnal]

What name should I put for the " board " tooltype with CGXMODE grex ( OS 3.1/A1200 ) after install ? "Voodoo" is useless. Thank you.

[Mad-Matt]

I'll give you a hint. It has to match the driver name.

[Zarnal]

Originally Posted by Mad-Matt

I'll give you a hint. It has to match the driver name.

I have another hint for myself : don't forget to replace with correct 68040.library... All is ok now.

[Zarnal]

I have another issue with GREX+OS 3.1 : when i select an resolution, I have the image of the Voodoo 3 but cannot open any directory or launch a file. After a few seconds everything freezes. I have tested many mode/settings and always same issue.

OS 3.1 fresh installation.
Specific grex drivers/libs.
Cyberstorm PPC 040.

PCI Scan ( pic 1 )
ShowGxConfig ( pic 2 )
CGXmode settings ( exemple, pic 3 )
Test is Ok ( pic 4 )
Saving ( pic 5 )
Voodoo mode 640*480*16 and freeze ( pic 6 ).

[Mad-Matt]

Disable Jit.

[Zarnal]

Thanks. I will try.