(12-24-2013, 02:43 PM)JMC47 Wrote: [ -> ]Huh, that's weird. I played this game for a few hours on dolphin without any special settings and didn't run into any issues whatsoever with freezing or crashing. Does it only happen during abnormal framerates?
Probably my PC is not really top of the line but i get 25 fps (50-90 unlocked) all the time with the PAL version as i said a way to force the freezes is using the turbo mode and quicksave.
Its probably the small fluctuations in fps while loading stuff battles for example which trigger the random freezes with a better PC you just dont have those fluctuations so it doesnt freeze.
I know it may not make for a playable experience, but Single Core should prevent crashes like that.
(12-24-2013, 08:08 PM)JMC47 Wrote: [ -> ]I know it may not make for a playable experience, but Single Core should prevent crashes like that.
It does actually its the only thing that really helps, sync gpu doesn`t at least for me and yes its to slow to play with single core.
Any update on the item text glitch?
Can you provide a savefile around it? I'm too lazy too busy to try and learn this game to play it right now, but I want to investigate this game regardless. thanks.
just get through with the tutorial on the battleship and beat the first "boss", then return to pirate's isle and it should occur then.
This attitude is a good reason why this bug isn't going to be fixed anytime soon. No, nobody here wants to spend 1h playing a game just to try and reproduce a bug.
I loaded an old save game of mine and tested with the latest version and did not encounter the text glitch bug. Latest dev version (750) Open GL and single core. I played from Shrine Island to Sailors Island and looked for the bug in and between battles. Can anybody confirm that this bug is gone with the latest version and single core?
btw I enjoyed the news about how you fixed the Zelda fire bug and how you found the wrong hex offset.
Namenios: If you upload the save, I will confirm it. Thanks ahead of time.
nameless confirmed it's mysteriously fixed in the latest svn.