• Bugs

  • Unable to open Spine trial on Windows 10

    영어

C:\jdk-15\bin>java -cp testopengl.jar Test1
Test1:
Setting up display.
Setting display title.
Setting display resizable.
Setting display background.
Setting display location.
Setting display pixel format.
Setting display buffer format.
Initializing OpenGL.
Extracting version.
Extracting extensions.
Extensions: 398
Creating OpenGL instances.
Checking FBO support.
Checking seamless cube map support.
Enabling seamless cube maps.
OpenGL initialization complete.
Test1 is running.

Test1 window opens.

C:\jdk-15\bin>java -cp testopengl.jar Test2
Test2:
Setting up display.
Setting display canvas.
Setting display title.
Setting display resizable.
Setting display background.
Setting display location.
Setting display pixel format.
Setting display buffer format.
Initializing OpenGL.
Extracting version.
Extracting extensions.
Extensions: 398
Creating OpenGL instances.
Checking FBO support.
Checking seamless cube map support.
Enabling seamless cube maps.
OpenGL initialization complete.
Test2 is running.

Test2 window opens.

Windows 10 Home 64bit, version 20H2, OS Build 19042.685, Experience 120.2212.551.0
nVidia driver is 460.79.

No problem, it would be nice to not have to mess with displays to open Spine. 😃

Related Discussions
...

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.

Test4 works. It says it's using monitor #0, the tv, but it actually displays on my main monitor which is listed as monitor #1.
Test5 fails at pixel format.
Test6 works. It says it's using monitor #0 and opens on monitor #0.
Test7 is the same as Test6.
Test8 is the same as Test6.

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!

I uninstalled the previous version of Spine and reset my computer. I launched Spine with my display set to 'extend' and it still didn't open. I switched to single display and opened the launcher, set the version to 4.0.43-beta and before I clicked 'Start' I switched back to 'extend'. Spine opened with multiple displays. I had tried that with the previous version and the launcher wouldn't open unless it was set to single display.

After Spine opened I closed it and opened the launcher again. It opened with multiple displays.

It seems to still have an issue when opening the first time, but after you get it open and switch to multiple displays it works.

I have also noticed that Spine leaves the 'Start menu' shortcuts when uninstalling, maybe I had an issue with this version because of a setting that was left behind by a previous version? Just speculation.

Thank you guys, I really appreciate it! After I recover from Christmas I plan on purchasing the Pro version. This software is great! Using the runtimes to import the animations looks so much better than using spritesheets, plus the amount of space saved, and decrease in load times is fantastic!

Thank you!

And obviously the support!

Edit: After switching the Spine version back to 3.8.99 and restarting Spine, it will still open with multiple displays. I believe this was not the case before the new update, but I only tried it once and did not wait more than a couple seconds for Spine to open.

I had hoped it would be perfect, but it seems we at least made some progress.

Maybe when you run with multimon for the first time, the monitor it chooses by default (which should be the OS' default monitor) for some reason hangs Spine. When you close Spine (the launcher or editor) it remembers the monitor it was on, so it can put the window there next run. So when you ran with a single monitor, then enabled multimon, then closed Spine, it remembered the monitor and subsequent runs should use the same monitor.

Can you please try running Spine with multimon, then move the window (the launcher window should be sufficient) to the other monitor, close Spine (normally, not via end task), then run it again? My theory is that if Spine tries to start on one of your monitors it fails for some reason but the other monitor is OK.

When you uninstall, your Spine user folder should be deleted and that's where it stores the monitor it will start on. Specifically, it's in the <userhome>/Spine/settings/start-1.json file. Note the monitor number Spine stores is not necessarily the same numbers that the OS gives to the displays. Anyway, just deleting that file will reset Spine's monitor choice like a fresh installation. If Spine can open on either monitor in the test described in the previous paragraph, then the next thing to try is deleting this file (or the whole <userhome>/Spine folder). If it also runs after that then everything should be working!

The Spine installer shouldn't leave shortcuts after uninstallation. At least, I see the installer code that should delete them and it looks right. We'll check it to be sure.

When you run 3.8.99 it takes a little longer to go from the launcher to the editor window appearing. The monitor choosing happens when the launcher is shown, so if the launcher can show then the editor should also.

Great, glad you'll join the Spine community! 🙂

After moving just the launcher to the second monitor it still opened on my main display. I moved Spine to the second display and closed it. After that the launcher would not show again. I had to switch back to single display.

The same happened when I deleted <userhome>/spine.

Windows is using the tv as the default display, but when I switch to extend displays I have it set as the second monitor. Usually everything opens on my actual monitor.

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:

It works!

I uninstalled Spine, checked to make sure the <userhome>/spine had been removed. It had.

After installing the new version, it opened with no issues. Good job guys!

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!

20일 후

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:
 Loading Image

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!).