WinUAE 3.4.0 beta series

[mark_k]

Originally Posted by Toni Wilen

- Added network led (N). red=transmit, green=receive. yellow=both in last 1 second or so.

That doesn't seem to be present in the on-screen display? It is on the status bar at the bottom of the window.

I may as well give a little LED-related suggestion which isn't beta-specific here: hide indicators for hardware which isn't present. So e.g. a plain A500 config would have no HD, CD or N text in the status bar/OSD. You could also hide the green boxes for not-present floppy drives in the OSD (they're already hidden in the status bar).

[Snake79]

I confirm that SB128 is working again and Cow3D demo using Wazp3D also without issues Thanks!

[psykicko]

Originally Posted by Toni Wilen

I can't duplicate. Difference must be either in CSPPC flash rom menu settings or your boot media.

Does switching off JIT make any difference? Removal of all harddrives except boot drive?

If i disable my work partition then it loads os4 fine.

I got the same result with beta2. No change there. Also with winuae.7z

[michaljarz]

AMIGASYSTEM, Snake79 - what are your configurations?
I'm still trying to run Wazp3D in 3.4.0.

My config:
Win XP x86 SP3
Kick 3.1 + Workbench 3.1
CPU: 68040, JIT (on or off) FPU CPU internal + More compatible, Fastest possible
Chipset: AGA, Immediate Blitter, Chipset Extra - Generic
ROM: Board type - original UAE
RAM: chip 2mb, z3 fast 32mb, z3 mapping - automatic
Harddrive: directory
RTG board: UAE Zorro III, 8mb, +hardware vertical blank interrupt, other default settings
Hardware info: attached

[AMIGASYSTEM]

Originally Posted by michaljarz

AMIGASYSTEM, Snake79 - what are your configurations?
I'm still trying to run Wazp3D in 3.4.0.

To me of OS3 (AFA OS) and OS4.1 everything works well with WinUAE 3.4.0, These steps I did:

- Warzp3D.library -> It goes Renamed as "Warp3D.library" and copied to Libs
- soft3d.library -> copy Libs
- soft3d.dll -> copy WinUAE Directory


My video showing the operation on two OS on WinUAE 3.4.0

[ Show youtube player ]

[michaljarz]

I did copied Wazp3D.library-winuae to libs:Warp3D.library
(EDIT: I improved a little bit, because I think badly written)

[Snake79]

Hi there michaljarz. I think AMIGASYSTEM has a point. In my case i was using Wazp3D in OS41FE (where things are simpler / different), not WB31. Remember that uppercase are important when you copy / rename files in AmigaOS (how teach readme file of Wazp3D). Good luck! and avoid to do offtopic (it's beta series and not necessarily Wazp3D topic, but you can start one)

[michaljarz]

When I use "Wazp3D.library-full" then work, but this version is slow on my computer (2fps). "Wazp3D.library-winuae" is much faster: 30fps software & 60fps hard rendering, but this version doesn't work for me on 3.4.0 beta.

[AMIGASYSTEM]

Originally Posted by Snake79

Remember that uppercase are important when you copy / rename files in AmigaOS (how teach readme file of Wazp3D).

Yet it is strange, It happened several times to rename libraries changing lower/upper case and libraries have always worked, perhaps this happens in special libraries? I tried renaming of OS3 (AFA OS) the Warp3D libraries and everything worked normally.

[thellier]

>Remember that uppercase are important
I dont remenber why I wrote that in the readme a long time ago but it seems to be false...
The problem seems to be with soft3d.dll that do (despite his name...) the hardware rendering the x86 side
I will have a look to this latest WinUAE+Wazp3D

Alain Thellier - Wazp3D

[AMIGASYSTEM]

Cio Toni, I was testing Duke Nukem 3D and I found that with v3.4.0 Beta 1 graphics does not look good, with v3.4.0 Beta 2 even worse, while with v3.3.0 the Duke Nukem 3D graphics you see perfect, resolution used 800x600 8bit. Else after doing tests with Duke Nukem 3D, WinUAE WinUAE occasionally crashes, i attach files .dmp and screenshot.
No problem with PAL resolutions with v3.4.0 Beta 2

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Cio Toni, I was testing Duke Nukem 3D and I found that with v3.4.0 Beta 1 graphics does not look good, with v3.4.0 Beta 2 even worse, while with v3.3.0 the Duke Nukem 3D graphics you see perfect, resolution used 800x600 8bit. Else after doing tests with Duke Nukem 3D, WinUAE WinUAE occasionally crashes, i attach files .dmp and screenshot.
No problem with PAL resolutions with v3.4.0 Beta 2

"Required information missing error!" (logging was disabled: no log in dump file either!)

EDIT: and as usual: dump files from non-official betas are still as useless as ever.

Also I am not so sure it is emulation problem only, 256 color palette screen + game that needs 256 unique colors in a window? That can't really work very well.

[AMIGASYSTEM]

Ciao Toni, the error after a while 'vanishes and is gone now, the error comes only if've been toying around on graphics resolutions of Duke Nukem 3D. I did not understand the last things you wrote, attaching video made some time ago with Duke Nukem 3D, now with AFA OS v3.3.0 and is much faster.

[ Show youtube player ]

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Ciao Toni, the error after a while 'vanishes and is gone now, the error comes only if've been toying around on graphics resolutions of Duke Nukem 3D. I did not understand the last things you wrote, attaching video made some time ago with Duke Nukem 3D, now with AFA OS v3.3.0 and is much faster.

So does it work or not? Always triple test everything! It is too easy to do tests differently.

btw, stop posting useless videos in this thread. I don't watch videos. Signal to noise ratio is 0.1% in videos. (In this case "it works" equals the video!)
EDIT: Especially now when they auto open. It can't get any more annoying.

[Toni Wilen]

Originally Posted by mark_k

That doesn't seem to be present in the on-screen display? It is on the status bar at the bottom of the window.

It was a bug.

I may as well give a little LED-related suggestion which isn't beta-specific here: hide indicators for hardware which isn't present. So e.g. a plain A500 config would have no HD, CD or N text in the status bar/OSD. You could also hide the green boxes for not-present floppy drives in the OSD (they're already hidden in the status bar).

Yes, it makes sense but it isn't that simple. It needs complete rewrite. Maybe someday..

[AMIGASYSTEM]

Toni if the videos do not need I can delete them, I just wanted to show that with previous versions of WinUAE Duke Nukem 3D you can clearly see, while with all the v3.4.0 the graphics you see badly.

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Toni if the videos do not need I can delete them, I just wanted to show that with previous versions of WinUAE Duke Nukem 3D you can clearly see, while with all the v3.4.0 the graphics you see badly.

There was nothing clear in your post.. Again: Still no config, no logs, no nothing..

[AMIGASYSTEM]

Excuse me Toni I did not realize you wanted to see Config and Log

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Excuse me Toni I did not realize you wanted to see Config and Log

They are always needed

Does same happen if you switch off JIT? Or if you enable Direct JIT?

Include log from 3.3.0 too.

[AMIGASYSTEM]

Here Log 3.3.0 tested high resolution (1024x768) and it shows perfectly. JIT without the same you see evil, does not change anything except the slowness.