@r_gigante
I've never used it before, and I'm pretty disappointed with this information.
@janbiko
While searching, I found this:
https://medium.com/gdplabs/build-and-debug-c-on-visual-studio-code-for-mac-77e05537105e
it might be able to help you ;)
Hi Jambiko
There is always the solution to use Visual Studio for Mac.
I've never used it before, and I use very little xcode. I prefer the good old Makefile :)
Hi Andreas
It is an external application, and therefore does not require the ownership of Cinema4D. It's not a plugin. Which means, no connection to C4D.
This application also imports OBJ, FBX, 3DS...etc formats and it is not necessary to have the original applications of these formats!
The SDK therefore does not seem to allow a total independent import of .c4d scenes.
There will therefore be no Cinema4D import/export.
Unless I can get the description on the structure of a .c4d file. In this case, I would write my own import/export library ;)
Of course, the information received will remain confidential.
Sorry but I remain convinced that there is, somewhere in the scene file, an information that allows you to reconstruct a parametric sphere!
Without this information, how does Cinema4D rebuild the sphere? With a session of spiritualism?
A normal user will not always think to activate the options of the Mix SDK.
I think I'll drop the c4d scene import.
Hi Andreas
Okay, thank you for these explanations ;)
At the moment, the only solution is to limit the import to polygonal objects and exclude all parametrics objects.
I hope that Melange will evolve to allow a total import of a c4d scene. This caching principle is not really practical:(
But how does Cinema4D know the size of a parametric sphere when loading a scene?
There's got to be a way to find that information somewhere, no?
Otherwise, can I get from Maxon, the specifications of the .c4d file format?
Unfortunately, that's what I thought :(
So I'll have to write a MakeEditable function ;)
Thanks Ricardo
For a polygonal object, I have no problem calculating the BBox.
My question concerns PARAMETRIC objects, which do not have points.
The information must exist in the.c4d file. Otherwise, how would Cinema4D find the size of a sphere or other parametric object?
So, unless I get a description of the structure of a.c4d file, I must be able to find the size somewhere!
How to get the size of a parametric object? As with BaseObject::GetRad()
Hi
The documentation of Melange is not very clear, and there is only one example :(
Can we convert a parametric object into a polygonal object, as we do with "makeeditable" in a plugin?
ViewportSelect.PickObject(), this is what I use to select an object in the 3D View.
What I'm trying to do seems complex and unreliable.
I'll try to find another solution.
As I said, when the scene is complex, it is difficult to reach a particular object, especially if it is small.
It's from R19 only. It will remove OnFloor compatibility from R13 to R18 :(
Hi Andreas
It's an improvement I want to make to OnFloor.
Currently, the tool is activated and then click on each object in the 3D view to place it on the ground.
In the case of a complex scene, it can be difficult to find an object in the 3D view. So I would like to include the possibility of clicking on the object in the scene tree structure.
Final version 1.2.4RC1.
Hi all
In a tooldata, is it possible to detect when the user selects an object in the tree structure?
Hi all
Update 1.2.3b
Only one version for C4D R13 to R20 ;)
The above-ground level can be specified in a different unit of measurement from that configured in the C4D preferences.
Parametric, Polygonal, Nurbs, Generator (array, atomarray etc...) objects can be moved.
I'm debugging for Null and Spline;)
Yes, it will be to discuss plugins and their development. The subject of my discord is 3D, with several chat rooms dedicated to Cinema4D.
I would put the invitation on my profile, instead of the website;)
You can come and see if you want, here's an invitation:
https://discord.gg/4SFvDa
PS: If you come, let me know so that I can give you access to all the sections
Thank you for all these details Maxime ;)
I solved the problem with a small loop that checks if the object has been converted or not ;)
The test reports I got are all positive :)
My plugin will therefore remain compatible from R13 to R20:)