Exporters: Add support for Cinema4D (.gltf / .babylonjs)
deltakosh
All 16 comments
+1
ThibaultJanBeyer
on 15 Apr 2018
crazy?! would this be a C4D plugin or ?
MacroMachines
on 5 May 2018
Probably :)
deltakosh
on 5 May 2018
+3
DonutKilla
on 24 Jul 2018
+1
flopanzer
on 13 Aug 2018
+1
jameslashmar
on 23 Oct 2018
+4D
couch4
on 30 Nov 2018
+1
readyforchaos
on 17 Jan 2019
Maxon just released a glTF exporter for Cinema4D to Maxon Labs: https://labs.maxon.net/?p=3360
donmccurdy
on 1 Mar 2019
Woot!
Closing the issue then :D
deltakosh
on 1 Mar 2019
I don't mean to re-open this. But since I am a C4D developer who is currently using Babylon I was wondering if it would still be useful to have a babylonjs exporter natively in C4D as a plugin. Is this something the community would want?
I may also write my own glTF exporter as well and integrate the new Basis texture compression into the pipeline, as well as sample textures and simplify the texture export process (maybe include baking) and a better PBR workflow, LOD support and anything else that makes sense.
Also thinking of adding in custom tags, objects, UI workflows and custom dialogs for C4D to essentially setup a full interactive scene ready for export and immediate play with no additional steps.
If this is something that interested people then let me know.
kentbarber
on 24 May 2019
Yes, I would use a c4d Babylon exporter with compression and rounding vertices. I use glTF but a Babylon.js exporter I would use more often.
DonutKilla
on 24 May 2019
Also thinking of adding in custom tags, objects, UI workflows and custom dialogs for C4D to essentially setup a full interactive scene ready for export and immediate play with no additional steps.
If this is something that interested people then let me know.
Yes, please! Let me know if you need help with testing!
flopanzer
on 24 May 2019
Yes, Do it!
DonutKilla
on 24 May 2019
Have you guys seen this?
https://labs.maxon.net/?p=3360
On Fri, May 24, 2019, 7:25 AM DonutKilla notifications@github.com wrote:
Yes, Do it!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BabylonJS/Exporters/issues/56?email_source=notifications&email_token=AGDHXKXNDZ6KXXCYJ2ETLHTPW6C4PA5CNFSM4EKUHEXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWEIZIQ#issuecomment-495488162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGDHXKUMSTRXXQYZSKNT7SLPW6C4PANCNFSM4EKUHEXA
.
jameslashmar
on 24 May 2019
Yeah this is great!!
deltakosh
on 24 May 2019
Related issues
echadwick-wayfair
·
5Comments
jcartie
·
8Comments
cptSwing
·
6Comments
Prospector-au
·
6Comments
jsellam
·
7Comments
Most helpful comment
I don't mean to re-open this. But since I am a C4D developer who is currently using Babylon I was wondering if it would still be useful to have a babylonjs exporter natively in C4D as a plugin. Is this something the community would want?
I may also write my own glTF exporter as well and integrate the new Basis texture compression into the pipeline, as well as sample textures and simplify the texture export process (maybe include baking) and a better PBR workflow, LOD support and anything else that makes sense.
Also thinking of adding in custom tags, objects, UI workflows and custom dialogs for C4D to essentially setup a full interactive scene ready for export and immediate play with no additional steps.
If this is something that interested people then let me know.