> > Hi everyone, I hope I'm putting this in the right place - I'm still waiting for my > > account to be verified so I can post this to mametesters. > > > > Running rungun2 from the command line with "mame64 rungun2" spits out a ton of > errors > > when you get to gameplay that look like this: > > GXT4: unknown protection command 125c (PC=209948) > > GXT4: unknown protection command 3a56 (PC=209948) > > GXT4: unknown protection command 1b55 (PC=209948) > > GXT4: unknown protection command 3357 (PC=209948) > > > > I saw this reported in the bug tracker, and the comments there made it sound like > it > > shouldn't be that big of a deal, BUT when you run the game from the built-in GUI, > it > > runs WAY faster than from the command line. When I run it from the GUI, I get 160% > > speed during gameplay (leaving plenty of headroom for 60fps all the time), and when > I > > run it from the command line, I only wind up with about 70% speed (making the game > > unplayable). > > > > Does anyone know what's going on with this or how to disable the error messages > from > > showing up? I can't just "run it from the GUI" because I'm using a different > > front-end for my games and obviously they get run from the command line. > > > > Any help is most appreciated! Thanks! > > printf spam to console window takes emulation cycles, no doubt about it. If you > capture the output to a file it should react the same as the GUI [ > output.txt 2>&1 > ]. > But, in this case, since it isn't under active development - commenting the printf > should be ok. > > I'll see that it is changed - no need to log a bug about it.
Thanks for offering to fix it. As an aside, won't capturing the output to a file leave me with a giant-ass text file after just a few minutes of gameplay?
|