GeezerVison is showing github.com — Once you've used a gesture, Application.Quit() crashes unity. · Issue #200 · TouchScript/TouchScript
Once you've used a gesture, Application.Quit() crashes unity. #200DescriptionEven if I create a simple scene that just has a single sprite object.
I create the sprite.
Add Transform Gesture.
Transformer Gesture.
Release Gesture.
On Release I tell it to run Application.Quit(). Crash to desktop.
This doesn't appear to be the case when I build to my Windows 10 machine. But on my touch table it's happening every time. Across all projects. If you close out before any TS gesture is sent everything closes gracefully.
Any ideas?
output_log.txt
2016-01-07_212300.zip
Also: Here is the >entire< body of scripts in the scene:
using UnityEngine;
using System.Collections;
using TouchScript.Gestures;
public class DestroyMe : MonoBehaviour {
void OnEnable()
{
if (GetComponent<ReleaseGesture>())
{
GetComponent<ReleaseGesture>().Released += DestroyMe_Released;
}
}
void OnDisable()
{
if (GetComponent<ReleaseGesture>())
{
GetComponent<ReleaseGesture>().Released -= DestroyMe_Released;
}
}
private void DestroyMe_Released(object sender, System.EventArgs e)
{
Application.Quit();
}
}That's it. You can switch the gesture to any other gesture and the outcome should be the same :). Activityoafkad commented on Jan 7, 2016 Additional observation. If you release both fingers (from resizing via transformer) simultaneously, there will be no crash. If you release one, then the other, there will be a crash. valyard commented on Jan 9, 2016 What OS does the touch table use?
The log says
[TouchScript] Initialized Windows 7 touch input.
valyard commented on Jan 9, 2016 oafkad commented on Jan 9, 2016 Alright. I won't be near the table until Monday but I'll give that a shot. It's windows 7 embedded for what it's worth. oafkad commented on Jan 12, 2016 Update on this issue.
5.3.0 crashes still.
BUT
5.3.1p1 does not!
So for my purposes the problem is fixed. As it works with the latest unity (on Windows 7 and 10). valyard commented on Jan 18, 2016 For me 5.3.1x crashes if I build a 32bit app. Are you building a 32bit app? 64bit don't crash on 5.2.2 nor on 5.3.1x. oafkad commented on Jan 19, 2016 Yeah building in 32, which I didn't actually notice until you mentioned it. Unfortunately I can't really downgrade at work to test it in 64 bit. But regardless, with the latest unity (the p build) it doesn't crash in 32 either. valyard commented on Jan 19, 2016 Hm. It does crash for me in 32bit. oafkad commented on Jan 19, 2016 Very peculiar. Yeah, I've double checked. My output is x86 (not the x86_64). So unless the engine is overwriting it somewhere else during build that I'm unaware it should be 32 bit. madhuatlink commented on Jan 20, 2016 oafkad commented on Jan 20, 2016 @madhuatlink Upon removing TS from all 5 of our projects the crash stopped happening. It's entirely possible that it wasn't TS but:
A) Removing it fixed the crash.
B) The changes made above stopped it even with TS for us.
Again though, I'm open to it being entirely coincidence. Correlation != Causation, but it's a fairly consistent outcome in my neck of the woods at least. That isn't to say folks shouldn't look elsewhere though. valyard commented on Jan 20, 2016 I have an empty project with nothing but TouchScript crashing on me.
But I'm fairly certain that it's not TouchScript q: I blame Windows! oafkad commented on Jan 20, 2016 @valyard What OS are you running on? Because since I got your changes I can't replicate my crashes anymore at work or at home.
I'm using the latest 10 in both places (well more updated at home because work requires an IT for updates).
I even updated my package at home with your latest on the front page (that has the 199 and 200 changes) and still my personal project is completely rock solid up from crashing almost 100% of the time on editor close.
Oh weird...asterisks make it italic. Gonna remove those, feels a bit too energetic. valyard commented on Mar 5, 2016 I'm investigating this and figured out that there are two types of crashes:
- App has stopped working dialog.
- Crash folder appears near the exe file.
(2) is less intrusive and lets the app to be restarted, (1) shows crash in the face.
What crash types are you guys getting? valyard commented on Jul 28, 2016 jonkeee commented on Jul 28, 2016 Thx for the reply!
Now the APP is not crashing anymore after shutdown.
But now the Touchscript is not working in Player. (32bit and 64bit)
No Interaction and no TouchVisuals visible.
But Touch is working in Editor..
see ouput.log
DllNotFoundException: D:/01-Projekte/New Unity Project/build/test3_Data/Plugins/WindowsTouch.dll
at (wrapper managed-to-native) TouchScript.InputSources.InputHandlers.WindowsTouchHandler:SetScreenParams (int,int,single,single,single,single)
at TouchScript.InputSources.InputHandlers.WindowsTouchHandler.initScaling () [0x00000] in :0
at TouchScript.InputSources.InputHandlers.WindowsTouchHandler..ctor (TouchScript.Tags tags, System.Func4 beginTouch, System.Action2 moveTouch, System.Action1 endTouch, System.Action1 cancelTouch) [0x00000] in :0
at TouchScript.InputSources.InputHandlers.Windows7TouchHandler..ctor (TouchScript.Tags tags, System.Func4 beginTouch, System.Action2 moveTouch, System.Action1 endTouch, System.Action1 cancelTouch) [0x00000] in :0
at TouchScript.InputSources.StandardInput.enableWindows7Touch () [0x00000] in :0
at TouchScript.InputSources.StandardInput.OnEnable () [0x00000] in :0 valyard commented on Jul 28, 2016 @jonkeee: I don't know why WindowsTouch.dll is not being copied. Can you see if you have it in the project and copy it to build/test3_Data/Plugins/? jonkeee commented on Jul 28, 2016 The Dll exists under this folder.
I tried to copy it to the Folder Managed/ but still same error?! valyard commented on Aug 6, 2016 I just built your test project with the test TouchScript package in Win10 working under Parallels on OSX. The dll is being copied fine. Can you provide more details?
 jonkeee commented on Aug 9, 2016 The Dll is copied fine in WIN7 to. Also touch is working. But if i Close the Application, i get the error. "Player is not working anymore"
