Search Issue Tracker
Fixed in 3.0.6
Votes
2
Found in [Package]
2.2.0 - 3.0.4
Issue ID
1181183
Regression
No
Visual glitches appear in play-mode when 2D Animation Package is used
How to reproduce:
1. Open Unity project, attached to a google drive
2. From the main menu select Nementic/Windows/Level Start
3. In the level start window press "Open World..." and select "World_01". Wait until the four World_01 scenes have loaded
4. Select Start Level Index 4 (CutsceneController_1.3)
5. Enter Playmode
6. Cut the rope/belt by holding the left mouse button and dragging over it
7. Drag the belt handle with the mouse to connect the motor wheel with the rightmost wheel and press the play symbol on the motor wheel
8. Observe the cutscene in which the glitch is most likely to appear
Reproduced with: 2019.2.5f1 (2D Animation preview.4 - 2.2.0), 2019.3.0b3 (2D Animation 3.0.4) ,2020.1.0a4 (2D Animation 3.0.4)
How to reproduce on a player:
1. Open development build, attached to user's last email.
2. Select Villaggio -> Windmill (Cutscene)
3. Do 6-8 reproduction steps.
Notes:
Not reproducible on an empty project.
There are video and image with reproduction attached in the last user's last email.
Can't test this issue on 2017.4 version of Unity because of a crash on opening project.
Can't test this issue on 2018.4 version of Unity because of errors.
Glitches not always appear in the same place.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- DisplayDialogComplex crashes with a long content string containg Cyrillic chars
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
Add comment