|
#1
|
||||
|
||||
![]()
Steps to reproduce:
1. Start the game, get to the Barn Boys chapter; select the Mad Pitchfork one. 2. Get to the cutscene after Frank the pitchfork says is going to "kick your ass". Then, I get this error: Quote:
PC Specs: Windows 7 SP1 x64, AMD E-450 APU with Radeon(tm) HD Graphics 1.65 GHz, 4GB RAM. If I remember correctly, I read some user in this forum (Squall, I think) said that the recompiler in this version is really broken, so it's better to choose Interpreter instead. But now that PJ64 is open source... EDIT: Btw, sorry if I didn't post this in the correct section, I tried to post this in the "Project 64 - v2.x - Issues" subforum, but I doesn't let me to create a new topic. Last edited by oddMLan; 8th April 2013 at 03:57 AM. |
#2
|
||||
|
||||
![]()
I don't know enough about the game to understand your reproduction instructions, sorry (never played it, seems too light and goofy to me but I don't play many games).
But yes, the recompiler is severed from the natural flow of an interpreter sometimes. The RDB was optimized for speed, not stability. So it was written to encourage error messages like what you got. So you should go to the "Recompiler" game settings and modify settings there for stability and not speed to see where the presumption was. It most likely will be because of "Fast SP", "Advanced Block Linking", or "Virtual Lookup Table".
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#3
|
||||
|
||||
![]()
I tested with different combinations, and disabling Register caching did the trick, but the game speed dropped almost around as the interpreter was.
|
#4
|
||||
|
||||
![]()
That's unfortunate, because register caching is one of the biggest optimizations of a dynamic recompiler. Without it, I have never noticed so much of a discernable difference in speed between the re-compiler and an interpreter.
Your best hope would be for an alternative recompiler configuration without having to disable that. Caching CPU registers was modified since 1.6 to fix Indiana Jones, but, it looks like other games were broken in the process. Recompilers...so hard to maintain ![]()
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#5
|
||||
|
||||
![]()
Enabling the debugger brought me another message:
Quote:
|
#6
|
|||
|
|||
![]()
Excuse me guys but i'm having the exact same issue. It's unfortunate because I'm trying to record this for a let's play and I've already started it but now I'm stuck due to this error. Did you end up fixing it?
Also you mentioned changing to interpreter and recompiler modes. How exactly do i do that? i'm terrible at using this program since I'm very new to it. Thanks for reading! |
#7
|
||||
|
||||
![]()
The bug is now fixed in the latest PJ64 git builds.
|