Emulator Issues #4181
closed
Baten Kaitos Origins (GC) - Nihal Desert area frame rate drop / crash.
0%
Description
What's the problem?
Once entering the Nihal Desert (North or South), frame rates drop and game will (potentially) crash. Graphical glitches are also showing up at times, as well. It would appear that the "sand storm" effect in the desert is the culprit.
Dolphin version with the problem (as it appears in the title bar, Ex.: "R
4779" or "R 6403M"):
r7257
(optional) Dolphin version that does not have the problem:
r6839 has no issue in this area. I'm not sure which revision between r6839 and r7257 caused the problem.
Operating system and version:
32-bit or 64-bit:
64bit, OSX Snow Leopard 10.6.6
Game ID (as it appears in game properties, Ex.: "GZ2P01" or "RSBE01"):
GK4E01
Build command-line (not on Windows):
Built precisely as mentioned in the "Project Home" link for Mac users.
Was the ISO a plain dump from disc, compressed and/or scrubbed?
Unsure.
Please provide any additional information below.
Changing XFB from Virtual to Real will not cause the game to crash. However, the desert area still experiences a large drop in frame rate and numerous graphical glitches.
Turning off XFB seems to have no effect.
Updated by iandylan2000 over 13 years ago
I should have done this in the first message, but let me attach a copy of my memory card file so that anyone can easily see the issue. Upon loading the save, you will be at the entrance to a town, simply walk "down" to exit to the world map. Head a little north to see the desert areas (North and South Nihal Desert). Enter and enjoy the slowdown.
Updated by iandylan2000 over 13 years ago
Well... I'll keep providing information here until someone wants to pop in and add anything to the problem. hehe. There are also times when entering the desert I am given a black screen (frame rate drops to 4). Hitting ESC won't exit the emulator, and I am forced to COMMAND - ALT - ESC (OSX) out of the program. Upon exiting, I am given the following error message:
Warning
GFX FIFO: Unknown Opcode (0x1).
This means one of the following:
- The emulator GPU got desynced, (etc)
- Command stream corrupted (etc)
- This really is an unknown opcode
- Some other sort of bug
Hope this helps!
Updated by
Updated by iandylan2000 over 13 years ago
I'm not sure what fixed it, but the errors/slowdowns in the desert are GONE! I just tested with r7278, and the desert now runs perfectly again! I would have posted in the changelog, but I am not sure exactly which revision fixed the problem... :(
Wait a second... This is really weird... I just tested again before posting, and I noticed that there was still some framerate drop issues and glitches... Then, I closed the emulator, reopened it, and went back to the desert. This time the program hanged, and I was forced to quit the program which gave me an Unknown Pointer error (Unknown pointer 0x42c00000)
This is extremely weird... I have tested it several more times now, and I'm getting the same old situation (framerate drops to 4)... I have no idea what it made it run perfectly the first time, mediumish the second time, and now utter crap each time I test. Very, very odd...
Updated by iandylan2000 over 13 years ago
Problem is gone! One of the recent changes (unsure of which... Can't compile them all) resolved the frame rate drop. There are still very minor graphical glitches, but the game is playable once again :)