(09-02-2013, 05:37 PM)YaPeL Wrote:(09-02-2013, 04:31 PM)[Unknown] Wrote: Even if it's gut-wrenchingly slow, does it at least show correctly with jit disabled? Or not even then?
Or if you compile it, you can swap the CONDITIONAL_DISABLE defines in Core/MIPS/x86/CompFPU.cpp and Core/MIPS/x86/CompVFPU.cpp, which will not be nearly as slow.
-[Unknown]
Yes, as I said, without jit it works fine, and yes, with CONDITIONAL_DISABLED it works now! I only tested one game but It run pretty good, (Black rock S), if you guys want to test it now:
https://www.dropbox.com/s/frthjo0ga1f2s8...puless.apk
So, what now? I test each function at a time till I found the guilty one? any suspicious one?
That should be pretty fast - just put DISABLE on the first line in half the functions, then if it still works, remove half the disables and so on (if it didn't, disable half of the other half instead) until you find the guilty one.

