Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.0
Issue ID
1104606
Regression
No
[Alembic] Camera Objects are still created as sub-asset even if we don't import the camera
Alembic importer creates "empty" camera objects when "Import Cameras" imported settings is unchecked
1. Make sure Alembic Importer package is install in the project
2. Import the attached "Particles_w_mesh.abc" file
3. In its import settings inspector, uncheck the "Import Cameras" setting
4. Click Apply
5. After the re-import, instantiate the model in the scene
6. Browse the object and select the "Main Camera" game object
Result : The import process simply didn't create a "Camera" component on the object when the object itself shouldn't have been created at all. We just end up with an empty game object with a name that suggest that we have a camera in the scene which is very confusing.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This works as expected. The camera node could have a transform