Ghost and Unity Layers

IndieDoroid

...message editing expired while I was typing. 🙄

hmm.. I just created a new URP project and the skeleton ghost works there.. ok something else must be happening with the main project. 🤔

Also another thing I noticed is that there is no warning about spine 4.0 incompatibility with this new URP project.

I wonder if that has anything to do with it?

Because on the main project, whenever I re-import the libraries I always get warning pop ups saying some spine example files being version 4.0 and weren't imported correctly. (because I updated all the spine files and runtimes to version 4.1)

I'll do a bit more testing and get back to you.
Thanks for the confirmation!

Harald

IndieDoroid Because on the main project, whenever I re-import the libraries I always get warning pop ups saying some spine example files being version 4.0 and weren't imported correctly. (because I updated all the spine files and runtimes to version 4.1)

Then I assume that you then did not cleanly remove the 4.0 runtime before installing the 4.1 runtime (as described here), and thus have some leftover 4.0 files remaining which trigger the warning. Unless you have modifed the spine-unity runtime files, I would recommend removing your potentially "mixed" 4.0 / 4.1 runtime again and installing the latest version of the 4.1 runtime cleanly. As always, backup your project first, just in case anything goes wrong or if you forgot about some modifications you did to the runtime.

IndieDoroid

Harald
Thanks Harald. Everything works now. I re-installed the runtime and deleted all the older Spine files using ver 4.0

Harald

@IndieDoroid Glad to hear you've figured it out, thanks for getting back to us!

IndieDoroid

Hi Harald
Ok the issue came back again. I was wrong with my previous reply.

I found out what was the cause. It's indeed because Spine Skeleton Ghost only renders to the Default layer. 😥

Could you please suggest how I could set the Skeleton Ghost to render on another layerID? I made a movie so you can see what I mean.

Sorry for the trouble and thanks again for your continued help 🙂

Harald

@IndieDoroid SkeletonGhost spawns GameObjects programmatically here, then sets the GameObject's hide flags to hide them in the hierarchy here. So you just need to change the layer of the hidden spawned ghost GameObjects accordingly.

IndieDoroid

Thanks Harald,

I'm not quite sure what that code is doing, but I'll give it a try.

If I hack this script, will it get overridden when a new Spine runtime is installed? 🤔

IndieDoroid

Thanks Harald,

I'm not quite sure what that code is doing, but I'll give it a try.

If I hack this script, will it get overridden when a new Spine runtime is installed? 🤔 -- I guess the fix is to use and save a different iteration of the script.

--UPDATE--
Ok got it working! I just added a line to change each spawned game object layerID.

I also changed this. Hopefully that doesn't do anything nasty to the script.
const HideFlags GhostHideFlags = HideFlags.None;

Just out of curiosity, what is the benefit of using the HideFlags variable\const? .. from what I can see, it just makes it harder to debug the hierarchy 😵‍💫

Also I read online that getcomponent() isn't suggested to be run at runtime? Best to keep it in Awake()\Start()? Is it ok to keep running all the time?
pool[i] = go.GetComponent<SkeletonGhostRenderer>()
I use the ghost script whenever a power up is used, which is frequently. 🤔

Harald

IndieDoroid If I hack this script, will it get overridden when a new Spine runtime is installed? 🤔 -- I guess the fix is to use and save a different iteration of the script.

If you modify the original script, then yes, you might accidentally override your changes. You could however easily just create a copy of this example script (named differently) an adjust it to your needs. The scripts in the Spine.Unity.Examples namespace are as reference for your own implementation. They are not a generic solution which covers all use cases.

IndieDoroid I also changed this. Hopefully that doesn't do anything nasty to the script.
const HideFlags GhostHideFlags = HideFlags.None;

It will just no longer hide it in the hierarchy, as the name implies.

Just out of curiosity, what is the benefit of using the HideFlags variable\const? .. from what I can see, it just makes it harder to debug the hierarchy 😵‍💫

This line is for hiding the many ghost renderer instances (10 per skeleton ghost) in the hierarchy. Otherwise it would be cluttering the hierarchy window with lots of entries.

IndieDoroid Also I read online that getcomponent() isn't suggested to be run at runtime? Best to keep it in Awake()\Start()? Is it ok to keep running all the time?
pool[i] = go.GetComponent<SkeletonGhostRenderer>()

I use the ghost script whenever a power up is used, which is frequently. 🤔

oh nevermind, it doesn't get run all the time! got confused.. 🥴

Yes, it's run only in Start. In general it's only an example component, if you dislike anything, please change it accordingly (in your own copy of the script).

IndieDoroid

oh nevermind, it doesn't get run all the time! got confused.. 🥴

IndieDoroid

Harald If you modify the original script, then yes, you might accidentally override your changes. You could however easily just create a copy of this example script (named differently) an adjust it to your needs. The scripts in the Spine.Unity.Examples namespace are as reference for your own implementation. They are not a generic solution which covers all use cases.

Yea, that's what I did. 🙂I had to also make a copy of SkeletonGhostRenderer.cs it seems.

Harald This line is for hiding the many ghost renderer instances (10 per skeleton ghost) in the hierarchy. Otherwise it would be cluttering the hierarchy window with lots of entries.

Now that you mention this.. I can see the benefits of it. I'm going to figure out how to incorporate this into my other scripts. 😁

Thanks for the help Harald!

Harald

IndieDoroid I had to also make a copy of SkeletonGhostRenderer.cs it seems.

I don't see why that is necessary, but you might have your reasons 🙂.

IndieDoroid Now that you mention this.. I can see the benefits of it. I'm going to figure out how to incorporate this into my other scripts. 😁
Now that you mention this.. I can see the benefits of it. I'm going to figure out how to incorporate this into my other scripts. 😁

Thanks for the help Harald!

🙂 Glad it helped.

IndieDoroid

Harald I don't see why that is necessary, but you might have your reasons 🙂.

Unity was telling me there were two versions of the same script even though I made a copy of SkeletonGhost.cs -- I narrowed it down to namespace Spine.Unity.Examples. I tried to remove the .Examples, but the duplicate SkeletonGhost script wasn't able to find SkeletonGhostRenderer.cs (it'd only work if I also remove .Examples from SkeletonGhostRenderer.cs) ...

Anyways its probably confusing.. but everything works now. Thanks again

IndieDoroid

Hi Harald,

So I dove deeper into the GhostSkeleton script. It's pretty interesting how the script functions. I swapped out the Ghost shader for Spine's Unlit shader, it created some cool results.

I wanted to adjust the render queue because Unity's depth blur was blurring the object pooled ghost mesh renderer. (This undesired blurring also happens even if I use the ghost shader)

I added line 176 in the SkeletonGhost.cs script, but it doesn't seem to update the new material at runtime. The goal was to have the render queue become alpha test with -100 offset.

My guess is that I think it might have to do with the fact the Spine shader uses the render queue offset variable. Is that correct? If so how do we access that at runtime? 🤔

Thanks for the help Harald. Hope you don't mind diving deeper into this subject.

IndieDoroid

Oh nevermind. fixed it. God I suck at coding 🤦‍♂️

I needed to put it outside of the ghostMat block

Harald

Glad to hear you've figured it out, thanks for letting us know!

Sonraki Sayfa »