OTOY Forums

BorisGoreta wrote:LW/Octane is tracking image file updates now. Whenever I re save some texture in PS and go back to LW, Octane reloads the whole scene. Is there a way to enable/disable this. This is not good for huge scenes where reloads take a lot of time.

I've added a new plugin option "Images Altered IPR update" to control if the IPR scene must be reloaded after detecting changes in the images list. Disabled by default.

Thanks,
-juanjo

Hi,

Just purchased Lightwave's plugin.

I'm having crashes when moving the camera or any object while IPR is active. All with LW2018.0.2

Best regards.

Also, LW's render region does not seems to work.
Edit: sorry, on IPR.

Great that it is is an option since when working on a simpler scene it is actually useful !

juanjgon wrote:

BorisGoreta wrote:LW/Octane is tracking image file updates now. Whenever I re save some texture in PS and go back to LW, Octane reloads the whole scene. Is there a way to enable/disable this. This is not good for huge scenes where reloads take a lot of time.

I've added a new plugin option "Images Altered IPR update" to control if the IPR scene must be reloaded after detecting changes in the images list. Disabled by default.

Thanks,
-juanjo

Asticles wrote:Hi,

Just purchased Lightwave's plugin.

I'm having crashes when moving the camera or any object while IPR is active. All with LW2018.0.2

Best regards.

Hi,

Can you please enable the plugin log file in the plugin options panel to check what kind of errors do you get after one of these crashes? It sounds to me like a problem with the drivers, or perhaps with your system. It is true that the 2018 plugin has some issues, but it should not crash doing basic things.

Thanks,
-Juanjo

Asticles wrote:Also, LW's render region does not seems to work.
Edit: sorry, on IPR.

Hi,

The IPR has its own region tool, that you can enable using the IPR "Region" button. Once enabled you can move it with the mouse, use the wheel to change its size or use CTRL+drag to draw a new region.

Thanks,
-Juanjo

Juan, in LW 20180.0.2 it looks like Octane UVMap node don't work anymore with Layers T channel mode, nor does Get T function work ?

On one machine every frame of the sequence renders until approx. 80% of the progress and then it hangs there for 7 seconds still in RENDERING mode and then it finishes.

On another machine the same scene renders without any hang at all.

What could be the cause for this ?
This makes a difference of 17 seconds per frame to 10 seconds per frame on the second machine, just because of this hang.

Is some single threaded CPU job happening at that time ?
First machine is slower in single CPU jobs then the second one but the difference is 7 seconds to almost no hang at all.

When changing the value inside this node using graph editor the changes aren't reflected in IPR, if not using E(nvelope) button (using single value) changes reflect in IPR.

Lewis wrote:Juan, in LW 20180.0.2 it looks like Octane UVMap node don't work anymore with Layers T channel mode, nor does Get T function work ?

Yes, this is known limitation in LW2018. The fact is that this feature in LW2015 works extracting the T texturing information of the standard LightWave material from the Octane material node, but now that the standard LW material is also a node it is not possible to have both LW and Octane materials working at the same time. The LW SDK functions used to get the texturing information only work if the LW material is linked to the surface input, as expected.

Probably on a solution could be trying to support the new LW2018 projection nodes, if you need to use the LW projections in the Octane scene, of work with the Octane native projections, although it is true that they can't be used for displacement.

Thanks,
-Juanjo