WinUAE 3.6.0 beta series

[emufan]

win7 trayicon does not appear in b10 - last seen in b8 (IIRC)
now I have to kill winuae with taskmanager.

taskbar icon - which appears when starting any program - does vanish
when playing an old FPS in fullscreenmode, it uses RenderDevice=D3DDrv.D3DRenderDevice
this is an old bug, cannot remember when it happened for the first time.

maybe related to DirectDraw I'm using as default in my winuae configs.

#1) in dx11 mode: minimized winuae window before starting the game.
after game exit, winuae window restores to normal window size, black screen, emulation paused

[Toni Wilen]

Originally Posted by emufan

win7 trayicon does not appear in b10 - last seen in b8 (IIRC)

Does winuae.7z fix it. (There was change in tray icon but MSDN document says feature is win7 supported. It looks like it really isn't...)

now I have to kill winuae with taskmanager.

alt+f4?

#1) in dx11 mode: minimized winuae window before starting the game.
after game exit, winuae window restores to normal window size, black screen, emulation paused

RTG or native window? Can you duplicate it?

Originally Posted by Saghalie

Having an issue where when I create a new config, all the descriptions on all of the configs disappear.

WinUAE issue or something else?

It broke in b9, will be fixed in next. (Nothing was lost, description is still in config file)

[emufan]

Originally Posted by Toni Wilen

Does winuae.7z fix it. (There was change in tray icon but MSDN document says feature is win7 supported. It looks like it really isn't...)

yes, trayicon back. but no program-toolbar-icon in DirectDraw mode --> after game exit.

alt+f4?

there was simply no way to get focus on winuae, so no alt+f4

RTG or native window? Can you duplicate it?

happens in rtg and standard mode.
minimized window before game starts,
game exit -> winuae window in default size pops-up , black, pause mode.
can unpause and emulation continues

[Toni Wilen]

Originally Posted by emufan

happens in rtg and standard mode.
minimized window before game starts,
game exit -> winuae window in default size pops-up , black, pause mode.
can unpause and emulation continues

Do you have "pause when minized" ticked? If it continues normally after unpausing, whats the difference vs DX9 mode? Only the blank screen before unpausing?

EDIT: attach winuaelog.txt, thanks.

[Saghalie]

Originally Posted by Toni Wilen

It broke in b9, will be fixed in next. (Nothing was lost, description is still in
config file)

OK Thanks. I did notice that the descriptions were still there but didn't have any issues with b9 (unless I missed b9 somehow).

[emufan]

Originally Posted by Toni Wilen

Do you have "pause when minized" ticked? If it continues normally after unpausing, whats the difference vs DX9 mode? Only the blank screen before unpausing?

dx11 & 9 config -> misc -> minimized: paused & sound disabled ticked
if so, after game exit, winuae un-minimizes window and I get the paused black screen

dx11 & 9 config -> misc -> minimized: nothing ticked
if so, after game exit, winuae un-minimizes window and emulation is running

D3D with any "minimize" option, after game exit the winuae-toolbar-icon vanishs

[Toni Wilen]

D3D or DirectDraw?

Anyway, logs and config required. I can't duplicate none of these.

[Toni Wilen]

D3D11 2D sprite routines added (that was boring..), both OSD and RTG HW cursor is now supported.

If you had D3D11 mode problems, download winuae.7z, test it and attach log if weird things still happen.

[bladecgn]

Since beta, the description of the config is not shown anymore, i.e. the box stays empty.

[Saghalie]

Originally Posted by bladecgn

Since beta, the description of the config is not shown anymore, i.e. the box stays empty.

See a couple of posts above, Toni addressed this.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3600b11.7z
http://www.winuae.net/files/b/winuae64_3600b11.7z

Beta 11:

- Updated to MSVC 2017 15.5
- Config file Description field caching broke in b9.
- Ignore WM_DEVICECHANGE messages during first 2 seconds when WinUAE GUI opens for the first time. Some systems seem to send spurious WM_DEVICECHANGE at program startup.
- Simple box art/screenshot config file support. (See http://eab.abime.net/showthread.php?t=89014 for details.)
- Direct3D11 mode OSD/RTG HW cursor support. All basic features are now implemented. Improved vsync and custom shaders to do.
- D3D11 is now the default (=config file does not override it) if Windows 7 or newer.
- Entering and exiting GUI in D3D11 fullscreen mode restored wrong texture size.
- If Wait for Blitter is enabled and blit size makes no sense (larger than chip ram size), don't wait. (Fixes long delay in Vital / Mystic)

EDIT: D3D11 fullscreen won't work if DXGI 1.5+ is available.

[DamienD]

Originally Posted by Toni Wilen

- Simple box art/screenshot config file support. (See http://eab.abime.net/showthread.php?t=89014 for details.)

...and it works a treat!!!

Sooooo much better than only having a "list" of games / configurations; though my memory it quite good but not perfect.

As they say, a picture paints a thousand words

[mark_k]

General suggestion for betas: Could you also upload PDB symbol files for each executable?

[Amiga68k]

Toni,

In Beta 9 you introduced 'something' that made booting my configuration a lot quicker than before. This behaviour was also seen in Beta 10, but disappeared again in Beta 11.

I attached log files, but I find it hard to see any differences that might be related.

Slow (Beta 11) versus fast (Beta 10) is experienced after the log file mentions the Gary timeouts (for the second time) followed by

waiting_blits detected PC=00fad11a

After this line in the logging, slow (Beta 11) versus fast (Beta 10) can then be 'seen' when keeping an eye on the FPS counter (after the LoadModule reset). With Beta 11 this counter stays on 50, with Beta 10 this value fluctuates a lot and it even goes all the way up to 500 something (making the process quicker I assume).

Let me know if additional information is needed.

[mark_k]

Originally Posted by Toni Wilen

- If Wait for Blitter is enabled and blit size makes no sense (larger than chip ram size), don't wait. (Fixes long delay in Vital / Mystic)

Could that check possibly be incorrectly triggered when using a config with >2MB chip RAM (in which case a blit of >2MB might actually be valid)?

[Toni Wilen]

Originally Posted by mark_k

Could that check possibly be incorrectly triggered when using a config with >2MB chip RAM (in which case a blit of >2MB might actually be valid)?

It would not matter. Any program that uses >2M chip RAM is assumed to not be bad (write to blitter registers when blitter is already active) and would work with or without wait for blitter

[Toni Wilen]

Originally Posted by mark_k

General suggestion for betas: Could you also upload PDB symbol files for each executable?

No, there is no space for those huge files (17M compressed!)

Originally Posted by Amiga68k

In Beta 9 you introduced 'something' that made booting my configuration a lot quicker than before. This behaviour was also seen in Beta 10, but disappeared again in Beta 11.

Does it only happen in D3D11 mode? In plain A500/A1200 mode?

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3600b12.7z
http://www.winuae.net/files/b/winuae64_3600b12.7z

Beta 12:

- Direct3D11 fullscreen + DXGI 1.5 works again (b11)
- D3D11 fullscreen -> GUI -> change resolution/display parameters -> exit GUI does not cause blank screen anymore.
- 68020 memory cycle exact CPU speed slider is again partially working, CPU speed can be reduced but not increased.

[Amiga68k]

Originally Posted by Toni Wilen

Does it only happen in D3D11 mode?

Yes:

FPS counter (my specific configuration):

          D3D9  D3D11

Beta 10    50   >200
Beta 12    50     50

Originally Posted by Toni Wilen

In plain A500/A1200 mode?

I tried to narrow it down to a specific Chipset Extra setting and the increase in speed is only seen when choosing "A4000T" specifically. For others (including A4000 and A1200) FPS counter remains stable around the 50 figure. I don't see a way to replicate this with plain A500/A1200 mode.

Hope that helps... and perhaps the FPS counter remaining stable is the desired value compared to the value fluctuating? The quicker boot time was a nice side-effect though...

[DualC]

I saw eirlier in the messages 16 bit mode should work?, i have tried in latest beta 12 and my screen is black then i try to start it up in 16 bit mode.

But it works in 32 bit.