AppleTV support

elvman · December 10, 2015, 2:13pm

You can not test it on AppleTV simulator, because Apple does not support using remote controllers on it. You must test it on actual device. I will check out the linker errors later.

piotrros · December 10, 2015, 2:24pm

Maybe I misunderstood, but by remote controller I mean that little window from screenshot I posted. If you’re saying about some pad I just want ordinary remote included with apple tv.

elvman · December 10, 2015, 2:37pm

Yes, that little window (virtual remote) can only interact with the GUI. Apple does not support it as a remote controller on the simulator, so it will not work with cocos2d-x or any non-GUI application.

piotrros · December 10, 2015, 2:45pm

Now I see! That’s very unfortunate. But it’ll work on real remote on real device?

elvman · December 10, 2015, 2:54pm

Yes, it works on a real device. Actually we already have two games released with my cocos2d-x branch: “Song of Pan” and “Dot Munch Fight Club”.

makalele · December 10, 2015, 6:31pm

Great game What framework you used to implement multiplayer?

elvman · December 10, 2015, 6:53pm

Well, by “us” I meant “cocos2d-x community”. These are not my games Dot Munch Fight Club is not multiplayer, opponents are bots.

makalele · December 10, 2015, 9:33pm

I see. Haha I got fooled I’m playing online

elvman · December 13, 2015, 7:57pm

Added “get/setAbsoluteDpadValues” method to Controller, so that you can change how MicroController (AppleTV remote) reports the D-pad values (touch area). When this flag is on, values are reported as absolute values (center of the touch area is 0, sides are 1), but if it is off, coordinates of the first touch are reported as 0 annd all the values are reported as relative to this point (ranging from 0 to 1).

piotrros · December 14, 2015, 10:01am

Is there any hack or something to simulate remote? Like keyboard arrows? I’m still waiting for usb-c cable and kinda stuck, because I cannot send any input to interact with my app.

elvman · December 14, 2015, 10:47am

AFAIK there is none.

nop · December 14, 2015, 12:56pm

I think this is working for me. In RootViewController.mm add:

   -(void)pressesBegan:(NSSet*)presses withEvent:(UIPressesEvent *)event {
      UIPress* p = [presses anyObject];
      if ((p.type >= UIPressTypeUpArrow) && (p.type <= UIPressTypeRightArrow)) {
        cocos2d::Scene* myScene = cocos2d::Director::getInstance()->getRunningScene();
            ((Game*)myscene)->arrowPressed(dir);
      }
    }

It’s good for testing only. It may give double keyPresses in the actual device. Not tested yet.

piotrros · December 14, 2015, 1:24pm

Just got the cable!
I’m trying to figure out how this is working.

I filtered logs to “key up only”. But it’s a bit strange.

I figured out that 1004 code is tapping (clicking) whole touchpad.

But how to recognize swipe in some direction?

piotrros · December 14, 2015, 1:38pm

Okay so I’ve got some more codes:

1004 = tap
1007 = play/pause
1024 = menu

1010, 1011, 1012, 1013 are popping (logging key up only) when going with finger around, but I can’t figure out by what rules it’s working and how to recgonize swiping left, right, up or down

also how can I block default “menu” button action? So I’d be able to go to the previous screen (or If it’s on first then close app).

elvman · December 14, 2015, 1:50pm

Please, as I said in the first post, download the sample app from here: https://github.com/elvman/tvos-test4
It should answer all the questions you asked.

piotrros · December 14, 2015, 2:14pm

Thanks, sorry I didn’t know you just recently added some stuff to your example.

So I got how to handle menu button, that’s solved (just comment 2 lines in RootViewController).

However I’m still struggling with movement.

I figured out that 1010 is up, 1011 is down, 1012 is left and 1013 is right and your latest example confirmed that.
In my app I have 2d tiled grid where you can move character in 4 directions. It look like it’s working, but not exactly. When I swipe up I’m getting up event indeed, but if it’s not perfect swipe I’m getting 2 events up - left or up - right. But I want up only. How can I solve it?
Also I saw you added mouse events, for what purpose? Using remote triggers only key events (so no mouse events and no touch events).

elvman · December 14, 2015, 2:29pm

Of course you will get two events, that is why I asked you to download my sample. If you look at lines 165-180 of MainMenu.cpp, you can see, that I am logging the value of each D-pad arrow (it is a value between 0.0 and 1.0). You should move your character only if a direction is 1.0 (fully pressed). This works similarly on controllers (GCGameController) with physical D-pads (they also report D-pad arrow values from 0.0 to 1.0).

piotrros · December 14, 2015, 2:46pm

Thanks. 1.0 is too hard to do on my remote, but If I’m going any less I’m getting more wrong turns… What’s this anyway?:

controller->setAbsoluteDpadValues(true);

edit:

problem fixed! works perfectly! I was using key down/up events instead of repeat.

elvman · December 14, 2015, 2:58pm

Yes, you have to use keyDown (in case user reaches 1.0 in the first swype) AND keyRepeat. Look a few posts higher to see what setAbsoluteDpadValues does.

piotrros · December 15, 2015, 7:26am

Thanks. When I handle menu button how should I close app the right way? I tried Director::getInstance()->end() but app won’t run again.

edit:
Also is this possible to use iphone remote app instead? I tried that it works in apple tv menu, but when I run app I can only see

“Controller connected Remote” and it only reacts to remote (the physical one), but doesn’t see iphone at all.