Hello!
I am trying something simple:
I have a cylinder mesh with a transparent shader graph on it that make the top transparent with a smooth step. No alpha clip and blending set to alpha.
I also have a basic particle system, with square particles using the URP/Particles/Unlit shader, set to transparent and blending to alpha.
Polyspatial is set up with BakeToMesh for the particles.
Here is what I want the result to look like (and it does look like this sometimes, depending on the view angle)
But unfortunately, most of the time, the result is this
I am using Unity 2022.3.32, with Polyspatial package version 1.2.3
Do you have any idea of what the issue might be? If it not an issue on my side but a general bug, I can fill am issue report !
Thanks!
2 Likes
Yes; it’s basically a sorting issue. Typically, you can resolve these issues using the VisionOS Sorting Group component; however, in the current version of PolySpatial, that doesn’t correctly override the sorting applied to bake-to-mesh particles. We have a fix for that that will go out with the next release.
Good to know, thank you for the answer!
1 Like
Our development work was hampered by this problem。When is the next version expected to be released
I can’t give you an exact date, but we’re actively working on it and hope to release soon.
Hello! I am trying the exact same scene with Unity 2022.3.32 and all the packages updated to 1.3.1 and I am still having an issue. I added the VisionOS Sorting group component, and set my cylinder order to 1, and my particle system to 0 (because I want the particles to be hidden by the visible part of the cylinder), but I am still having the exact same rendering issue that I showcased in my initial post. Am I missing an option that need to be checked? Thank you!
(I am testing on the simulator version 1.2)
Sorry; it looks like we fixed the issue in 2.0.0-pre.9 (“VisionOS Sorting Group … components will now apply to particle systems.”), but didn’t backport to 1.X. We will be sure to fix that in a subsequent release.
Understood, thank you for the answer. Is it something to be expected in 1.3.X of the package, or more 1.4? (The question is basically how long would the wait be for the backporting haha)
I believe it should be possible to include it in the next bugfix release (1.3.X), though I don’t have a time estimate for that at the moment. Thanks for your patience!
Understood, thank you for your answer!
