Ouya export bug?

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    hey guys, I haven't had any issues building OUYA games with MMF2 or Click Fusion 2.5.

    Here is sample game I made, it has two levels. I tested it on my OUYA, works flawless.
    Please login to see this link.

    here is the .APK you can run this on your OUYA
    Please login to see this link.

    let me know how it goes :D

    the apk was exported with ClickFusion 2.5

    Please login to see this link.Please login to see this link.
    Take a course in Clickteam Fusion Please login to see this link.
    Youtube Please login to see this link.
    Please login to see this link.

    I just ran it again to confirm, but It can't get this .apk to crash. Tested on 2 OUYAs a brand new ouya and the first version too.

    When OUYA is giving you problems, unplug the cord and plug it back in again, then turn the OUYA on again
    I get the app crashing problem not only with fusion games but just about everything
    that usually works.

    Also you can manually go to the settings and stop any app still running in the background, when you are developing
    sometimes these apps just get stuck and stay there running, especially if you forgot to put the ON SYSTEM DOUBLE TAP === EXIT APP
    on one of your OUYA tests.

    Please login to see this link.Please login to see this link.
    Take a course in Clickteam Fusion Please login to see this link.
    Youtube Please login to see this link.
    Please login to see this link.

    I have decompiled the apk for both my Blast.apk and an older Ouya game that works. I am comparing the code trying to isolate where the problem is lying.
    If it helps any, the problem that is being caused is:
    E/ActivityManager( 319): ANR in com.bizzy.dog (Please login to see this link.)
    E/ActivityManager( 319): Reason: keyDispatchingTimedOut    .

    Looking around, this stand for Activity Not Responding (No response after 5 seconds). It would seem that one of the threads is getting caught up during initializing and is timing out on the Ouya. The problem also seems to only be relevant in the newer exporter and not the older one. I am at work right now so I cannot test anything on the console, but I'll play around with it when I get home and see if I can find out where the timeouts occur.

    Edited once, last by BiznessMan (February 4, 2014 at 9:38 PM).

    I was able to get a copy of MMF2 and will attempt to compare older versions of the exporter until I find the version that causes the Ouya to crash.
    Hopefully then we can compare what differences were made between versions and find out what is causing the Ouyas to crash. Hopefully we can figure this out so I can rest easy :)

    Dude, I think I'm on to something. I think it's a problem the OUYA has with 8 direction movement. Unfortunately, I don't know how to fix it. Darksparck, did you use 8 direction movement with perl diver? Could you post the fusion file so we can investigate further? My platform games are working fine.

    Edited once, last by doki: spelling (February 8, 2014 at 2:41 PM).

    Its not the 8 directional movement. I made a test that has 0 controls, just a counter which shows the framerate and it still was crashing. It has something to do with the Ouya controller sending a bunch of commands to the console when the applications are initialized. Ouya support told me that a bunch of Unity games were having the same problem.

    Solved for next beta!

    as Biznessman said, OUYA controller are not working/react the same, some of them are speechless and some of them are talkies.

    this is happening for all game creator, but Now we are OK for the next beta.

    was difficult to test since it did not happens here, but BizznessMan have a new console, my guess was that something in their hardware change and was that some of them are talkies so they bombard the game from start with message even if they are steady/idle.

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    Can I ask, does the latest beta install directly on Fusion 2.5 start-up? I'm having the exact same problem as these guys. Any idea when it'll be fixed? Can't wait to get the most out of my little shiny box ;)

    Just imagine the flood of new games coming when this is fixed! They'll be up to a thousand in no time! :)

    Doki, just out of curiosity does your controller ever seem to "hang" on you? Sometimes on mine if I press a button the Ouya acts like I am holding it down (Say I move down on a menu, it will act as if I am holding down on the stick for about 2 seconds)
    This might be the cause of the controllers being talkative. Mine is slightly out of view of my console so I wonder if its sending more commands in an attempt to stay synced.

    I can't say I've noticed that, but I tend to use d-pad for menus. I will try it tonight when I get home and let you know what I find. I'm still not convinced that it's controllers as I've connected PS3 controllers too and my APKs still crash. You're right about it not being the 8-directions, I made a game that uses one button but unless you hold it constantly while the frame ends, that crashes too. :/

    It might not be the controllers per say, but its the way the Ouya tries to communicate to them with the bluetooth. If you run a logcat on the Ouya and try to run your app you will see a huge flood of:

    W/InputMethodManagerService( 321): Ignoring showSoftInput of uid 10018: com.android.internal.view.IInputMethodClient$Stub$Proxy@42e29538

    and finally you'll see

    I/WindowManager( 321): Input event dispatching timed out sending to com.yourcompany.yourapplication/com.yourcompany.yourapplication.Main

    Fernando doesn't get the input floods on his device and most other people don't. This is just on a small amount of consoles and I am not 100% sure why. However as Fernando stated above, it'll be fixed in the next beta :)

    Noticed the same thing happening on Lazy Caverns game, it seems the same bug that used to happen when pressing multiple buttons at launch can cause crashes between frames now. Happened with buttons that aren't used in game though so didn't spoil my enjoyment. :) Also, d pad seems to stop-start, not as good as the left stick control, that happens in my games, too. Could just be happening on my Ouya, though. How's yours doing, Business?
    Looking forward to the next build fix :)

    Hey guys! Any news on the next beta build? Sorry to nag but my OUYA and Fusion gear has been sitting there patiently since Christmas (I even bought a new laptop for making games on). I'd like to contact Clickteam directly, how do I find my serial number? It seems more complicated with downloads. I really wish I got it on DVD now so I could simply send it back and get a replacement and then see if it's the OUYA that's the problem. I just wanted to make games for the TV but nothing lasts longer than a couple of frames so far! How are you getting on BiznessMan? Thanks for any help you can give. :)

    Edited 2 times, last by doki (March 6, 2014 at 10:24 PM).

    I have since launched a game on Google Play while I wait for the beta to come out. I don't have any news since I am not affiliated with ClickTeam. My advice would be to just start getting your game together and hopefully the beta will be out before you're completely done. That is what I'm doing at the moment

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login