Resolution Autoswitch + Auto Integer Scaling: Screen stuck 25% below top of screen

[bladecgn]

I have a weird issue since upgrading form Os 3.9 to Os 3.1.4:


I am using resoution autoswitch and auto integer scaling. Before the aforementioned update, everything was fine. I was and stilll am using dblpal screenmode.



Now the screen gets stuck 25% below the top border of the screen. You can't drag it fully upto top position. You can drag it down though.


If I use Fullscrenn (Max) the screen ist not stuck 25% too far down.

If I disable auto integer scaling, it works, too.


This must have been a long standing issue., I have seen this effect at a friends place almost a year ago, too. He also was puzzled.


Her are both configs: config-nonworking (the config I have been using for years that now ceased to work) und config-workaround where I disabled resolution autoswitch.


What confuses me a bit that an update of the OS on the Amiga side triggered this. But it is clearly a WinUAE problem.


Toni, could you hae a look into this matter?

[Toni Wilen]

I don't have 3.1.4. I refuse to buy all of them when the only "gain" is ability to do free support for free software..

So nothing will happen until someone donates it. (with proof that it is not pirated!)

[bladecgn]

I am in for 10 Eur! Come on, two more willing to donate to Toni out there?

[Toni Wilen]

Log may also help.. (But I usually don't do anything complex if I can't duplicate it). EDIT: winuaelog.txt from both cases.


Note that 3.1.4 set must include ALL rom variants. All or nothing.

[Romanujan]

All ROM sets means 5 variants to purchase - about 150 EUR with VAT.

@Toni, couldn't we just send individual donations with comments like 'towards OS 3.1.4 purchase', and once you get the full amount you buy all sets on Hyperion page by yourself? This way you would be sure it is not pirated.

[DamienD]

I've donated a lot more to Toni in the past for various features / additions / bug fixes e.g. €400 just for the sterling work done with the boxart panel

...but I'm not going to donate towards this as it's something that I personally will never use.

Guys, if you really want 3.1.4 to be fully supported in WinUAE then it's not much money really...

Guess it depends on how badly you want this at the end of the day

[Toni Wilen]

Same "problem". I don't have any useful use for 3.1.4 and I also prefer to not to have anything to do with Hyperion (I prefer some other company that actually supports me with emulation related things), so donating money probably isn't going to fix this problem. And no NDAs!

[Zilog]

Originally Posted by Toni Wilen

Log may also help..

Hi Tony,
I have the same problem from long time, but i thought that problem was link a my video card, but now i think it’s a bug.

Now post my test and problem with classic software.


Problem: AutomaticScaling is “OK”, Automatic Intenger Scaling “NO”

Pc Video Card: Intel Grapghic 530 + Nvida GTX 960M (The problem is present both if use Intel , both if use use Nvidia.)

Resolution: 1920 x 1280

Winaue 4.0.1 (both 32 and 64 bit)

Directx Hardware 9 and 11

Amiga Emulated: Classic Base 1200

KickStart: 40.68

Os: Classic Workbenh 3.1

------------------------------------------------ I Thing the problem is in this part single o double line --------------------------------

Resolution AutoSwitch: On "PROBLEM ARE PRESENT"

Resolution AutoSwitch: Off (when autoswitch is active is not possible select)
Single Line "PROBLEM ARE PRESENT"
Double Line "OK"

--------------------------------------------------------------------------------------------------------------------------------------------

I have test both Workbench and both Games use Hi-Res.
Games use for test: _Pimball Fantasy (Intro screen have the screen in hi-res)
_Super Stardust AGA (Intro screen have the screen in hi-res)

In particular with Workbench 3.1 i have test all resolution:
Lo-Res Not-Interlaced Ok
Lo-Res Interlaced Ok

Hi-Res Not-Interlaced "PROBLEM ARE PRESENT"
HI-Res Interlaced "PROBLEM ARE PRESENT"

