Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.8f1, 2023.1.9f1, 2023.2.0b4, 2023.3.0a1
Votes
32
Found in
2021.3.24f1
2022.2.19f1
2023.1.0b16
2023.2.0a15
2023.3.0a1
Issue ID
UUM-36242
Regression
No
Console displays warning about importing c4d files when a Scripted Importer for c4d files is implemented
Reproduction steps:
1. Open the attached project “Cinema4DImporter“
2. Observe Console
Expected result: Unity shouldn't log a warning about unsupported files because the project contains a Scripted Importer for c4d files
Actual result: There is a warning in Console: Assets/aa.c4d: Unity no longer supports importing Cinema 4D files directly, but we're working with Maxon to make the experience better. To import Cinema 4D files, install Maxon's external importer
Reproduced with: 2020.3.47f1, 2021.3.24f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a15
Reproduced on: macOS 13.0.2 (Intel), Windows 11 (user reported)
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
- The camera's Gizmos frustum does not display correctly when there is a script containing the OnGUI method
- "InvalidOperationException" and additional errors throw in the Console window when using a custom Composite
- The Visual Effect Graphs Custom HLSL node does not generate errors when the HLSL code used is incorrect
- The Capacity field in the “Particle System Info“ is not updated when changing the Visual Effects Graph is not saved
- [VFXG] Setting an exposed texture to none assigns a random texture
Immu
Jul 30, 2023 11:37
Quite annoying issue for heavy C4D users. Thanks for fixing.
Ammar_Negm
Jul 18, 2023 11:05
pls fix