-
-
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
Support 3D scaling #105
Labels
Comments
@gabry90 |
mob-sakai
added a commit
that referenced
this issue
Oct 4, 2020
github-actions bot
pushed a commit
that referenced
this issue
Oct 4, 2020
# [3.0.0-preview.38](v3.0.0-preview.37...v3.0.0-preview.38) (2020-10-04) ### Bug Fixes * delete unused file in package ([2e69974](2e69974)) * material dirty on validate (on editor) ([fa34301](fa34301)) ### Features * display material properties in inspector ([313c1fc](313c1fc)), closes [#104](#104) * support 3D scaling ([a508c3b](a508c3b)), closes [#105](#105)
🎉 This issue has been resolved in version 3.0.0-preview.38 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
LionelPerrault
added a commit
to LionelPerrault/Unity-Particle
that referenced
this issue
Jul 25, 2023
# [3.0.0-preview.38](mob-sakai/ParticleEffectForUGUI@v3.0.0-preview.37...v3.0.0-preview.38) (2020-10-04) ### Bug Fixes * delete unused file in package ([2e69974](mob-sakai/ParticleEffectForUGUI@2e69974)) * material dirty on validate (on editor) ([fa34301](mob-sakai/ParticleEffectForUGUI@fa34301)) ### Features * display material properties in inspector ([313c1fc](mob-sakai/ParticleEffectForUGUI@313c1fc)), closes [#104](mob-sakai/ParticleEffectForUGUI#104) * support 3D scaling ([a508c3b](mob-sakai/ParticleEffectForUGUI@a508c3b)), closes [#105](mob-sakai/ParticleEffectForUGUI#105)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can you restore previous scaling mode with X,Y,Z input instead a single value? I've tried this in previous version and is better have more scaling options then one
The text was updated successfully, but these errors were encountered: