Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

[Bug][Fixed-rc4] Input blocked

Discussion in 'Samsung Smart TV' started by gboulard, Oct 2, 2014.

  1. gboulard

    gboulard

    Joined:
    Nov 28, 2012
    Posts:
    21
    Hello,
    we have an annoying bug regarding inputs on unity for samsung TV.
    it is possible to 'block' an axis to a constant value.
    this is in our applications, but also in the unity launcher itself and in angry bots demo.

    by using the standard remote control :
    in angry bots : spamming top and down arrow then click on left or right arrow. (not sure about the repro steps, this is as close as we can explain it..)

    with smart touchpad (model 2013 for us) :
    in unity launcher itself: swap from center to right , then swap to the top(continue to swap and 'exit' the touch area with your finger)
    => the horizontal axe will be blocked to a value of 1.
    you won't see it, but if you try to swap another time to the right, nothing will happens the first time (value will go back to 0, but it won't be interpreted as a swap, as it was only 1 > 0, and not 0 > 1 > 0)

    anyone else havingg the same problems ?
    any fix /workaround ?
     
  2. gboulard

    gboulard

    Joined:
    Nov 28, 2012
    Posts:
    21
  3. Josh-Naylor

    Josh-Naylor

    Administrator

    Joined:
    Jul 1, 2014
    Posts:
    216
    Hey, could you please submit a bug report and post the case number in here.
     
  4. gboulard

    gboulard

    Joined:
    Nov 28, 2012
    Posts:
    21
    done
    case number 637189
     
    Last edited: Oct 3, 2014
  5. AlexThibodeau

    AlexThibodeau

    Unity Technologies

    Joined:
    Jul 23, 2013
    Posts:
    309
    Hey there,

    A similar issue came up earlier regarding the IR (standard) remote and here was the response from Samsung:
    In regards to the issue with the smart remote I'll spend some time trying to reproduce your issue with it. In initial attempts I haven't been able to lose any swipe events.

    Thanks,
    Alex
     
  6. gboulard

    gboulard

    Joined:
    Nov 28, 2012
    Posts:
    21
    Last edited: Oct 3, 2014
  7. AlexThibodeau

    AlexThibodeau

    Unity Technologies

    Joined:
    Jul 23, 2013
    Posts:
    309
    Thanks the video helped a lot. I see the issue now.
     
  8. gboulard

    gboulard

    Joined:
    Nov 28, 2012
    Posts:
    21
    Glad i could help,
    Do you plan on having a fix about this issue on your side (or a workaround on ours) ? or is it unfixable ?
     
  9. AlexThibodeau

    AlexThibodeau

    Unity Technologies

    Joined:
    Jul 23, 2013
    Posts:
    309
    So I found out the problem and implemented a fix. I'm in the process of getting things moving through the process so I can get a new build out that includes the fix. What the problem was is if you issue more than one swipe command on the touchpad on the smart remote without lifting your finger only the last command will receive a button up event when you lift your finger. Therefore all the previous cardinal directions that were used would be stuck in the down position.
     
  10. gboulard

    gboulard

    Joined:
    Nov 28, 2012
    Posts:
    21
    Nice,
    Isn't the standard remote problem similar ? (due to "sensitivity" and "gravity" input settings values adding some delays in the down and up process)
     
  11. AlexThibodeau

    AlexThibodeau

    Unity Technologies

    Joined:
    Jul 23, 2013
    Posts:
    309
    A new build has been posted to the sticky post that fixes the input problem for the smart remote.

    I personally have not tried the standard remote. This fix could potentially help out there as well.
     
  12. gboulard

    gboulard

    Joined:
    Nov 28, 2012
    Posts:
    21
    Thanks !
    It seems to fix it all (both touchpad and standard remote)

    I still have somme problems tweaking touchpad in joystick mode (regarding gravity and sensitivity), but this major issue is behind now :)