Question How to simulate finger touch control of mobile at game play mode?

So I get some finger touch character movement UI control script for mobile phone from googling.

How to test this code inside unity editor's play mode without porting or making mobile APK build file?

Thanks.

 

I go same problem.
My solution is quit urgly that just sperate the finger logic and build apk.

 

Isn't this what the simulator is for? https://docs.unity3d.com/Manual/device-simulator-introduction.html

 

yes looks what I need, how to test this? how to turn this simulator on?

 

I've never used it, but I'm sure the docs can get you rolling: https://docs.unity3d.com/Packages/com.unity.device-simulator@3.1/manual/index.html

 

Right. Actually doesn't the Unity Remote app still exist / work? The Unity remote is like the name suggests simply a remote control for the Unity editor. So you start the UnityRemote app on your phone, make it connect to the editor and the editor will simply stream (often a bad quality version) of your game output in the editor to your device. Inputs of the device are send to the editor. So that should enable you to use multi touch and accelerometer input inside the Unity editor. Though I barely ever used it and that was years ago. So I don't know the state of the app.

Though for simple tests the simulator should be enough.

Note: about 10 years ago when I worked for a games company we actually created a new apk and install it on the phone. However the usual build-and-run pipeline was way too slow as installing and uploading it through the ADB interface was way too slow. What we did instead:

1. We build the game into a dropbox folder
2. On the device back then I used the FileManagerHD on my tablet that had direct dropbox support.
3. I had a shortcut (widget) to the dropbox folder on my homescreen for quick access
4. Just tap the new apk, the filemanager downloads it over wlan in an instant and it installs within seconds

It wasn't the perfect workflow, however certain minor changes could be tested in the editor just fine. However at some point you always have to test on your actual device, especially when we talk about testing and optimising performance. A lot has changed since then, especially the profiler got expanded quite a bit.

So the short answer is that there's no one-size-fits-it-all solution. It depends on what you need to test. In most cases you can not simulate multi-touch input on a PC (unless that PC may have a touch screen?).

 

I wrote a

MicroTouch

class that combines mouse (when on PC or in the editor) with Touch (when on mobile targets) and gives you a single unified list of touches. You can grab it in my proximity buttons project.

proximity_buttons is presently hosted at these locations:

https://bitbucket.org/kurtdekker/proximity_buttons

https://github.com/kurtdekker/proximity_buttons

https://gitlab.com/kurtdekker/proximity_buttons

https://sourceforge.net/projects/proximity-buttons/

 

The code I tested is this,
https://gist.github.com/cwmagnus/ffeb9b0beb452e00ccbdaebc35a73928

But this does not work at phone simulator (galaxy note 20). I clicked the knob image by mouse left button and drag, but not moved.
Why?

 

Mine works... see above or get to debugging! The link you posted above is less than 20 SLOC but is highly dependent on UI setup... find out what's happening!

The link above does have crazy ninja stuff like this though:

Code (csharp):

1. knob = transform.GetChild(0).GetComponent<Image>();

Keep in mind that using GetComponent<T>() and its kin (in Children, in Parent, plural, etc) to try and tease out Components at runtime is definitely deep into super-duper-uber-crazy-Ninja advanced stuff.

This sort of coding is to be avoided at all costs unless you know exactly what you are doing.

If you run into an issue with any of these calls, start with the documentation to understand why.

There is a clear set of extremely-well-defined conditions required for each of these calls to work, as well as definitions of what will and will not be returned.

In the case of collections of Components, the order will NEVER be guaranteed, even if you happen to notice it is always in a particular order on your machine.

It is ALWAYS better to go The Unity Way(tm) and make dedicated public fields and drag in the references you want.