Okay... it's still giving me the Cannot find path thing...
But I can confirm that it's not the calibration. Even though TS2 wont install until the end now, the guns will still register in M2. Still only in diagonals... I couldn't even calibrate ingame because the guns only move in diagonals.
It also seems like sometimes the game would register triggering, sometimes not. Right now hotd doesn't want me to shoot but it's working in VCOP.
EDIT: I checked TS2's icon and both guns are registered correctly.
You guys are going to have to elaborate a little on "only in diagonals" Do you mean it smoothly can go from the top left to the bottom right and any amount along that line? or do you mean it either jumps to the absolute top/left or bottom right?
Ok now let me explain how the inputs work a little to help with that. When ts2 installs the stuff for model 2, it copies over cfg files for hotd, vcop, vcop2, bel, gunblade and rchase 2.
Essentially these cfg files are setup to block all buttons from p1 and p2. Only the two triggers are mapped to the Z and A keys. Now for all of the gun games, when the trigger is pulled, ts2 simply simulates a keypress for either z or a. So it works like the old troubleshooter. Obviously, if model2 doesn't have focus, key presses won't register. Since the aimtracks show up as mice, clicking around while in windowed mode is bound not to work correctly.
On top of that, vcop and vcop 2 have their own issues. The only way I could block model2 input detection for those games was to turn on raw input for model2 and set the id numbers in the emulator.ini to numbers that are NOT the mice I'm using. As I said, model 2 attempts to do this, but you might want to check manually. If your guns are ids 3 and 4, for example, set the id to something nice and high like 6.
You guys might want to use the input test menus in the games to determine if the triggers are actually being pulled, but the game just isn't registering them due to the aim issues.