 No.21462
ICEknight Tester
May 27, 2023, 00:55
|
By the way and since closed reports here can't be replied to, somebody please reopen issue 8603. Vas mixed up the shader's Overscan X/Y function (which is "like adjusting the size controls on a CRT TV") with MAME's Stretch/Move X/Y function (which stretches/moves everything output by the shader including its frame, and is what the report was about). (I'll remove this post afterwards not to clog this report) |
|---|---|
 No.21464
cuavas Administrator
May 27, 2023, 04:19
|
You are wrong. Those controls act like monitor adjustments even if their functionality duplicates or interacts with shader controls. They do not, never have, and are not intended to adjust the screen area geometry within the layout. |
|
No.21465
cuavas Administrator
May 27, 2023, 05:17
|
In relation to this report, this isn’t a crash or freeze – the emulator is running fine. The game jumps into the weeds for some reason (it’s stuck infinitely executing "rst $38" instructions in what’s apparently $FF fill). But if I understand it correctly, “Crash/Freeze” on MT refers to the emulator itself, not the software running in emulation. |
 No.21466
Robbbert Senior Tester
May 27, 2023, 09:08
|
Confirmed In both cases the game runs to a STOP opcode which is followed by what appears to be a spurious instruction. If this instruction is jumped over, the game runs. konamic2 - skip code at 092C konamic4 - skip code at 024C Perhaps the STOP (10) instruction should be 2 bytes? I'm not familiar with this CPU's special instructions. |
|
No.21467
Robbbert Senior Tester
May 27, 2023, 09:13
|
As cuavas says, the emulator has not crashed nor has it frozen, so I've chosen "Gameplay" for now. Someone else might want to choose something more appropriate. |
|
No.21470
cuavas Administrator
May 28, 2023, 04:06
|
The STOP instruction is a single byte ($10), but due to a quirk of the CPU, the following byte is fetched but ignored. It’s usually filled with $00 (NOP). MAME seems to be failing to ignore the byte. |