WinUAE 4.0.1 beta series

[Toni Wilen]

It was correct date but wrong fix.. Does it work now?

[PeterK]

Update found and tested. Thanks Toni
FACOS works correctly now in "round to nearest" and "round to zero" mode with Jit, non-Jit and softfloat. "Up" and "down" not tested.

Of course, other trigonometric/logarithmic functions may also have critical zero points, turning points or poles, which could need some more investigation (and motivation to check them).

[Toni Wilen]

http://www.winuae.net/files/b/winuae_4010b3.7z
http://www.winuae.net/files/b/winuae64_4010b3.7z

Beta 3: (Possibly final beta, I wasn't supposed to do 4.0.1 vsync updates but below updates should have been in 4.0.0..)

- If CD audio playing from real/virtual CD (not directly mounted image) was restarted because of config change, playback always started from beginning (or possibly failed to restart).
- 68060 FPU disable behavior change (68060 accelerator boards have "$f0" ROM to disable FPU because exec does not understand 68060 FPU and will crash if enabled), FPU is not anymore automatically disabled at hard reset if any emulated accelerator board is configured (matches now real world), if no accelerator board: if UAE boot ROM is at $f00000 ("old" mode), it disables FPU (just like real accelerator board do), if UAE Boot ROM is any other address: ("new" mode), m68k RESET instruction will disable FPU. Previously 68060 config got stuck in reboot loop because of not-disabled FPU if system was software reset.
- D3D9/11 vsync modes (lagless and standard) will now support 100/120Hz with optional black frame insertion.
- Always check interrupts immediately after MOVE to SR instruction (except if JIT enabled). Previously it was delayed until following instruction if fast 68020+ mode.
- Above FACOS JIT fix.

[DamienD]

Cheers Toni

[Marty2AGA]

Great Toni

One Question.
http://eab.abime.net/showpost.php?p=...3&postcount=74

Is this a normal state ?

[hexaae]

@Toni
When switching from <-> to Windows desktop with ALT+TAB in full-window mode there is no window auto-reactivation http://eab.abime.net/showthread.php?t=93308 with Windows mouse cursor floating (you have to click after ALT+TAB to really restore emulation).
Is this ok?

[hexaae]

Got 2 strange crashes on immediate reboot after WB3.9BB2 boot (i.e. booted, and used C:Reboot; JIT was ON)... Can't reproduce though… Attached dmp.

https://nofile.io/f/NZkyOrvmUc0/winu...9_03.48.12.zip

EDIT:
switched from SFS -> PFS3Asio 2 days ago but I don't think is related

EDIT2:
confirmed PFS3AIO is not reliable: since 2 days ago I moved from SFS (rock stable and never had a single case of corruption for more than 10 years with WinUAE and other 10 years before with my real A1200) I got many troubles, especially after reboot.
I experienced random HALT3 errors booting from those HDF, and sometimes changes where NOT saved on the HD after editing text files and after copy files + quick reboot few seconds later (!). Never happened with SFS. Restored old SFS HDF and forgot about PFS3 forever! :P

[Toni Wilen]

Dump does not seem to be from official beta. winuae.7z = useless dump file. (EDIT: it is divide by zero but it won't help much)

[hexaae]

Mmmh, ok, I think we can ignore it. Probably related to this WB3.9 software bug testing corrupting mem: http://eab.abime.net/showthread.php?t=93302 (Copy v40.1 case n.1…)

[Toni Wilen]

http://www.winuae.net/files/b/winuae_4010b4.7z
http://www.winuae.net/files/b/winuae64_4010b4.7z

Unfortunately b1 path handling change was more complex than I assumed so there will be some more delay.. (If I would have known this, I would not have done it yet..)

Check that existing configs still work, including disk swapper.

Beta 4:

- Floppy, CD, Tape, HDF geometry, HDF filesystem, disk swapper, RTC and flash rom file paths also support b1 resolve environmental variables update. (b1 update had issues requiring partial rewrite so it was good idea to update all other paths too. Excluding special paths like ROM paths.)
- Previously only some SCSI controllers flashed CD led when emulating CD drive.

Short description about path handling change: Previously any path was always converted to either full absolute or relative path with possible environmental variables resolved when config was loaded or path was typed/selected from dialog. When config was saved, old path (possibly containing environmental variables) was lost. Now paths are loaded unmodified from config file and only converted when needed. "Normal" path strings (no environmental variables) are still automatically converted to absolute/relative when saving config.

[Marty2AGA]

Originally Posted by Toni Wilen

- Previously only some SCSI controllers flashed CD led when emulating CD drive.

Top Works, a2091 and Connected CD-Drive is Flashing.

@mclane: I can not answer your PN. Since you turned it on in the options that can not send a private message.

[Mclane]

@marty......Ok, found out the answer anyway..ta...

Sorry Toni...unexpected pm prob..Sorry for the hijack...

[Torkio]

Hello, I tested these options:

- D3D9/11 vsync modes (lagless and standard) will now support 100/120Hz with optional black frame insertion.

here is my report:

Using G-Sync Monitor keeping G-Sync on
ticking VRR monitor
Using 100Hz PAL
Lagless VSync (Beamraced)

The desktop settings (144Hz) prevails the internal emulator 100Hz PAL so basically CPU runs out to 180% and in the FPS adj. says 144.001007

To avoid this I set desktop to 100Hz that match the 100Hz PAL.
In this way the emulation speed is OK (FPS adj. says 50.0)

The problem is that with G-Sync on tears are present on the screen. the more slices the more tears.
BFI isn't working with G-sync, both Direct X 9 and 11.

Disabling G-Sync, things run very well
Internal emulator 100Hz PAL rightly prevails desktop setting (144Hz)
FPS adj. says 99.930000
Speed is correct, no tears (I tested 2/4/8/16 slices) and I had no tears.
BFI Direct X 11 works perfect without flicker or hiccup.
Instead BFI Direct X 9 has some troubles, slow downs (CPU>100%) and flickering out of sync.

I Used Windows 10 64bit NVIDIA Geforce GTX 970 with latest drivers 398.36 and AOC G2460PG monitor.

Hope I've been helpful.

[hexaae]

@Torkio
With G-Sync I don't use Lagless or Std Vsync options, I leave it empty since g-sync will automatically sync video refresh to 50/60 Hz/fps. Games run perfectly in PAL/NTSC native mode and super smoothly at 50 (PAL) or 60 (NTSC) fps as it was 20 years ago thanks to G-Sync.
I have the HW in signature and a 75Hz Windows desktop native resolution.

[DamienD]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae_4010b4.7z
http://www.winuae.net/files/b/winuae64_4010b4.7z

Unfortunately b1 path handling change was more complex than I assumed so there will be some more delay.. (If I would have known this, I would not have done it yet..)

Check that existing configs still work, including disk swapper.

Beta 4:

- Floppy, CD, Tape, HDF geometry, HDF filesystem, disk swapper, RTC and flash rom file paths also support b1 resolve environmental variables update. (b1 update had issues requiring partial rewrite so it was good idea to update all other paths too. Excluding special paths like ROM paths.)
- Previously only some SCSI controllers flashed CD led when emulating CD drive.

Short description about path handling change: Previously any path was always converted to either full absolute or relative path with possible environmental variables resolved when config was loaded or path was typed/selected from dialog. When config was saved, old path (possibly containing environmental variables) was lost. Now paths are loaded unmodified from config file and only converted when needed. "Normal" path strings (no environmental variables) are still automatically converted to absolute/relative when saving config.

Heya Toni,

Unfortunately using this latest beta, WinUAE now takes an absolute age to start... 40 seconds as opposed to 5 seconds

I guess it's to do with all the above and me having 2480+ configurations.

[Toni Wilen]

Originally Posted by DamienD

Heya Toni,

Unfortunately using this latest beta, WinUAE now takes an absolute age to start... 40 seconds as opposed to 5 seconds

I guess it's to do with all the above and me having 2480+ configurations.

Does it only happen if "art" paths panel option is set?

Originally Posted by Torkio

Hello, I tested these options:

- D3D9/11 vsync modes (lagless and standard) will now support 100/120Hz with optional black frame insertion.

here is my report:

Using G-Sync Monitor keeping G-Sync on
ticking VRR monitor
Using 100Hz PAL
Lagless VSync (Beamraced)

The desktop settings (144Hz) prevails the internal emulator 100Hz PAL so basically CPU runs out to 180% and in the FPS adj. says 144.001007

To avoid this I set desktop to 100Hz that match the 100Hz PAL.
In this way the emulation speed is OK (FPS adj. says 50.0)

The problem is that with G-Sync on tears are present on the screen. the more slices the more tears.
BFI isn't working with G-sync, both Direct X 9 and 11.

Disabling G-Sync, things run very well
Internal emulator 100Hz PAL rightly prevails desktop setting (144Hz)
FPS adj. says 99.930000
Speed is correct, no tears (I tested 2/4/8/16 slices) and I had no tears.
BFI Direct X 11 works perfect without flicker or hiccup.
Instead BFI Direct X 9 has some troubles, slow downs (CPU>100%) and flickering out of sync.

I Used Windows 10 64bit NVIDIA Geforce GTX 970 with latest drivers 398.36 and AOC G2460PG monitor.

Hope I've been helpful.

It is quite interesting that g-sync "causes" different side-effects (Perhaps it works slightly differently in different nvidia chip generations?). I can't notice any obvious differences, both with and without are stable in 50 and 100hz lagless vsync modes.

I have same problem with D3D9, unstable in BFI. But it is fine as long at least D3D11 mode works.

Originally Posted by hexaae

@Torkio
With G-Sync I don't use Lagless or Std Vsync options, I leave it empty since g-sync will automatically sync video refresh to 50/60 Hz/fps. Games run perfectly in PAL/NTSC native mode and super smoothly at 50 (PAL) or 60 (NTSC) fps as it was 20 years ago thanks to G-Sync.
I have the HW in signature and a 75Hz Windows desktop native resolution.

This is apples to oranges comparison because lagless vsync has noticeably less input lag than any other mode (which is the whole point of this mode). G-Sync alone unfortunately can't reduce lag. (and unfortunately has annoying side-effect of forcing next refresh immediately that makes it impossible to have glitch free lagless vsync, perhaps workaround can be found someday..)

[hexaae]

Ok, thanks for explanation about g-sync vs new lagless modes, since there is lack of documentation. I will definitely try lagless mode then

[DamienD]

Originally Posted by Toni Wilen

Does it only happen if "art" paths panel option is set?

I'd imagine so but at work currently so can't test further until tonight.

[hexaae]

b4:
the problem in the GUI if you edit manually the HDF fs string is still unfixed.

Repro steps:
- load a cfg with already defined dh0: for example using SFS from .\ROMS\SmartFileSystem
- now manually change dh0 (click Properties or double-click on it) and choose another HDF from file requester
- then manually edit the fs string below (it was .\ROMS\SmartFileSystem, edited manually as .\ROMS\PFS3aio)

- press OK to confirm and exit HDF setup
- start the emulation (should give you "Not a DOS Disk" error on boot since the fs is not actually matching)

The issue: WinUAE will ignore changes and still see fs as .\ROMS\SmartFileSystem.

[Toni Wilen]

Originally Posted by hexaae

b4:
the problem in the GUI if you edit manually the HDF fs string is still unfixed.

Repro steps:
- load a cfg with already defined dh0: for example using SFS from .\ROMS\SmartFileSystem
- now manually change dh0 (click Properties or double-click on it) and choose another HDF from file requester
- then manually edit the fs string below (it was .\ROMS\SmartFileSystem, edited manually as .\ROMS\PFS3aio)

- press OK to confirm and exit HDF setup
- start the emulation (should give you "Not a DOS Disk" error on boot since the fs is not actually matching)

The issue: WinUAE will ignore changes and still see fs as .\ROMS\SmartFileSystem.

I think this has nothing to do with 4.x.. Always confirm it first.

Ok, thanks for explanation about g-sync vs new lagless modes, since there is lack of documentation

"Documentation" is in this forum. Search.