Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0b10
2018.1
Issue ID
976091
Regression
Yes
[Renderer] Mesh Particle Pivot offset adjustment based on particle size has changed from 2017.3 to 2018.1
Looks like we were using size*size before, and now it is just size.
(i.e. to make the particles appear in the same position, a size of 0.5 in 2017.3 has to be 0.25 in 2018.1, a size of 2 in 2017.3 has to be 4 in 2018.1, etc.)
Repro steps:
1. Open Scene1 from the attached project in 2017.3 (I tried in b10)
2. Observe position of particles
3. Open Scene1 from the attached project in latest trunk (I tried 2018.1.0a5)
4. Observe the different position of the particles.
Notes:
- Seems to be Mesh mode specific; 2018.1 has both modes behave identical, while 2017.3 meshes were receiving a different offset from billboards. So this might be a fix and expected behavior.
- Regression, introduced in 2018.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment