Mafdet MSTe crash

[Official Ninja]

Mafdet, after pressing space at the screen shot,  crashes with a white screen and two bombs.

[Official Ninja]

Just  an update, I noticed on all the games Ive tried today, Leviathan, Mafdet, Treasure, Zool, StarRay, when I use M to set the speed to 8Mhz it does not change. When back at the 1st screen it still says 16Mhz.....

*edit, updated games that the M function didnt work properly.

[Petari]

Mafdet is fixed. Leviathan will be soon.
Considering MSTE CPU speed settings:  you need to deactivate Xcontrol Mega STE CPU settings. Or at least set there to 8MHz.
It works in background, as ACC does, and will set to 16MHz while you try to set to 8.   2 SW affecting the same thing can not work at once well. And some games like Operation Wolf will not work at 16MHz.
And generally, games do not like accessories. Especially TOS dependant ones.

[Official Ninja]

Never was a problem before. Ive used plenty of patches able to set 8Mhz. No problem. As an example, any of Klaz's patches.

There is not a problem with the control panel app. For example, Elvira. MSTE is set to 16Mhz Cache. Run the game. In the launcher press M and press 1 for 8Mhz. Press enter to return back to the launcher screen. Screen still says 16Mhz.

However, the system IS running 8Mhz. I can tell by the game running slower. Also, if I quit the game and check the control panel app, it now says 8 Mhz.

So, your launcher did change the cpu speed and the control panel app only reports the speed. Probably only changes the speed if you make a change and click OK.

So, your launcher/patch is not fighting with the control panel app. There is just a bug in the launcher not properly reporting the change in cpu speed.

[Official Ninja]

Just tested Mafdet as well. The launcher shows no change to 8Mhz yet quitting the game and checking the control panel app reports an 8 mhz change.

[Petari]

This is pretty strange.  Without Cpanel no errors.
Anyway, I need to take deeper look into it. Maybe unused bits are different masked ?
Fixed Leviathan - not MSTE clock settings, just RAM layout config.

[Official Ninja]

I don't think there are no errors. The launcher just acts different with no CPANEL loaded.

I just tried Mafdet and Elvira.

With no control panel the launcher says 8>16 Mhz when you use M and 2 to set 16 Mhz.
(I actually defaults to this 8>16 Mhz)
However the launcher, when changed to 8 Mhz does display that at the starting screen.

With the control panel loaded both games say just 16 Mhz. (not 8>16 Mhz)
The starting launcher screen does not show a change to 8 Mhz.

Would be really cool if the game could set the cpu speed back to what it was before changing it on exit.

[Petari]

OK, MSTE CPU clock displaying is now fixed. Updated only few last ZIPs for now. I already planned to add MSTE clock restoring at exit. It will be done soon, and I need to do gamestate saves too for TOS calling games - but still not enough free time at once to do the hard part of it.
Updated Blood Money too. Did not encounter savestate problems - after several tests. But if it happens, blame rather programmers of game and their weird IKBD code    I really did not expect so much time spent with fixing of bugs and lame/bad code in games.

[Official Ninja]

I have not tried any game besides Elf and Elvira and both of those don't display the proper cpu speed changes on the MSTE.
Game play seems fine though.

[Petari]

Where HAGA is dated after 23 April should be OK. Elvira is not updated yet (but you can copy there HAGA from some newer ZIP).  And I added restoring of start CPU clock by exit to Desktop too.
I fixed Elf graphic glitches for TT, Falcon. But game is pretty large, so could not test it until end.

[Official Ninja]

Where HAGA is dated after 23 April should be OK. Elvira is not updated yet (but you can copy there HAGA from some newer ZIP).  And I added restoring of start CPU clock by exit to Desktop too.
I fixed Elf graphic glitches for TT, Falcon. But game is pretty large, so could not test it until end.

Thanks. I used HAGA from cyber assualt and it changes cpu speed display between 16 Mhz and 16>8 Mhz but not 8 Mhz.