A Common Error...

[CEO1999]

It seems I've come across an error that is very common for many different games, not just mine. I am new, so I don't know how things work (well, for now). Instead of talking about my specific game (which I will only do for context in this post), I assume a general discussion about the error itself would be a good enough match for this section, though apologies in advance if that's not the case. Anyway, the game I am emulating is an relatively old Wii game called Rune Factory Frontier (could be classified as a Harvest Moon spinoff game).

It ran fine for a while until I got to the bottom of the Green Ruins. The errors shown are in the pictures attached. The issue can be replicated consistently and it always happens and does not allow the 4th floor to be loaded, which means I have no access to the boss. What's worse, when I did some research about the error, it seems there are many other games with similar issues (as I mentioned earlier), such as Paper Mario, Zelda games, Xenoblade Chronicles, etc...

There are so many games with these kinds of errors. Either they can be consistently replicated in the same environment, like mine, or they happen randomly or before a game even boots up. Because of this, the issue is complicated to pin down. I've also noticed that many of the threads that mention this issue don't usually ever seem to have it resolved, so I'm not getting my hopes up that it will be fixable. Be we can still try. So take a close look at the pictures I've provided (update: now text provided). I tried disabling Duel Core but that didn't work. So what can be done about the issue from here?


Update: I don't know how to display pictures. Every time I insert them, it's just text. Anyway, I'll just write them all here:

1. GFX FIFO: 

Unknown Opcode (0x07 @ 0000000091C7EECA, preprocess=false).
This means one of the following:
*The emulated GPU got desynced, disabling dual core can help (actually it did absolutely nothing)
*Command stream corrupted by some spurious memory bug
*This really is an unknown opcode (says unlikely, but in this case I think that may be the issue)
*Some other sort of bug

Something about further errors and a sarcastic message saying I should enjoy myself.  

2.
Illegal command 07
CPBase: 0x00587de0
CPEnd: 0x00687dc0
CPHiWatermark: 0x000fc000
CPLoWatermark: 0x00080000
CPReadWriteDistance: 0x0000ff60
CPWritePointer: 0x006873c0
CPReadPointer: 0x00677460
CPBreakPoint: 0x00000000
bFF_GPReadEnable: true
bFF_BPEnable: false
bFF_BPInt: false
bFF_Breakpoint: false
bFF_GPLinkEnable: true
bFF_HiWatermarkInt: true
bFF_loWatermarkInt: false

3. Unknown Pointer 0x0af5a2e0 PC 0x8022f45c LR 0x8022f45c

Please see the new information regarding my computer's specs:

[color=#000000]Operating System:
Windows 10 x64
Processor/CPU:
Intel® Core™ i5-2500K CPU @ 3.30GHz
Video Card/GPU:
NVIDIA GForce GTX 1060 6GB/ Cannot find model number
Memory/RAM:
16GB/ don't know about RAM for now
Dolphin Revision Currently Using:
ac267a29405ae768037a8774b84b805a4180d1af/5.0/x64[/color]

[Venomalia]

Is there any reason why you are using this Dolphin revision?
if not you should try the latest beta versions
https://de.dolphin-emu.org/download/

[CEO1999]

When I installed the more recent version of Dolphin, at least it gave me new information about the error. I am quite sure this is an Opcode problem. First of all, what's an Opcode?

Condition: stream_size_temp < 16
File: C:\buildbot\release-win-x64\build\Source\Core\VideoCommon\OpcodeDecoding.h
Line: 160
Function: RunCommand

The error still exists. It isn't a version problem. It's a problem with the code itself. What's going on?

[Neui]

Just in case, can you let Dolphin verify the game? Rightclick on the game in the game list → Properties → 'Verify' tab → [Verify Integrity] button.

(05-16-2022, 11:46 PM)CEO1999 Wrote: First of all, what's an Opcode?

Games send commands to the GPU, and to identify what kind a command it is there is a number describing that, which is called Opcode (operation code). In this case, it seems Dolphin (tries) to run the command (which needs to check the opcode to know what to do), except it had an assumption about the data/arguments which doesn't hold up (assertion), usually being nonsensical values (like from an game bug, or from an corrupted game copy).