Cinema4D direct export error

[Valery]

Hi everyone!
Trying an export vectorworks model directly into cinema4d (command "send to cinema4d") i've faced a problem.

So i click on button "send to cinema4d", then i see menu with export options, 
click on "Export" button,

vectorworks starts to calculate geometry,
then calcuclation reaches 100%, and then... just nothing, no further actions neither from vectorworks nor from cinema4d.

any thoughts? 

thanks in advance

 

[zoomer]

Usually I do a standard export to C4D from VW.

 

So that I can save it to a proper location instead of having it in any arbitrary temp folder

and AFAIR i was able to set C4D to its default "cm" units, which won't get lost after

further exchanges.

And usually I start cleaning/setting up at that point, like sorting my VW Classes in C4D's

Layer list, assigning Materials to C4D Layers and such stuff.

 

After the next changes in VW I start to use Exchange by "Sent to C4D".

And I will have C4D already open and my initial C4D file loaded before I "Sent to C4D".

 

What should happen is that, after VW sends,

(C4D starts if not already open)

in C4D a popup window opens with the usual options and it will refresh/load in

new or changed geometries and new materials.

 

That was how it always worked.

And with my last attempt a few years ago it did work that way - on Mac.

But C4D Exchange did no more work on Windows for me.

What ever I tried, C4D did not react after I "Sent to C4D" from VW.

So basically what you experience.

 

But I asked on both DE and US VW Forums and it seemed that nobody else

was experiencing that problem.

 

 

My last C4D Version is R21 and I think it was with VW 2021 or VW 2022.

 

Initially I thought my C4D version may be too old, in a way that VW's Cineengine

sends a C4D file format that is too new and no more compatible with my old C4D.

But Exchange still worked flawlessly and lossless on Mac though.

 

 

I wanted to do my C4D Renderings on the faster PC at that time but the job got

a nightmare because for each Exchange I had to take over the VW and C4D Model

to Mac, do the Exchange, care about some path problems between Windows and Mac

before I could go on working and rendering on my PC. 

 

 

So can you please give some more information about your hardware, operation System

and VW and C4D versions ?

Edited March 29 by zoomer

[zoomer]

BTW,

 

here was my initial thread about this issue :

 

 

 

[VIRTUALENVIRONS]

1 hour ago, Valery said:

rying an export vectorworks model directly into cinema4d (command "send to cinema4d") i've faced a problem.

What versions of VW's and what version on C4D?  Newer Versions of VW's won't export to past C4D R-21.

 

This is a work around that should work.

1-Make a copy of your work.

2-Go to Modify>Convert to 3D polygons

3-Export DXF and choose DXF text from the drop down menu.  Not Binary.

4-Import into C4D.  

NOTE: Objects that need to be separated need a separate "pen colour"

[Valery]

@zoomer @VIRTUALENVIRONS 
Guys, thanks for the asnwers.

Currently i use
Vectorworks 2024 SP4
Windows 10 x64
Cinema4D R21, R23

@VIRTUALENVIRONS instead of this attempt i usually use fbx export to import it into c4d.

[VIRTUALENVIRONS]

4 minutes ago, Valery said:

instead of this attempt i usually use fbx export to import it into c4d.

If it works then good stuff.  

 

FYI, the "Send to C4D only" command was based on the steps that I posted.

[zoomer]

8 minutes ago, VIRTUALENVIRONS said:

 Newer Versions of VW's won't export to past C4D R-21.

 

Does this on the other side mean that R21 can still read/exchange with VW 2024's C4D exports ?

 

 

5 minutes ago, Valery said:

Currently i use
Vectorworks 2024 SP4
Windows 10 x64
Cinema4D R21, R23

 

And on another thread I can see you are using Windows, not Mac.

 

As said, VW 2022 and C4D R21 worked, at least on Mac.

If C4D too outdated for VW'S exports ... and that manifests on Windows a year earlier than on Mac !?

 

