WinUAE v3.0.0 - 720 x 576 issue
 

Hello there Toni,

Long time no speak; hope things are good?

Been playing around with WinUAE v3.0.0 and have come across a slight bug (I think) that's driving me crazy.

Basically I am using Windows 7 64-bit and have an in-build Intel HD Graphics 3000 card (+ NVidia GeForce GT 540M). WinUAE uses the Intel HD Graphics 3000 card by default.

Anyway, my issue is as follows:

• I have created a "custom" video resolution of "720x576" for Intel HD Graphics 3000 card and in Windows can swap to this successfully.
• If I have a game set to use "Fullscreen" / "720x576" WinUAE don't swap over to this resolution.

I've tried everything I can think of but can't get it working...

As another test, I used my very old Windows XP SP3 laptop with WinUAE v1.0.0. A custom video resolution of "720x576" has been created also. Games set to use "Fullscreen" / "720x576" WinUAE swap over to this resolution without issue and are displayed successfully in WinUAE.

Any ideas?

Kind regards,
Damien.

Ooops...

I should probably mention that I also tested WinUAE v3.0.0 on the old Windows XP SP3 laptop with the exact same game / configuration (that works with WinUAE v1.0.0) in "Fullscreen" / "720x576" and WinUAE v3.0.0 doesn't swap over correctly here either.

Logs? Possibly also DirectDraw<>D3D difference. How did you create the resolution? If some 3rd party utility, there is no guarantee resolution is fully supported.

Sorry about that; of course I should attach logs. Will get them once I'm home tonight.

With my Windows 7 64-bit laptop / in-build Intel HD Graphics 3000 card I used the Intel HD Graphics utility to create the custom 720 x 576 resolution. Windows can switch to this successfully. WinUAE v3.0.0 just seems to ignore it in fullscreen mode though and goes to a resolution of 640 x 480. Even if I set a resolution of 800 x 600 (which is natively supported via the graphics card) WinUAE v3.0.0 still goes to a resolution of 640 x 480 in fullscreen mode. I can't test WinUAE v1.0.0 on this laptop as it crashes upon startup...

With Windows XP SP3 laptop I used PowerStrip to create the custom 720 x 576 resolution. Again WinUAE v3.0.0 just seems to ignore it in fullscreen mode though and goes to a resolution of 640 x 480. If I test with WinUAE v1.0.0 though the custom 720 x 576 resolution works perfectly.

Hello Toni,

Logs are attached; thank you in advance for taking a look.

Kind regards,
Damien.

Hello Toni,

I've been busy testing older versions of WinUAE to see in which version it last worked.

Anyway, the last version that works with a resolution of 720 x 576 on both my Windows 7 + Windows XP laptops is: v2.3.0

Hopefully that helps you track down what's going on.

I can't see anything wrong in the log, resolution is correct and so on..

EDIT: start from clean config (make sure default.uae does not exists in configurations), select for example A500 quickstart, then select resolution, start it. Any difference?

Yeah I had a quick look also and could see the resolution listed:

and I also saw this:

Is the above correct though; I don't have 800x600 listed anywhere and it seems to change to a resolution of 640x480 in Fullscreen mode? Windowed mode gets correctly displayed as 720x568.

This is what's in the config file:

Windowed / Full Screen WinUAE v2.3.0 definitely works on both laptops perfectly with this resolution. Any versions afterwards don't unfortunately ;-(

I also have the latest video card drivers installed on my Windows 7 laptop.

Is there anything else I can do to help you track down the issue? Would be cool to be able to use the latest version of WinUAE with this resolution on my laptops.

Just saw your edit. Will try and get back to you ;)

Unfortunately that didn't make any difference Toni.

It still seems to be using a Fullscreen resolution of 640x480 even though 720x576 is selected.

Anything else I can try / test?

If 2.3.0 is last working, please test which 2.3.1 beta introduced the problem.

http://www.winuae.net/files/b/winuae_2310bX.zip where X = 1 to 13.

Of course, will do ;)

I did test the following versions and it was broken in all of these:
... v2.4.0
... v2.3.3
... v2.3.2
... v2.3.1

Just tested "winuae_2310b1.zip" and the problem is there.

I guess you don't want me to test "winuae_2310b2.zip" to "winuae_2310b13.zip"?

There is nothing interesting in 2310b1, display mode enumeration is slightly changed but nothing major..

Attach both logs files from 2.3.0 and 2.3.1b1, perhaps there is some differences. Use exact same config.

Ok will do Toni.

Just so you can see what I'm talking about I took a few screenshot:

WinUAE 2.3.0 with a fullscreen resolution of 720x576:
... see attached "WinUAEV2.3.0___Banshee_720x576.png"

WinUAE 3.0.0 with a fullscreen resolution of 720x576:
... see attached "WinUAEV3.0.0___Banshee_720x576.png"

WinUAE 3.0.0 with a fullscreen resolution of 640x480:
... see attached "WinUAEV3.0.0___Banshee_640x480.png"

Alrighty, both logs files attached; 2.3.0 and 2.3.1b1.

From looking at the comparison screenshots I uploaded it looks like the resolution is changing correctly.

What seems to be happening (with my limited knowledge) is that the image rendered is been moved / scaled or something...

I don't have anything ticked that would cause this and am using the same configuration in all versions.

Check Filter panel. If you see checkbox that says "Default", change it to "No scaling".

OMG; that's it Toni. It was set as "Default"...

Regarding the above, it's strange how the same config behaved differently in 2.3.0 to later versions.

Anyway; I'm very happy. Thank you so much and so sorry for also wasting your valuable time.

It was changed because for most "normal" users scaled display is better than huge borders.

(btw, it is good idea to check the actual resolution before assuming resolution is wrong :))

Will do and again thank you for taking the time to investigate and give me a solution.

I guess the real issue is that I was trying to use my 500+ configs from WinUAE v1.0.0 --> WinUAE v3.0.0. Of course you have made many improvements to WinUAE over the past 8+ years and I didn't realise these would effect my original configs in that way. Anyway ;)