WinUAE 4.0.0 beta series

[Toni Wilen]

4.0.0 beta series.

3.6.1 and older bugs: create new thread, this thread is only for 4.0.0 discussion!

http://www.winuae.net/files/b/winuae_4000b1.7z
http://www.winuae.net/files/b/winuae64_4000b1.7z

Huge graphics subsystem rewrite to support multiple virtual monitors.
Lagless vsync.
New debugger.

If any existing configuration that works with 3.6.1 crashes or works strangely, attach config and winuaelog.txt, thanks. Do not attempt to "fix" it by adjusting config!

Changelog:

Lagless Vsync:

Previous discussion: http://eab.abime.net/showthread.php?t=88777&page=8

Implemented lagless vsync mode (https://www.blurbusters.com/blur-bus...or-developers/)
Replaces old low latency vsync mode.

What does it do? It reduces input latency from usual 20ms-40ms+ to less than 5ms! (or even less)

Current limitations:

- Does not support black frame insertion or frame doubling = use only standard 50Hz or 60Hz modes. (or up to 85Hz or so )
- Native mode only. Cycle-exact/approximate/fastest possible/JIT supported.
- Direct3D 9 and 11 only.
- Fullscreen only.
- Amiga display to monitor position mapping must be border to border vertically (or close enough) or you may see tearing lines.
- Does not gain anything from G-Sync.

Current features:

- Input is read after each slice.
- Default is 4 slices (adjustable in GUI) which makes max input latency about 6ms. (Assuming quality "gaming grade" USB input devices that use <=1ms USB rate.)
- Because output is shader based, outputting each slice requires full render pass each time. It technically means same as rendering screen 4 times the frame rate. (for example 50Hz output requires rendering 200 frames) -> don't enable any extra shaders unless you have powerful GPU. Most likely requires GPU with on-board RAM (discrete GPU) because this mode increases VRAM bandwidth requirements heavily. Or reduce resolution.
- END+F9 toggles debug colors when in low latency vsync mode (In normal modes END+F9 changes screens). When debug colors are disabled, useless screen clearing before each slice rendering is also disabled.

--

Multi virtual Amiga monitor support:

Enables multiple virtual Amiga monitors. Amiga monitor = single WinUAE window.

Default mode is unchanged, highest priority Amiga display output appear in single WinUAE window, switches automatically or manually (END+F9).

Optionally any video port display adapter or any RTG board can be disconnected from default monitor and connected to other monitor. (Monitor 1 to 4 select box in GUI, 1 = default). Only one signal source can be connected to non-default monitors. Only default monitor support on the fly switching/END+F9 manual switching.

Native (chipset) video output is always connected to first (default) monitor.

Each active monitor (WinUAE window) content is refreshed in real-time.

For example x86 VGA can be now visible at the same time with WB.

Limitations and other information:

- Windowed mode only (later full-window with single virtual monitor to physical monitor mapping)
- Fullscreen is not supported and won't be supported.
- Direct 3D 9/11 mode only. DirectDraw won't be supported.
- GUI options adjusts all monitors. If native/video port: native filter and all other native related settings are in use for all windows in native/video port mode, if RTG: GUI RTG settings are used for all monitors in RTG mode.
- Non-default monitors are always opened next to default monitor. Positions are not stored.
- It does not matter which window has focus/captured mouse. All windows listen for input normally.
- Non-default windows don't have status bar or OSD and only have name of monitor in title bar.
- Video port device's window opens immediately at startup, RTG board's window open when board's output is enabled with valid display configuration for the first time.

--

New debugger features:

http://eab.abime.net/showthread.php?t=91321

--

Minimal Macrosystem Casablanca "emulation"

Supports Casablanca ROM images, none of Casablanca special IO address spaces supported. It is has very unknown custom hardware.

If you want to help with debugging/reverse-engineering Casablanca internals using emulation:

- Set correct ROM, either original 2x512k 1:1 ROM images (ROM scanner supported) or 1x1024M manually merged and byteswapped. (Don't ask me, they contain KS modules, in scrambled format.) If rom starts with "00 00 00 00 00 00 00 18 44 52 42 52 00 01 00 06 ........DRBR...." = correct merged and byteswapped image.

- CPU must be set to 68060 (MMU bus error handler assumes PC always points to faulting instruction, 68040 documentation says it isn't guaranteed)
- MMU emulation must be enabled.
- Chipset extra must be set to Casablanca.
- Other chipset options don't matter.
- RAM must be set manually: Select Z3 Fast #1, set size (32M/64M), tick "Manual configuration", set Address range start = 40000000. (End address is set automatically). Casablanca RAM uses Z3 space but does not use autoconfig.
- Log window should be enabled.

It "works" if you see lots of casablanca io access log messages, including MMU enable message. (MMU: TC=109dc enabled=0 page8k=0 PC=00000106). Finally it gets in infinite loop with exec partially initialized.

Because ROM is descrambled and copied to RAM by boot code and MMU is used to remap it to usual $f80000 region, also "zero page" is remapped, you need to enable UAE debugger mmu mapping support (for example "mmu 1" = use current MMU tables to translate user space addresses, 5 = super space) or you most likely get random garbage when using debugger commands.

--

Other Changes

- Directory harddrives now use uaehf.device as a fake device driver (instead of non-existing uae.device), SysInfo does not anymore crash in Drives page when selecting directory harddrive. (SysInfo bug: it does not check for device driver open failure) HD_SCSICMD is also partially supported in this situation, mainly identification commands that don't access the drive, like READ CAPACITY and INQUIRY. Unsupported commands return Incompatible Medium Installed ($05/$30 00) error.
- Partition hardfiles also support above HD_SCSICMD SCSI commands.
- Don't show loaded config file ".uae" extension in GUI title.
- GUI title didn't show loaded config file if it was loaded from command line or via doubleclicking config file.
- MSVC code analyzer warnings fixed (uninitialized variables, buffer size checks).
- ROM is slow -option only changed $e0-$e8 ROM space timing (wrong end address)
- Toccata recording used wrong interrupt bit.
- Fixed WD33C93 based SCSI controller and no SCSI devices: boot hang (3.6.1)
- If CD was changed and system was reset during change delay, drive become empty and new CD was never inserted.
- DKB RapidFire and SpitFire use same boot rom. Renamed to RapidFire/SpitFire. Only difference seems to be RAM expansion.
- Added Xetec FastTrak, CSA Magnum 40, GVP A1230 Series II, Hardital TQM and MacroSystem Falcon 040 (without SCSI).
- Real harddrive imager attempts to automatically temporarily dismount source drive first.
- Directory filesystem harddrive block size is dynamic adjustment now starts from smaller disk size to also fix WB free space calculation overflow.
- Disk swapper config file data is restored from statefile.
- If memwatch point is watching for blitter accesses, blitter registers at start of blit and current register are output when breakpoint is hit.

Xetec FastTrak:
- 5380 based SCSI controller, byte wide fake DMA, uses MOVEP.L.
- "bootdisk.device" "bootdisk 1.42 (22 Mar 1990)" "Xetec FastTrak Autoboot"

CSA Magnum 40:
- A2000 68040 accelerator.
- 53C710 based SCSI, true DMA.
- ROM is loader only, SCSI driver is installed to RDB LSEG blocks by the installer.

GVP A1230 Series II:
- A1200 68030 accelerator.
- Usual GVP WD33C93 + 24-bit GVP DMA chip combination, with 2 extra external DMA bits to support up to 32M of RAM.
- ROM v5.0 gvpscsi.device.
- Clock not emulated. (DS1994 1-wire clock)

Hardital TQM:
- A1200 68030 accelerator.
- ROM only adds RAM to system.
- Possibly clone of DKB 1230. Nearly identical ROM contents with "DKB1230" string in "hidden" nybble based data!

MacroSystem Falcon 040
- A1200 68040 accelerator.
- Only non-SCSI boot ROM currently available, adds only RAM to system. Uses MOVEP, not 68060 compatible. (SCSI boot ROM wanted!)

[White]

Hi Toni,
Thanks for the new version of winUAE 4
the application crashes when I select the configuration file to run OS4.1
I hope it is useful, I attach the files:
Thank you.

[Amiga68k]

Impressive list again Toni.

No serious issues or strangeness seen here after playing with it for a short while. For me the default value of 4 slices presents some slight tearing though, especially seen with pinball games. Changing this to 3 (and even 2) fixes that here.

Will continue working on my setups with this version and report back when needed.

[mark_k]

Press "End+F9" to show stripes in lagless vsync mode. Open setting window then continue emulation. Stripes are no longer visible so you have to press End+F9 again to show them.

Load the config below. In display settings, full-screen resolution is set to Native (3840×2160 in my case). Start emulation. The Amiga display is scaled far too large. Open settings window, change resolution to 3840×2160 and continue emulation, then display appears as it should.

http://www.media!fire.com/file/ynv4onil9ig64iq/A500_1.2_test_DX11_DOC_15.uae.7z

[AMIGASYSTEM]

Toni with WinUAE 4.0.0. found something strange about the function "ClipBoard Sharing" (Windows To Workbench), it's not easy to explain, now I try, 3.6.1 no problem.

If you try to copy-paste from Windows to the Workbench get one Clipboard "Previous" (old); if you restart WinUAE you get the last clipboards captured.

[mark_k]

AMD graphics card, Windows 10 1709. In lagless vsync mode emulation runs too fast (~double speed, or maybe just unthrottled???) with the 2-slice setting. Emulation speed is fine with any other number of slices. Example pic:

http://www.media!fire.com/file/xj5uz5begezj7e7/2_slices_tearing.jpg

[Leandro Jardim]

WinUAE 4.0 with Intel HD Graphics 4400, Windows 10 Single Language (10.0.16299). My configuration is a simple A500 based on quickstart, with Low Latency VSync and 4 slices. WinUAE lock up at boot phase with a blank screen and I must kill it with CTRL+ALT+DEL and the task manager.

When I change to 3 slices or less, it doesn't lock up but it changes my LCD TV resolution to a very small one that is awful to see (less than 320x240 I guess). Seems to be something with Low Latency VSync in general, because I get the same thing with the resolution when I change it to 1 slice.

Maybe my graphics chipset can be incompatible with frame slicing, but it used to work very well with Low Latency VSync in previous versions of WinUAE, and I am interested to see it fixed because I am a little "worried" to lose this feature on WinUAE.

Copy the host config attached below and load it with quickstart for trying to see what I am talking.

[White]

Hi Toni,
Excuse me, strangely on the dedicated partition with windows 7 64bit
I use a customized version of windows with just 22 services enabled and other tweaks
so with only windows 7 64bit service pack 1 and netframework 4.7.1 no crash occurs.
I will install a version of 4.1 completely from the beginning with winUAE 4 to see if it works with Windows 7 professional completely updated on the main system.
Thank you for your patience and your work!
Thanks again.

[White]

Hi Toni,
Excuse me I found the problem of crashing,
it occurs if you use a virtual hard disk with programs like AMD-RAMDISK
in this case the new version does not seem to work with virtual HD created in the ram and for some reason as soon as you choose the configuration crashes.
The final version 3.6.1 does not have this problem.

Thanks and sorry for the report.

[White]

Hi Toni,
I completely removed AMD-RAMDISK from windows 7 64bit professional updated in April.
The problem remains as soon as I try to use a 4.1FE1 configuration
or even the 3.9 AFAos etc.
if it can be useful my configuration is:
I5 2400 geforce Titan 750ti 2giga gtx 12giga ram
Thanks and sorry again for my reports.
In my light version of windows 7 this does not happen.
I wait patiently without continuing to write.
Thanks again for your work.

[AMIGASYSTEM]

Originally Posted by White

The problem remains as soon as I try to use a 4.1FE1 configuration
or even the 3.9 AFAos etc.

Sorry Paul that you have problems with AfA_OS, possibly if you want to discuss in Italian we can hear on Amiganews.

[Toni Wilen]

Originally Posted by White

Hi Toni,
Excuse me, strangely on the dedicated partition with windows 7 64bit

I think you forgot to include required information, including crash dump if winuae crashes.
EDIT: I missed your first post which has enough information

[Toni Wilen]

Originally Posted by Leandro Jardim

When I change to 3 slices or less, it doesn't lock up but it changes my LCD TV resolution to a very small one that is awful to see (less than 320x240 I guess). Seems to be something with Low Latency VSync in general, because I get the same thing with the resolution when I change it to 1 slice.

Try selecting real resolution from the list, not "native", it seems "native" has some issues..
EDIT: Also make sure to select 50hz or 60hz refresh rate, don't select "default".

[AMIGASYSTEM]

Originally Posted by AMIGASYSTEM

Toni with WinUAE 4.0.0. found something strange about the function "ClipBoard Sharing" (Windows To Workbench), it's not easy to explain, now I try, 3.6.1 no problem.

If you try to copy-paste from Windows to the Workbench get one Clipboard "Precedente" (old); if you restart WinUAE you get the last clipboards captured.

Toni i know you do not like watching videos, but if you do not understand what I wrote i think it is necessary to see my little video (only 949 KB) which clearly shows the problem, sorry if you annoy you

[Steve]

When running my SWOS configuration on the latest beta I am getting black lines on the display and constant display issues like tearing etc all over the screen. Note this only occurs when I use the low latency vsync option. Standard vsync works perfectly but I don't think this supprts the lagless vsync mode.

[Retro-Nerd]

I get the black lines with the lagless vsync on too with a ClassicWB, PAL hires 640x256.

Also some tearing in vertical scrolling games. 3 solid horizontal tearing lines trough the whole image. But mostly only if centering -> vertical is enabled, without it works fine (e.g. Slam Tilt).

[Toni Wilen]

Originally Posted by White

Hi Toni,
Thanks for the new version of winUAE 4
the application crashes when I select the configuration file to run OS4.1
I hope it is useful, I attach the files:
Thank you.

Your config is too complex to duplicate but as a workaround try switching filter from none to null.

Originally Posted by AMIGASYSTEM

Toni with WinUAE 4.0.0. found something strange about the function "ClipBoard Sharing" (Windows To Workbench), it's not easy to explain, now I try, 3.6.1 no problem.

Fixed in next beta.

Originally Posted by mark_k

AMD graphics card, Windows 10 1709. In lagless vsync mode emulation runs too fast (~double speed, or maybe just unthrottled???) with the 2-slice setting. Emulation speed is fine with any

Can't duplicate.

Originally Posted by Steve

When running my SWOS configuration on the latest beta I am getting black lines on the display and constant display issues like tearing etc all over the screen. Note this only occurs when I use the low latency vsync option. Standard vsync works perfectly but I don't think this supprts the lagless vsync mode.

Only when running SWOS or always? Press END+F9 to confirm color bars are stable.

[Steve]

Originally Posted by Toni Wilen

Only when running SWOS or always? Press END+F9 to confirm color bars are stable.

I can confirm that turning off horizontal and vertical centering fixes the issue (thanks Retro-Nerd). Alt-tab no longer works though in this mode. Is that by design? All I get is the mouse pointer appearing.

[Retro-Nerd]

Alt-Tab works fine for me though. It takes a bit longer because the display has to switch from 50Hz fullscreen to 75Hz desktop.

[Toni Wilen]

Originally Posted by Steve

I can confirm that turning off horizontal and vertical centering fixes the issue (thanks Retro-Nerd). Alt-tab no longer works though in this mode. Is that by design? All I get is the mouse pointer appearing.

Vertical centering seem to mess up partial updates..

ALT-TAB should work normally but I have noticed that very randomly it takes long time before it switches, reason unknown..

Does F12 work identically? Also note that ALT-TAB works unexpectedly (but also by design, unfortunately) if desktop does not have any other programs open, it just switches back..