Sorry for the trouble. Could you please try running SpineTrial.com from the command line and pass the parameter "

trace" (without the quotes) and tell us what the output is?

That is indeed behaviour we haven't seen before. Could you give us details on your display setup as well as your system specs, including what GPU(s) you run, and what driver version(s) you have installed?

I'm glad you found a way to fix it! It's very strange that happened though and we'd really like to fix it. We've tested enabling and disabling multiple displays, moving them so the last Spine location is off screen, etc and haven't been able to reproduce the problem.

To be sure, is the 1278x714 resolution shown in the Spine log the correct resolution for one of your monitors?

What's strange is that your log never gets to printing the GPU info or to Launcher window shown. That means the problem is not that the window is shown off screen, but that it never gets to the code that shows the window. Instead it gets stuck somewhere. The most likely culprit is when initializing OpenGL, as that is pretty complex and relies on the GPU drivers. I don't mean to push all the blame the drivers of course, I'd much rather that we are able to fix it!

Thanks for your patience as we work on this issue!

We've released a new launcher, version 4.0.19. Can you please try downloading Spine again, installing, and running with `

trace`? That may give us a little clue.

In case the updated launcher doesn't correct the problem, could you please tell us which monitors you are using?
I'm especially curious which monitor runs with a resolution of 1278x714

Also could it be that you are running any display sharing software? For example, to have a mobile device show up as a monitor, or any software related to monitors or arrange windows at all.

We've tried so many things now, but still can't reproduce the problem. There's got to be something interesting going on with your hardware or software setup that we are missing.

We experimented with Actual Multiple Monitors but didn't find it to cause any problems with Spine. Damn, it seemed likely!

Your log indicates that something hangs during OpenGL initialization. Our best guess so far is something bad is happening with the graphics driver, but to really dig into it we need to see it happening. We don't currently have an RTX 2060 but we've tested with an RTX 2070 Super and an RTX 2080 without luck. If other users with the same problem are using an RTX 2060 then we may need to buy one. Someone just posted what looks like the same problem.

We've create a little tool that creates an OpenGL window similar to Spine, but is a whole lot simpler and does more logging. Our hope is that if this is run on a computer that has problems launching Spine when multiple monitors are connected, then the logging will give us some clues so we can fix Spine.

The tool can be downloaded here. To run it, from a command line type:

java -jar testopengl.jar

You'll need a relatively new version of Java, for example Java 15 which you can get here. Under 15 GA click the zip link to download, then extract the ZIP to a folder and find the bin subfolder. That contains the java.exe file that you need to run the command above. For example:

C:\path\to\java.exe -jar C:\path\to\testopengl.jar

What you run the tool it should show a bright green window with buttons to minimize, fullscreen, maximize, and close. If you don't see that then please paste all the logging the tool output in the command window. Thanks a lot for your help!

Thanks! That is actually sort of good, it means the simple test sees the same problem. It's a loooot easier to work on than Spine, which is much more complex.

Can you please try this, to run Test1? (using the same testopengl.jar file you already downloaded)

java -cp testopengl.jar Test1

That will run the simplest possible test. This will help narrow down the problem.

And also:

java -cp testopengl.jar Test2

That will run a slightly more complex test than Test1, but not as complex as Test3 (Test3 is run when you do -jar).

Can you please let me know the exact version of Windows you are on? Instructions to find that are here. It would also be very helpful if you could let us know the exact version of the graphics driver you are using. Our hope is that we can use these versions to reproduce the problem. If not it is much harder to debug and we may need to create another test tool.

Thank you for your assistance and patience as we work through this problem!

This is surprising, I expected Test2 to fail like Test3. Now we just need to narrow down the difference!

We've updated the tool at the same link. Can you please try running tests 4, 5, 6, 7, and 8? You don't have to paste the output, I'd just like to know which of those shows the window, if any. If the window has no title bar, you can click anywhere to exit.

Fantastic, thank you! I believe the information you have provided is sufficient to solve the problem. It appears that some graphics drivers really don't like if we change the application's window size/position too early. We've implemented a fix in launcher version 4.0.21 and editor version 4.0.43-beta. Both are released now. Please note you'll need to download and reinstall Spine to get the latest launcher. I'm anxious to hear how it goes!

Seems it's something about the second monitor (the TV). We've tried all the monitors we have, messing with EDIDs, custom resolutions, and virtual monitors, but haven't gotten it to fail the same way. Maybe if your TV isn't terribly expensive we could buy one.

Oh wait! The monitor fix is OK in the editor, but we found an error with how it was done in the launcher. I'm hopefully this is the answer. We've just uploaded a new launcher, version 4.0.22. Could you please give it a try when you get a chance? :dizzy:

Wooo! That's the best news this year! What a nightmare. It's really hard to fix something we can't see. It wouldn't have been possible without your patience

thank you for all your help!

Hi, I'm currently experience a similar issue with Spine not opening. My company has pivoted to employees working from home and I'm unable to get Spine working on my home PC. I've installed, reinstalled, and even tried installing the Spine trial just in case. None of them want to launch. The installer version I'm using is 4.0.23.

There are no spine.log files being created and when I try launching it through Command Prompt it also doesn't report any activity. It seems like nothing is happening at all no matter which method I use to open Spine.

I am running a multi monitor setup and I've tried restarting using only one monitor still to no avail.

I followed as much of the trouble shooting as I could above, I ran all of the java OpenGL tests 1 through 8 mentioned above and didn't get any errors. All of the tests were able to open the green window.

Are there any other suggestions or troubleshooting help I can follow?

My PC specs are:
AMD Ryzen 9 3950X
Nvidia RTX 3080
Two 3440x1440 ultrawide monitors and a single 4k 3840x2160 monitor

@reddums Sorry you are having trouble!

When you run from a command prompt, be sure you run Spine.com by typing either spine or spine.com (case doesn't matter). If you type spine.exe then it will run but it will not print anything.

When you run by typing spine.com, is anything printed? Does it hang or does it bring you back to the command prompt where you can type another command?

Are you running antivirus software? If nothing at all is printed when running spine.com from the command line then it sounds like an antivirus is wrecking Spine's files.

@Nate I am running spine.com and it hangs for a second before returning to the command line.

The only type of protection installed is SentinelOne, which I'm unfortunately unable to disable or interact with without IT intervention. I can get in touch with IT to see if they can temporarily disable it and see if that fixes the issue.

@Nate

I was able to find an older installer for version 3.8.99 and it installs and opens just fine with this version. Any idea why this one works but newer versions won't?

Our company has Spine Professional licenses, if I install this older version, are we able to update to the latest version with our license?

Ah, SentinelOne definitely wrecks Spine. Other users have had this problem with SentinelOne. You'll need your IT department to whitelist Spine. You can show them this SentinelOne configuration screenshot:

Изображение удалено из-за отсутствия поддержки HTTPS. | Показать

As far why SentinelOne doesn't wreck the old launcher, only they can say. Antivirus software uses heuristics to guess at what might be malicious and they often get it wrong. The old launcher can run Spine editor versions up to and including 3.8.99, but not versions higher than 3.8.99.

Alright, I'll let IT know and hopefully that fixes the issue.

Thanks Nate

A coworker and I have run into this problem (2 weeks apart) we got it running on another pc but we're nervously awaiting to see if that stops working too. It's quite a serious problem for us at the moment.

• Have tried restarting device, admin launch, command prompt, reinstalling Spine
• Run through all troubleshooting Spine Troubleshooting but no luck
• Spine.log exists but is empty.
• Confirmed it is not an issue with antivirus/anti-malware or firewall.
• nothing in sentinel one agent on local machine.
  Have looked at similar issues on the forums
• Does not work after unplugging second monitor
  Checked and tried somethings from this
  Spine not launching on Windows 10
  Unable to open Spine trial on Windows 10 )

My coworker has tried to using the trial version to get by part of the workflow but it's also not opening and leaving empty log.

Device Specifications:

Processor 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz 2.50 GHz
Installed RAM 16.0 GB (15.9 GB usable)
Device ID 954CF3F4-85F5-45F4-9780-9AD045C06B71
Product ID 00330-80027-44357-AA909
System type 64-bit operating system, x64-based processor
Pen and touch Pen support
Windows 10 Pro

@Hana, have you tried running Spine from the command line? You may see messages there that don't make it to the log.

Sentinel One is known to interfere with Spine heavily. It will actually kill the Spine process before it is even able to log anything. How did you ensure it's not interfering?

@Nate The command promt was empty

Our internal and External IT ran some Sentinel tests and confirmed wasn't interfering but I asked for details to share here and they have taken another crack at it. So hopefully it's that!

Sentinel is very invasive, it's almost certainly that. It can be configured to leave Spine alone though (unlike others, like Comodo, which can't!).

Hello, we are a gaming company and we've ordered the enterprise license for our art teams, however, we are unable to run Spine v4.XX on any of our win10 computers. the older version like v3.xx is working fine but the latest version v4 isn't.
The issue is pretty similar to described above, after clicking the spine shortcut, seems like nothing is happening at all.

After a deeper investigation, we've found an error in the Windows Application Log - related to a faulty module of ucrtbase.dll and in the log of spine another error, attached to this post.

We are not using SentinelOne, however, we do have other security tools installed on our computers - ForcePoint and BeyondTrust.
We cannot disable them so easily, please let me know if there is any possible way to troubleshoot or work around this issue.

Your help/support will be highly appreciated and let me know if it's better to open a separate post about this issue.

@mbarkov Discussion here or in a separate post is fine. The error in the log you've shown indicates that other software you have is interfering with Spine. We haven't encountered ForcePoint or BeyondTrust specifically yet, but like other invasive security software, I assume it attaches and injects code into other processes. Spine is very sensitive to this. Having other software manipulate Spine only causes problems, leading to crashes or other instability and malfunctions. It's impossible for us to tell if those problems are our bugs or caused by other software. You'll need to whitelist Spine to keep such software from interfering.