I haven't tested every revision. All I know is this didn't ever happen between 3.0 and 4.0.2 (on the versions I tested between that period).
So its entirely possible whatever caused the issue started in one of the later revisions after 4.0.2. I'll grab the latest revision and test it out later on the same games, and see if the problem still persists.
Would you prefer if I saved and posted the logs for when this error happens? Although I'm unsure how to get the logs if the emulator crashes, unless it saves the last activity in a file somewhere. I'm more than happy to help you out if you tell me how to get the information you need to solve problems.
And I'm not suggesting this is a bad revision either, because it runs a few FPS faster on the minimum and maximum over what it ran in 4.0.2, so speed wise its definitely an improvement. I get 30fps running around town in Last Story with an I5 2500k @ 4.2ghz. Parts that used to dip to 26-28 are now 30, and at least 5fps higher on the top end. I'm actually quite pleased with the progress.
So its entirely possible whatever caused the issue started in one of the later revisions after 4.0.2. I'll grab the latest revision and test it out later on the same games, and see if the problem still persists.
Would you prefer if I saved and posted the logs for when this error happens? Although I'm unsure how to get the logs if the emulator crashes, unless it saves the last activity in a file somewhere. I'm more than happy to help you out if you tell me how to get the information you need to solve problems.
And I'm not suggesting this is a bad revision either, because it runs a few FPS faster on the minimum and maximum over what it ran in 4.0.2, so speed wise its definitely an improvement. I get 30fps running around town in Last Story with an I5 2500k @ 4.2ghz. Parts that used to dip to 26-28 are now 30, and at least 5fps higher on the top end. I'm actually quite pleased with the progress.