Search Issue Tracker
By Design
Votes
0
Found in [Package]
4.1.0
Issue ID
1190821
Regression
Yes
[ProBuilder] Exporting a ProBuilder object as an asset does not generate a prefab file
When exporting as an Asset in ProBuilder, it should generate a .prefab and .asset file.
Only generates an .asset file.
1. Create a new project.
2. Install ProBuilder package. (Window -> Package Manager)
3. Open ProBuilder window. (Tools -> ProBuilder -> ProBuilder Window)
4. Create a new ProBuilder shape. (i.e. CTRL+K for a cube, or click 'New Shape')
5. In the ProBuilder window, click the '+' next to 'Export'.
6. Set Export Format to 'Asset'.
7. Click 'Export'.
Expected Outcome: Creates two files in chosen folder - .prefab and .asset file.
Actual Outcome: Only creates the .asset file.
Working in 2019.3.0a9 with package version 4.0.5 - errors when downgrading to 4.0.5 in newer unity versions.
Reproducible in package version 4.1.0
Working in package version 4.0.5
License type: Pro
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note:
This is by design - TestRail case was out of date.