WinUAE v3.3.0 - AGA - Screen "tearing"

[DamienD]

Hello there Toni,

Would you mind having a read of posts #71 - 74 in this thread "[unreleased] Amiga games...":

http://eab.abime.net/showthread.php?t=83574

If needed I can do any tests that you require on previous versions and provide logs etc.

[Toni Wilen]

Seems normal. The later the winuae version, the faster fastest cpu mode has become in relation to chipset.

[DamienD]

I'm not sure if I understand your answer Toni

I'm using the exact same configuration in both v3.3.0 and v3.0.0. It doesn't matter if I use the "hard drive install on a Classic WB 3.1 .HDF" or my custom made ".ADF".

If I jump around / firing in different directions (hold fire for a few seconds) the screen tear is definitely present in WinUAE v3.3.0 while not v3.0.0...

Can I provide any more info / logs / tests etc. if needed?

[Toni Wilen]

It was the best answer without more information. You mentioned 68040 and so on in your post which usually equals fastest possible.

You need to narrow it down to specific version, preferably to specific beta version. Statefile (without harddrives) that can be used to instantly see the problem is even better. Logs rarely help in these kinds of problems.

[DamienD]

Originally Posted by Toni Wilen

It was the best answer without more information. You mentioned 68040 and so on in your post which usually equals fastest possible.

You need to narrow it down to specific version, preferably to specific beta version. Statefile (without harddrives) that can be used to instantly see the problem is even better. Logs rarely help in these kinds of problems.

Definitely don't have "68040" set. I'm using a standard "Quickstart A1200 - 2MB Chip & 4MB Fast RAM configuration"

Have tested with v3.1.0 (no issues) and also with v3.2.0 (issue is there just like v3.3.0).

Ok, using my custom .ADF (which is the same as when using a hard drive install on a Classic WB 3.1 .HDF) I will create a statefile and attach my friend. Much appreciated for your time in advance

[DamienD]

Here you go Toni: http://download.abime.net/zone/ACSYS.uss

...not idea as to why it's so large in comparison to usual Save States.

Anyway, let me know if there's anything else I can do?

[Toni Wilen]

It is same as: http://eab.abime.net/showthread.php?t=83080
(so there is at least 2 programs now)

[DamienD]

Oh, I see. Thanks for looking into it

Well, let me know if you want me to test anything more in order to assist you with working out the cause

[DamienD]

Originally Posted by Toni Wilen

It is same as: http://eab.abime.net/showthread.php?t=83080
(so there is at least 2 programs now)

From reading above people talk about the issue when using "default" scaling and the issue goes away when using "auto" scaling.

I don't use any scaling:



Tested again:

... v3.0.0 [no issue]
... v3.1.0 [no issue]
... v3.2.0 [issue]
... v3.3.0 [issue]

So the bug crept in somewhere between the v3.1.0 and v3.2.0 release.

Can you provide the betas URLs so that I can test all between the above range to find out when it started?

[DamienD]

Ok have done more testing now with beta versions.

... winuae_3200b18.7z [no issue]
... winuae_3200b19.7z [issue]
... winuae_3200b20.7z [issue]
... winUAE3200.zip [issue]

Bug starts from "winuae_3200b19.7z"; hope this helps Toni and do let me know if there's anything else I can do

[Toni Wilen]

I said in above URL that it is already fixed.

[DamienD]

What? In this post back from the 12th of June:

Originally Posted by Toni Wilen

"Just do <something>" is not acceptable. "3.x.x" is even worse, it would have been nice to have smaller version range.. (For example it does not happen with 3.1!)

</rant>

Fixed (or more like worked around).

Ok; let me find you're latest WinUAE beta file and test

[DamienD]

Ok, just tested http://www.winuae.net/files/b/winuae.7z dated today and all is good

Thank you kindly Toni