WinUAE 2.8.0 beta series (Was 2.7.1)

[thomas]

Originally Posted by Toni Wilen

Does it happen in 2.7.0?

No.

Does it happen if you use latest beta but set superhires in display panel before starting emulation?

Yes. (dump attached)

Does it happen in DirectDraw mode too?

No.

[Toni Wilen]

http://www.winuae.net/files/b/winuae.zip should fix the crash. (fill border area end value is length, not absolute end position..)

[thomas]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.zip should fix the crash.

Yes, it does indeed.

[bladecgn]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.zip possibly fixes it. (This is yet another worked accidentally.. Filters aren't really designed for programmed modes)

Now the image is caled correctly, yet the screen starts vertically too much down, it starts at about 1/3rd of the screen measured from the top so some parts of the bottom are missing.

[Toni Wilen]

Originally Posted by bladecgn

Now the image is caled correctly, yet the screen starts vertically too much down, it starts at about 1/3rd of the screen measured from the top so some parts of the bottom are missing.

What about now? (if not correct, attach winuaelog.txt)

[bladecgn]

Originally Posted by Toni Wilen

What about now? (if not correct, attach winuaelog.txt)

It is displayed correctlyy now. Thank you Toni!

When switching resolutions the screen flickers shortly a few times and displays the graphics misscaled for a tiny short period. This did not happen in 2.7.0, it is not much of a problem but I thought I'd report it anyway.

[Toni Wilen]

Originally Posted by bladecgn

It is displayed correctlyy now. Thank you Toni!

When switching resolutions the screen flickers shortly a few times and displays the graphics misscaled for a tiny short period. This did not happen in 2.7.0, it is not much of a problem but I thought I'd report it anyway.

It is caused by new programmed mode specific autoresolution feature that selects matching hires/shres mode to prevent too wide or too narrow programmed mode display (including wrong aspect ratio).

I probably add option to disable it but leave it enabled by default.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2800b17.zip

Beta 17:

- Debugger breakpoints work again. (b14)
- Full CPUSHA/CPUSHL/CPUSHP disassembly implemented.
- Integer scale mode compatibility improved with programmed display modes.
- Integer scale mode changes Filter panel zoom slider range to -99 to 99 and is used to adjust integer scaling calculation. For example -10 means if next largest scaling factor is selected even if display height is 10% too big to fit normally. (This was implemented already but it didn't work properly)
- Fixed fill_line() top/bottom background line drawing buffer overflow in some programmed modes.
- Some programmed modes had single short background colored line in left horizontal blanking area.
- Command line (or icon doubleclick) loaded config didn't reset previously loaded config (default.uae, if it existed)
- Emulated more Fat Gary address regions that are unmapped (CIA is same as Gayle, upper 32k in clock space and Gary register space are unmapped, 0xdf0000-0xdf7fff is also unmapped)
- Emulate Fat Gary invalid address space access timeout if Gary timeout bit is set, first 50 timeouts are always logged. To prevent last moment stupid bugs or bug reports, delay is not yet enabled.

[amilo3438]

Hi Toni,
I have just found that the A500 demo "The end by Trilobit" stop to work somewhere from 2710 beta 8 ?! (A500 ECS 0.5+0.5mb)

p.s.
tested some of demos, not all, from "Already fixed" category so hope the other demos are also still working fine ... unfortunately doesnt have lot of free time as before (real life) so cant help much in testing demos, sorry.

[Leandro Jardim]

With the following config inside the zip, when I run A/NES to play a NES game with a 320x240 CGX screen on a 1920x1080 Windows resolution, the screen aspect ratio is wrong, I suppose the aspect ratio is not changed at all.

And when I use a 1600x1200 CGX mode with A/NES no screen is shown.

This bug isnt new but isnt corrected yet.

[Toni Wilen]

Originally Posted by amilo3438

Hi Toni,
I have just found that the A500 demo "The end by Trilobit" stop to work somewhere from 2710 beta 8 ?! (A500 ECS 0.5+0.5mb)

If you check b9 change log, you'll see what you need to do and why it is done.

[Toni Wilen]

Originally Posted by Leandro Jardim

With the following config inside the zip, when I run A/NES to play a NES game with a 320x240 CGX screen on a 1920x1080 Windows resolution, the screen aspect ratio is wrong, I suppose the aspect ratio is not changed at all.

And when I use a 1600x1200 CGX mode with A/NES no screen is shown.

This bug isnt new but isnt corrected yet.

Does not seem to have anything to do with emulation. 1152x900 resolution is requested, not 320x240 or similar. A/NES probably tries to guess some larger resolution but fails with "strange" PC resolutions.

Do you have 320x240 configured in CGX?

[amilo3438]

Originally Posted by Toni Wilen

If you check b9 change log, you'll see what you need to do and why it is done.

b9 ?!

2700b9 -> http://eab.abime.net/showpost.php?p=...&postcount=206

or

2710b9 -> http://eab.abime.net/showpost.php?p=939581&postcount=83


I am afraid you forgot that the CIA tod bug option in Advanced chipset is set to be always ON in newer versions, so there should be no problem for this demo ... but ...

starting from 2710b8 got an guru after a while (btw. last version where it still works fine is 2710b7)

Cheers

[Leandro Jardim]

Originally Posted by Toni Wilen

Do you have 320x240 configured in CGX?

Yes, I do.

EDIT: A/NES screen mode requester seems to be "bogus", as it never hilights the screen mode that I choose before. Yes, I always choose 320x240.

[Toni Wilen]

Originally Posted by amilo3438

starting from 2710b8 got an guru after a while (btw. last version where it still works fine is 2710b7)

You said "not working" which is always bad idea -> I thought it was that usual old issue. "Not Working" never works.

Demo has horrible code (probably explain why it says "Ei toimi AGAlla" which is finnish for "does not work with AGA") that only works accidentally. ADD.W D0,$DFF066 is not that good idea.. (or writing to blitter registers, then waiting for blitter and finally writing to BLTSIZE..)

Tweaked to work again but behavior of reading write-only custom register is not fully known. (Value that gets written to register is known, value that CPU gets back is not known)

Undefined emulation parts can and will break, even if it appeared to work previously. Fortunately these kinds of situations are rare. (Similar to writing to blitter registers while blitter is active, behavior is not known)

[Toni Wilen]

Originally Posted by Leandro Jardim

Yes, I do.

EDIT: A/NES screen mode requester seems to be "bogus", as it never hilights the screen mode that I choose before. Yes, I always choose 320x240.

Still not my problem because mode that hardware gets is not 320x240, or even any integer multiple of 320x240.

[amilo3438]

Originally Posted by Toni Wilen

Tweaked to work again but behavior of reading write-only custom register is not fully known. (Value that gets written to register is known, value that CPU gets back is not known)

Well, regarding the "behavior of reading write-only custom register is not fully known" is maybe not quite true ... why ?!

On an real amiga is possible to check what values written in some write-only custom register will be returned after reading and thus f.e. can be created some table for every write-only custom register, right ?!

It is similar to "black box"; we dont know what is inside and how it function but we know what values we got.

Originally Posted by Toni Wilen

You said "not working" which is always bad idea -> I thought it was that usual old issue. "Not Working" never works.

Thanks for fixing the demo, but also I never said it is "not working" ?! ... what I said is its "stop to work somewhere from 2710 beta 8", right ?

Cheers

[Toni Wilen]

Originally Posted by amilo3438

Well, regarding the "behavior of reading write-only custom register is not fully known" is maybe not quite true ... why ?!

On an real amiga is possible to check what values written in some write-only custom register will be returned after reading and thus f.e. can be created some table for every write-only custom register, right ?!

It is similar to "black box"; we dont know what is inside and how it function but we know what values we got.

It does not work. Result depends on previous state of system and not just last cycle. You get different results if you repeat same test multiple times.

Result only seems to be stable if previous cycle was idle cycle (no cpu and dma accesses), most likely result is FFFF in that case.

It seems there is some low level chip behavior which causes some kind of semi-random AND logic behavior. Result usually looks like it last bus value AND last value in buffer chip between CPU and Agnus.

It is most likely chip level undefined state, reading chip outputs when chip is in high-z mode or similar, it depends on internal design.

Thanks for fixing the demo, but also I never said it is "not working" ?! ... what I said is its "stop to work somewhere from 2710 beta 8", right ?

Cheers

Yes you did. "not working" means problem was not described. It could mean it stopped booting, it crashes before it starts, it has bad colors, bad graphics, sound problems, anything.

Something like "it now crashes with graphics corruption before camera part" would have worked to get some information and to confirm I have duplicated exact same problem.

[amilo3438]

... so its the same story here then:

Originally Posted by Toni Wilen

If you check b9 change log, you'll see what you need to do and why it is done.

the winuae version is not defined, it could mean any b9, right ?!

cheers


p.s. Thanks for detail explanation.

btw. What still stays unexplained is why were demo programmers use such "undefined" parts in their demos; by accident or with a reason ?!

[mc6809e]

I miss in 2.8.0 the ability to use F12 in Amiga Forever to bring up the WinUAE config screen. Is there anyway to bring this back? Works okay under 2.7