Resolved: Microvu bug reports official thread

[omnikam]

Th mtvu hack is a hack, some games will work, some just wont. There isnt much that can be done im afraid.

Sure i understand, its just that prier versions did work, so i guessed you may have changed something with MTVU that would break this game with MTVU hack. If it helps i might be able to find out what svn broke it?

[rama]

It would be one that changes the VU access pattern. Would be a nice to know but not really helping much

[refraction]

Yeah see if you can find ou where. I did have to change 1 small thing in my recent gif unit changes, bu that seemed ti sort it for everything I tried.

[omnikam]

I traced the build responsible for MTVU hack not working with Final Fight Round 3 to svn r5398
Worked fine before this build (r5397 is good)
5398 [email protected] 2012-09-02 21:33:16
SPU2-X: Don't force align transfer addresses, fixes The Bouncer. I honestly don't know on what basis they were force aligned in the first place. The Bouncer very strangely has correctly aligned sample data in IOP memory which it uploads using an unaligned DMA with SPU2 set to an unaligned address, resulting in the data being correctly aligned in the end. Weird. It also writes the address twice in the order high word, low, low, high, the first pair being aligned and the second pair not. Really weird.
UPDATE: I copied my SPU2-X file from r 5397 to r5398 and it doesn't work so its not the SPU2-X file

[refraction]

An you try some slightly newer revisions then as that wont be the cause

[omnikam]

An you try some slightly newer revisions then as that wont be the cause

How can it not be the cause? r5397 works and r5398 doesn't, there is no build between them, but i did try anyway here`s my result
pcsx2-5347- works
pcsx2-5392 works
pcsx2-5397- works
pcsx2-5398- broken
pcsx2-5403 broken
pcsx2-5404 broken
pcsx2-5406 broken
pcsx2-5428 - broken
pcsx2-5530- broken
pcsx2-5539- broken
pcsx2-5544 broken
pcsx2-5551 broken
pcsx2-5553- broken
pcsx2-5556- broken
I`m not a coder but logic dictates that if r5397 works and r5398 doesnt then r5398 is "Somehow" the culprit

[refraction]

I`m not a coder but logic dictates that if r5397 works and r5398 doesnt then r5398 is "Somehow" the culprit

maybe so but that still doesn't make sense. If you replaced your SPU2-X with an earlier version and it still crashed, then it has to be something else as you have nullified the only thing that changed in r5398

[omnikam]

I agree, Its very strange, but its also whats happening. Ive done what I set out to do, which was to find the build in which it stooped working, ive tested it on my computer and as unlikely as it seems r5398 is the first build with this problem. As its been said though, MTVU is a hack and as the game isn't broken when not using MTVU hack its probably of very little concern. Pcsx2 is still better than my ps2

[omnikam]

I did some more tests and noticed that svn r5397 and svn r5398 actually had the same svn pcsx2 exe namely pcsx2-r5393.exe, so the problem is actually not in pcsx2 but in a pluggin or something
My test was to copy the exe from r5398 into r5397 folder and overwrite it, i then tested final fight round 3 with MTVU hack on, and it worked, so its not the exe
UPDATE: I have fount the error, and its not a pluggin error..Its actually an ini error . Whatever changes to the ini`s that where made in r5398 caused Final Fight round 3 to crash when using MTVU hack im sure this would be an easy problem to solve, ill find the exact ini and report back

Update 2: This is the file" PCSX2_vm.ini " in svn r5397 it works allowing Final Fight Round 3 to work with MTVU hack, but in r5398 the file has been changed somehow and causes the error

[refraction]

I think your ini must just be buggred as there were no ini changes in that revision, only spu2x functionality