OTOY Forums

Method wrote:
Edit.: It's cool. Just set Gamma to 1 and tick Ipm.Samp

This had me sxcratching my head for a while too. Couldn't work out why the HDRi map I was loading in the plugin was blowing out all the highlights but in the Standalone Octane was fine. Then I realised the plugin was importing the HDRi at Gamma 2.2

Maybe Aoktar can set the default for HDRI to Gamma 1 for future versions of the plugin.

Finally Got my Copy,So excited!

As soon as the Mac version is out, you have my cash! This will be a great alternative to C4D's good-but-slow renderer.

A quick question..

The "Update Geometries" option warns you not to use it in its current state for complex or large scenes. I can certainly understand why.. But what criteria would you say makes a complex scene?

Also down the road, what hardware would you say most drives the ability to keep the live stream between octane and c4D for this live geometry update? I see the plug-in as a potential live design tool while sitting with a customer, but some of our scenes can be extremely large. Currently using one Tesla C2075 6GB GPU with this plugin and loving the results, however down the road we are looking at the new K series Tesla - my thinking is the increase in memory speed may help this live plug-in update faster, and the additional cuda cores help the rendering times.. Or perhaps the updates to the GPU are more of a system memory speed issue? Just wondering your thoughts on where to spend the money.

Thanks again!!

adecemployee wrote:A quick question..

The "Update Geometries" option warns you not to use it in its current state for complex or large scenes. I can certainly understand why.. But what criteria would you say makes a complex scene?

Also down the road, what hardware would you say most drives the ability to keep the live stream between octane and c4D for this live geometry update? I see the plug-in as a potential live design tool while sitting with a customer, but some of our scenes can be extremely large. Currently using one Tesla C2075 6GB GPU with this plugin and loving the results, however down the road we are looking at the new K series Tesla - my thinking is the increase in memory speed may help this live plug-in update faster, and the additional cuda cores help the rendering times.. Or perhaps the updates to the GPU are more of a system memory speed issue? Just wondering your thoughts on where to spend the money.

Thanks again!!

I must give more info about Update Geometries process. This option do same thing with full scene export process, but only for updated objects. So each process has voxelisation phase. This is most time consuming step in update operation. And done by Octane SDK. I'm not sure what is the most slow part. Data transfer or geometry parsing. Before 1.11 version, voxeling was taking long time due single threaded processing.
Best way to test with different cards on same pc configuration. Which will give a idea. Maybe Titan or Tesla K20 can give you boost.
I can compare Titan vs. Gtx 590 for some processes.

.... sorry, but news about the macversion...?!

Actually, to be very honest, as eager as I am to have Octane C4d on my Mac, I'm equally happy to have the Windows version all sorted out and bugs squashed before it's ported over. Aoktar's roadmap is pretty clear anyway, so it's definitely coming soon. I hope he takes his time and makes it a solid release.

mustardseedsg wrote:Actually, to be very honest, as eager as I am to have Octane C4d on my Mac, I'm equally happy to have the Windows version all sorted out and bugs squashed before it's ported over. Aoktar's roadmap is pretty clear anyway, so it's definitely coming soon. I hope he takes his time and makes it a solid release.

Mac sdk is near. I'll bring you asap.

So are all the Mac plug-ins simply waiting for the SDK to appear? Same with LW?

yes, just like maya archicad and daz
ciao beppe