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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
This works as expected. The camera node could have a transform