Can't get trigger to work with complex cycle commands

[jdb2]

Well, I finally got my Panther XL USB ver 3 working. The latest software update didn't do it; Instead I just disabled ( using the device manager ) the AKI3 ID01 Joystick #2 device that Rob said was causing the problems. XD Still, there are issues, such as the profile ceasing to function outside of PGP necessitating repeatedly stoping and starting the profile before it starts working again -- This gets a little irritating as time goes by. Other than that, I haven't noticed any other issues.

Moving on, I have a (semi)complex set of mutually interacting cycle commands for Crysis 2 -- one for the "Fire" and one for "Armor Mode."

They work as follows, which I will summarize with screen captures :









The problem I'm having is that pressing the trigger does nothing.

The effect the above is supposed to have is to start firing when the trigger is pressed, toggle armor mode, and zoom. Then upon release, armor mode remains enabled, zoom is disabled ( because it isn't pressed anymore ) and firing stops ( for the same reason that zoom is disabled ). Also, the cycle pointer is set to Fire (Alternate #1) and Armor Mode Off.

Then, when the trigger is pressed again, Fire (Alternate #1) is executed which leaves armor mode alone ( such as not to toggle it ), and just zooms and fires and then sets the cycle pointer to loop back on itself.

When Armor Mode is toggled after a weapon has been fired then since it's in the state Armor Mode Off, it toggles armor mode, thereby turning it off but it sets the cycle pointer for the firing sequence back to Fire ( Primary ) such that when the weapon is fired Armor mode is turned back on.

Also, if Armor Mode is toggled active from just pressing the Armor Mode button then the state goes to Armor Mode On and the cycle pointer for the firing cycle is set to Fire (Alternate #1) so that armor mode stays on if a weapon is fired / the trigger pulled.

I've tested this with a Logitech Extreme 3D pro Joystick and the trigger doesn't work with that controller either with the above configuration so I know it's not a hardware problem.

I've attached the .pin file for reference.

Any help would be appreciated.

Thanks,

jdb2

[Pinnacle [Rob]]

I'm glad to hear you got the Panther XL working... but I wasn't expecting the latest version to fix the problems you were having, instead it was just logging additional data so you should send your pinnacle.log file to support@pinnaclegameprofiler.com so I can try to find a better solution for you.

I'll also try to take a look at your profile tonight when I am at a machine I can test on...

[jdb2]

I forgot to mention that there is one major problem, best summarized with this video :

http://www.mediafire.com/?r0bpwh9pybaqitt

Or, if you don't want to download the whole video, I've posted it to my Youtube channel :

http://www.youtube.com/watch?v=GxqnihMhKIA

Here's the log file as requested...

jdb2

[Stabba]

From watching the video it appears to be a similar problem that I get on my WoW profile.
On that it makes me run continually forward at times, as though the 'w' key is pressed down or that my joystick is continually in the up position..
Would the 'w' key on your profile or joystick up make this happen?
If so then I think you have the same problem as me.
Pinnacle suspect it is a problem with the hot-swapping of profiles on my build so I would be interested to know if you also use hot swapping.
Also, sometimes when the software bugs out it does not enter a continual command (i.e. 'wwwwwwwwwww') and instead does nothing at all.
Does yours also do this at times?

From taking a nosey at your log file the number 32768 is repeated a lot at the end, I would guess that this relates to the 'Up' command or 'wwwww' as it is only broken with a few other numbers such as 32767 which I guess is you trying to move the joystick to stop it from cycling.

[jdb2]

From watching the video it appears to be a similar problem that I get on my WoW profile.
On that it makes me run continually forward at times, as though the 'w' key is pressed down or that my joystick is continually in the up position..
Would the 'w' key on your profile or joystick up make this happen?

No. You'd have to make the game think that you were holding down an arrow key or that the mouse cursor was continuously cycling in a loop.

If so then I think you have the same problem as me.
Pinnacle suspect it is a problem with the hot-swapping of profiles on my build so I would be interested to know if you also use hot swapping.

I do not use hot swapping.

Also, sometimes when the software bugs out it does not enter a continual command (i.e. 'wwwwwwwwwww') and instead does nothing at all.
Does yours also do this at times?

Yes. This is the basic problem with my trigger button -- it does nothing with the configuration presented in my post. Also, if I re-enable the 2nd AKI Joystick device then nothing works.

From taking a nosey at your log file the number 32768 is repeated a lot at the end, I would guess that this relates to the 'Up' command or 'wwwww' as it is only broken with a few other numbers such as 32767 which I guess is you trying to move the joystick to stop it from cycling.

Actually, no. I purposefully enabled the 2nd AKI Joystick device so that PGP wouldn't work with my controller as Rob wanted debugging output in the form of raw data from my device to determine why PGP would not work in that situation. The data you see is just me going through the normal routine in the device setup wizard, pushing buttons in the "Edit Configurations" screen, and moving the joystick around with notepad open.

jdb2

[jdb2]

Any progress on getting this config working? You only need notepad to test it.

Has anyone tested the profile? ( note that it doesn't use the default Crysis 2 button layout ) As I said, all you need is notepad.


I've owned PGP for over 2 months and I've yet to get it to work properly. This is getting kind of old.

jdb2

[jdb2]

Anyone? :/

jdb2

[eiekal]

"I wasn't expecting the latest version to fix the problems you were having"

I'm expecting my modified panther XL in the mail any day now. Has the issues with this controller been fixed with a later patch?

[jdb2]

"I wasn't expecting the latest version to fix the problems you were having"

I'm expecting my modified panther XL in the mail any day now. Has the issues with this controller been fixed with a later patch?

You have a PM.

jdb2

[Pinnacle [Rob]]

The latest version of PGP has special logging for this device. You should go to START MENU > RUN and enter REGEDIT then navigate to the following location.
HKEY_CURRENT_USER\Software\PowerUp Software\Pinnacle Game Profiler\

Now right-click in the white-space on the right panel and select NEW > STRING VALUE then call it "IncreasedLogging" and set the value to "True".

Then when you run PGP the next time it will record info about your device and you can send your pinnacle.log file to support@pinnaclegameprofiler.com