WinUAE Voodoo 3 emulation testing

[Seiya]

[White]

I had to complete the windows 10 update in all its parts after the new computer arrived.

what is the latest beta available for voodoo? (beta12 2020 12.17)
thanks

[Toni Wilen]

One more update before official beta:

Framebuffer access is now fully indirect, including byteswapping, fixes wrong colors in RGB modes and possibly allows 3D to work. (Note: I ignore any 3D problem unless same config is confirmed working on real hardware!). This probably reduces speed but compatibility comes first. Direct access for compatible modes can be added later.

[White]

Thanks I will do other tests on the 68k side

I just wanted to add:
I tried 4.1FE on the fly it works again and all resolutions are now supported 16-24-32bit with the right colors.
The Odyssey browser also works well with the right colors
many applications are supported such as mplayer (also works with opengl I don't know if this is important) the colors are right but this is the 2D part but to be a prebeta now it is very fast.

Maybe it's not specific to 4.1FE but it works fine
I have to try a clean install with warp3d out of curiosity
Thanks.

[Toni Wilen]

Reupload. It wasn't fully indirect, now pcem access functions are properly called and texture writes etc should also work.

EDIT: Voodoo 3 has JIT filtering/blending which is not yet enabled and won't be until someone proves hw accelerated 3d works

[AC/DC HACKER!]

Oh, okay, I'll redownload. Ahhh! That fixed some 2D screen problems I noticed from the "bad" upload. Now to test a bit more.

[AC/DC HACKER!]

Hardware isn't yet functional here. I've tried Payback 68K.. The prefs will allow enabling Hardware but a requester won't show to pick a screen. 2D (software) screens look decent, with a couple "hesitations"..I'll record a log soon.

[Toni Wilen]

Not being able to select screenmode rarely depends on hardware. You really sure everything required is installed?

[AC/DC HACKER!]

I've looked a SnoopDOS...and it LOOKS good...but I'm checking into it. That's my wonderment also. I'm new to Mediator and Vooodoo, so I'm checking for what I missed.

[Mad-Matt]

Warp3D not quite their yet. Sticking with Warptest, the programe runs but shows no texture. But its a start! just like when CVision3D support was starting out.

[AC/DC HACKER!]

I didn't notice that Mediator has an update to Warp3D. Screen modes are selectable, but..I get a grey screen for Payback 68K/PPC hardware. I get correct screens for 2D, both Payback versions. Wipeout, won't display in Window on Workbench, doesn't matter what screen.. 3D not supported. Expected that, from 16-Bit and 32-Bit. However, picking a Screen mode, that shows...2 splash images show, but the "game" or interactive screens are black.

Progress! Whoohoo!

[Toni Wilen]

Hardware driver available
Available drivers:
S3 ViRGE
        Supports format 0x1B
        Hardware Driver
        Primitives supported:
        [POINT] [LINE] [TRIANGLE] 
        Filtering:
        [BI-FILTER] [MM-FILTER] 
Permedia2
        Supports format 0x79FF
        Hardware Driver
        Primitives supported:
        [POINT] [LINE] [TRIANGLE] 
        Filtering:
        [BI-FILTER] 
Voodoo 3 Avenger
        Supports format 0x80
        Hardware Driver
        Primitives supported:

        Filtering:

Voodoo 3 Avenger
        Supports format 0x20
        Hardware Driver
        Primitives supported:

        Filtering:



Error: No ModeID found
Closing down...

Really useful error. Mode this program wanted apparently must not be mentioned in public. (at least all 640x480 modes exist)

[Toni Wilen]

There is something strange going on with Mediator 1200.

Driver properly sets window address pointing to start of BIOS ROM when it reads it but when it tries to write in VRAM bank window gets set to beginning of PCI space (first PCI BAR which contains IO stuff) when it should be set to second PCI BAR which points to VRAM.

Anyone have Mediator 1200 + Voodoo 3 + latest driver (MM_CD_UP2.6.lha) and Voodoo working correctly?

[White]

to install warp3D with 4.1FE in this step what should I select?
CyberGraphX V3 / V4
or both
thanks

[Toni Wilen]

Originally Posted by White

to install warp3D with 4.1FE in this step what should I select?
CyberGraphX V3 / V4
or both
thanks

I don't think this is really on topic here but sounds like you are installing non-OS4.x Warp3D because OS4.x has Picasso96 built-in.

[Mad-Matt]

I can pull my Amiga 1200 to bits and setup a med+voodoo3 if it can help development (I have the original 4 slot version with updated mach chips for mmcd). I never really liked it as its a slower setup than the BVision and it was a pain to setup. You don't realize how useful the built in aga mode promotion is until its gone

or maybe best to see if someone shows up with a working setup already.

@white Also you dont need to install warp3d in os4 as its build in!

[Toni Wilen]

Originally Posted by Mad-Matt

Warp3D not quite their yet. Sticking with Warptest, the programe runs but shows no texture. But its a start! just like when CVision3D support was starting out.

Assuming warptest starts in your config, what mode does it want? What does the mode requester list?

Originally Posted by Mad-Matt

I can pull my Amiga 1200 to bits and setup a med+voodoo3 if it can help development (I have the original 4 slot version with updated mach chips for mmcd). I never really liked it as its a slower setup than the BVision and it was a pain to setup. You don't realize how useful the built in aga mode promotion is until its gone

or maybe best to see if someone shows up with a working setup already.

At least pciinfo output would be nice to have.

[White]

@Toni
I apologize for the request the system is configured for voodoo3
warp3D 4.2a was downloaded from the hyperion site
i have never used warp3D with 4.1FE i don't want to get wrong version to install

which version of warp3D should be installed in 4.1FE
thanks

[White]

@ Mad-Matt
thanks I have only read now

[abu_the_monkey]

Originally Posted by Toni Wilen

Hardware driver available
Available drivers:
S3 ViRGE
        Supports format 0x1B
        Hardware Driver
        Primitives supported:
        [POINT] [LINE] [TRIANGLE] 
        Filtering:
        [BI-FILTER] [MM-FILTER] 
Permedia2
        Supports format 0x79FF
        Hardware Driver
        Primitives supported:
        [POINT] [LINE] [TRIANGLE] 
        Filtering:
        [BI-FILTER] 
Voodoo 3 Avenger
        Supports format 0x80
        Hardware Driver
        Primitives supported:

        Filtering:

Voodoo 3 Avenger
        Supports format 0x20
        Hardware Driver
        Primitives supported:

        Filtering:



Error: No ModeID found
Closing down...

Really useful error. Mode this program wanted apparently must not be mentioned in public. (at least all 640x480 modes exist)

are you sure you have the correct driver 'W3D_Picasso96.Library' in Libs/Warp3D/GFXdrivers?
I get that error when i use the standard warp3d version but it works when using the elbox version.
they are both v4.2 so the only way to check is the size

standard warp3d v4.2 = 38664 bytes
elbox mediator v4.2 = 39216 bytes

the first 2 pics are with the elbox version and the last is with the standard version

br