New Type of Nub Behavior?

[EssoAir]

I was reading this --> http://pandorawiki.org/Nubs#Nub_Configuration and it got me wondering, what would be involved in writing an entirely new type of behavior for the nubs. I'd like to map each directoon to keys as apposed to Joystick/mouse funtions.


Can this be done?

 

[LTStone]

Yes I agree we have these great nubs , its a shame not be able to use them to their full potential.

 

[AnimatedFreak]

If you want to mapp things to the nubs you can do so with a PND called QJoyPad compiled by mcobit 


You can find it here http://boards.openpandora.org/index.php?/topic/8217-d-pad-modding-accessibility-issue/page__hl__qjoypad#entry145300

I wish he would put it on the repo so people can download it. It is just a quick compile of it but works good I think to map the D-pad to the nubs or something. It shows up in the game catogory on the menu and you have to put the nubs in joystick mode before starting the program. 

 

[danielo515]

So, there is an experimental secert-non-avaiable mode which everybody will love?

 

[EssoAir]

Thanks for the mapping PND. I'll check it out tonight

 

[danielo515]

Looks promising!

 

But this can take advantage not only for android,  Amtrong interface too.

 

Make the right nub do whatever you want. You don't use double click? Just map, left to left-click, right, and any other thing you want to nub-up/down. Do you think this can be accomplished by QjoyPAd?

 

 

But, two questions:

 

Will this affect normal Linux behavior?

How can we translate this "mapping-layer" to Android?

 

[EssoAir]

Looks promising!
 
But this can take advantage not only for android,  Amtrong interface too.
 
Make the right nub do whatever you want. You don't use double click? Just map, left to left-click, right, and any other thing you want to nub-up/down. Do you think this can be accomplished by QjoyPAd?
 
 
But, two questions:
 
Will this affect normal Linux behavior?
How can we translate this "mapping-layer" to Android?

I'll need to check, but since it doesnt actually edit the system files, I would assume that this app does not translate to Android like the Nub Configurator does. The only real solution is adding new system-level configurations for the nubs.

 

[danielo515]

I tried it.

I configured right nub to be a joystick, and mapped to IJKL (wich in android is used to move the virtual nub).

In Linux everything works. Left nub works as mouse, right nub writes the corresponding letters. 

I think the problems is when I start android, it kills the QjoyPad process (which runs under XCFE), so in android nothing happens.

Any program seems to recognize the nub as joystick

 

[EssoAir]

I tried it.
 
I configured right nub to be a joystick, and mapped to IJKL (wich in android is used to move the virtual nub).
 
In Linux everything works. Left nub works as mouse, right nub writes the corresponding letters. 
 
I think the problems is when I start android, it kills the QjoyPad process (which runs under XCFE), so in android nothing happens.
Any program seems to recognize the nub as joystick

I don't believe you understand quite how the Nub Configurator works. QjoyPad is a PND that works on top of Angstrom, the Nub configurator edits the system files changing the Nub funtions entirely. Nothing "transfers" to Android, however, when you run the configurator, since the nubs are entirley and 100% changed, Android changes too without knowing anything different. Does that make sense? I suggest you read the link I posted in the OP to learn more.

 

[danielo515]

I took the point about how Nub Configurator works.

But I thoug Amstrong runs under Android, so I suppose the PND will too.

Anyway, I configured one NUB as joystick, and Android doesn't recognize it as joystick.

Some weird things about Dead-Triger is this:

 * D-pad works as a D-dap, no matter how many mappings or reconfigurations you do at android Gamekeyboard

 * If you map AXBY to work as virtual nub, it works flawlessly for movement (placing the virtual nub at the left side of the screen) but if you try to use it for aiming it works horrible.

Now I'm  using, Dpad for movement, left shoulder button for fire, and touchscreen for small aiming.

 

[EssoAir]

I took the point about how Nub Configurator works.
But I thoug Amstrong runs under Android, so I suppose the PND will too.
 
Anyway, I configured one NUB as joystick, and Android doesn't recognize it as joystick.
 
Some weird things about Dead-Triger is this:
 
 * D-pad works as a D-dap, no matter how many mappings or reconfigurations you do at android Gamekeyboard
 * If you map AXBY to work as virtual nub, it works flawlessly for movement (placing the virtual nub at the left side of the screen) but if you try to use it for aiming it works horrible.
 
Now I'm  using, Dpad for movement, left shoulder button for fire, and touchscreen for small aiming.

Can you post the GameKeyboard Profile so I can look at it?

 

[danielo515]

Sure!

AXBY are mapped to ijkl, so and Virtual NUB is set to been used with those keyboard keys, so if you put the virtual NUB at the left side of the screen, you can move yourself with AXBY, and if you place it at right you can "try" to aim.

touchScreenSimle_dot_gkp.txt

 

[EssoAir]

Thanks! I'll check that out tonight!

 

[LTStone]

This is a nice thread, i’ll upload my configs for Nova 3 and Max payne later tonight, I have mapped all the controls perfectly for Max Payne, and everything but looking around for Nova 3. The problemwith Nova 3 is it uses multitouch so you can only use one motion at a time. My config for Shadow Gun is the same as daniel515's, which is wierd because it won't let you hard config the i,j,k,l, to the butons for some reason.
Where do I upload my configs to? Any suggestions?

 

[EssoAir]

This is a nice thread, i’ll upload my configs for Nova 3 and Max payne later tonight, I have mapped all the controls perfectly for Max Payne, and everything but looking around for Nova 3. The problemwith Nova 3 is it uses multitouch so you can only use one motion at a time. My config for Shadow Gun is the same as daniel515's, which is wierd because it won't let you hard config the i,j,k,l, to the butons for some reason.
Where do I upload my configs to? Any suggestions?

Mind uploading those to my other thread instead?

http://boards.openpandora.org/index.php/topic/11395-gamekeyboard-profiles-post-them-here/

 

[LTStone]

"Now I'm  using, Dpad for movement, left shoulder button for fire, and touchscreen for small aiming."

So it let you map the left trigger for fire?

 

[danielo515]

"Now I'm  using, Dpad for movement, left shoulder button for fire, and touchscreen for small aiming."


So it let you map the left trigger for fire?

I'ts pretty easy.

Just map the left trigger to A button (for example. Because if you want left triggers to appear on screen you need to select at least 8 buttons controller, and you don't need so many) and place that button over the fire zone.

 

[LTStone]

Weird, you can map the buttons on Dead Trigger but not me, only the dpad works. I loaded your settings but still nothing.. I must be missing a setting somewhere but I can't seem to find the problem. Shadow Gun has the exact same settings and problems. Any suggestions, I'm using the latest gamekeyboard update 3.2.0

"Now I'm using, Dpad for movement, left shoulder button for fire, and touchscreen for small aiming."


So it let you map the left trigger for fire?

I'ts pretty easy.
Just map the left trigger to A button (for example. Because if you want left triggers to appear on screen you need to select at least 8 buttons controller, and you don't need so many) and place that button over the fire zone.

 

[danielo515]

^If you don't mind, we will continue discussing how to map android buttons in the other thread.

There you said thanks for a tip, can you confirm it was about the same topic?

Cheers.

 

[EssoAir]

^If you don't mind, we will continue discussing how to map android buttons in the other thread.
There you said thanks for a tip, can you confirm it was about the same topic?
Cheers.

haha! "cheers". You obviously learned from a Brit