(04-23-2013, 06:31 AM)pauldacheez Wrote: [ -> ]Swapping the "true" in line 63 of Source/Core/Core/Src/CoreParameter.cpp with a "false" and recompiling should do it, if you can compile your own builds. https://code.google.com/p/dolphin-emu/source/detail?r=47f1505499dd0ba8cd78c2d5ff3600c937d75236
Or just add Fastmem = false to the ini...
edit: actually i don't think just changing line 63 will even do anything. I don't think that's ever even called except immediately before being overwritten by loading the .ini (which will set a default itself if nothing is specified in the .ini, so that's the value you'd need to change if you really wanted to go that route).
Since i don't have the time to convert my windows vm to a physical own, i'll try to get some usefull thing with the fastmen=false
Does the attached log is what is needed ?
How i produce the crash : just launching "new game"
I've try with two PAL dump of the game.
Regards.
That log doesn't tell anything either, that stuff always appears when starting a game. :\
Doesn't an error message pop up? Or if you get the "Dolphin has encountered a problem and needs to close" thing, can you post what's inside the sendable error report? IIRC, the stacktrace in that error report is what fastmem prevents us from getting. (And IIDRC, it's still useful anyway.)
Uh, this might be two possibly-related bugs, but the 556-7 stated in the first post seems somewhat suspicious to me.
Assuming it's the same bug, where in the game INI do you put the FastMem=false? In the core section?
(04-24-2013, 10:56 AM)jimbo1qaz Wrote: [ -> ]Assuming it's the same bug, where in the game INI do you put the FastMem=false? In the core section?
In dolphin.ini, under core.
Is there some kind of tutorial for getting usefull information for debugging ?
And should i report the bug in the tracker in order to be more efficient ?
Regards