Emulator Issues #3060
closed
BackPatch - no support for operand size 1 (crash msg)
0%
Description
What steps will reproduce the problem?
1.Baten Kaitos - Eternal Wings -> game crash when entering bossfight "Magnus Giganticus"(enter the final door to Magnus Giganticus bossfight (in Mystical Garden))
What is the expected output? What do you see instead?
expected:begin of bossfight
instead:game crash with:
"BackPatch - no support for operand size 1"
immediately followed after this error message "Read from invalid memory
region (0x79edb2da)
What version of the product are you using? On what operating system?
tried several SVNs from old to newest.Without Interpreter,DC,JIT,IL and with.Both x86/x64 My OS: Windows 7.GFX Nvidia 8800GTS512
Please provide any additional information below.
I included my Memory Card.It's save state Nr.2.Just walk in the pacman like
labyrinth (to the left hand side from the save point flower) and there
chose the door which had golden barricades (in former save states)
Updated by Bohlio44 about 14 years ago
Just thought I'd add that I recently encountered a very similar error. Playing MarioKart Wii, Immediately after selecting "Automatic" or "Manual". Error Text reads:
BackPatch - no support for operand size 1
Error encountered accessing emulated address c2e46846.
Culprit instruction:
movzx eax, byte ptr ds:[rbx+rcx]
at 000000001161accb
This was encountered using x64 revision 6120, compiled myself, on Win 7 x64
Updated by MofoMan2000 about 14 years ago
- Savestates are not stored in the memory card. They are in \User\StateSaves
- Don't attach files here, the space Google Code projects get for attachments is limited. Upload to MediaFire or a similar off-site file hoster and link to it.
- Be sure to specify the region of the game you're using. It's probably PAL since your memcard is EUR, but in the future…
Updated by CadeFoster23 about 14 years ago
Yes the game is in PAL.I thought memory card and explanation will suffice to reproduce the bug,but if wished for I can make a savesate and upload to RS or MU.Can anyone of the devs explain what this BackPatch operand size 1 means and how this error can occur in emulation?I'd be very interested,thanks
Updated by dok.slade about 14 years ago
The bug with 8-bits backpatch (operand size 1) should be fixed in r6120.
Can you confirm?
Updated by dok.slade about 14 years ago
Sorry, didn't see that it was happening in r6120... I'll have a look.
Updated by Bohlio44 about 14 years ago
I feel like a fool, but now I can't even seem to recreate my own issue with Mario Kart. It did it three times in a row at the same spot, now I can't get it to do it again...
Updated by dok.slade about 14 years ago
Bohlio: Which mode were you using (Jit or JitIL) when you had the bug in r6120?
Updated by Bohlio44 about 14 years ago
I was using Jit when I encountered the problem.
Updated by CadeFoster23 about 14 years ago
Things have changed.In 6120 the BackPatch Error doesn't occur anymore in JIT,but instead the screen goes black music plays for a while (slowly fading out) until nothing happens in audio or video (black screen remains),but Dolphin still running at Speed 100%.(tested with x86/x64 Interpreter+JIT+JITIL)If someone would like to have a closer look on this,I uploaded a SaveState right before entering the doomed door which makes the screen go black. http://www.multiupload.com/1LIVTDS3QP
Updated by Bohlio44 about 14 years ago
Are you saying that it should be fixed in JIT under 6120, or that the error itself cant be generated in the code in 6120. I'm 100% certain that I was using JIT and 6120 when I had the error on mariokart.
Updated by skidau about 14 years ago
dok.slade, the error can still occur in r6120 if there is a JIT problem in the LoadStorePaired or lfs instructions. The address quoted "c2e46846" is not a valid gamecube address, so the problem is likely due to a bug in the JIT.
Bohlio, can you try it with JITIL?
Updated by dok.slade about 14 years ago
skidau: the backpatch error at "c2e46846" is caused by a 8-bit access. But neither lfs nor any LoadStorePaired instructions are doing 8-bit accesses, if I remember.
Updated by Bohlio44 about 14 years ago
@skidau & Dok - Sorry if I muddied up this ticket a little bit. The address "c2e46846" was posted by me with a Wii game, not GameCube, so keep that in mind. Also, I can't recreate my issue, under JIT or JITIL, so I apologize for that.
Updated by skidau about 14 years ago
- Status changed from New to Fixed
ok. That pretty much means that r6120 fixed it. I am quite familiar with this part of Dolphin and the cause of that error has been plugged in r6120.
Updated by skidau about 14 years ago
Issue 1176 has been merged into this issue.
Updated by Larissa.Scholz over 11 years ago
I had this problem, too.
Open Dolphin and right-click on the game where that error message appears, then go to "properties".
You should see a box which says "core". there you have to check "enable mmu" and "speed up disc transfer rate"(these are needed for some games).
I'm not 100 % sure if this will solve your problem but it worked for me :)