Page 1 of 2

hdrlightstdio + octane

Posted: Thu Jul 25, 2013 9:40 am
by Rickky
is there some plan to make a plug between hdrlightstudio & octane ?

Re: hdrlightstdio + octane

Posted: Mon Aug 05, 2013 9:20 pm
by nbreslow
Seconded. This would be extremely useful!

-Nick

Re: hdrlightstdio + octane

Posted: Tue Aug 06, 2013 3:34 am
by FooZe
Hi Guys,

HDR light studio have already made support for the 3ds max plugin:
http://www.hdrlightstudio.com/workflows ... s_max_live

We don't have any plans for anything like integrating it into the standalone if that's what you were meaning...

Thanks
Chris.

Re: hdrlightstdio + octane

Posted: Tue Aug 06, 2013 7:09 am
by Interfaces
finally octane standalone is doomed to disappear to the detriment of plugins for 3d modeling software

Re: hdrlightstdio + octane

Posted: Tue Aug 06, 2013 9:01 am
by rappet
Interfaces wrote:finally octane standalone is doomed to disappear to the detriment of plugins for 3d modeling software
Might look like that is the case. What are the pros and cons of that :?:

Re: hdrlightstdio + octane

Posted: Fri Aug 09, 2013 12:16 am
by Rikk The Gaijin
Interfaces wrote:finally octane standalone is doomed to disappear to the detriment of plugins for 3d modeling software
I hope not... I really like the standalone version

Re: hdrlightstdio + octane

Posted: Fri Aug 09, 2013 12:51 am
by nbreslow
It would be great if you could work with the HDR Light Studio People to also make this happen for the Octane-Maya plugin.

(Personally I would like to see some sort of link in Standalone but in Maya would be the next best thing)

-Nick

Re: hdrlightstdio + octane

Posted: Tue Aug 13, 2013 10:25 am
by ROUBAL
Interfaces wrote:
finally octane standalone is doomed to disappear to the detriment of plugins for 3d modeling software

Might look like that is the case. What are the pros and cons of that
The main drawback of integrated plugins versus the Standalone version is that you have your scene open in both Octane and the host 3D package : this requires almost twice the amount of system RAM required by the standalone only ! As much system RAM is required to manage the data in GPU VRAM (around 16GB for a 3GB scene in Octane standalone), the required amount for big GPUs is huge. A 6GB Titan card used with a plugin instead of standalone could require up to 64GB of VRAM ! Not many motherboards can host 64GB !

The main advantages of Plugins are the interactivity and easier animation.

Re: hdrlightstdio + octane

Posted: Tue Aug 13, 2013 11:01 am
by face_off
The main drawback of integrated plugins versus the Standalone version is that you have your scene open in both Octane and the host 3D package : this requires almost twice the amount of system RAM required by the standalone only ! As much system RAM is required to manage the data in GPU VRAM (around 16GB for a 3GB scene in Octane standalone), the required amount for big GPUs is huge. A 6GB Titan card used with a plugin instead of standalone could require up to 64GB of VRAM ! Not many motherboards can host 64GB !
This is absolutely not true. I've done lots of testing in this area on my plugins, and yes, if live update is on for all geometry items, there is a memory overhead - but absolutely nothing like 64GB! If live geometry updating is not on, then the memory overhead of the plugin is small. For example, the ArchiCAD, Revit and Inventor plugins all load the scene and then release ALL memory. So once loaded....no overhead....(other than the host app). The Poser plugin keeps a copy of the vertices in RAM, which even on a massive scene requires only a small amont of memory.

Paul

Re: hdrlightstdio + octane

Posted: Thu Aug 15, 2013 4:36 am
by ROUBAL
Well, I will be able to test only when the Blender plugin will be available, but it had been confirmed by someone from Otoy some time ago ... :roll: