Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice

Issues reading delta/x [Touchscreen] on device

Discussion in 'Input System' started by donov, Sep 2, 2019.

  1. donov

    donov

    Joined:
    Apr 15, 2013
    Posts:
    55
    Hi,
    tried the latest update hoping the touch stuff would be refined, but still running in to issues.
    I am trying to read a continuous touch/x delta on device and PC, the code below works on PC, but on device the performed value is always the same(some negative value probably the screen width).

    Any pointers would be much appreciated.

    upload_2019-9-2_16-57-40.png

    upload_2019-9-2_16-52-16.png
     
  2. jonas-echterhoff

    jonas-echterhoff

    Unity Technologies

    Joined:
    Aug 18, 2005
    Posts:
    1,666
    What kind of device/platform are you testing this on?
     
  3. donov

    donov

    Joined:
    Apr 15, 2013
    Posts:
    55
  4. Schubkraft

    Schubkraft

    Unity Technologies

    Joined:
    Dec 3, 2012
    Posts:
    1,075
  5. donov

    donov

    Joined:
    Apr 15, 2013
    Posts:
    55
    Done
     
  6. mvriel

    mvriel

    Joined:
    Mar 17, 2015
    Posts:
    13
    I am running into what seems to be the same problem with Input System version preview.2 1.0.0; is it possible that this bug is not fixed yet?

    On my PC (with a touchscreen) I get correct values and can move my character using touch; on Android (Samsung Galaxy S6 Edge in this case) the character always heads into the same direction; independent of how I swipe.

    I use these settings:

    upload_2019-11-9_13-26-54.png
     
  7. mvriel

    mvriel

    Joined:
    Mar 17, 2015
    Posts:
    13
    @donov do you know which bug number this is tracked under? I would like to view if and when there is progress on this bug and I couldn't find it in the issue tracker