If C4D R21 does no more work with VW 2022 for me,

maybe it makes "sense" that R23 does also no more work with VW 2024 for you ?

[Valery]

@VIRTUALENVIRONSapologies, did not get it 🙂 . Okay, so will try it now manually. thank you!

[zoomer]

I am not sure, but it is likely that I tested my VW file in an earlier VW than 2022 at that time.

And can't remember that I had ever managed to run Exchange on Windows again.

[Valery]

@zoomer Still no effect, when i've recently opened VWX2022 with C4D R21 and tried again...
Let me check thread you've sent before

[zoomer]

Just now, Valery said:

Okay, so will try it now manually. thank you!

 

But please also try to export as C4D.

 

I am pretty sure that should work.

But it would be interesting to know if not.

 

(Beside, VW's FBX is pretty good and works great for imports in a lot of 3D Apps.

Also I never noticed much if any quality difference between c4d or fbx exports

to C4D)

[zoomer]

1 minute ago, Valery said:

@zoomer Still no effect, when i've recently opened VWX2022 with C4D R21 and tried again...
Let me check thread you've sent before

 

 

Thank you very much for testing.

 

But would VW 2022 work with R23 ?

(In case R21 was too old for me)

[Valery]

@zoomer amazing
c4d export from vwx24 works fine in c4d r21 🙂

[zoomer]

Great !

And good to know.

 

But when you do some VW changes and try an Exchange by send to C4D,

I assume C4D won't react again.

 

So at least, by your last experiment, it looks like the C4D File version that VW up to 2024

exports, is still compatible with my old C4D R21.

Which is great.

 

But why at all doesn't VW/C4D Exchange work anymore.

 

And why do we both seem to be the only persons on earth experiencing this problem ?

[EAlexander]

I always use export to c4d (3d only) and then I merge that file into a new blank scene. I've had scale issues or camera issues (clipping) when I just open the c4d file that VW writes. Merging solves this. 

 

Send to c4d has always been squirrelly for us. 

[zoomer]

C4Ds beloved standard unit is centimeters.

In VW I usually work in meters.

But AFAIK a VW send or export will result in a millimeter C4D.

 

Maybe that can cause such camera clipping issues.

In the past, not sure if before VW or before VW Exchange, I was used

to always have camera clipping issues with imported geometry in C4D.

 

Could be that I had the whole geometry off scale sometimes but more likely

(like in Modo) only parts like camera sub settings or texture sizes seem

to miss the scaling.

 

I also export the first C4D.

But through the last years I was very happy to have a reliable and lossless

Exchange for design changes in VW.

So I could not live without "Send to C4D"

[VIRTUALENVIRONS]

You can correct the initial cameral clipping under the Project Menu, but I also copy to a new file as it corrects automatically.  But, there have been times when I correct in the original file.

 

The camera clipping has always been unclear though.

 

I do not use C4D as another program.  I use both VW's and C4D as a single application.  Granted I begin in VW"s and end in C4D, but I plan in VW's so things in C4D will behave correctly.  I tend to transfer partial sections of a project using pen fore colour in VW's for a finer level of granularity when using "Combine Project" in C4D.

 

Thee are many functions in C4D like polygon reduction that are extremely useful.

 

 

[zoomer]

11 minutes ago, VIRTUALENVIRONS said:

You can correct the initial cameral clipping under the Project Menu,

 

Yes.

And in the past I had to do that each time after an import.

Either my camera viewport was clipped or even showed nothing

(when the model was also slightly off from origin) and I thought

the import failed 🙂

 

But I think that got much better since FBX scaling options and such.

[VIRTUALENVIRONS]

23 hours ago, zoomer said:

model was also slightly off from origin)

One of the things that screws with the origin are symbols.  Although you can send to C4D as a symbol, most times I send them as geometry.

 

Although recently I did send over 20,000 plus object as symbols, but I planned for the re-centre in C4D.