LWOctane: IPR is not working message (mac)

[griffithpictures]

Hi,
New to the forum. Been using Octane for the past two months with wonderful results. Often, I would deactivate the plug in from office computer to use on home computer on weekends. One time, I forgot to deactivate the lightwave plug -in, only deactivating the standalone. From that point on , all of my scenes would freeze lightwave... even after I did proper deactivation and waited an hour.

I uninstalled the plug-ins, and reinstalled them, did a proper reactivation and the scenes open again. However, Octane doesn't work anymore in lightwave at all, displaying a message at the bottom
No GPUs available for rendering (can't render the scene).

It also displayed the following messages attached as a screen cap. Don't know what I should do next

[juanjgon]

So the problem is that the plugin doesn't have GPUs available for rendering? ... can you please open the plugin options panel to see what GPUs are available?

Are you working with the last plugin release 2.20? ... also please check if the Standalone 2.20 works fine in your system.

I think that the message "No GPUs available for rendering (can't render the scene)." is not related to the licensing.

-Juanjo

[griffithpictures]

Standalone is working fine, but it's 2.06... Should I download the next version? (note, when I reinstalled the plug in, I did download a later version of the LW plug).

[juanjgon]

The problem is that for Octane 2.20 you need to update your CUDA and NVidia drivers to the last versions. Octane 2.2 needs CUDA 6.5 to work.

-Juanjo

[griffithpictures]

All good! Whatever licensing crash that occurred sent me down a strange path. But in the end, it was the driver. Thanks a bunch for the swift replies.

[griffithpictures]

Hi again,
Well, I'm now having a new issue where the scene won't advance frames (was set to 2 minutes a frame). It just holds on the first one, and lists a negative remaining time (currently -4:50). Is there a new checkbox I might have missed?

[juanjgon]

Are you working with the last 2.2 plugin release? ... please try this version if you are working with and older one.

-Juanjo

[griffithpictures]

2.16 for the Standalone version. 2.1 for LW. (I thought 2.2 was beta?)

[griffithpictures]

(this project is for the title sequence of a nightly TV show)

[juanjgon]

Please, try to 2.2 version to see if you have the same behavior. I has some changes in the rendering loop that could fix your problem. It is a beta release, but it is stable so far.

-Juanjo