WinUAE 4.9.2+ beta series

[Toni Wilen]

Originally Posted by aribeth23

Hey really like where this is going but I still have trouble with DblPAL screenmode (640x512) I cannot get a good scaling with any 4.9 betas.

Did it work differently (better or worse) in 4.9.1? This is the important bit.

Note that doublescanned (and other programmed) modes were never really made to work with filters properly. Usage is quite rare (most use normal modes or RTG).

Better post all information you can think of in separate thread and I'll take a closer look after 4.9.9 is out. It is far too late now.

[Maijestro]

Originally Posted by Toni Wilen

Leider hilft bootlog.txt nicht. Sie müssen sowohl config als auch winuaelog.txt einbeziehen (am einfachsten ist es, im Pfadbedienfeld "Vollständige Protokollierung aktivieren" anzukreuzen, dann Ihre Konfiguration zu laden und die Emulation zu starten. Wenn sie hängen bleibt, öffnen Sie das Pfadbedienfeld erneut, klicken Sie auf Alle speichern, um eine Datei zu generieren, die sowohl Protokolle als auch die Konfiguration enthält)

Hi Toni,

thanks for the help. Via Uaegfx configuration AmigaOs 4.1 boots. Unfortunately not anymore via Vodoo 3 emulation and I get a green screen when booting. Tested with WinUae 4.9.9 RC 1.

I created the log file as you explained.

Sorry for my bad English.

[Toni Wilen]

