|
|
Post by David on Mar 23, 2011 7:08:25 GMT
Are you 100% sure that the Mustang via the MPA causes the bumping also?? I connected my Mustang via my MPA and I'm not seeing any problems. Is is possible that you had the Squire connected and swapped it out with the Mustang which tricked the MPA to thinking the Mustang was still a Squire?
Thanks
David
|
|
|
|
Post by raynebc on Mar 23, 2011 14:45:10 GMT
I just confirmed it again, plugged the MPA into my computer, plugged the Mustang into it, launched Phase Shift. The bumping issue still occurred. And this was my second MPA, which I hadn't taken out of the box yet, so this may be consistent behavior for multiple/most/all MPAs.
|
|
|
|
Post by markv on Mar 23, 2011 18:13:26 GMT
Are you both trying the PS3 Mustang ? Is it possible it does something different than the Xbox one?
|
|
|
|
Post by raynebc on Mar 23, 2011 18:26:21 GMT
I only have Xbox 360 peripherals.
|
|
|
|
Post by David on Mar 23, 2011 21:56:14 GMT
I only have Xbox 360 peripherals. Does the XInputSignals2.exe app I sent you before. If so can you tell me if it registers the pulse signal at all? Thanks David |
|
|
|
Post by raynebc on Mar 23, 2011 22:25:14 GMT
I'll give it a look.
|
|
|
|
Post by raynebc on Mar 24, 2011 0:27:56 GMT
XInputSignals2 shows an empty input message every 3 seconds, coinciding with the keep alive signal of the Mustang. I connected the Squier and re-opened the utility, and it showed the same thing. I don't think I ever looked up the Squier's keep alive signal in MIDI OX, so I decided to examine that now, it is as follows:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
0000068A 1 -- F0 Buffer: 18 Bytes System Exclusive
SYSX: F0 08 40 08 09 00 00 00 00 00 00 00 00 00 00 00 00 F7
For comparison, this is the Mustang's keep alive signal:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00001037 1 -- F0 Buffer: 18 Bytes System Exclusive
SYSX: F0 08 40 0A 09 00 00 00 00 00 00 00 00 00 00 00 00 F7
Until these MIDI messages can be read, I'm not sure what the best solution would be, perhaps aside from ignoring all empty input messages.
|
|
|
|
Post by David on Mar 24, 2011 7:37:39 GMT
This is what's puzzling, the game does ignore empty messages.  This is strange. David |
|
|
|
Post by raynebc on Mar 24, 2011 14:33:49 GMT
I guess they're not empty from Phase Shift's perspective, but the Xinput utility doesn't display anything for them.
|
|
|
|
Post by David on Mar 24, 2011 19:10:07 GMT
When you press the XBOX button on your mustang does it do the same thing? Because pressing that button should generate a blank packet too.
Thanks
David
|
|
|
|
Post by raynebc on Mar 25, 2011 0:00:41 GMT
When the Mustang is connected via the wireless Xbox controller adapter, pressing the Xbox button sends a blank packet, and releasing the button sends another blank packet.
|
|
|
|
Post by David on Mar 25, 2011 15:11:39 GMT
When the Mustang is connected via the wireless Xbox controller adapter, pressing the Xbox button sends a blank packet, and releasing the button sends another blank packet. But does it bump the frets Ingame? like the Signal Pulse? Thanks David |
|
|
|
Post by raynebc on Mar 27, 2011 2:17:02 GMT
When I had the Mustang connected via the wireless controller adapter, pressing the Xbox button in-game did not bump the track. When I had the Mustang connected via the MIDI pro adapter, pressing the Mustang's Xbox button did nothing noticeable in Phase Shift, however it does appear that pressing the MIDI pro adapter's Xbox button does cause the track to bump.
|
|
|
|
Post by David on Mar 28, 2011 19:55:36 GMT
The only thing I can think of is that you are using a different driver to me which is why we are getting different results.
Can you let me know the driver details for the MPA?
Thanks
David
|
|
|
|
Post by raynebc on Mar 28, 2011 20:09:29 GMT
Xbox 360 Controller for Windows (signed by Microsoft):
Driver date: 8/28/2007
Driver version: 2.1.0.1011
Files:
xusb21.sys (file version 9.18.1011.0)
WdfCoInstaller01005.dll (file version 1.5.60000.0 (vista_rtm.061101-2205))
I have Microsoft Xbox 360 Accessories 1.1 (version 1.10.123.0) installed, I believe this came with my Xbox wireless controller adapter. I also have Microsoft XNA Framework Redistributable 3.0 (version 3.0.11010.0) installed, but I don't know if this contributes to controller detection at all.
If you have another way for me to identify which driver is handling the controller, let me know and I'll take a look.
|
|
