Gamepad support (need testers with controllers): Page 2

Gamepad support (need testers with controllers)

Jacowaco

Woah! Just tried with an X-box pad and a usb pad and it worked perfectly! Nice! 🙂

gsynuh

Hi everyone,

I just fixed the errors that would happen when you unplug the controller (actions wouldn't stop correctly, and major infinite loops everywhere)

I'm not very happy with how the I'd let the developer create and include his own maps:

I've got a dictionnary where keys are sub strings to look for in the device's name, values are Classes that should extend GamepadMap which looks for the os (using Capabilities) and run functions according to the result (setupWIN/MAC/LNX/AND) so that everyone could in fact create one map for each possible os, based on the devices name, to override everything we do by default would be a simple matter of just replacing that dictionnary with your own and a set of classes defined the same way the xbox360 map we have for example is defined.
I create an object from that class if the substring was found, run setupXXX(gamepad) on the gamepad instance to create the ButtonControllers or StickControllers required.

So far I'm happy that it works for other people! it just looks bad as an API (or whatever it should be called).
So if you've got suggestion please go ahead.

I also don't have a system where you would be able to leave a player the opportunity to create his own map as I'm not listening to all control changes, just the ones that are setup internally which means you couldn't just see if a new control is changed and create a new 'InputController' for it if your map didn't already create it.

With the major lag/freeze issue still here and the will to release CE 3.1.8 asap, I don't think this will be included just yet - so lets call that experimental but very usable (specially for xbox360 controllers, and with something like
http://code.google.com/p/x360ce/
we'll just make do until default maps are as complete as we can make them.

I'll still provide an example/test state along with the nice graphic that shows what buttons are being pressed, with what 'force' and the sticks directions (as seen in the video) - I've got an .swc just for that.

will do that once I'm done with the remaining features to be implemented for 3.1.8 which is the new sound manager (something very important.)

JaimeDominguez

Hi there,

I was triying to use OUYA pad on my game but I found out it doesnt work as expected, it doesnt trigger my own addEvent so I decided to have a go with this new CE system.

I have to read everything several times. Cause I don't know how to initialize the mapping... that SWC file with the assets could be amazingly useful for our tests.

If you share it i will be able to put it up on my latest dev version of beekyr and see if works in ouya and pc using xb360 / ouya controllers...

Mean while i will read it again and keep on trying....

gsynuh

Hi Jaime,

The gamepad layout .swc is here : https://github.com/alamboley/Citrus-Engine/blob/master/lib/gamepadLayout.swc

this commit's comment (expand it) contains details on the swc and how to access its graphics :
https://github.com/alamboley/Citrus-Engine/commit/a3baa65653fe87b18822fee510191e82247439c8
(sorry that's not very readable)

ideally it should update by itself but it doesn't yet.

I guess I'll setup an example in which I simply setup a custom map (even though it might already be there) and just display the layout on screen.

GamePadManager.devicesMapDictionary is a dictionary that associates a substring to find in a device.name with a Class that extends GamePadMap.

GamePadMap just looks for the os, and run the related setupXXX() function.
If you extend GamePadMap (check how the 360 one is done for example)

and do
GamePadManager.devicesMapDictionary["string"] = CustomMap;

then whatever device plugged in that has "string" in its name, will use CustomMap to setup the mapping on this gamepad (it will run CustomMap.setupWIN(gamepad) if on windows, CustomMap.setupMAC(gamepad)....

You can in fact clear all default map by clearing that dictionary, and override all default this way.

I know its not super friendly as a system. I'm really open to ideas !!!

JaimeDominguez

Thanks. SO .. should I initialize like this?

protected function initGamePad():void
		{
			var gamePadManager:GamePadManager = new GamePadManager(1);

			gamePadManager.onControllerAdded.add(addGamePad);

		}

		protected function addGamePad(gamepad:Gamepad):void {

			gamepad.setStickActions(GamePadMap.STICK_LEFT, "up", "right", "down", "left");
			gamepad.setStickActions(GamePadMap.STICK_RIGHT, "zoomIncam", "rotateCam+", "zoomOutcam", "rotateCam-");

			/*gamepad.setButtonAction(GamePadMap.L1, "rotateCam-");
			gamepad.setButtonAction(GamePadMap.R1, "rotateCam+");

			gamepad.setButtonAction(GamePadMap.L2, "zoomOutcam");
			gamepad.setButtonAction(GamePadMap.R2, "zoomIncam");

			gamepad.setButtonAction(GamePadMap.L3, "addPoint");*/

			gamepad.setButtonAction(GamePadMap.BUTTON_BOTTOM, "shoot");
			gamepad.setButtonAction(GamePadMap.BUTTON_RIGHT, "bomb");

			gamepad.setButtonAction(GamePadMap.BUTTON_BOTTOM, "shoot");
			gamepad.setButtonAction(GamePadMap.BUTTON_RIGHT, "bomb");

			gamepad.setButtonAction(GamePadMap.START, "menu");

			gamepad.debug = true;

			trace("addGamePad!:"+gamepad);

		}

It captures the hits (It shows traces()') but doesn't do anything else for now...

gsynuh

Yes this is the way.
But I can only speak for the xbox controller right now,
the ouya map is this one :
https://github.com/alamboley/Citrus-Engine/blob/master/src/citrus/input/controllers/gamepad/maps/OUYAGamepadMap.as
it all defaults to the Android mapping, and is setup when the "OUYA" substring is found in the device's name.

to check if a button is registered you can try
trace(gamepad.getButton(GamePadMap.BUTTON_BOTTOM));
which should return a ButtonController InputController.

(same for sticks with getStick)

if those aren't in, the registration didn't work/ the map setup failed.

JaimeDominguez

My only issue now is that game doesnt detect if the action is triggered...

I tried with this:
if (_input.isDoing("right", inputChannel)){

};

but doesnt trigger. i tried with input -1 , 0 , 1
and still not happening...

I dont think that using: gamepad.getButton(GamePadMap.BUTTON_BOTTOM) would be usefull because that invalidates the "actions system" that I set up with gamepad.setButtonAction().

In GamePad.as . in 'protected function onChange(e:Event):void'
I added a trace to check which buttons are being read and they all display properly:

PRESSED: AXIS_2 =-0.09759819330423902
PRESSED: BUTTON_18 =0
PRESSED: BUTTON_17 =1

But isDoing doesnt seem to know anything about those buttons. I'm using XBOX arcade in PC for testing before I try in OUYA..

How can i read for actions?

JaimeDominguez

I dont think the actions are registered at all... So TriggeredON / OFF is not really happening. Im implmenting it but I'm sure you will end up doing it. I tried for a few hours now. And still not happening... I'm missing something. Do you want my progress and you finish it off? Or shall I wait for you to do it?

I just have very limited time with the OUYA (3 days more). you see?

gsynuh

hello everyone,

just to let you know I pacakaged a quick air app to test the system:

http://labs.gsynuh.com/coffee/CEgamepadtest.air

note: it uses the default maps we have in CE , and still doesn't make use of the keyboard events some buttons might trigger.
the graphic is here :
https://github.com/alamboley/Citrus-Engine/blob/master/lib/gamepadLayout.swc

and used as follows (in a normal State):

//init
gamepadlayout = new GamepadLayoutGraphic(); //class in the gamepadLayout.swc
gamepadlayout.scaleX = gamepadlayout.scaleY = 0.7;
gamepadlayout.x = _ce.screenWidth/2;
gamepadlayout.y = _ce.screenHeight/4;
addChild(gamepadlayout);

//update
var gamePad:Gamepad = GamePadManager.getInstance().getGamePadByChannel(0);
if (!gamePad)
{
	gamepadlayout.alpha = 0;
	return;
}

gamepadlayout.alpha = 0.7;
gamepadlayout.L1.alpha = gamePad.getButton(GamePadMap.L1).value;
gamepadlayout.R1.alpha = gamePad.getButton(GamePadMap.R1).value;
gamepadlayout.L2.alpha = gamePad.getButton(GamePadMap.L2).value;
gamepadlayout.R2.alpha = gamePad.getButton(GamePadMap.R2).value;
gamepadlayout.L3.alpha = gamePad.getButton(GamePadMap.L3).value;
gamepadlayout.R3.alpha = gamePad.getButton(GamePadMap.R3).value;
gamepadlayout.SELECT.alpha = gamePad.getButton(GamePadMap.SELECT).value;
gamepadlayout.START.alpha = gamePad.getButton(GamePadMap.START).value;
gamepadlayout.BUTTON_TOP.alpha = gamePad.getButton(GamePadMap.BUTTON_TOP).value;
gamepadlayout.BUTTON_BOTTOM.alpha = gamePad.getButton(GamePadMap.BUTTON_BOTTOM).value;
gamepadlayout.BUTTON_LEFT.alpha = gamePad.getButton(GamePadMap.BUTTON_LEFT).value;
gamepadlayout.BUTTON_RIGHT.alpha = gamePad.getButton(GamePadMap.BUTTON_RIGHT).value;
gamepadlayout.DPAD_UP.alpha = gamePad.getButton(GamePadMap.DPAD_UP).value;
gamepadlayout.DPAD_DOWN.alpha = gamePad.getButton(GamePadMap.DPAD_DOWN).value;
gamepadlayout.DPAD_LEFT.alpha = gamePad.getButton(GamePadMap.DPAD_LEFT).value;
gamepadlayout.DPAD_RIGHT.alpha = gamePad.getButton(GamePadMap.DPAD_RIGHT).value;

gamepadlayout.LEFT_STICK_POINTER.alpha = gamePad.getStick(GamePadMap.STICK_LEFT).length;
gamepadlayout.LEFT_STICK_POINTER.rotation = gamePad.getStick(GamePadMap.STICK_LEFT).angle * 180 / Math.PI + 90;
gamepadlayout.RIGHT_STICK_POINTER.alpha = gamePad.getStick(GamePadMap.STICK_RIGHT).length;
gamepadlayout.RIGHT_STICK_POINTER.rotation = gamePad.getStick(GamePadMap.STICK_RIGHT).angle * 180 / Math.PI + 90;

gamebuilders

Has anyone tested PS3 controller on Windows? I attached the controller on win 7 and vista and I get the device attached with the following mappings reported:

ControllerInputManager - Button ID = AXIS_0 | Max = 1 | Min = -1
ControllerInputManager - Button ID = AXIS_1 | Max = 1 | Min = -1
ControllerInputManager - Button ID = AXIS_2 | Max = 1 | Min = -1
ControllerInputManager - Button ID = AXIS_3 | Max = 1 | Min = -1
ControllerInputManager - Button ID = BUTTON_4 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_5 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_6 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_7 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_8 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_9 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_10 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_11 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_12 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_13 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_14 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_15 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_16 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_17 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_18 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_19 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_20 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_21 | Max = 1 | Min = 0
ControllerInputManager - Button ID = BUTTON_22 | Max = 1 | Min = 0

but I can't seem to get any change event notifications from the individual controls. Has anyone seen this as well? Does the GameInput API not support PS3 controller inputs on windows?

gsynuh

Hi gamebuilders,

I have a report of the ps3 controller working both on windows and mac with the current version of the GamePadManager class we have in CitrusEngine

The mapping we have set by default were based on this spreadsheet by @zeh (thanks again by the way.)
https://docs.google.com/spreadsheet/ccc?key=0AkkprH0hOE5cdGpmeDVTVFQ5M0syOGdXZ0xjVDJkSnc&usp=sharing#gid=1

So I don't know what the ControllerInputManager class does sadly, but I think you can compare the mappings with this document.

you can be sure at least these are confirmed, I'm pretty sure there is some info out there on what Adobe is tapping into to get the inputs but I never bothered to look for that.

gamebuilders

@gsynuh Yea thats what I have been using as well for reference. @zeh (+1 on that) But there is no mapping in the spreadsheet for a pure PS3 controller by itself. And when I physically connect the controller to a windows machine the controls that are returned from this code:

for (var i:uint = 0; i < device.numControls; i++) {
				var control:GameInputControl = device.getControlAt(i);
				controlMap[control.id] = control;
			}

are the same controls as the mac mapping but when you listen to the individual control objects for the Event.Change notification there is no event received on windows. It works perfectly on a mac. I haven't tried installing the MotionInJoy driver was hopping to avoid it

zeh

The PS3 controller is a shitshow in Windows in general. It's not officially supported, there are no official drivers, so when you have problems, it's more likely the driver's fault more than anything. There's no "pure mapping" on Windows on the spreadsheet because none exists. You're forced to use motioninjoy or whatever. I'm a fan of the PS3 controller but I never use that on my PC, ever, just because of that. I used to use my PS3 controller but it'd fail all the time requiring me to restart the shitty ghetto chinese drivers I had... too much hassle. An XBox wired controller is better.

With that said, what people normally do with PS3 controllers is set the driver to emulate the XBox 360 controller. That's normally what PC games expect. So as long as your code supports the XBox 360 controller, you're all set.

There are ways to use PS3 gamepads with a different configuration, but not sure why would anyone do that unless they're trying to emulate other gamepads.

(Luckily they did it differently with the PS4, and it works out of the box.)

My understanding is that Adobe AIR wouldn't care about what you have. Since it just forwards you what Window is passing to it, it doesn't need to especifically support the PS3 controller. If the gamepad works on Windows at all, it'll work on AIR.

Also -- For what's it worth, I've just published this GameInput tester.

Web: http://hosted.zehfernando.com/key-action-binder/game-input-tester/
Android/OUYA: http://hosted.zehfernando.com/key-action-binder/game-input-tester/GameInputTester.apk
Source (pure AS3): https://github.com/zeh/key-action-binder/tree/auto-controls/tests/GameInputTester

This will show you which device you have connected, its control, and their state. Somewhat more useful than the spreadsheet if you have a controller that's not there, or that you want to double-check (e.g. your PS3 one with whatever mapping it's set to use). It's on my KeyActionBinder repository but it's independent of it (it doesn't use that, it's just a raw display of the controls).

gamebuilders

Hey @zeh thanks for all your work on this stuff and the new links, will give them a try. I figured it was a driver issue because the controller reports correctly but just wasn't sending any control notifications. Thats fine, I will just let users know that PS3 can't be used on windows unless they setup some sort of emulating driver.

gsynuh

You could explore ANE solutions for windows and mac perhaps,I don't think it would be really hard and maybe you'll have a lot of happy users for small development time ? I don't really know what's available yet but I'll try existing solutions someday.

I don't expect GameInput to become a 2 way communication system where I could set off the controllers to vibrate - zeh do you think this would ever be considered , or is it already? I just don't see why adobe would consider this (low expectations) but it would be very cool.

zeh

gsynuh: I never saw any official announcements from them in regards to vibration on anything. Certainly the current API doesn't support it, or hint at it. Given the state of AIR right now, and how broken certain features of GameInput have been for a while and how long it has taken them to fix it (the timer delay bug on Windows, and the unresponsive GameInput events on Android depending on how you start it) I wouldn't bet on it either. They just don't seem to have the resources or the will to do too much in that front.

Personally I wouldn't invest too much time in creating, or using, ANEs. *when it works*, the GameInput class does what it's supposed to do and it should be all one needs... it'd be better to focus on that for cross-platform development. The Windows+PS3 problems are a problem that is likely to be present on ANEs as well since it's a system/driver level problem.

(Of course, ANEs for vibration would be a great idea though - maybe some already exist?)

bigboer

Hi Guys

[EDIT!!!] I got it all working using the devPlatform = "MAC" property. I was simulating my app on an Android AIR build so it was using MapAND instead of mapMAC

Been doing some testing. and am getting the following. Using a PS3 Controller. IE only Left Stick is binding.

Seems like my PS3 Game controller names are different.

joy = _gamepad.registerStick(GamePadMap.STICK_RIGHT, "AXIS_2", "AXIS_3");
and not
joy = _gamepad.registerStick(GamePadMap.STICK_RIGHT, "AXIS_11", "AXIS_14");

and then for buttons from BUTTON_4 to BUTTON_22 for the rest.

Binding AXIS_0 to STICK_LEFT
Binding AXIS_1 to STICK_LEFT
gamepad0 trying to bind AXIS_11 but AXIS_11 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind AXIS_14 but AXIS_14 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_102 but BUTTON_102 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_103 but BUTTON_103 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_104 but BUTTON_104 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_105 but BUTTON_105 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_108 but BUTTON_108 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_106 but BUTTON_106 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_107 but BUTTON_107 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind AXIS_36 but AXIS_36 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind AXIS_38 but AXIS_38 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind AXIS_37 but AXIS_37 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind AXIS_39 but AXIS_39 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_96 but BUTTON_96 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_99 but BUTTON_99 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_100 but BUTTON_100 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 trying to bind BUTTON_97 but BUTTON_97 is not in listed controls for device PLAYSTATION(R)3 Controller
gamepad0 using map [class PS3GamepadMap]

so am reworking the mapping to test

gsynuh

Hi bigboer, Thanks for the info.

Can you please put your edit text into 'strong' tags so they will be shown as bold text and also change mapAND/mapMAC to setupAND/setupMAC - I could do it but I wouldn't like to mess with someone's post :p

markerline

A little different angle, do you know gsynuh if it is possible to add MIDI controller support the same way you did for a modern game controller? I am interested in using a 4x4 16-pad MIDI controller for an audio sequencer.

Mistakenness

Ok, do you know if POWERSHELL by Logitech is supported on iOS ? I'm developing a platform, I would add that feature.

« Previous Page Next Page »