Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
1
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a25
Issue ID
UUM-22313
Regression
No
[macOS] Animated objects are displayed with a transformation from a few frames ago when “Graphics Jobs” setting is enabled
How to reproduce:
1. Build And Run the user’s attached “GraphicsJobsMixedUpFrames.zip” project
2. Observe the movement of a characters
Expected result: Characters movement is smooth
Actual result: Characters constantly jump back when moving
Reproducible with: 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
Could not test with: 2020.3.44f1 (Errors after project downgrade)
Reproduced on: macOS 12.4 (Intel)
Notes:
Not reproducible in the Editor and Windows (user’s info)
Not reproducible if Graphics Jobs is not enabled
Project displays a large number of units because otherwise, the problem does not occur often enough.
Issue is reproducible if there are animated objects (skinned or rigid). When modifying transforms from code and not using animators issue is not reproducible.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.1.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.