Importing issues - Istances
-
Hi everyone, has anyone noticed an issue when importing STEP files into Cinema 4D?
Specifically, when I import an instanced element with child objects, instead of creating a null object with the instances underneath it, it creates an instance with the child instances that make up the parent.
This results in duplicate geometry, which is problematic for rendering.This issue was not present before version 2024.
I am currently using version 2024.3.2.The image will certainly help illustrate this:
WRONG import:
CORRECT import:
Thanks in advance
-
Hi LAB-CH,
It is not fun, and I am sorry you have to endure this, but I can't see a fix since 2024.3.2
https://support.maxon.net/hc/en-us/articles/8658038724124-Cinema-4D-2024-4-1-May-28-2024I'm not a big fan of guessing, but I'd rather have the file here. Let us try these three things.
What happens when you make the Parent editable? (C- key)
To work around this, you could create a Null and use the replace function
https://help.maxon.net/c4d/en-us/?_gl=11323nba_gcl_au*NjgyMjc2OTg1LjE3MTc1NTc3NjY.#html/68788.htmlWhat object is in theParent linked to, and what happens when this is deleted?
Anyway, this is a case for tech support:
https://www.maxon.net/en/support-centerIf you have a small file (Please use Dropbox, Google, Apple, Adobe, or Wetransfer; anything else is ignored for security reasons, sorry)
If I can reproduce it, I can file the report.All the best
-
Hello Mr. Sassi,
thanks for your kind reply.Unfortunately, I cannot share with you the file because it contains a lot of sensitive data of the client.
In any case, I will create a file that makes the same issues during the import as soon as I can.
The file is made in Solidworks and exported in step (350Mb)The replace with option is the best, it simply removes the instance and replaces it with a null with the same naming, bringing the situation as per a correct import.
If I press "C" I get a new null with underneath the instances, also here double geometries
The parent Instance is linked to a null with underneath a null containing geometries or other instances
As you can see here:
I'll be back to you with the file that replicates this error.
-
Thank you very much for your efforts and patience, LAB-CH.
With a file that allows me to replicate the problem, I can work in the best way to file a report.
Will the following work with the C treatment:
Object Manger> Object> Delete without ChildrenCheers
Dr. Sassi -
Here are the files, there are also the source files from Solidworks.
https://we.tl/t-ZnXSqmC8Kl -
Thank you very much, LAB-CH.
Here is my result importing the LEVEL_00.step
This is done with 2024.4 on a Mac M1
Since there was no mentioning of a fix, I'm not sure hwere the problem starts. In other words, if it makes sense to use 2024.4
If you have a chance to check this out, if your setup allows this (Production based freeze for updates, etc.), that might work.All the best
-
Currently, I cannot update the software, but I can work around this issue by replacing what causes problems in rendering.
Anyway, it would be great if Maxon could investigate this issue.
Is it something you can report to them, or do I need to contact the support team?
It would be great to have this issue fixed in the next release. -
Thanks for the extra time, LAB-CH.
It seems you are in the middle of a project; I will take the file and images and create a report. But I guess the reply will be, how about the current version.
Anyway, perhaps it helps to prevent future problems.
All the best
-
Hello Dr. Sassi,
unfortunately also in version 2025 the issues during the import of a model is still present, did you get any feedback from your report??Thank You!
-
Hi LAB-CH,
I'm sorry about this.
If there is no change, I suggest checking with tech support.
https://www.maxon.net/en/support-center
Or did you check with them when I suggested the above? What was the reply, if so?
Sorry if my input has not shown any progress so far.
Have a great start to your week.
-
Honestly, I didn’t realize I was supposed to open a ticket with the support team; I thought you were going to handle it. Anyway, I’ll take care of it in the next few days!
-
Thanks for clearing that, LAB-CH.
The tech support case should be always direct. Otherwise, I would act as a middle person, and anything becomes delayed, so I suggested it.
Without your file, my report would have little value in solving your problem.
I can write reports, but that is a different place, not a tech support database.Sorry for the confusion. Thanks for your patience.
Cheers