This was modified and is by design as many users were not expecting the old behavior. To do this you should hold alt and rotate.
Rotating a constraint does not update its range of motion based off of angular limits. The user who reported this also mentioned that migrated constraints do not see this issue (eg: migrating a physics asset with constraints made in 4.20 to 4.21 works without an issue) but rotating them after migration to a version where this issue is present makes it occur.
Regression?: No
This occurs in 4.21.
This is however a regression from 4.20 where it did not occur.
How does TextureRenderTarget2D get TArray<uint8> type data?
Why does the REMOVE method of map container remove elements have memory leaks?
UMG RichText not appear image when packaged
How do I set a material as a post-processing material?
How to delete some elements correctly when deleting an array loop?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
What is the difference between Camera and CineCamera?
How does TArray loop correctly remove elements in blueprints?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-72542 in the post.
8 |
Component | UE - Simulation - Physics |
---|---|
Affects Versions | 4.21, 4.22, 4.23 |
Created | Apr 9, 2019 |
---|---|
Resolved | Apr 19, 2019 |
Updated | Nov 4, 2020 |