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
- Crash on ConvertBufferToEXRBuffer when Lighting Generation is cancelled
- [URP] TrailEffect in URP package samples does not draw Trail Effect
- "NullReferenceException" error is thrown when calling UIDocument.runtimePanel in OnEnable with ExecuteInEditMode
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
Resolution Note:
This works as expected. The camera node could have a transform