Can you send the testbuild? valyard commented on Aug 9, 2016 Seems to be Windows 7 issue.
Report from other users:
The touchscreen does not work for me with Windows 7 Unity 5.4 (latest release) and an IIyama T2735MSC screen. Your previous versions worked just fine. The boxes won't move or receive any touch. The old version sometimes crashes, and sometimes not. Haven't really figured out a correlation yet.
Although nmax from the forum (http://touchprefab.com/viewtopic.php?f=1&t=24473) reports that it works fine on Windows 7 with 5.3.4.
This is damn inconsistent and I don't have any touch device on win7... Need a dev with Win7 and a touch screen capable of debugging stuff. jonkeee commented on Aug 9, 2016 With this testproject I get no Touches in Player.
Also no crash at App Quit.
WIN7
Unity 5.3.4
No Touchdevice connected
Still this error in log:
Fallback handler could not load library C:/Users/Tim/Downloads/p/build/test_Data/Mono/libC:/Users/Tim/Downloads/p/build/test_Data/Plugins/WindowsTouch.dll
DllNotFoundException: C:/Users/Tim/Downloads/p/build/test_Data/Plugins/WindowsTouch.dll
at (wrapper managed-to-native) TouchScript.InputSources.InputHandlers.WindowsTouchHandler:SetScreenParams (int,int,single,single,single,single)
at TouchScript.InputSources.InputHandlers.WindowsTouchHandler.initScaling () [0x00000] in :0
at TouchScript.InputSources.InputHandlers.WindowsTouchHandler..ctor (TouchScript.Tags tags, System.Func4 beginTouch, System.Action2 moveTouch, System.Action1 endTouch, System.Action1 cancelTouch) [0x00000] in :0
at TouchScript.InputSources.InputHandlers.Windows7TouchHandler..ctor (TouchScript.Tags tags, System.Func4 beginTouch, System.Action2 moveTouch, System.Action1 endTouch, System.Action1 cancelTouch) [0x00000] in :0
at TouchScript.InputSources.StandardInput.enableWindows7Touch () [0x00000] in :0
at TouchScript.InputSources.StandardInput.OnEnable () [0x00000] in :0 jonkeee commented on Aug 16, 2016 Even with new version 8.2 the app crashes after quit.
Is it needed to connect a multitouch device?
Do i have to switch to WIN10 to fix the problem? valyard commented on Aug 18, 2016 8.2 doesn't include this change since it's not working for everyone... jonkeee commented on Aug 18, 2016 Ok so I tried it on 3 different Machines.
2x PCs WIN7 5.3.4 & 5.4 and 1PC WIN10 5.3.4 & 5.4
Game works as expected but crashes after Quit with an Access Violation Error on all machines ... also the example Projects. Don't know what's wrong with my machines :-(
For this Project I have to skip Touchscript unfortunatly. Hopefully it works for my next Project. Wim-Alligence commented on Nov 9, 2016 When I disable "Standard Input" I don't have the exit error... (using TUIO input) valyard commented on Nov 10, 2016 valyard commented on Dec 8, 2016
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|
