OctaneRender™ 3.0 for LightWave™ - Test build 3.08.0.7 RC1 Tweet

[promity]

If i have open both modeler and layout with loaded in each same object and i save object in layout after material's changes and go to modeler after this - modeler crashes.

[BorisGoreta]

I have lot's of modeler crashes, don't know why.

[promity]

I found that the modeler crashes even if you do not run Octane. But before this you need to save the objects of the scene in Layout and if the Modeller is open - it crashes.

[juanjgon]

If i have open both modeler and layout with loaded in each same object and i save object in layout after material's changes and go to modeler after this - modeler crashes.

This (and these kinds of problems after updating objects from the Modeler) are a known issue due to a bug in the LightWave 2018 SDK. The LW team is aware of this issue, and it should be fixed in the next LightWave build. Meanwhile I'll try to find a workaround from the plugin side for the next plugin build.

Thanks,
-Juanjo

[promity]

Thank's Juanjo!

[lightvu]

I see that this is RC1.
Also I noticed a lot of people reporting bugs/crashes with the LightWave 2018 plugin.
I have it installed but the first thing I encountered was the fact that I can not render to disk using F10 through native LightWave menus, it must be done through render passes in the Octane Editor. This does not let me render to PSD files, only EXR & PNG. Not too happy about that.

Should I wait for final release before really diving into this version of LightWave & Octane? At the moment I am using 2015 and the most stable Octane build available.

Thank you for your time.

[juanjgon]

Yes, currently the LightWave 2018 plugin only support the Octane native image files output functions using the render passes node, the same functions used always in all the LightWave versions if you want to export any render pass other than the beauty one. At some point, I'll try to support the new LightWave 2018 buffers system, but I don't have an ETA yet about when this feature will be available.

Thanks,
-Juanjo

[lightvu]

Thanks for the response.

It wouldn't be such a problem if:
-EXR files were not so darn big.
-The imported frames into AE looked like they did in the render window in LW. At the moment neither tone mapped or not do now show up 'proper'

[juanjgon]

The render to disk feature for the beauty pass using the LW saving functions was a limitation on the LightWave 2018 side. It has been fixed by the LW developers for the next LW2018 build.

Thanks,
-Juanjo

[juanjgon]

Hey Juanjo, I'm having a problem with the IPR on LW2018, I have a scene that uses the raycast node, when I hit F9 it renders fine, but if I open the IPR, the software stops responding. I tried removing the rayacst nodes and even the objects I used wit the nodes, it doesn't fix it. I,ve attached the project files. If you have the time, take a look at it. I just moved back to 2015 and it works fine.

This problem and all these kind of problems related to freezes starting the IPR (especially on OSX) should be fixed in the next plugin build for LW2018, including some problems reported a long time ago in LW2015, that are now also fixed thanks to the new features in the LW2018 SDK.

Thanks for reporting it!
-Juanjo