Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b1
Issue ID
1081098
Regression
No
[Timestep] Some discrepancies exist with particle systems running with a higher timestep
There are some potential discrepancies when the timestep is increased.
Possibly by design, but logging for the sake of completion
Repro steps:
- Open the [Particles] FTP project from Collab.
- In Settings/Time, set the Fixed Timestep to 0.066
- Play the SceneController scene, and navigate to the following:
- (09) Collision / (10) 2D Collisions: - the radius scale (yellow spheres) effect jumps on top
- (11) Collision Improvements - the forces act erratic, and the impacts (especially on the bottom row tests) is quite much stronger
- (17) Trails Module - the external forces test starts scrambled, and eventually fixes itself
Note:
- not regressions, just possible improvement points.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment