Thanks Paul!!

Thanks for answering so quickly! Your quick response helps me to think I should pay closer attention to the Modo plugin.

Any word on how the Octane 4 plugin will be handled?

1. Will we see an Octane 4 plugin for DAZ Studio?
2. Will the plugin for DAZ Studio, if it's created, be one of the free plugins?
3. If we get to enjoy an Octane 4 plugin for DAZ Studio, do you have any ETA or have a strategy about when it could ...

I've heard from an interview that the 3.08 code is moving into Version 4, which begs the question - will the Lightwave version of Octane be one of the free versions or no? If you know, Juan, please let us know.

Oh, sorry, Juan. I didn't know. Thanks for taking time to answer!

juanjgon wrote:Well, nothing changes from the Octane point of view. LightWave 2018 has a whole new render engine with a new set of PBR material and tool nodes, but Octane works with its own PBR nodes, like always.

Thanks,
-Juanjo

PBR and how materials now work - should we assume not only 2015, but also 2018 usage of material, which is new.

This (http://static.lightwave3d.com/marketing/lightwave_2018/release/pbr-unified-renderer.html) and volumetrics are a curiosity for me in understanding the new Octane updates coming up ...

But, Juan, it will still work with the new way of texturing in 2018, too?

I would also like to know what the changes/improvements are to Octane's plugin for LW2018, since I own the standalone and am considering this LW plugin as a first purchase.

From DAZ forums today -

An updated SDK means:
1) At best, anyone using an older version of Studio can’t use the plugins compiled with the new SDK.
2) At worst, all users must get new versions of all plugins.

#1 is annoying for the people who don’t want to be on the latest version of DAZ Studio ...

t_3 - If DAZ's API is not being updated, how does that affect the future release of 2.0? Do you think DS is actually dissing 3rd-party developers?