Nothing major here but when using MicroVU1, NFL BLITZ 2003 has several pretty major graphic glitches. See screenshot. Only happens with this one option on (no speed hacks). Using the latest revision of everything (as of 8/14/09) but this has been happening every since the MicroVU went into place. Shame since it actually makes the unusally slow game run normally. Hopefully, it can be resolved so this game can be playable finally.

http://farm4.static.flickr.com/3541/3834...ed20_b.jpg

svn r1648 with microVU (no any speed hack)
FF12-ZJS

it was 3 times...

hmm, do you have FPU and VU clamp modes set to "normal"?

those are some weird errors you're getting (they're EE errors).
AFAIK, mVU with clamp mode set to 'normal' shouldn't have SPS in ffxii.

Are you getting the crash with sVU?

wohoo somwhere around the recent changes to µVU
Justice League got a lot better
some periodic SPS are still there and the geometry is changing textures
since I usually don't do devel builds I can't quite tell if there are these possible infiloops
   

also a loading screen came up which was never shown on pcsx2 before OO
   

PS:aside from the SPS slowdown the game works on marvelous speeds as far as I tried^^
bottomline great work cotton

kabooz: have you tried hitting F9 key to run gsdx in software mode?
this usually fixes the half-screen problem in games (but of course it runs slow unless you have a powerful cpu)

thanks yeah fixes the half screen prob but nothing else
also tested on devel build no possible infi loop anymore!!!

The game is Shadow Hearts. It is running great. Just thought that the unknown micro opcode thing was odd...and could be a bug. Hopefully I'm not wasting space.

LethalEnd thats interesting.
Can I ask which version of pcsx2 you're using?

There was a case where unknown opcodes were being called that i fixed a few weeks ago.
But there's still 1 more case I haven't implemented where its possible for this to happen; but its an illegal thing for games to do on the VU's, so it'd be very-very-rare. (I do know yugioh does it though :/)

I'm using Pcsx2 beta 1474.

okay i think that's probably fixed in the latest SVN, but thanks for reporting it.
We're going to release a new beta soon (within a few days), which will most likely have that problem fixed.