- 수정됨
Spine Editor takes a while to start (Beta)
Hi, I am facing an issue with the editor, starting the launcher works fine but after I click on "Start" the editor takes about 1-2 minutes to open (the spine icon is still visible in the Windows taskbar but does not open nor displays anything).
Tried running:
"C:\Program Files\Spine\Spine.com"
---
trace | lessAnd got the following output:
TRACE: Home: C:\Program Files\Spine
Spine Launcher 4.0.20 (23)
Esoteric Software LLC (C) 2013-2020 | http://esotericsoftware.com
Windows 10 Home amd64 10.0
TRACE: Parameter:
---
trace
TRACE: Reading settings: C:\Users\Sam\Spine\settings\start-1.json
TRACE: Initializing OpenGL...
NVIDIA Corporation, GeForce GTX 1070/PCIe/SSE2, 4.6.0 NVIDIA 432.00
TRACE: Started launcher: 12.25s
TRACE: Launcher window shown.
TRACE: Request: api, updateCheck
TRACE: Connected: https://usapi.esotericsoftware.com:443
Starting: Spine 4.0.41-beta Professional
Spine 4.0.41-beta Professional
Licensed to: **************************************************************
TRACE: Reading settings: C:\Users\Sam\Spine\settings\start-1.json
TRACE: Reading settings: C:\Users\Sam\Spine\settings\editor-1.json
TRACE: Reading settings: C:\Users\Sam\Spine\settings\recent-1.json
TRACE: Reading settings: C:\Users\Sam\Spine\settings\views-1.json
TRACE: Editor window created.
TRACE: Reading settings: C:\Users\Sam\Spine\settings\hotkeys-1.txt
TRACE: Started editor: 2.69s
TRACE: Editor window shown.
OpenAL 1.1, Default audio device
TRACE: Temp file runnable failed: C:\Users\Sam\AppData\Local\Temp\.spine\Sam\xfiledialog64.dll
[invoke]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at s.PYy._(_:211)
at s.uid._(_:157)
at s.Snc._(_:119)
at s.Snc._(_:100)
at s.Snc._(_:152)
at s.PYy.V(_:153)
at s.PYy._(_:55)
at net.tomahawk.XFileDialog.<clinit>(_:33)
at s.GXc.V(_:336)
at s.tDz.run(_:262)
<events>
Cause: [UnsatisfiedLinkError] C:\Users\Sam\AppData\Local\Temp\.spine\Sam\xfiledialog64.dll: Can't find dependent libraries
at java.lang.ClassLoader$NativeLibrary.load0(Native Method)
at java.lang.ClassLoader$NativeLibrary.load(Unknown Source)
at java.lang.ClassLoader$NativeLibrary.loadLibrary(Unknown Source)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.load0(Unknown Source)
at java.lang.System.load(Unknown Source) ...
...
...
...List of similar errors continues...
...
...
TRACE: Temp file runnable failed: C:\ProgramData\SpineTrial\.5f42bc25b382e921\xfiledialog64.dll.1663decc239c9908.tmp
[invoke]
at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at s.PYy._(_:211)
at s.kAJ._(_:188)
at s.Snc._(_:119)
at s.Snc._(_:100)
at s.Snc._(_:132)
at s.PYy.V(_:184)
at s.PYy._(_:55)
at net.tomahawk.XFileDialog.<clinit>(_:33)
at s.GXc.V(_:336)
at s.tDz.run(_:262)
<events>
Cause: [UnsatisfiedLinkError] C:\ProgramData\SpineTrial\.5f42bc25b382e921\xfiledialog64.dll.1663decc239c9908.tmp: Can't find dependent libraries
at java.lang.ClassLoader$NativeLibrary.load0(Native Method)
at java.lang.ClassLoader$NativeLibrary.load(Unknown Source)
at java.lang.ClassLoader$NativeLibrary.loadLibrary(Unknown Source)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.load0(Unknown Source)
at java.lang.System.load(Unknown Source) ...
ERROR: Unable to load file dialogs:
[error] Error loading library for Windows 10 Home, 64-bit: xfiledialog
at s.PYy._(_:58)
at net.tomahawk.XFileDialog.<clinit>(_:33)
at s.GXc.V(_:336)
at s.tDz.run(_:262)
<events>
Cause: [error] s.fPx: Unable to create a temporary file (xfiledialog64.dll).
at s.PYy.V(_:197)
at s.PYy._(_:55) ...
Cause: s.fPx: Unable to create a temporary file (xfiledialog64.dll).
at s.Snc._(_:157)
at s.PYy.V(_:153) ...
Cause: s.fPx: Unable to create a temporary file.
at s.Snc._(_:113)
at s.Snc._(_:152) ...
Cause: [invoke]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at s.PYy._(_:211)
at s.uid._(_:157)
at s.Snc._(_:119)
at s.Snc._(_:100) ...
Cause: [UnsatisfiedLinkError] C:\Users\Sam\AppData\Local\Temp\.spine\Sam\xfiledialog64.dll: Can't find dependent libraries
at java.lang.ClassLoader$NativeLibrary.load0(Native Method)
at java.lang.ClassLoader$NativeLibrary.load(Unknown Source)
at java.lang.ClassLoader$NativeLibrary.loadLibrary(Unknown Source)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.load0(Unknown Source)
at java.lang.System.load(Unknown Source) ...
Basically I get lots of those UnsastifiedLinkError messages until the editor is able to finally start, this seems to be happening only in the beta since opening Editor version 3.8.99 with the same
trace command works fine and no errors are displayed in the output.
Any idea of what could be causing this?
Thanks in advance.
I managed to solve the problem, in case somebody else runs into this, try the following:
1- Whitelist spine in your antivirus software.
2- Update your graphics drivers to the latest version.
3- Delete your temp folder "C:\Users<USERNAME>\temp\".
Sorry that happened to you, but I'm glad you figured it out. We haven't seen that as a result of antivirus software. It looks like your system is missing a library that one of Spine's DLLs needs, but maybe the antivirus is doing something odd. It's also strange that it takes minutes. It tries many times because some users have really screwy file permissions (temp or user folder not writable by the user, etc) and it doesn't know if it will fail every time. We'll reduce the number of tries so it doesn't take so long, and we can add checks if a DLL can't load to make sure the DLL file hasn't been deleted or modified, which may give a better error message.
No worries, the issue was on my end since it was a combination of both my antivirus and outdated drivers. Whitelisting Spine in my antivirus allowed the editor to open faster but errors still appeared in the
trace command, updating the drivers finally got rid of them.
I was using the default drivers provided by Windows 10 so they were probably very old and/or were missing stuff. Also, not sure if related, but the Microsoft Visual C++ 2017 Redistributables were installed alongside the new drivers so I wonder if missing those were causing the errors.
Ahh, that would make sense. We'll rebuild the problematic DLL so it doesn't require those redistributables. Cheers! :beer:
Sounds good, thank you very much! 