aoktar wrote:No that's my mistake on compiling flags. I fixed and re-uploaded archive.NVN wrote:Hi Aoktar.
I've some strange Error's.
I cant UVW Mapping.
I deinstall all old files, installed the new Octane Standalone and the plugin also.
C4D R15.
Have i forgot something what i have to do?
Version 3.00 - Alpha10.1 (30.04.2016)
Moderators: ChrisHekman, aoktar
thx! 
- gordonrobb

- Posts: 1247
- Joined: Sat Mar 16, 2013 9:08 am
Hold the phone, I've just been in other discussions about how TFD is not yet supported, or doesn't do what is needed by Octane 3. Is this working only because you are using the C4D version?Asym93 wrote:I did a quick test with TFD. I have to say the integration is like magic. The plugin itself is explosive!
Amazing work Aoktar!
Congrats to the Octane dev team!
Windows 8 Pro | i7 3770 OC | 32 GB Ram | Single Titan (plus Black Edition on Order) | Octane Lightwave |
Your settings are right! Also you check out the example files Aoktar provided.eyeonestudio wrote:Could you share the Scene?Asym93 wrote:I did a quick test with TFD. I have to say the integration is like magic. The plugin itself is explosive!
Amazing work Aoktar!
Congrats to the Octane dev team!
I want know voxel & tfd setting.![]()
Thanks...
-------------------------------------------------------------------------------------------------------------- I found Something
Maybe some very, very kind person is nice enough and makes a quick tutorial about setting up volumes and makes a quick tutorial to TFD and what things must be set and how tehy have to be set. Like i did for jewelry rendering and the new live viewer a year ago. It would be highly apreciated and would help hundrets of users to save some time. So please. Is there someone who is kind enough?
Have a nice day. Chris!
Have a nice day. Chris!
The good news is TFD is now totally supported! Make sure the combination is Octane for c4d(v3) + TFD(c4d version). The only thing you can't do with TFD is exporting OpenVDB. But TFD provides the option to read voxel data (at least in Xpresso), I guess which exactly makes this integration possible.gordonrobb wrote:Hold the phone, I've just been in other discussions about how TFD is not yet supported, or doesn't do what is needed by Octane 3. Is this working only because you are using the C4D version?Asym93 wrote:I did a quick test with TFD. I have to say the integration is like magic. The plugin itself is explosive!
Amazing work Aoktar!
Congrats to the Octane dev team!
Aoktar has posted several early tests in this thread:
viewtopic.php?f=30&t=51688&start=10
First, thanks a lot for your fantastic work! I'm a fan!
One question: what about xpDomain voxels from X-Particles? Is this will be supported in future?
Maybe this is already supported but i can't find the right setup...
One question: what about xpDomain voxels from X-Particles? Is this will be supported in future?
Maybe this is already supported but i can't find the right setup...
Win10 64bits | 3x 980 + 2x 670 + 1060 | Cubix XPander + network | Core i7 3600 MHz | 32GB | 1300w PSU
Sorry for my bad english...
Sorry for my bad english...
I think Standalone thread is fine to get idea about volume fundemantals. In TFD i'm still working with TFD developers. Also Otoy are changing the somethings on density/temperatures/etc... Long story....
For TurbulenceFD
density -> absorption/scattering or emission (if no temperature)
temperature -> emission
Also "3rd party shaders" for evaluating TFD->Render->Smoke/Fire shader. I added this as a option because some slowness on TFD's api. They will fix it.
Currently we have not any texturing option for volumes. Just we can set densities for voxels.
Also we don't yet support XParticles volumetrics. But i'll work on after TFD.
For TurbulenceFD
density -> absorption/scattering or emission (if no temperature)
temperature -> emission
Also "3rd party shaders" for evaluating TFD->Render->Smoke/Fire shader. I added this as a option because some slowness on TFD's api. They will fix it.
Currently we have not any texturing option for volumes. Just we can set densities for voxels.
Also we don't yet support XParticles volumetrics. But i'll work on after TFD.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- indexofrefraction

- Posts: 178
- Joined: Wed Jul 25, 2012 9:53 am
hi aoktar...
what i still dont understand is what's the relation between the c4d plugin and the standalone app...
i exclusively use the plugin, never do anything with the standalone...
so does the plugin need or access the standalone? (libs or anything)
do i need to update the standalone to the same version of the plugin?
do i need to start the standalone once, even if i exclusively use the plugin?
lots of questions
what i still dont understand is what's the relation between the c4d plugin and the standalone app...
i exclusively use the plugin, never do anything with the standalone...
so does the plugin need or access the standalone? (libs or anything)
do i need to update the standalone to the same version of the plugin?
do i need to start the standalone once, even if i exclusively use the plugin?
lots of questions
Mac Pro (2012) 2x6 Core | 24GB | 1 x Geforce GTX580/3GB
Forget the gui of Standalone but else of codes are used by plugin. All renderer core is distributed by plugins and plugins can't work without this part.indexofrefraction wrote:hi aoktar...
what i still dont understand is what's the relation between the c4d plugin and the standalone app...
i exclusively use the plugin, never do anything with the standalone...
so does the plugin need or access the standalone? (libs or anything)
do i need to update the standalone to the same version of the plugin?
do i need to start the standalone once, even if i exclusively use the plugin?
lots of questions
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
