03 November 2019, 11:53 | #1 |
Registered User
Join Date: Jun 2015
Location: San Francisco, USA
Posts: 169
|
A2024 broken since WinUAE 4.0.0
Looks like A2024 has been broken since WinUAE 4.0.0. This config/hdf in 3.6.1 boots to WB screen on A2024 just fine. If I try it on 4.0.0 or later, only part of the screen is visible. It is still possible to drag windows around into invisible parts of the screen, so the whole screen "exists" but all of it cannot be seen. I didn't see any differences in the logs that stand out to me, but I included them anyway.
http://eab.abime.net/zone/A2024%20br...UAE%204.0.0.7z Have fun! |
03 November 2019, 18:37 | #2 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,611
|
Confirmed. A2024 is the only display port adapter that uses different positioning and size than native display. This mode is broken.
All others either replace native display or it works as an overlay. Size or position is not changed. |
08 November 2019, 11:03 | #3 |
Registered User
Join Date: Jun 2015
Location: San Francisco, USA
Posts: 169
|
I tested with latest alpha, looks like it's fixed now. Thanks Toni!
|
08 November 2019, 16:20 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,611
|
Yeah, it is fixed but not in "multimonitor" mode.
A2024 is a special case, it is sort of RTG like (static size and position, not hardwired to native display timing) but still is connected to native chipset display out. It probably should be emulated like RTG (window size getting automatically resized) but current framework does not support it. Maybe someday.. |
07 July 2024, 01:42 | #5 |
IRATA.ONLINE Operator
Join Date: Apr 2018
Location: Denton
Posts: 39
|
I need to report that A2024 does not work at all with WinUAE 5.3.0, in either 10hz or 15hz modes, and neither with explicitly setting A2024 or Autodetect in Video Port expansion. :-(
|
02 August 2024, 20:15 | #6 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,611
|
Works for me. You probably have "too adjusted" native mode settings, for example resolution must be at least Hires. (Lores won't work). Make sure display panel settings are default and try again.
I assume you get mostly yellow screen with flickering partial WB screen parts? (="non-decoded" A2024 display mode) |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Fastlane Z3 broken since WinUAE 3.6.0 | superfrog | support.WinUAE | 2 | 01 November 2019 17:53 |
Free: broken/incomplete Commodore A2024 high-res monitor | mark_k | MarketPlace | 0 | 22 January 2017 13:44 |
WinUAE 2.5.0 graphics API change issue with A2024 modes | mark_k | support.WinUAE | 2 | 09 December 2012 16:19 |
Trying to load a broken DMS will stall WinUAE | andreas | support.WinUAE | 3 | 12 December 2008 21:11 |
Is WinUAE Midi Broken ? | efmsynth | support.WinUAE | 4 | 01 December 2008 21:47 |
|
|