Super-Hires Not-Interlaced "PROBLEM ARE PRESENT"
Super-Hires Interlaced "PROBLEM ARE PRESENT"


if you don't wont resolve the problem beacause follow other developments, no problem.

Thanks again.

[bladecgn]

A friend of mine also had the same issue and it was on 3.1, so it's not 3.1.4 related this bug.

[Toni Wilen]

No logs -> nothing happens.

[Zilog]

Originally Posted by Toni Wilen

No logs -> nothing happens.

Ok Tony.
Sorry, the correct command for active log are winaue -log?


Thaks.

[Zilog]

Originally Posted by Toni Wilen

No logs -> nothing happens.

Ok. The log are in attache files,but with another bug for now.
When start the worbench set in Hi-res and the autoswitch is on, winuae autoswitch bad, in low-res.

[bladecgn]

Hey Toni, how can I help to resolve this issue? Maybe finding out the version the problems started?

Edit: I am sure it was working till not too long ago. Yet I tied all Versions, down to 3.1.0 and all habe the issue.

So my guess is the problem could be in the shader files. Yet I can't download an old Version of the shaders on the winuae page.

[Toni Wilen]

I have no idea anymore, there are too many confusing posts. For example Zilog's post don't seem to have anything to do with this. Or does it?

EDIT: and as usual. Remove everything unneeded one by one. It includes shaders.

[Zilog]

Originally Posted by Toni Wilen

I have no idea anymore, there are too many confusing posts. For example Zilog's post don't seem to have anything to do with this. Or does it?

EDIT: and as usual. Remove everything unneeded one by one. It includes shaders.

Hi Toni,
if shader is 2xSaI_sRGB.fx,Scale4x.fx ,CRT.D3D.fx...ecc....not.
I never use shaders for my test.


If you can help with other test i'am available.

[Toni Wilen]

Yes but I can't see anything common with OPs report in your report ("Now the screen gets stuck 25% below the top border of the screen", your screen is completely visible in screenshots). And nothing in OPs post mention anything about shaders.

[Toni Wilen]

Back to OPs problem..

Attach:

- screenshot (and if you have non-3.1.4 install, also working screenshot)
- winuaelog.txt (or minimum requirement: whole BEAMCON0=xxx... HSYNCEND=xxx part of the log which gets logged when mode switches)
- sys:prefs/env-archive/sys/screenmode.prefs
- sys:prefs/env-archive/sys/overscan.prefs

[bladecgn]

Here you are Toni.

The first screenshot is without Resolution autoswitch and double line mode. Pixel perfect display on 1920x1080 screen.

When I enable resolution autoswitch, line mode switches to single. it should stay at double. horizontal width is correct, vertical size is half of what it should be.


My display has 1920x1080 resolution. My screenmode ist DblPal 720 pixels wide but limited to 540 prixels vertical, in order to have it doubled tho 1440x1080 = pixel perfect display on 1920x1080.

[Leandro Jardim]

I also have a problem with resolution autoswitch and integer scaling, but this time with PAL HiRes screens, I'd like to talk with you Toni, if it would be possible to fix it too.

But I'd rather open my own thread after you've finished fixing the bug for bladecgn.

This is only a "little intermission" that will not happen again!

[Toni Wilen]

Originally Posted by bladecgn

Here you are Toni.

The first screenshot is without Resolution autoswitch and double line mode. Pixel perfect display on 1920x1080 screen.

When I enable resolution autoswitch, line mode switches to single. it should stay at double. horizontal width is correct, vertical size is half of what it should be.


My display has 1920x1080 resolution. My screenmode ist DblPal 720 pixels wide but limited to 540 prixels vertical, in order to have it doubled tho 1440x1080 = pixel perfect display on 1920x1080.

Quick workaround: switch off resolution autoswitch. I am not sure how you managed to make it work previously because resolution autoswitch has never been designed to work correctly in double scan modes.. (select lowest possible resolution/doubling without losing pixels)

VGA mode resolution autoswitch is designed to handle doublescan modes. (Keep aspect)