Spine version: 3.8.99 PRO
Launch: 4.0.08-legacy
Editor is lagging every few second.
(p.s. Window and graphic drive are up-to-dated)
Spine version: 3.8.99 PRO
Launch: 4.0.08-legacy
Editor is lagging every few second.
(p.s. Window and graphic drive are up-to-dated)
Sorry for that. Could you let us know what hardware you have (CPU, GPU, RAM)? Could you try version 3.8.98? Does it happen for any project or a specific project?
Mario escribióSorry for that. Could you let us know what hardware you have (CPU, GPU, RAM)? Could you try version 3.8.98? Does it happen for any project or a specific project?
Processor: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz 3.30GHz
no GPU
Installed RAM: 16.0 GB
I have tried version 3.8.98, but the lagging problem still happened.
But it just happen in a specific project.
The size of that project or other setting are same as other project that can run smoothly.
Thank you. :tear:
Nate escribióWe'd love to figure out what is going wrong on your computer. I've sent you an email.
Note you definitely have a GPU.
Spine prints it out when it starts, so you can post your spine.log to see it.
Here is the spine log.
But the directory shown in log isn't the one that I opened. I duplicated the folder form server which is "//address/Game_Graphic/Resource/folder name/03_Spine/folder name/project name"
" to my located disk.
Spine happens lagging problem no matter I open the project from server or located disk.
Spine Launcher 4.0.08-legacy
Esoteric Software LLC (C) 2013-2020 | http://esotericsoftware.com
Starting: Spine 3.8.98
Spine 3.8.98 Professional
Licensed to: (company)
NVIDIA Corporation, Quadro K620/PCIe/SSE2, 4.6.0 NVIDIA 456.71
Started.
OpenAL 1.1, Default audio device
WARNING: Extremely slow file system access: //address/Game_Graphic/Resource/folder name/03_Spine/folder name/project name
"
Thanks, that helps. It appears the problem is your Spine project is configured to use a path that is a network share. Paths that start with //
will access paths on other computers over the network and that can be very slow. You may have opened your Spine project file from a local folder, but the project file has other paths in it: for each skeleton there is an images path and an audio files path. You should check the Images
and Audio
tree nodes for each skeleton in your project and make sure they don't use a path that starts with //
.
Nate escribióThanks, that helps. It appears the problem is your Spine project is configured to use a path that is a network share. Paths that start with
//
will access paths on other computers over the network and that can be very slow. You may have opened your Spine project file from a local folder, but the project file has other paths in it: for each skeleton there is an images path and an audio files path. You should check theImages
andAudio
tree nodes for each skeleton in your project and make sure they don't use a path that starts with//
.
Thank you very much! It works!
You help me a lot! :love: