Driver for test Cybervision64 3D under WinUAE

[White]

@Zilog
thanks so i try better cgx because i encounter some problems.
thanks also for the picasso settings
while with picasso in practice almost everything works apart
gears68k small
gears68k window
gears_68k

I also tried the ppc works the games start but they are extremely slow
i had tried this long ago without CVision3D support

I need to configure the system better
this topic helped me a lot, thanks again

[White]

I tried quake 2 with the JIT activated the executable of quake 2 is RTG I think it's the right one.
I have no idea :-)
[ Show youtube player ]

[Mad-Matt]

Just to throw it out there, Hardware Overlay is working for video playback. This allows a lowres workbench (256c color in this case) with truecolour video on the same screen as well as some video decode acceleration. Very useful on my BVision setup for mpg and vcd playback.

[Seiya]

@White
well, Quake2 run ok. at me Quake2 with Cybervision64/3D guru

[abu_the_monkey]

@White,

after testing on real hardware, try adding the following tooltype in the icon info for 'gears68k small' and 'gears68k window'

STACK=100000

gears_68k just crashes no matter what on the A1200 with CV64/3d

br

I have just tried this in WinUAE and it seems to work also. probably a MiniGL bug.

[AC/DC HACKER!]

With Beta 8 I can now see what you've seen Mad-Matt, Wipeout 2097, Payback WOS, and so on. Albeit...very slow. CGX4 for now.

[White]

@Seiya
i tried picasso 2.0 drivers the result is the same
everything works.
while instead I encounter problems with the cgx drivers I have to try again.
@abu_the_monkey
thanks for the tip i increased the stack the result still looks random

@Toni
now gear 68k small is running with JIT activated
is there a way to save the session to give you a log or dump of this session in progress?
here the video
thanks, the session is currently in progress
[ Show youtube player ]

[Seiya]

Wipeout 2097 working good also with Picasso96. i notice a thing. i put in 320x200 and initially very slow, but in some moment became very fluid and then strangely slow down again at few frame per seconds. Of course with JIT.
Later i made a video

[White]

@Seiya
You can make a video with the settings
Is your configuration currently with ppc or without?
thanks

[Seiya]

https://fb.watch/1x3lsiIcph/

i forget to say config:
Blizzard PPC A1200, 128 MB, Picasso 96 2.0 and Virge on Zorro II (like original because Zorro III was only on A3000/4000). Here i have also installed WarpOS 5.1

Later i build a new config with A4000 Zorro III

[White]

@Seiya
thanks for the video to me it doesn't open the requester to choose CVision3D while instead
freespace for example works but they are ppc games
I am confused long ago I had emulated a 68k ppc system but it was slow.
But is it right to try or now with the new winuae is there support for powerpc 68k?

[Seiya]

now i tried to make new system from scratch with A4000 and Cyberstorum PPC. i setup 128 MB on Cyberstorm, i installed Cybervision64/3D Zorro III board, i installed Warp3D, but now i have RAMlib error on every application.
Also for BlizzardPPC sometimes i notice that driver not always are really installed. after 2 or 3 tries is ok.

Edit
With A4000 setup and CyberstormPPC i have ramlib in any Warp3D games and demos

[White]

@Seiya
Some time ago I had made the ppc-68k work for example "shogo"
I don't remember the exact steps but it had to do with "terminator" in warpos "
and used "rewarp" (maybe)
but I don't want to give you wrong suggestions.
at the moment everything works with the 68k + cvision3d / 64
except gear 68k that sometimes start and sometimes don't
and quake 3 wrong textures part but seems slow.
If you need 68k + ppc I can try again to configure everything if supported by winuae.
for example fpse 68k works by selecting cvision3d / 64 but I don't know the advantages.
I have to try the other applications.
Everything works with JIT enabled

I sent you a pm

[Seiya]

my A1200 BlizzardPPC emulation working good both ppc side both 68k side.
A4000 setup with CyberstormPPC not working. ramlib crash

[White]

here the video of shogo and quake with 68k + ppc
[ Show youtube player ]

[AC/DC HACKER!]

@ White

To exit Shogo, instead of going down the list to exit when the selection is at the top, tap up and you'll see it moves to Quit. Cycling through the menu to the end isn't needed.

@ Seiya

To pick a screen mode just double-click it. You don't have to select it then click OK. For Kickstart 3.x.

Using my original "complex OS 3.5" and Picasso96 2.0 with "Grant Direct Access" disabled with CVision3D Wipeout 2097 does load "quicker" than CGX4+last update. I'm checking with JIT first. CyberStormPPC/060. It's funny to hear the voice sounding sort of like Max Headroom a bit with the stuttering.

Edit: Corrected message.

Update: With JIT in/direct the speed seems about the same. Slow, not at all playable, but I see smooth video vs what Seiya recorded. I haven't seen any video glitches with WipEout. Currently using Indirect and sound has pauses or delays but video...when moving is clean. I ran Payback WOS to CV/633D menu and it loaded about as fast as WipEout does...but the menu selection was quicker than with CGX4+last update. Again Picasso96 2.0. It's sweet to see the progress. Furthermore, I didn't reinstall Windows or reinstall WinUAE. It's all because of "Public Beta Beta 8".

[White]

@Seiya
@AC/DC HACKER!
reviewing the video it occurred to me that I used the phase 5 cd if I'm not mistaken.
I had an i5 as a processor so I guess I'll have to redo all the installation to get 68k + ppc again and it should be fast.
but if it's not supported I don't know if it's worth it

[White]

@AC/DC HACKER!
I am not understanding but now the JIT can be used together with the PPc + 68k?

[Zilog]

Originally Posted by White

@AC/DC HACKER!
I am not understanding but now the JIT can be used together with the PPc + 68k?

The JIT influence 68k ,but more speed 68k, more speed access ram, device,ecc ...and more speed pcc.

[White]

@Zilog
thanks, now I try again the video dates back to 2 years ago
then I had abandoned the configuration
the 4.1FE was much more practical, but if something has improved I like to experiment :-)