-
-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple UIParticleOverlayCamera in scene. #73
Comments
@as3mbus I will use |
ah yes. i used some RuntimeInitializeOnLoadMethod to always load setup scene before starting actual scene. so most likely scenario is overlay camera might not be fully initialized before changing scene to setup scene, and when going back to actual scene where particle ui reside it'll try to setup init itself one more time. (idk if this actually happen, but reading the code lead me to such assumption) |
🎉 This issue has been resolved in version 3.0.0-preview.8 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
somewhat solved it with workaround by moving overlay camera into my setup scene. i believe warning is somewhat not necessary for this case as you will always destroy the camera if one already exist. |
Please try to use |
tested, and it worked fine thanks for your fast response 👍 |
# [3.0.0-preview.8](mob-sakai/ParticleEffectForUGUI@v3.0.0-preview.7...v3.0.0-preview.8) (2020-03-03) ### Bug Fixes * abnormal Mesh Bounds with Particle Trails ([518a749](mob-sakai/ParticleEffectForUGUI@518a749)), closes [#61](mob-sakai/ParticleEffectForUGUI#61) * multiple UIParticleOverlayCamera in scene ([3f09395](mob-sakai/ParticleEffectForUGUI@3f09395)), closes [#73](mob-sakai/ParticleEffectForUGUI#73)
Describe what help do you need
Is there any limitation on using multiple ui particle on scene with overlay camera canvas ?
there are warning that pops out that gets me worried if i use stuff wrong.
Additional context
would love a help to either fix / ignore this warning according to the previous question answer.
thank you
The text was updated successfully, but these errors were encountered: