Search Issue Tracker
Fixed in 4.4.1
Votes
0
Found in [Package]
4.3.1
Issue ID
1256154
Regression
No
[ProBuilder] causes a StackOverflow when using ProBuilderize on a specific 3D model
How to reproduce:
1. Create and open a new project
2. Install the ProBuilder Package
3. Import the attached "ProblematicModel.fbx"
4. Drag it into the "SampleScene" and select it
5. Open the BroBuilder window from Tools > ProBuilder > ProBuilder Window
6. Click ProBuilderize in the BroBuilder window
Expected result: the model is successfully prepared for work with ProBuilder
Actual result: a StackOverflowException occurs and the model gets corrupted
Reproducible with: 3.0.0 (2018.4.23f1), 4.2.1 (2020.2.0a15), 4.2.3 (2020.1.0b13), 4.3.0-preview.4 (2020.2.0a15), 4.3.1 (2018.4.23f1, 2019.4.1f1, 2020.2.0a15)
Notes:
-Very rarely the Editor crashes without leaving a stack trace
-The issue also reproduces with .dae and .obj file formats
-The issue doesn't seem to be related to the size of the model as a smaller version of the provided model still reproduces the issue
-There are no errors when importing the model to warn about the incompatibility of it
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Add comment