Driver for test Cybervision64 3D under WinUAE

[Toni Wilen]

Originally Posted by Mad-Matt

What are you doing to enable/disable the texturing?

On startup of WarpTest you should see the Wall texture which you can spin up and resize with the mouse. You can press T to switch between texturing and shading. This is the same as on Permedia 2 so from my point of view it is expected behavior. The only notable issue I have is that the screen flickers. Maybe a refresh issue. The same effect happens with the Engine demo.

As I've mentioned before I'm only testing with CGX4 and don't know how it reacts with P96.

Running warptest in CGX4: 3d image is missing (and only 2D graphics are updated, no access whatsoever to 3D hardware). Press T and image appear in shaded version (and Virge 3D registers are accessed).

So it seems this is CGX software side issue if it works in your CGX4 config.

[Mad-Matt]

As in a previous post these are the important settings for cgx and warp3d :-

CVision3D Monitor Driver:
Bitmapcache=YES
Dragging=NO (something todo with being compatible with v39 multibuffering)
Multimediamem=NO (For Warp3D), Multimediamem=YES is required for anything using cybervirgin.lib. Multimedia mem is what splits the card into 3mb and 1mb texture ram. Warp3d doesnt need this and can manage the whole 4mb.

CybergraphX:
cybergraphx/usesemaphores=1

also for Warp3D 68k&PPC

Env vars:-

Powerpc/gfxaddr=$40000000
Powerpc/force=1

[Toni Wilen]

Thanks.

Dragging=NO was the important bit. Multimediamem=YES or NO don't affect (at least) warptest.

Strange limitation.

[AC/DC HACKER!]

Originally Posted by Mad-Matt

What are you doing to enable/disable the texturing?

On startup of WarpTest you should see the Wall texture which you can spin up and resize with the mouse. You can press T to switch between texturing and shading. This is the same as on Permedia 2 so from my point of view it is expected behavior. The only notable issue I have is that the screen flickers. Maybe a refresh issue. The same effect happens with the Engine demo.

As I've mentioned before I'm only testing with CGX4 and don't know how it reacts with P96.

I wasn't running WarpTest much at all. I was concentrating on the 2 games. I ran WarpTest once in a great while and I got the same results as you...with CGX4. Now I'm only concentrating on demos..and I made simple Workbench 3.1 with Picasso96 2.0 and WarpTest is doing the same as you described. So I'm checking the others now. I got it memorized you're only using CGX4.

[Zilog]

Originally Posted by Mad-Matt

As in a previous post these are the important settings for cgx and warp3d :-

CVision3D Monitor Driver:
Bitmapcache=YES
Dragging=NO (something todo with being compatible with v39 multibuffering)
Multimediamem=NO (For Warp3D), Multimediamem=YES is required for anything using cybervirgin.lib. Multimedia mem is what splits the card into 3mb and 1mb texture ram. Warp3d doesnt need this and can manage the whole 4mb.

CybergraphX:
cybergraphx/usesemaphores=1

also for Warp3D 68k&PPC

Env vars:-

Powerpc/gfxaddr=$40000000
Powerpc/force=1

Great Mad-Matt,
now with this setting CGX and Warp3D , warptest show image.
You run to small-gears-68?


Thanks a lot!

[Zilog]

Originally Posted by Mad-Matt

As in a previous post these are the important settings for cgx and warp3d :-

CVision3D Monitor Driver:
Bitmapcache=YES
Dragging=NO (something todo with being compatible with v39 multibuffering)
Multimediamem=NO (For Warp3D), Multimediamem=YES is required for anything using cybervirgin.lib. Multimedia mem is what splits the card into 3mb and 1mb texture ram. Warp3d doesnt need this and can manage the whole 4mb.

CybergraphX:
cybergraphx/usesemaphores=1

also for Warp3D 68k&PPC

Env vars:-

Powerpc/gfxaddr=$40000000
Powerpc/force=1

Thanks to Mad-Matt's tip,
"Dragging=NO (something todo with being compatible with v3D"
warptest show image wtich CGX+ Warp3D.

Very Thanks Mad-Matt!

Main thread updated.

[Seiya]

Originally Posted by Mad-Matt

As in a previous post these are the important settings for cgx and warp3d :-

ah, now it works. Thanks Mad-Matt
however W3DDemo continue not to working. crash or guru. Other mesa and glut demos working, as Cow3D
Only "Engine" works good and GLSokoban68k works for a while. Strange that Gears 68k not working in window mode (open the window only and Fullscreen version guru 80000003

[Zilog]

Originally Posted by Seiya

ah, now it works. Thanks Mad-Matt
however W3DDemo continue not to working. crash or guru. Other mesa and glut demos working, as Cow3D

Confirm Seya,

i have try a gears small windows 68k and show white windows, but i'am sure Toni still working

[Seiya]

yes, because now we are trying beta version.

[Toni Wilen]

Is there screenshot of gears_m68k_small how it is supposed to look? (It mostly works in CGX4, only texture/coloring seems wrong)

btw, you can enable JIT without direct to get huge speed increase. JIT + direct won't work at the moment.

[Zilog]

Originally Posted by Toni Wilen

Is there screenshot of gears_m68k_small how it is supposed to look? (It mostly works in CGX4, only texture/coloring seems wrong)

btw, you can enable JIT without direct to get huge speed increase. JIT + direct won't work at the moment.

Here,
Picasso96 v2.0 + Warp4.2a + JIT OFF

gears68k.JPG

[Zilog]

Originally Posted by Toni Wilen

Is there screenshot of gears_m68k_small how it is supposed to look? (It mostly works in CGX4, only texture/coloring seems wrong)

btw, you can enable JIT without direct to get huge speed increase. JIT + direct won't work at the moment.

Hi Toni,
JIT indirect speed increase, confirm.

Thanks a lot.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Is there screenshot of gears_m68k_small how it is supposed to look? (It mostly works in CGX4, only texture/coloring seems wrong)

Toni If it can be important:

Cybervision 643D + CGX4 + Wazp3D, gears_68k-window and gears_68k-small work well, gears_68k-fullscreen instead goes to Guru.

Cybervision 643D + Picasso + Wazp3D + JIT InDirect, gears_68k-window, gears_68k-small and gears_68k-fullscreen perfect everything works well

[Mad-Matt]

Why would you use Wazp3d on cv3d lol.

Gears fullscreen is an insta crash with both 68k and ppc. Small and normal work fine and are correct colours on a 15bit wb.

Its an older screenshot, but it still stands.

[AMIGASYSTEM]

Originally Posted by Mad-Matt

Why would you use Wazp3d on cv3d lol.

Because everything works better on WinUAE, i use 68k, PPC does not work well yet, why don't you like Wazp3d?

Gears fullscreen is an insta crash with both 68k and ppc. Small and normal work fine and are correct colours on a 15bit wb.

Gears fullscreen works well if i use Picasso Driver, with CGX4 i have the guru

[Mad-Matt]

Wazp is perfectly find for uae use but why use it when testing for hardware 3d features? Doesnt really make sense to use it for anything other than the uae gfx card with no ram limits.

[AMIGASYSTEM]

I am not using Wazp3d-WinUAE, which among other things does not work with Cybervision 64/3D !!!! but the one that does not use hardware acceleration !!!

[Mad-Matt]

Right , but why would you want to do that? When selecting to emulate a CV3D, we want to be using it with all of its hardware might (or lack of) and run with all its limits intact. Running a software renderer doesn't really test anything and may as well be using any other card. Anyway ill say no more on this as it is not in the spirit of this forum thread.

[Zilog]

Originally Posted by AMIGASYSTEM

I am not using Wazp3d-WinUAE, which among other things does not work with Cybervision 64/3D !!!! but the one that does not use hardware acceleration !!!

AMIGASYSTEM,
I have nothing against the Wazp3D, but i have open this theread only for Warp3D.

You can open another thread with the Wazp3D and the new Jitter if you want.

Thanks a lot.

[AMIGASYSTEM]

Ok i close here with Wazp3D, for my characteristic I always like to get the best, I use WinUAE and I always try to use the best tools to try to get a more beautiful and more performing Amiga.