Your config works fine here. Try removing everything unnecessary first (like recuding Z3 memory size. It shouldn't make any difference when using 64-bit version but perhaps there is some limit in older Windows versions?).

("picasso_getwritewatch 87" messages are mostly harmless)

btw, don't enable 68k CPU more compatible or data cache. It only makes booting slower until PPC CPU takes over.

[Zarnal]

Pinball Illusion AGA ( IPF 0710 or WHDLoad versions ).

There seems to be a slight glitch between the "Loading" screen and the start of the game since beta 1 ( pic 1,2,3 ). It's ok with version 4.9.1 and older versions.

Quickstart A1200 ( and others configs ).

To reproduce with Quickstart A1200 ( or WHDLoad version 2.2 ) :

Select the first table " Law'n Justice " and wait for the game to start ( the glitch occurs just before the table appears ).

Note : i'm not fast enough to produce a proper save state for this case ( with IPF 0710 ). It's going too fast.

Thanks.

[Toni Wilen]

Originally Posted by Zarnal

Pinball Illusion AGA ( IPF 0710 or WHDLoad versions ).

Looks normal, swaps copper list to in game copper list before updating bitplane pointers or data. Almost certainly the usual: depends on CPU speed.

[Toni Wilen]

https://download.abime.net/winuae/fi...ae_41000b10.7z
https://download.abime.net/winuae/fi...64_41000b10.7z

Beta 10 (RC2) Official release in max 1 week:

- Bumped version to 4.10.0
- 64-bit natmem limit increased to support G-REX PCI VRAM modification detection (Only draw lines that have been modified). Previously Voodoo 3 + G-REX always forced whole screen refresh. G-REX PCI memory space is above 2G "limit". Check also current limit to prevent "picasso_getwritewatch 87" log messages when running 32-bit version.
- SupraDrive AMAB5 and AMAB6 are also 8k. Removed extra duplicated 8k. Previous SupraDrive 2000DMA ROM is called "44-25B" (Hand written text on ROM label did say 44-25B but I thought it was some kind of checksum or something but SupraRomChk on SupraBoot3.8B install disk does detect it as "44-25B"). Updated 2000DMA ROM mapping, SupraRomChck now detects supported ROMs correctly. Remaining undumped official Supra ROMs are "33-11B" and AMAB1, listed inside SupraRomChk executable. (Also some AMAB5 and AMAB6 beta roms are listed)
- Added Hardital Synthesis/Super Big Bang v48.5 (previous was v53.1)
- Serial port ring indicator (RI) signal support (RI is shared with printer port SELECT line)
- Fix out of bounds buffer access when checking what should be written to write-only register that was read. (b5)

[Ponki1986]

My apologies, but is the version numbering correct? Since there has already been 4.1, 4.2, 4.2.1, 4.4, 4.9, 4.9.1, Beta 4.9.9 then the 4.10 number is equal to 4.1. Since you have made so many changes it would be correct to give the version number 4.9.9.9 or even 5.0.

[Toni Wilen]

Originally Posted by Ponki1986

My apologies, but is the version numbering correct? Since there has already been 4.1, 4.2, 4.2.1, 4.4, 4.9, 4.9.1, Beta 4.9.9 then the 4.10 number is equal to 4.1. Since you have made so many changes it would be correct to give the version number 4.9.9.9 or even 5.0.

Version number is not a decimal number. It is major number.minor number.

It is not 5.0 because this version is guaranteed to have stupid bugs. 5.0 comes later.
(EDIT: It will be explained in official release notes)

[hexaae]

Can others confirm this strange random white bitplane flickering in Lionheart, 2nd level (first cavern with spiders):
http://eab.abime.net/showpost.php?p=...&postcount=186


WHDLoad version. Seems reproducible in all conditions (starting with 060 AGA) even degrading emu to "cachesize 0 cpu_speed real cycle_exact true" and NOCACHE tooltype.
This wasn't reproducible with 4.9.1 public and previous WinUAE versions.

[Zarnal]

Originally Posted by hexaae

Can others confirm this strange random white bitplane flickering in Lionheart, 2nd level (first cavern with spiders):

WHDLoad version. Seems reproducible in all conditions (starting with 060 AGA) even degrading emu to "cachesize 0 cpu_speed real cycle_exact true" and NOCACHE tooltype.
This wasn't reproducible with 4.9.1 public and previous WinUAE versions.

I can't reproduce with simple configuration. (at least with a Quickstart 1200 + 8MB Fast + Whdload version 2.3 with default options ). Have you tested with IPF ?

Edit : 060 + JIT is ok for me in level 2 but i have flickering with water and default options in level one. Issue with the slave ?

[Toni Wilen]

Sorry, not really interested in playing any game long enough, without level skips or similar. Even with infinite lives it is annoying.

I can check if you create statefile using basic WB + whdload directory harddrive config, with enough memory to get everything preloaded. (Can continue playing without HD accesses. No need to include the HD)

But probably CPU speed as usual. There is no guarantee whdload glitches would mean emulation problem. It simply has been few years since internals changed enough to change CPU speed.

[Supamax]

Originally Posted by Ponki1986

My apologies, but is the version numbering correct? Since there has already been 4.1, 4.2, 4.2.1, 4.4, 4.9, 4.9.1, Beta 4.9.9 then the 4.10 number is equal to 4.1. Since you have made so many changes it would be correct to give the version number 4.9.9.9 or even 5.0.

No:
4.1 means 4.01
4.2 means 4.02
...
4.9 means 4.09
4.10 means 4.10

[rutra80]

Toni there is a short emulation pause on screenmode switch when Interlaced filters are enabled, even with same shader or without shaders. Would it be possible to be (more) fluent?

[hexaae]

Originally Posted by Zarnal

I can't reproduce with simple configuration.

Reproduced even with basic cfg A1200 + 4MB fast... You have to move around a bit and pay attention to strange filckerings at the border (right usually) or the whole screen. Usually visible within a 60-120 secs in the 2nd level.

Video example (see 00:45, 00:48... sometimes the flickering is a vertical column on the right):
[ Show youtube player ]

Originally Posted by Toni Wilen

Sorry, not really interested in playing any game long enough, without level skips or similar. Even with infinite lives it is annoying.

I already posted how to quickly skip to this level:
crouch down + P (pause)
CTRL+HELP (screen will shake, cheat activated)
F2 will bring you to lev2, cavern with spiders.

I can check if you create statefile using basic WB + whdload directory harddrive config, with enough memory to get everything preloaded. (Can continue playing without HD accesses. No need to include the HD)

Here is a statefile (basic cfg: A1200 + 4MB fast):
https://1drv.ms/u/s!ApMUGr0cuN39grwt...12bXA?e=fNJRsS
This statefile loaded with 4.9.1: unreproducible, with 4.9.2betas (b10): reproducible.

But probably CPU speed as usual.

Seems to happen even degrading emu to slowest/closer to bare A1200, without success...

[Toni Wilen]

Do you mean it should start flickering immediately after loading the statefile? I can't see any flicker.

But first level clouds and mountains flicker. (EDIT: when using fast config) Are you really sure you don't have some non-standard config?

[hexaae]

Originally Posted by Toni Wilen

Do you mean it should start flickering immediately after loading the statefile? I can't see any flicker.

No, it's random as in the short YT video above... you have to play the game for 60-120 secs scrolling left-right

But first level clouds and mountains flicker. (EDIT: when using fast config) Are you really sure you don't have some non-standard config?

Uh, yep sorry some adjustments are still required to workaround main menu and in-game gfx gliches. I use these tts:

SLAVE=Lionheart.slave
PRELOAD
QUITKEY=$5D
ExecuteStartup=
(ExecutePostDisk=uae-configuration cachesize 0 cpu_compatible false cpu_cycle_exact true immediate_blits true)
ExecutePostDisk=uae-configuration cachesize 128 cpu_speed real cpu_throttle -420 cpu_memory_cycle_exact true cpu_multiplier 2 immediate_blits true
Custom4=0
Custom5=124

the first ExecutePostDisk between () is also the alternative workaround I used before with WinUAE 4.9.1. In general immediate_blits is required for main menu, cpu_memory_cycle_exact for the clouds in-game. This worked with all previous WinUAE versions. >4.9.1, whatever I try (including basic configs), shows that random biplane flickering in the cavern...

[Toni Wilen]

Lionheart second level flashes are an emulation bug. Unfortunately so far I can't find the reason. Probably some CPU modes messing up chipset timing in some rare situations.

[Toni Wilen]

https://www.winuae.net/files/b/winuae.7z updated. Possible fix for Lionheart without breaking anything else. But it could break something else because this change was done to fix something else but I don't remember anymore what. But that fix was clearly wrong..

[Mclane]

I just tried it, I did see the odd glitch on the right of the screen but I must admit I didn't have the disks in, it suddenly seemed to crash the game and I could hear the drive ticking away to a black screen with random noises..

Will hunt the disks out and try again. Edit: wait, this was a WHDLOAD, so disks not needed.

I'll leave it to the OP, don't want to muddy the water, as it were..

[Toni Wilen]

Originally Posted by Mclane

I just tried it, I did see the odd glitch on the right of the screen but I must admit I didn't have the disks in, it suddenly seemed to crash the game and I could hear the drive ticking away to a black screen with random noises..

Will hunt the disks out and try again. Edit: wait, this was a WHDLOAD, so disks not needed.

I'll leave it to the OP, don't want to muddy the water, as it were..

This isn't very useful. Single test only. Single beta only.
Almost certainly this crash has nothing to do with this specific beta.