Do Cinema 4D and c4dpy use different lists of plugins?
-
Hello!
It seems like Cinema 4D uses more plugins then c4dpy.
I've written (copypasted) this code:import c4d def main(): importPlugins = c4d.plugins.FilterPluginList(c4d.PLUGINTYPE_SCENELOADER, True) for p in importPlugins: print('{} : {}'.format(p.GetName(), p.GetID())) if __name__=='__main__': main()
If it runs within Cinema 4D it returns this list:
3D Studio (*.3ds) : 1001037 Alembic (*.abc) : 1028081 BVH (*.bvh) : 1001048 CATIA (*.CATPart *.CATProduct *.cgr) : 1039778 Cinema 4D (*.c4d) : 1001025 COLLADA 1.4 (*.dae) : 1022315 COLLADA 1.5 (*.dae) : 1025754 DEM (*.dem) : 1001046 DWG (*.dwg) : 1021372 DXF (*.dxf) : 1001035 FBX (*.fbx) : 1026369 IGES (*.igs *.iges) : 1039779 Illustrator (*.ai) : 1001045 JT (*.jt) : 1039780 Lightwave (*.lws) : 1001043 Lightwave Object (*.lwo) : 1001044 MeshObject JSON Asset : 1040819 SKP (*.skp) : 1033845 Solidworks (*.SLDPrt *.SLDAsm *.SLDDrw) : 1039781 STEP (*.stp *.step *.p21) : 1039777 STL (*.stl) : 1001020 Updater loader : 450000233 Volume (*.vdb) : 1039864 VRML 2 (*.wrl) : 1001033 Wavefront OBJ (*.obj) : 1030177
However when it runs via console
c4dpy *pathToScript*
it logged this one
3D Studio (*.3ds) : 1001037 Alembic (*.abc) : 1028081 BVH (*.bvh) : 1001048 CATIA (*.CATPart *.CATProduct *.cgr) : 1039778 Cinema 4D (*.c4d) : 1001025 DEM (*.dem) : 1001046 DXF (*.dxf) : 1001035 IGES (*.igs *.iges) : 1039779 Illustrator (*.ai) : 1001045 JT (*.jt) : 1039780 Lightwave (*.lws) : 1001043 Lightwave Object (*.lwo) : 1001044 MeshObject JSON Asset : 1040819 SKP (*.skp) : 1033845 Solidworks (*.SLDPrt *.SLDAsm *.SLDDrw) : 1039781 STEP (*.stp *.step *.p21) : 1039777 STL (*.stl) : 1001020 Updater loader : 450000233 Volume (*.vdb) : 1039864 VRML 2 (*.wrl) : 1001033 Wavefront OBJ (*.obj) : 1030177
It's a little bit shorter. And there is no FBX
Is it bug? May be I do something wrong?I use Cinema 4D R20.030 on Windows.
P.S. I'm sorry for any grammar mistakes.
P.P.S. C4D developers! You're awesome! C4D is just amazing! I really love it! -
Hi @kisaf, thanks a lot for reporting this.
I've reported it to the development team.Sadly there is nothing to do on your side.
The only way would be to use the Cinema 4D command line instead of c4dpy.Cheers,
Maxime. -
Hi @m_adam, thank you for your answer! I'll try command line.
Cheers -
This issue is now fixed in R21.
Cheers,
Maxime.