Kick off 2 flickering

[msayed1977]

Hi Toni,
I would like to inform you that the AGA problem is still there.
I do not know whether you targeted it with your last Blitter DMA change in beta 13.
Thank you.

[msayed1977]

- Adjusted read-write-only-custom-register-side-effect in AGA mode. (Artificial Paradise / NGC missing loading screen, does stupid bset #9,$dff104 which, depending on previous accesses, either writes $0200 or "random bits" OR $0200)

I do not want to annoy you, but like to inform you that this fix did not fix my problem.
I would like to thank you for your continuous progress in developing WinUAE.

EDIT: I would like to remind you that the bug doesn't happen with AGA only. It happens also with ECS Agnus and Full ECS.

[Toni Wilen]

Originally Posted by msayed1977

I do not want to annoy you, but like to inform you that this fix did not fix my problem.
I would like to thank you for your continuous progress in developing WinUAE.

EDIT: I would like to remind you that the bug doesn't happen with AGA only. It happens also with ECS Agnus and Full ECS.

Create OCS and ECS statefiles, do they have same problem? (Use A500 quickstart, OCS = 1.3 most common, ECS = 1.3 ECS 1M). Switching modes on the fly isn't always same as starting from scratch. Quit emulator before switching configurations. (btw, I am starting to think that this is normal and would happen on real hardware too)

Mentioning AGA and using weird config = much less interest.. Don't do it unless it is required

[msayed1977]

Originally Posted by Toni Wilen

Create OCS and ECS statefiles, do they have same problem? (Use A500 quickstart, OCS = 1.3 most common, ECS = 1.3 ECS 1M). Switching modes on the fly isn't always same as starting from scratch. Quit emulator before switching configurations. (btw, I am starting to think that this is normal and would happen on real hardware too)

Mentioning AGA and using weird config = much less interest.. Don't do it unless it is required

Using both Quickstart configs you've mentioned, the problem is gone. I've tried them in default compatibility and best compatibility.
I've also found that with my weird config but without CE, the problem is almost gone.
With WinFellow and similar config, the problem does not happen.
I think the problem is my weird configs with WinUAE.
I think there is no need for the state files now, as both of them are identical in having no problems.
If you'd like to have the state files after all, tell me and I'll attach them immediately.

[msayed1977]

I've also found that with my weird config but without CE, the problem is almost gone.

Similar to what happens with 2.6.0 beta 5.

[Toni Wilen]

Working with quickstart config means there is no problem. Weird config = I don't care. There is no real Amigas that have these kinds of "weird" configs so no one can know if it should happen or not. The end.

[msayed1977]

Originally Posted by Toni Wilen

Working with quickstart config means there is no problem. Weird config = I don't care. There is no real Amigas that have these kinds of "weird" configs so no one can know if it should happen or not. The end.

Thank you, Toni for your care and effort in that mysterious problem. I think it is a pseudo problem.

[msayed1977]

Again Toni,
If it matters you,
After many many tests, I found that it was not my weird configuration.
I managed to determine the problem exactly.
The bug happens always with AGA, with any config.
About ECS Agnus and Full ECS:
It happens if the chip RAM is more than 1M.

The problem is not with kickstarts, because WinFellow runs ECS Agnus with more than 1M with the same kickstart without any problems.

[dlfrsilver]

Forget winfellow, Winuae is the more accurate emulator out there

[Toni Wilen]

Originally Posted by msayed1977

Again Toni,
If it matters you,
After many many tests, I found that it was not my weird configuration.
I managed to determine the problem exactly.
The bug happens always with AGA, with any config.
About ECS Agnus and Full ECS:
It happens if the chip RAM is more than 1M.

The problem is not with kickstarts, because WinFellow runs ECS Agnus with more than 1M with the same kickstart without any problems.

Then it is easy to test with real A500 with 2M expansion (or A500+). Attach your adf + instructions how to duplicate it.

(Ignore fellow, it does not emulate any special situations or undocumented features)

[CFou!]

Originally Posted by dlfrsilver

Forget winfellow, Winuae is the more accurate emulator out there

i am agree

WinUAE is 'Ultimate Amiga Emulator' for me too

[msayed1977]

Originally Posted by Toni Wilen

Then it is easy to test with real A500 with 2M expansion (or A500+). Attach your adf + instructions how to duplicate it.

(Ignore fellow, it does not emulate any special situations or undocumented features)

Instructions:
1. Use Kickstart 1.3.
2. Start Single Game.
3. Choose "1 Player" game.
4. After the players enter the field, they will align in a row.
5. With WinUAE, it is very clear that the players will blink very fast.
6. After that, the bug is less clear in the progresses of the match.

With WinUAE, you can duplicate that easily with the default WinUAE configuration using ECS Agnus with more than 1M chip ram. I have tested that using Kickstart 1.3.

If you want any further information, please ask.
Thank you, Toni again for your great effort.

[msayed1977]

With WinUAE, you can duplicate that easily with the default WinUAE configuration using ECS Agnus with more than 1M chip ram. I have tested that using Kickstart 1.3.

I have forgotten to say that you should also use Cycle-Exact emulation, as the bug is almost gone without using Cycle-Exact (as I mentioned before).

[Mclane]

Unless there's some part you have not mentioned I ran it on the latest beta and there was zero flickering, and yes it was cycle exact?

Are there other settings you didn't mention or are you using some non standard config?

[msayed1977]

Originally Posted by Mclane

Unless there's some part you have not mentioned I ran it on the latest beta and there was zero flickering, and yes it was cycle exact?

Are there other settings you didn't mention or are you using some non standard config?

I use Windows XP Pro SP3 with nVidia GeForce display card.
As I mentioned before, I use WinUAE default settings.
I cannot remember anything else to say.
BTW, I use Direct3D not DirectDraw.
As I can remember, I had the same problem with my old Pentium 4 computer with also nVidia display card, running Win XP Pro.
If you would like to ask me for any further detail, I am ready.

[dlfrsilver]

can you please post your winuae config file ?

EDIT : i have just tested with an A500, OCS, 512kb RAM, CPU "CE" + "Wait blitter" ticked, and the game works normally with the very latest winuae.

[Toni Wilen]

All kickoff 2 posts moved from beta thread.

Only thing this needs is real hardware test with 2M Chip RAM installed. Everything else is 100% irrelevant.

[msayed1977]

Originally Posted by dlfrsilver

can you please post your winuae config file ?

EDIT : i have just tested with an A500, OCS, 512kb RAM, CPU "CE" + "Wait blitter" ticked, and the game works normally with the very latest winuae.

As I said before, OCS and ECS Denise work perfectly. Also the problem happens with ECS Agnus, only when the chip ram is more than 1M.
Use the default settings of the emulator, but match the criteria I mentioned in my earlier posts.

[Mclane]

Yes but you are saying use 1.3 with ECS....

Its not an official mix..

[dlfrsilver]

some amiga 500, in very latest batches used ECS.

But kick off 2 is an OCS game / 512kb / KS1.3 and nothing else.

EDIT : tested on A500, ECS and 2mb chip, the sound is not working correctly

EDIT 2 : tested on A500, OCS, 512kb, game and sound work correctly

EDIT 3 : tested on A500+, KS2.0, 2Mb ram, game work correctly, sound is not working correctly.