OTOY Forums

MrFurious wrote:Juanjo I found another bug with the latest release 2.6.1

Open my sample scene, open IPR and go to the Editor. In the render target check Enable Surface Override. then select 'override object' = none and uncheck 'Enable surface override'. Crashes every time.

This bug is fixed for the next release. Thanks for report it.

-Juanjo

Hello,

i've a little problem with the latest dayly builds.
When rendering animations with imagewiewer enabled, it makes lightwave crash (randomly). It seems to be linked to my configuration ( 3 graphic cards, 1 ATI FIREPRO V4900 for 3screens and openGL display and 2 GTX780ti for cuda rendering - no display on them ).

If i disable the GPU 0 ( the first GTX 780ti ), it renders without problem.
If i disable the GPU 1 ( the second GTX 780ti, with GPU 0 enabled again of course ), it crashes
If i enable both of the GTX and disable the Imagevieweroutpout, it works...

Not really ennoying because Imagewiever display while animation rendering is not really usefull, so i always disable it now, , but just in case, i reveal this problem...

Tested on different animations, and the random crash behaviour ramains the same. I can't say if it was the case on previews versions ( octane 1.5 ... ) because this workstation is 4 months old... ( i7 4930K @ 4.3ghz, 64 Go ram, win8.1 64, LW 11.6.3 )

Juanjo a couple minor things that would be really helpful in the next release, I can't imagine these being difficult to implement.

- IPR not reloading when adding a null (someone else mentioned this in the forums). I add lots of nulls for parenting and the constant unnecessary reloading grates after a while.
- Persistent IPR option buttons. I posted a separate thread about this but thought I'd mention it here also. I'm pretty sure I remember MatUpd being always ON pre v2.0. This works better for me, but having it always OFF might work better for others. Would be nice if it just remembered the last state, either per scene or globally.

Thanks,
Dino.

I second the Null thing again.

MrFurious wrote:Juanjo a couple minor things that would be really helpful in the next release, I can't imagine these being difficult to implement.

- IPR not reloading when adding a null (someone else mentioned this in the forums). I add lots of nulls for parenting and the constant unnecessary reloading grates after a while.
- Persistent IPR option buttons. I posted a separate thread about this but thought I'd mention it here also. I'm pretty sure I remember MatUpd being always ON pre v2.0. This works better for me, but having it always OFF might work better for others. Would be nice if it just remembered the last state, either per scene or globally.

Thanks,
Dino.

+1 null thing. Also Juanjo, if making persistent IPR buttons, please also include active GPUs too. I often only use one GPU when setting up scenes - and with a max samples of 60, 80 or 100 at that.

Whay is manipulating objects in viewport while IPR is rendering so smooth now ?

I think Juanjo is busy with Renderman/Ris development.
That's 3 renderers he's handing already

geo_n wrote:I think Juanjo is busy with Renderman/Ris development.
That's 3 renderers he's handing already

Believe me, the Octane plugin support and development has always the highest priority

-Juanjo

I hope you're having fun though. Handling 3 major projects is not easy.
Looking forward to the renderman plugin for lw, too.

I'm having some issues with the latest build (Windows and OSX): RELEASE 2.6.1 - 15/Aug/2014:

For reference, my system details:

OS: Windows 7
GPU: Geforce 780TI (Galaxy), using driver version 340.52
Lightwave version: 11.6.1

1) Plugging in the environment node always crashes Octane. If IPR is on, it crashes immediately, if I hit f9 to render, it crashes if the environment node is plugged in.

2) Displacement is very unstable and crashes my video card. Specifically, when rendering or using IPR with displacements, the screen freezes for about 10 seconds, then I get this error:

"The NVIDIA OpenGL driver detected a problem with the display driver and is unable to continue. The application must close. Error code: 3.

My nodal setup involves using images as masks for the displacement, I don't know if that would be an influencing factor or not. If a sample scene would help narrow down why I'm getting these errors, let me know whom I could send it to to narrow things down.