Cineversity

Good day,

During a few larger Solidwork assy imports, some parts are not imported and I can’t figure out why. I have a zip file with the assy (ROF PRO 100 405 ) and its parts, linked below. I also have 2 images showing what parts were not imported. Can someone please check what I’m missing?

It’s mainly the handrails and pipes that have issues (STD MAT RDT 041_.SLDPRT, STD 311 151 010.SLDPRT, STD 413 151 359..SLDPRT) and it’s happening on all the projects that have these items, as well as some others.

Is there a log file generated during the import, so that we can look for errors, as none are shown during the import process?

We have used pack and go, making sure all parts are resolved as well as copy tree to make sure all the files referred to in the assy is copied to the folder. It did not make a difference regarding the missing pipe/tube issue.

Tested with S24 and R25

Hi jjordaan,

Please check your Private Messages here on Cineversity.

All the best

Hi jjordaan,

Thanks for the dropbox upload (sorry about that, but security first)

I have loaded all files but one: AUG FST 001 018.SLDASM

There are 39 SLDASM files, and only 38 showed up in the Object manager.

What of the 179 sldprt (parts) files are in each and every sldasm (assembly) file is not clear to me. Since the position of those parts is defined here in the sldasm files, loading all sldprt helps only to see that from 179, only 178 show up. I manually compared all sldasm files, but I’m gladly leaving to figure out what part is missing from the 179 to you; I think that is fair.

Perhaps the one who had to send you the file could wrap it all in one sldasm file to make things simpler? (I’m not a Solidworks user, so that is just an idea)

Have a great weekend

Hi Dr. Sassi,

Thanks for having a look. I normally import only the main SLDASM file and not all of them, as that contains all the info and references of the sub-assemblies and parts.

As long as the sub-assemblies and parts are in the same folder as the main assy, it normally works fine.

If there is another way to import, then please let me know.

Have a great weekend as well

You’re very welcome, jjordaan. Thank you.

One question: how would I have found the main SLDASM?

I tried to import the single missing one, but no result.

All the best

I should have been clearer in my initial post, but the main assembly is ROF PRO 100 405, sorry about that. I with click open project or merge projects and then only select that file. In the past on smaller assemblies, it has worked perfectly, so I can’t figure out why some of the parts on this one is not importing.

Thanks for the extra information, jjordaan!

Yes, I missed a single main file, so I exported all with a Shift click+ drag to the scene editor and clicked 38 times OK. I will keep in mind to search for files with the folder name. It makes sense to do so after you mentioned it.

However, even I get it loaded with one click now, instead of all, again, this one is missing: The file AUG FST 001 018.SLDASM. It has data, so something has worked, but the file is not human readable, even if it opens in a text app just fine. I do not assume that it is corrupted, but somehow something is missing.

I have no indication that the tech support could say more. My suggestion would be to request that file and its parts again.

Sorry to only confirm what you already know.

I hope you have a lovely weekend despite this problem.

Cheers

P.S.: Did you notice that the missing parts have all a (double) .. instead of one . ?

I changed that to one period, but no luck. But isn’t it interesting that all the parts that have that are missing? While all the over 200 files work?

Fingers crossed that leads to something!

Yes, I did see that the file structures of those are different, and perhaps that is what is causing it to break the reference. There is also an extra “_” in some of the files, but on another project the structure was normal, so that stumped me a bit.

Regarding the missing file, I asked the designer to remove any sensitive data that might have caused this, but the handrails and pipes are an issue on all projects that I import.

Solidworks is very forgiving if you stay in the ecosystem, but issues like this pop out as soon as you try to export it to other vendor systems.

As an example, I am able to rebuild the complete project using only the main assembly file in Solidworks Visualize. It takes forever and the software is very basic, but it’s crazy how it could use virtual sub-assemblies and parts to rebuild it. I don’t have access to it anymore, so now I try this method. If it works I have much better quality models and control over the process, and it’s much faster.

Do you suggest I send this same file to support?

Thanks for your help so far.

Hi jjordaan,

You’re very welcome.
I’m not sure which support you have in mind: SolidWorks or Maxon?

If you contact Maxon support, please point out that the “extra point files” are the only one that causes trouble.
https://www.maxon.net/en/support-center

Perhaps that leads to something, but my idea is to fix the file and check first. Anyway, you do what feels right to you.

My best wishes and fingers crossed that this will be solved soon.
(I close shop now, it is Sunday 11:00 p.m. here.)

Thanks, I will look at the file first and then talk to Maxon. Do you know if there is a log file that’s created so that I can do some debugging myself? I have looked but it’s not in an obvious location, or is there a debug mode in C4d?

Hi jjordaan,

There are two places where information about processes are provided

Process specific: Main Menu> Extension> Console
https://help.maxon.net/c4d/r25/en-us/Default.htm#html/44913.html?TocPath=Extensions menu|Script|_____1

If there was a crash, then there is a crash report, I don’t see that here, and the support would guide you to the place where it is.
https://help.maxon.net/c4d/r25/en-us/Default.htm#html/PREFSCOMMUNICATION-PREF_COMMUNICATION_MAINGROUP.html#PREF_COMMUNICATION_BUGREPORTS

All the best

Thank you Dr. Sassi

I received feedback from Maxon support, it’s a known bug, so I will try something else for now:

Unfortunately this is an already known bug, connected to objects from solidworks, which includes multiple assemblies.
These objects cannot be updated inside Cinema 4D and aren’t loaded correctly.
I hope the combination of our developer and the solidworks developer can solve this issue soon.

Thanks a lot for the feedback, jjordaan.

So, at least we know what causes it. I assumed that this was related to the overall project file.
However, since I imported AUG FST 001 018.SLDASM and that should have worked. OK.

Fingers crossed that it will be fixed soon.

All the best