Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
3.0.0
Issue ID
1191338
Regression
No
[ProBuilder] 'Merge Objects' does not result in a consistent pivot location and orientation
1. Create a new unity project.
2. Install the ProBuilder package. (Window -> Package Manager)
3. Open ProBuilder toolbar. (Tools -> ProBuilder -> ProBuilder Window)
4. Create a new ProBuilder shape. (i.e. CTRL+K or 'New Shape' in ProBuilder toolbar)
5. Duplicate this shape twice, so there are three shapes in total.
6. Enable 'Pivot' and 'Local' in the Unity Toolbar, to the left of the Play button.
7. Select a duplicate shape, and randomly change it's rotation.
8. Select all ProBuilder shapes in Scene view, selecting the one you edited the rotation of last. The handle should match this object's orientation and position.
9. In the ProBuilder toolbar, click 'Merge Objects'.
10. Undo Step 9 and repeat it a few times.
Expected Outcome: Merged objects should have pivot location and orientation matching the last selected object.
Actual Outcome: Merged objects have varying pivot location with each merge attempt. Orientation does not match the last selected object.
GIF attached to demonstrate the varying handle positions after merge in version 3.0.0
Note that sometimes Step 10 needs to be done a few times to see a different handle location.
Reproducible in package versions: 4.1.0, 4.0.5, 3.0.0
3.0.0 is the earliest version I can find.
You may have to use earlier versions of unity to test earlier packages.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment