WinUAE 4.9.1 beta series

[Toni Wilen]

Originally Posted by DZh

In full screen mode, the cursor moves along with the bitplane (normal). In the window mode, when RIA changes (and enable and disable), the cursor rises to several tens of pixels up.

You need to include much more details because I have never seen anything like this (and I always use windowed mode), only bug I saw (and which was fixed few moments ago) was "1/2" scanline sprite offset (sprite started in odd line when it should have started in even line).

EDIT: and is it "real" offset (as in mismatch for example between sprite position and WB icons, or left clicking on WB screen and dragging, dragging lines are out of alignment with mouse pointer = this is a problem), or just some unexpected mouse event coming from somewhere that moves the mouse a bit (=this is not a problem).

[DZh]

EDIT: and is it "real" offset (as in mismatch for example between sprite position and WB icons, or left clicking on WB screen and dragging, dragging lines are out of alignment with mouse pointer = this is a problem), or just some unexpected mouse event coming from somewhere that moves the mouse a bit (=this is not a problem).

The situations you described do not cause problems, everything works well.

[twitek]

Hi,

I'm using Gamebase Amiga (2.3) to start the WHDload version of Chase H.Q.
WinUAE 4.9.0 beta 34 is working fine (screenshot 1)
starting WinUAE 4.9.0 beta 35, the screen looks wrong (screenshot 2).
Tested with several newer version including 4.9.0 and 4.9.1 beta 5, they all look wrong.
Tested with several other WHDLoad games in Gamebase, they all seem to have this problem.

Best regards,
Thomas

[Toni Wilen]

Originally Posted by twitek

Hi,

I'm using Gamebase Amiga (2.3) to start the WHDload version of Chase H.Q.
WinUAE 4.9.0 beta 34 is working fine (screenshot 1)
starting WinUAE 4.9.0 beta 35, the screen looks wrong (screenshot 2).
Tested with several newer version including 4.9.0 and 4.9.1 beta 5, they all look wrong.
Tested with several other WHDLoad games in Gamebase, they all seem to have this problem.

Best regards,
Thomas

Strange.. Could you attach uae config file and s:whdload.prefs.

EDIT: I used whdload.uae from GBA 2.3 but Chase HQ still works fine.

EDIT2: probably too weird config combined with CPU speed adjustment.

[R-TEAM]

Works fine on 4.9.1 beta5

[Toni Wilen]

https://download.abime.net/winuae/fi...nuae_4910b6.7z
https://download.abime.net/winuae/fi...ae64_4910b6.7z

Beta 6: Possibly becomes final 4.9.1 (beta tags removed).

- Use pre-430b5 lagless vsync behavior by default if Windows 7. -beamrace 0 command line will force 430b5+ behavior and -beamrace 1 will force pre-430b5 behavior.
- ECS Denise CSYNC blanking fixes. Denise ignores vblank strobes when deciding blanking if EXTBLKEN=1.
- Remove interlace artifact option enabled: bitplanes and sprites had 1 scanline offset. (introduced in some 490 beta)
- NTSC mode and software switch to PAL: display was incorrectly vertically stretched.
- Integer scaling only worked correctly if horizontal and vertical resolution matched (correct aspect ratio). Now also other combinations work correctly (for example superhires + any or lores + doubled)

[twitek]

Here are the config files.

[Toni Wilen]

Originally Posted by twitek

Here are the config files.

Config file has %parametername% things that get replaced with something by GBA. You need to run the game and then press F12 and save the config file to get the "real" config file.

[twitek]

Here's the saved config file.

[timeslip1974]

Hi Everyone, Im developing a new game via Blitz Basic and have been developing it for the last 12 months via winuae 4.4.0 to no problems, I did try out the 4.9 beta version had a few random freeze ups, figured well its beta software and rolled back to 4.4 - Now over the last few days Ive released the demo of it ( https://timeslip1974.itch.io/black-dawn-techomage-demo ) and multiple people using 4.9 have all experienced random seezeups. Ive tested it for 12 months on 4.4.0 also on Amiga Forever,fs-uae and on real hw to no such problems which obviously points to an issue with the Beta version. my question is has anyone else had issues with it ? Obviously if whatever the issue is carries over to the full release thats going to cause me and my publisher many headaches......

[Toni Wilen]

Originally Posted by timeslip1974

Hi Everyone, Im developing a new game via Blitz Basic and have been developing it for the last 12 months via winuae 4.4.0 to no problems, I did try out the 4.9 beta version had a few random freeze ups, figured well its beta software and rolled back to 4.4 - Now over the last few days Ive released the demo of it ( https://timeslip1974.itch.io/black-dawn-techomage-demo ) and multiple people using 4.9 have all experienced random seezeups. Ive tested it for 12 months on 4.4.0 also on Amiga Forever,fs-uae and on real hw to no such problems which obviously points to an issue with the Beta version. my question is has anyone else had issues with it ? Obviously if whatever the issue is carries over to the full release thats going to cause me and my publisher many headaches......

Not enough information is obviously the first reply.

But if it is "simple" freeze, just create statefile and I'll take a look. Use config without harddrives and no unneeded expansions.

But first MUCH more information is needed.

(and there is no proof it being emulator bug or not a bug because "it worked previously" or "it works in any other configuration/hardware" won't really mean anything. It has happened many times..)

Biggest problem is not being in pure assembly/C. It can make debugging ultra-painful.

[Toni Wilen]

Originally Posted by twitek

Here's the saved config file.

Thanks. This is fixed, new chipset side interrupt delays conflicted with old implementation of 68020+ interrupt delays causing too long delays.

btw, strange config, no DF0: but otherwise quite normal looking config. No DF0: and not CD32: long boot delay.

[twitek]

Originally Posted by Toni Wilen

Thanks. This is fixed

Thank you very much!

Originally Posted by Toni Wilen

btw, strange config, no DF0: but otherwise quite normal looking config. No DF0: and not CD32: long boot delay.

Thanks, this is fixed.

[timeslip1974]

Originally Posted by Toni Wilen

Not enough information is obviously the first reply.

But if it is "simple" freeze, just create statefile and I'll take a look. Use config without harddrives and no unneeded expansions.

But first MUCH more information is needed.

(and there is no proof it being emulator bug or not a bug because "it worked previously" or "it works in any other configuration/hardware" won't really mean anything. It has happened many times..)

Biggest problem is not being in pure assembly/C. It can make debugging ultra-painful.

Im quite happy to help, how does one create a statefile and in what context ?

[Toni Wilen]

Originally Posted by timeslip1974

Im quite happy to help, how does one create a statefile and in what context ?

Set config, Paths panel -> Enable full logging. Boot normally, make it hang. F12, Paths panel -> Save all (creates zip with config and logs), misc panel -> Save state. Attach/email all files.

EDIT: even better if you manage to create statefile just before the hang. For example if the hang only trigger if you do something specific.

[Toni Wilen]

https://download.abime.net/winuae/fi...nuae_4910b7.7z
https://download.abime.net/winuae/fi...ae64_4910b7.7z

Beta 7: Getting later.. Next release attempt: this weekend.

- 68020/030 CE mode too long interrupt delay fix.
- Possible fix for mouse counter overflow after emulator has been running many hours.
- Weird programmed mode blanking position calculation fix.

Interrupt fix might be the reason for above game hang, if used config was 68020 or 30 + "cycle-exact".

[vulture]

Hi Toni,

With "Full Contact" using the .IPFs and either a standard "A500 / OCS / Cycle-exact" or "A500 / ECS Agnus / Cycle-exact" Quickstart; there are now issues with the fighters shadows etc,

[INDENT]WinUAE 4.9.0:

WinUAE 4.9.1 beta:

[twitek]

Originally Posted by vulture

there are now issues with the fighters shadows etc,

Can you check with which beta version the problem started (1-7)?

[Toni Wilen]

Normally it would be nice to know but this was simple enough

Already fixed but I also found another graphics problem (not related to this bug) that needs to be also fixed. This never gets finished enough..

[Mclane]

Originally Posted by Toni Wilen

This never gets finished enough..

Seems to be the case this time, best of luck...