Controller lag and inaccuracy

Ayrik · February 2013

Changing it from event. will not allow the OuyaController to change the axes based on its controller mapping system. I copied it directly from my code, so there's obviously something different here. Which version of the ODK jar are you building from?

VAMflax · February 2013

0.0.6

tgraupmann · February 2013

0.0.6 includes "1C". There's "1D" which includes the pause fixes.

The 0.0.6.1 minor update will be coming next week.

VAMflax · February 2013

What are the pause fixes?

tgraupmann · February 2013

When you hit the system button it exits and unity stops playing music/running.

Monzerol · March 2013

Chiming in to say THANKS A TON to everyone who contributed to this thread. You guys saved me lots of time for eliminating the controller latency in my project :)

EMcNeill · March 2013

Sorry if this information is already out there; I'm just trying to get a sense of the state of this.

Is the controller lag issue A) already fixed in 0.0.6.3, B) going to be fixed in a later update, or C) neither and I should try to implement Ayrik's solution from this thread?

My game is very much twitch-action and local-multiplayer-focused, so getting rid of the lag is a high priority for me.

Ayrik · March 2013

I don't have the answer for you, but I am going to say to ignore my fixes and recommend you use OuyaUnityBridge by @goodhustle if you need the fix right now, which you probably don't unless you need to send your game to a QA team or something to get it done by release.

Presumably the lag will be fixed in the 1.0.0.1 release of the official plugin, so you should probably just wait unless you really need it now. @tgraupmann will probably answer you shortly with an official answer.

tgraupmann · March 2013

As @Ayrik said. If you want it right now follow the awesome post. Otherwise it's my next priority. I have some repro projects. If you want to share your project with me, I can use that validate the fixes.

Subscribe for updates to stay up to date.

EMcNeill · March 2013

I can wait a week or two before integrating it. I'll hold off and see how the next version works. Thanks, guys!

Shiels · March 2013

@Ayrik Is OuyaUnityBridge for Unity 4 only? I'm on Unity 3.5.7 and I can't seem to get it working. Adding UNITY_OUYA into scripting define symbols isn't possible in Unity 3 (as far as I know), but that can't be the problem because I can simply change them to UNITY_ANDROID.

Ayrik · March 2013

Does the documentation say anything about it? It is not my tool, @goodhustle made it.

tgraupmann · March 2013

Only these defines exist:
http://docs.unity3d.com/Documentation/Manual/PlatformDependentCompilation.html

That said you can put logic into a DLL and use your own symbols.

Shiels · March 2013

@Ayrik Not really... it only merely implies that Unity 4 is required so I wanted to find out if it's true.

@goodhustle Is it true?

goodhustle · March 2013

@Shiels, sorry, the project tagline didn't mention that I did build it in Unity 4. The first line in the README.md does say: "A minimalist, unofficial bridge between the OUYA ODK and Unity4." I've updated the project tagline on github to be more clear.

The prefabs and example project won't work with Unity 3, but I can't think of any other reason (than the preprocessor defines - see http://forum.unity3d.com/threads/71445-How-To-Set-Project-Wide-pragma-Directives-with-JavaScript) that the actual source code would be incompatible. Is there a specific problem you're having?

Shiels · March 2013

@goodhustle There wasn't really a specific problem, it was just crashing on startup so I assumed it was because I am on Unity 3. But it is fine for now. I'll try again some other time.

Arakade · April 2013

Thought it'd be good to close the loop on this thread.

After my last post here, @goodhustle's response gave me pause and and I immediately ceased implementing my 'shared-memory' approach. In explanation, I guesstimated relative performance as follows (for multiple simultaneous controllers -- not so bad with 1 controller):

score 100% : theoretical ideal performance (probably not possible without /dev/input use?)
score 10% : JSON approach incurred every type of lag possible (a.k.a. "Legacy input")
score 70% : OuyaUnityBridge from @goodhustle (current implementation transfers data via JNI and does this once per stick per frame but this could be reduced to 1 JNI making it 80%?)
score 90% : anticipated shared-memory approach (still required 1 JNI call per frame but no transfer)
score 90% : Android-pure approach from 1.0.1.9 (assuming Unity code is fast ;-) )

When I originally posted, I'd not known @goodhustle had taken his further so had thought (2)->(4) was a worthwhile investment. After his response, I found it harder to justify going from (3)->(4) without trying (3) first so I did that. ...and it was good. Thank you, @GoodHustle :-)

Now, however, I'd hope it's all moot since Tim's released his 'non-Legacy' version which directly calls the UnityPlayer event handling code meaning (a) low latency and processor time and (b) we can use Unity-standard Input methods! (though I'm not yet sure how much controller compatibility we lose/gain for this? Hopefully Unity have this in hand!) With 'non-legacy', I'm see solid 60FPS cap experience so far! Fingers crossed ;-)

HTH, Rupert.

Arakade · April 2013

p.s. @Shiels OuyaUnityBridge worked fine for me under Unity3 once I put #defines in the 2 files it's used in.

goodhustle · April 2013

@Arakade, thanks for your summary. :)

Unfortunately it's not 100% moot yet! I haven't tried out the non-legacy Unity Input system yet, but now that I've worked with the ODK's OuyaController class a little more, I'm wondering if some of the nicer features would be lost. The hotplugging-safe Player Number system is way better than the poor ordering of the Unity joysticks array, and that alone is almost worth all the work. I don't know it's even possible to figure that out from Unity-land Input joystick numbers.

That is to say, Unity is sort of infamous (amongst us desktop devs) for having some really old joystick bugs that never seem to be fixed. Last I checked, there was no support for hot-plugging of joysticks and the joysticks array sometimes doesn't match with joystick indices in input. Maybe it's been fixed and I'm just not up to date - but it's always a pain in the butt, and letting OuyaController do all the work has been really awesome.

And it's sort of a separate issue, it turns out that using one Activity class to manage everything has made it a lot easier to implement IAP and regular ODK calls by staying really close in lockstep with the official iap sample app (which is also basically one activity class). Turns out that there were a lot of big improvements between 0.6 and 1.0 which I was able to take advantage of quickly. So I'm sticking with my solution for now.

tgraupmann · April 2013

I've had feedback from the Unity folks, and they don't actually like how we've done our own Activity.

But I think it's mostly because the Unity plugin system does not support handling multiple plugins that have their own activity code.

Mainly because there's only one Plugins\Android folder that is used.

I would prefer that the plugin architecture would support Assets\PluginName\Plugins\Android that way every plugin could contribute snippets to the main activity.

They also suggested that input works for now, but we may be forced to use UnityNativePlayerActivity route if they ever decide to change the input system.

They have some comment about managing 3.X vs 4.X code paths is a maintenance nightmare. But what else can we do because there's no more updates coming to 3.X?

When Unity headquarters receives their OUYA console, we'll start to be able to loop their devs into our forum threads here to get their best practices and ideas. And in turn they'll be getting our feedback.

goodhustle · April 2013

@tgraupmann Boy, would I love to have them change the Input system for the better. :D

Seriously, though, I know @AngryAnt was around early on in the forums, and may have already suggested he had some ideas for optimizing the plugin in the very beginning. Not sure if he's still hanging around!

It would be great to get their feedback and recommendations especially with respect to handling input on consoles that provide advanced SDK features for controllers. I can only imagine that their support for controllers on XBLA/PS3 is way better than what they offer for standalone, but as I'm not a licensed dev for either of those platforms, I can only guess.

AngryAnt · April 2013

@tgraupmann We're getting an OUYA? A bit late, don't you think? :P I'm just waiting for my own box to arrive from my Kickstarter backing before I get involved in my spare time.

@goodhustle Still kicking, waiting to get my hands on an actual box before I can get started. I have a bunch of notes on the Unity integration which I'll test out when I get the box, but it's all spare time, so we'll see.

I haven't even received my tracking info yet and have no idea how to find my backer #, so it'll probably take a while. I'm heaving off for Unite Asia next week. Hopefully the OUYA is waiting for me at home when I get back.

tgraupmann · April 2013

I'm still waiting on my tracking #. You assume I have power over such things.

The OUYA console is headed for Stockholm. Which office are you in Angry?

Hicsy · April 2013

lol yup waaay too late :P

tgraupmann · April 2013

The first thing to try when you get the OUYA is controller #4 in the experimental build.

http://tagenigma.com/ouya/OuyaSDK-1.0.0/

Just using controller #4 crashes the Unity player.

freso · July 2013

Is the controller latency fixed in the latest ouya-unity-plugin? Because I have probably 100ms lag.

If not, should I try the methods used in this thread?

tgraupmann · July 2013

if you use the ShowUnityInput example you shouldn't see any lag.

freso · December 2013

I never answered this, but I did get lag with ShowUnityInput, so I assumed it was not the plugin. However since we couldn't get rid of this 100ms input latency, we lost interest in coding for OUYA. It's a real shame. :/

Had some dead time now during holidays so I was thinking of trying a wired controller just to see if it helps.

Howdy, Stranger!

Categories

Controller lag and inaccuracy

Comments