Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

Serious Problem with URP. SkeletonGraphic gonna disappear!!

ggzerosum

<Symptom>

SkeletonGraphic disappear in playmode & build when 'Renderfeature' existing in 'pipeline renderer'.
This is serious problem with my team because we should use post process effect on certain layer.
Please help!!!!

<Reproduce>
Unity version

4. 3f1 (Reproduced also with 2019. 3. 0)
Spine version
Runtime : spine-unity 3.8 (updated 2020-08-17)
URP Shader Package : spine.urp-shaders 3.8 (updated 2020-08-07)

Spine Setting
Export Setting

Unity Settings
Canvas (Master canvas in video)

Spine Setting

Pipeline Setting
Pipeline

Pipeline Renderer

Existing Renderfeatrue(New Render Objects) do nothing.

Camera Setting

ggzerosum

Harald

Unfortunately we could not reproduce this problem. Does the problem not occur when you disable the New Render Objects render feature?

Could you please send us a minimal Unity project that still shows this problem, as a zip package to contact@esotericsoftware.com. Then we can have a look at what's going wrong.

ggzerosum

Harald написал
Unfortunately we could not reproduce this problem. Does the problem not occur when you disable the New Render Objects render feature?

Could you please send us a minimal Unity project that still shows this problem, as a zip package to contact@esotericsoftware.com. Then we can have a look at what's going wrong.

After few trying to solve the problem, i have assurance my problem is related with some kind of unity's bug.

I just move z position of main camera and restart project. And then, all problem gone.

I can't believe this. Because ScreenSpace-Overlay is not related with camera's position.
It seems that unity has some kind of bugs only occured on first setting of URP.....

Anyway, problem does not occured with same project now.

But for other users who can suffer same problem, i will create and send other project can reproduce problem in today.

Harald

Oh dear, thanks very much for sharing your insights. This indeed sounds like an unfortunate bug on Unity's side.