- Modifié
Hi,
Anyone experience where they check the color management in the setting and it crashes Spine on mac(M2 mac Studio). I wanted to check the linear blending mode but unfortunately can't on a mac.
Hi,
Anyone experience where they check the color management in the setting and it crashes Spine on mac(M2 mac Studio). I wanted to check the linear blending mode but unfortunately can't on a mac.
Hello, which launcher version do you have?
This issue was solved some months ago and requires a Spine Launcher update.
Try to update the launcher and see if the issue has been solved.
You can download the latest version of the launcher from your license page.
To reach your license page and download the latest version of the Spine launcher, you can use the link provided in the email you received when you purchased Spine. If you have lost this email or cannot find the link, you can recover it using the Spine license recovery page. Once you have access to your license page, you can download the latest launcher from there.
Unfortunately still no luck. I just downloaded the latest Spine Launcher and still ended up with black screen after I switch color management to linear blending.
Seems to work if I open 4.2 with Linear blending checked but opening it again with 4.1, I get the black screen again.
Thank you for taking time to help me out. I guess my work around would be to switch between 4.1 and 4.2 to check with Linear blending and turning it off after to get 4.1 working again. : )
Yah, Im very excited with the new features added on 4.2.
The project was saved with Unity that can't take 4.2 spine export. So need to wait until develop migrate to a newer Unity that can take spine 4.2. That's what I was told. So not sure the exact details of the compatibility issue.
Is it okay to work with 4.2 but in the export setting select 4.1? Though it says it "Data may be lost"
Generally no, you don't want to export JSON for an older version. Data can indeed be lost. It varies by older version. 4.1 to 4.2 loses physics constraints/keys and transform mode keys. You should not lose other data, but it is still not a great workflow.
Also note that to be sure you don't have issues, you should export with the version matching your runtime. So you can export 4.1 JSON, import into the 4.1 Spine editor, then export 4.1 JSON. This ensures the export is compatible, as exporting directly to an older version isn't exactly the same in all cases as the older version doing the export.