WinUAE 3.6.0 beta series

[kamelito]

I use my laptop closed with a usb keyboard.
I let WinUAE running all night, when I get back to it in the morning the mouse cursor is moving all over the screen. I don't remember any of this with previous beta.
Might be just a touch screen issue.

[Toni Wilen]

Originally Posted by Amiga68k

When I change Display settings of the first one to Full-window the mouse is 'off'. When clicking on the screen it 'activates' the click further to the right. Second symptom is I can move the mouse on the black parts of the screen on the left and right side.

Does http://www.winuae.net/files/b/winuae.7z fix it? (I assume it only happens in D3D11 mode?) If it still happens, does unchecking hardware sprite in RTG panel also "fix" it?

[Amiga68k]

Originally Posted by Toni Wilen

Does http://www.winuae.net/files/b/winuae.7z fix it?

Yes. Something strange here though. I still see the complete mouse pointer on the right black side of the screen with this version. Normally I would expect only seeing one dot and the right side of the pointer gone.

(I assume it only happens in D3D11 mode?)

Correct, just noticed though that in D3D9 the mouse pointer is too small then (Beta 15)...

If it still happens, does unchecking hardware sprite in RTG panel also "fix" it?

Yes, this also seems to 'fix' the issue in Beta 15.

[Toni Wilen]

Originally Posted by Amiga68k

Yes. Something strange here though. I still see the complete mouse pointer on the right black side of the screen with this version. Normally I would expect only seeing one dot and the right side of the pointer gone.

It is separate 2d sprite which is not clipped to edges of screen, it may look strange but it does not have functional differences. (and D3D9 had wrong size but I didn't change it yet)

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3600b16.7z
http://www.winuae.net/files/b/winuae64_3600b16.7z

Beta 16:

- Fixed statefile memory corruption if CPU is 68060. (Introduced when 68040/060 data cache support was added)
- Made SA-1000 and SA-2000 suboptions (like SupraDrives) SA-2000 is same as SA-1000 without $f0 ROM mapping. (Old SA-1000 configs must be re-created)
- GUI opened in D3D11 fullscreen mode: GUI minimization fixed.
- D3D11 mode fullscreen alt-tab, then clicking GUI reset button didn't restore fullscreen mode correctly.
- D3D11 scaled RTG mode hardware mouse cursor position and scaling fixed.
- D3D11 fullscreen RTG, enter GUI, exit GUI: there may have been long delay before fullscreen mode was restored.
- Handle D3D11 mode possible DXGI_ERROR_DEVICE_REMOVED error by retrying mode setup instead of stopping screen updates.
- Catweasel expansion caused hang (infinite autoconfig loop), it was not fully updated to new expansion system.
- SA-1000 Amax driver hang fixed (WD reset command didn't clear busy in all situations)
- Tape emulation now returns single file mark after last file before final end of file/blank state, no filemark returned if last file of index file does not have ending linefeed. Fixes Amix installation error if last file on tape (X11r5src) was selected for installation. When writing, multiple filemarks between files are supported.

[DamienD]

Cheers Toni

When is 3.6.0 going to be released?

[Toni Wilen]

Sometime in Janury 2018.

[DamienD]

All good Toni; it's ready when it's ready

...just hanging for it, but that's cool, I can wait however long necessary until you think it's time.

Going to be a cracking release (not that any older version weren't)

[Retro-Nerd]

- D3D11 mode fullscreen alt-tab, then clicking GUI reset button didn't restore fullscreen mode correctly.

Alt-Tab doesn't work for me with D3D11 in fullscreen mode. The screen stays black and i can't switch to other running tasks (also black screen). Do you need logs?

[Toni Wilen]

Originally Posted by Retro-Nerd

Alt-Tab doesn't work for me with D3D11 in fullscreen mode. The screen stays black and i can't switch to other running tasks (also black screen). Do you need logs?

Works fine here. Does GUI still open normally (desktop appears normally and then fullscreen re-activates after exiting GUI)

winuaelog.txt and config probably needed.

[Retro-Nerd]

I probably shouldn't have quoted the part with the GUI. Sorry.

Well, Alt-Tab doesn't work for me at all. Screen stays black.

[Toni Wilen]

Originally Posted by Retro-Nerd

I probably shouldn't have quoted the part with the GUI. Sorry.

Well, Alt-Tab doesn't work for me at all. Screen stays black.

Lets simplify your config first: remove all harddrives: does it still happen in "insert disk" screen? Then disable shaders, still happening?

How did you quit winuae after creating the log? It looks like log is truncated, if you killed it (via task manager etc), it will cause truncated log, use -logflush command line parameter to force flush after each log line.

And finally, attach config file.

[Retro-Nerd]

1. Happens with a more complex WB setup or a simple Amiga 500 disk setup.
2. Happens with shaders enabled/disabled.
3. Yes, i had to quit WinUAE via task mananger. There is no other way to quit it. The GUI isn't accessible and the usual short keys don't work. Only the windows mouse arrow is visible over a black screen.

[Amiga68k]

My 1024x768 windowed session is 1 pixel too high in the window: i miss the top line and the bottom line is black.

[Toni Wilen]

Originally Posted by Retro-Nerd

1. Happens with a more complex WB setup or a simple Amiga 500 disk setup.
2. Happens with shaders enabled/disabled.
3. Yes, i had to quit WinUAE via task mananger. There is no other way to quit it. The GUI isn't accessible and the usual short keys don't work. Only the windows mouse arrow is visible over a black screen.

Still waiting for logflush log and config file

Originally Posted by Amiga68k

My 1024x768 windowed session is 1 pixel too high in the window: i miss the top line and the bottom line is black.

Totally not enough information. (Usual information must be included + screenshot from working and non-working case)

[Amiga68k]

My 1024x768 windowed session is 1 pixel too high in the window: i miss the top line and the bottom line is black.

Originally Posted by Toni Wilen

Totally not enough information. (Usual information must be included + screenshot from working and non-working case)

I thought I could do it with one sentence this time, sorry

It seems this has been introduced in Beta14, please find screenshots of Beta13 and Beta16 attached. Screenshots display a part of the top right and the bottom right of the screen. Attached you will also find the log files.

Some extra testing done, issue is also seen in Full-window and Fullscreen mode. Issue not seen in Beta14 D3D9 mode.

(The winuaelog files can be found in the next post due to the number of attachment restrictions)

[Amiga68k]

The winuaelog files that are part of the previous post attached.

[Retro-Nerd]

Still waiting for logflush log and config file

Ah, sure.

[Toni Wilen]

Originally Posted by Retro-Nerd

Ah, sure.

This is strange, still nothing, it looks like winuae never got any messages that winuae is not anymore active.

Does anything change if you do:

1) have at least one other application running (even windows explorer) before starting winuae.
2) change buffering to double.

Originally Posted by Amiga68k

My 1024x768 windowed session is 1 pixel too high in the window: i miss the top line and the bottom line is black.

Fixed.

[Retro-Nerd]

Does anything change if you do:

1) have at least one other application running (even windows explorer) before starting winuae.
2) change buffering to double.

No, i'd tested this yesterday too. Also found nothing suspicious enabled in the latest Radeon driver installed, and D3D9 works perfectly fine in fullscreen.

I can switch through all open tasks with Alt-Tab, seeing the tiny preview pictures. But all shows a black screen when selected. Not really sure if the switched task is really open due to the black screen. Very strange indeed.