Version 2.14.0 - TEST

Maxon Cinema 4D (Export script developed by abstrax, Integrated Plugin developed by aoktar)

Moderators: ChrisHekman, aoktar

User avatar
sadece
Licensed Customer
Posts: 216
Joined: Sun Apr 06, 2014 11:25 am
Location: Bursa, Turkey
Contact:

I've just noticed something weird. i a have an object which has emmison polygones. i used mograph to duplicate. see what happens with/without checking "render instances"
Attachments
render.jpg
http://www.sadece.com.tr
--------------------------------------------------------------------------
i7 990x // 12GB Ram // 2x Titan X + Titan + 780 // Octane for C4D // Win7 x64
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

sadece wrote:I've just noticed something weird. i a have an object which has emmison polygones. i used mograph to duplicate. see what happens with/without checking "render instances"
when you don`t use object tag, all objects will be collected a single mesh. but object tag exports all as individual meshes. but situation is different o render instances. they are always exported as individual meshes.
so what's the relationship for your problem?
emissions seems different due polygon area. on your first images, 3 objects are a part of big single mesh. check octane node graph to see what happens actually
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
sadece
Licensed Customer
Posts: 216
Joined: Sun Apr 06, 2014 11:25 am
Location: Bursa, Turkey
Contact:

aoktar wrote:
sadece wrote:I've just noticed something weird. i a have an object which has emmison polygones. i used mograph to duplicate. see what happens with/without checking "render instances"
when you don`t use object tag, all objects will be collected a single mesh. but object tag exports all as individual meshes. but situation is different o render instances. they are always exported as individual meshes.
so what's the relationship for your problem?
emissions seems different due polygon area. on your first images, 3 objects are a part of big single mesh. check octane node graph to see what happens actually
Thanks for the info.
Btw is it right behavior for the emmision materials are related to size of objects? Same emission material on a huge sphere and a tiny one, should the brightness be same ?
http://www.sadece.com.tr
--------------------------------------------------------------------------
i7 990x // 12GB Ram // 2x Titan X + Titan + 780 // Octane for C4D // Win7 x64
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

sadece wrote: Thanks for the info.
Btw is it right behavior for the emmision materials are related to size of objects? Same emission material on a huge sphere and a tiny one, should the brightness be same ?
i think so. Seems like that reflects same amount of illumination without accounting size. this explains why collected meshes don't casts the illumination for each boxes as a indivual mesh.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Dean
Licensed Customer
Posts: 21
Joined: Sun Oct 05, 2014 3:42 pm

Hello,
I have a problem with the rendering of animated textures.
The same setting final render is different from that which shows the preview window.
Illumination is also different.

Preview from Octane window

Image

Final render

Image
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
atome451
Licensed Customer
Posts: 285
Joined: Mon Feb 22, 2010 8:04 pm
Location: Brussels - Belgium
Contact:

About importing .ORBX materials from standalone (in LocalDB or not) or savings in the OctaneLive DB storage from C4D.

When you import complex nodes structure with cascading mix materials in .ORBX file format from the standalone or from materials made in C4D and saved in the OctaneLive DB storage, even if you rename the mix materials nodes in the standalone or in C4D, these are all named "Octane Mix Material" when imported back in C4D. With complex materials, it's sometimes time consuming to find the right final mix material to connect to the object(s).

Aoktar, do you think it's possible to restore the name of the mix material nodes from the .ORBX file in the C4D material manager? It could be wonderfull! :)
Win10 64bits | 3x 980 + 2x 670 + 1060 | Cubix XPander + network | Core i7 3600 MHz | 32GB | 1300w PSU
Sorry for my bad english...
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

atome451 wrote:About importing .ORBX materials from standalone (in LocalDB or not) or savings in the OctaneLive DB storage from C4D.

When you import complex nodes structure with cascading mix materials in .ORBX file format from the standalone or from materials made in C4D and saved in the OctaneLive DB storage, even if you rename the mix materials nodes in the standalone or in C4D, these are all named "Octane Mix Material" when imported back in C4D. With complex materials, it's sometimes time consuming to find the right final mix material to connect to the object(s).

Aoktar, do you think it's possible to restore the name of the mix material nodes from the .ORBX file in the C4D material manager? It could be wonderfull! :)
ok, will try to fix for 2.16 ;)
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
atome451
Licensed Customer
Posts: 285
Joined: Mon Feb 22, 2010 8:04 pm
Location: Brussels - Belgium
Contact:

Great! Thanks a lot! :D
Win10 64bits | 3x 980 + 2x 670 + 1060 | Cubix XPander + network | Core i7 3600 MHz | 32GB | 1300w PSU
Sorry for my bad english...
User avatar
Oleg
Licensed Customer
Posts: 55
Joined: Thu Nov 07, 2013 3:47 pm

What is that in the bottom corners, some sort of red vignette? Showed in wire mode

Image
Image
Post Reply

Return to “Maxon Cinema 4D”