OTOY Forums

juanjgon wrote:

Mastoy wrote:I get this error message when trying to add the plugin :

I tried to download the file again but no success
Any idea ?

I'm fairly sure that at some point you are mixing old Octane.dll/.dat files with the new plugin. Please, be sure that you have removed the Octane.dll and Octane.dat files from your LightWave/bin folder or any other place in your hard disk. Currently these files are deployed with the plugin .p file and must be all in the same folder used by the plugin. Nothing must be copied to the LW/bin folder.

Thanks,
-Juanjo

That was it, I was sure I deleted those files in the previous installation, sorry for that and thanks a lot for the lightspeed answer !

Great work Juan......might be the best Octane integration there is

Very good works Juan ! Converter is fantastic !

Thanks Juanjo!

Thanks much
Material converter awesome

I have a scene (contains animated TFD cache sequence) that renders without error in Octane 3.03.2B, crashes when doing an F10 (render scene) with this updated Octane version if I have Update scene (instead of Full scene reload) set in the Octane Render Target root node. It renders one frame and then Lightwave crashes. It does not crash when viewing in the IPR. However, I don't notice any difference when setting Full scene reload or Update scene in the IPR; it always does a full scene reload). The update to timeline scrubbing appears to work, even though its slow/sluggish; only allowing me to advance slowly one frame at a time).
The attached Lightwave dump may help diagnose this. Also, I noticed erratic behavior with the Backplate Visible option within the Environment: Texture node. In the previous version, I did not check this when I wanted my texture image to be scene. But in this version, in the IPR I see my texture image when only when Backplate visible is checked/selected. I first notice this when I rendered an animation sequence and saw the the environment image appear and disappear on a few frames before it was gone for most of the frames.

With my slave machines, I noticed I keep seeing 'slave is authenticating' in the Netion options pane. I did not notice this before. When network rendering I noticed the nodes not contributing (I see the Slaves 2, GPU 3, but in the render window I see Net Slaves 2/0, Net GPUs 3/0 (total/updated). So there might be a problem with the code in this area as well.

I updated to get better performance with scenes that have animated TFD volumetrics. But for me there is not an improvement in this area since I have to use the Full scene reload option to avoid the application crash.

In the previous versions I have been successful with rendering sequence files. But with the current build, I can only render still textures. I want to use an animated texture (use texture emission) on a monitor screen object. But unfortunately after wasting a lot of time troubleshooting this, I failed to solve this issue.

On a positive note, I will say the network rendering does appear to be working. In my previous post, I mentioned it appeared the slaves were not participating in the rendering. This was true on frames where the master/workstation rendered the frame in 3 second. But later on while rendering that scene, the frames needed more time (volumetrics were building up, etc.) and it was obvious the slaves were participating in the rending.

Because of the above mentioned issues, I'm about ready to roll back to the previous build/version. But I'm tired right now and going to sleep..

cyborgty wrote:I have a scene (contains animated TFD cache sequence) that renders without error in Octane 3.03.2B, crashes when doing an F10 (render scene) with this updated Octane version if I have Update scene (instead of Full scene reload) set in the Octane Render Target root node. It renders one frame and then Lightwave crashes. It does not crash when viewing in the IPR. However, I don't notice any difference when setting Full scene reload or Update scene in the IPR; it always does a full scene reload). The update to timeline scrubbing appears to work, even though its slow/sluggish; only allowing me to advance slowly one frame at a time).

So, when do you get a crash, in update mode or in full reload mode (or in both modes)? Perhaps there is a problem with the new volumes update feature introduced in the latest build. In update mode, do you have the new "update volumetrics" option enabled?

Anyway if you can send me the scene with this crash, I could test it here. Unfortunately, the dump file is not very useful.

Thanks,
-Juanjo

cyborgty wrote:Also, I noticed erratic behavior with the Backplate Visible option within the Environment: Texture node. In the previous version, I did not check this when I wanted my texture image to be scene. But in this version, in the IPR I see my texture image when only when Backplate visible is checked/selected. I first notice this when I rendered an animation sequence and saw the the environment image appear and disappear on a few frames before it was gone for most of the frames.

The three "Visible" options available in the environment nodes are used only if the node is linked to the "Visible Environment" render target root node input. When the environment node is used as a normal environment, these options are ignored. Perhaps the problem is related to other issue, but if you have a sample scene to reproduce it, please send it to me.

Thanks,
-Juanjo

cyborgty wrote:In the previous versions I have been successful with rendering sequence files. But with the current build, I can only render still textures. I want to use an animated texture (use texture emission) on a monitor screen object. But unfortunately after wasting a lot of time troubleshooting this, I failed to solve this issue.

The texture sequences seem to work fine here. Remember that if you are using a texture sequence in a material you must enable the "Update Materials" option if you are rendering the scene in update mode, and you must enable the "Mat. Upd" option in the IPR if you want to see the sequence while time scrubbing.

Thanks,
-Juanjo