If you are using this package, you have to configure the cursor manager correctly. If you place the cursors incorrectly, you will have a duplication problem since the touches will not disappear correctly. I recommend using the ones in the example

Over all this is a great asset, I'd love to give it 5 stars but there are a few issues which have resulted in me giving it a lower review score. 1) The asset was last updated on July 30 2017. It's now 8/11/2022 and there is an outstanding list of 72 bugs that haven't been addressed. For all intents and purposes it looks like the asset is no longer being maintained. 2) While this asset has great documentation, the forums the github site redirects to wants to install some shady plugin before you can even visit the site. I believe I tried the link a short while back and simply found myself at an expired web address. It looks like someone might have bought the domain and is now using it to potentially spread malware via browser extensions. 3) Assumptions were made: 1) One of the first assumptions being made by the C++ plugin code is that there is only a single screen. Screen Height/Width/Scale/Offset are all set globally. So if you have a Unity Game which has multiple screens with varying resolutions or camera settings you'll have to modify the code because this is not going to work as an out of the box solution for you. 2) Touch processing is limited to a single touch digitizer. This results in functionality similar to unity's default touch behavior as introduced in Unity 2020 (prior to unity 2020 it was possible to detect touches on 2 different touch screens without the touch getting redirected to the primary display). I've personally been working on extending this functionality by creating a new variation that uses RAWInput in windows and processes any touch on any touch device thanks to the INPUT_SINK flag. 4) The plug-in's code could use a bit of cleanup. Passing in a context to the Init function of the plugin would've been a better way to support Windows7, Windows8, TUIO and even RAWInput devices rather than having explicit parameters. 5) I've used TouchScript for well over 3 years now and one of the largest complaints I have with the asset is one any touch plugin would have. At first things go well after you import this asset into the project...touches work as intended and at some point in development you notice a touch isn't being registered....You turn on/off game objects, enable/disable colliders, play with the physics layers and hours later you find out some invisible object from another scene that stuck around after it was unloaded has been blocking your touches. While the asset comes with tools to help debug these types of issues it's not really always obvious why a touch wasn't processed and trying to figure out why a third party asset that uses C++ code in a dll and speaks to unity isn't doing what you expect can be a bit of a time sink from a development perspective.

不错

挺好用的

so convenient

this plug-in is Just Amazing !! and ... FREE!!

good

Really wonderful asset!

Really qualitative asset. Must be tried ! It was well thought and architectured. Unfortunately the project is no more maintained. But all the documentation provided on the GitHub project is clear. You will need to remove some deprecated line of code (clearly mentionned by Unity) and after all works really fine !

Just works!