OTOY Forums

- I get a crash only when performing an F10 render with Update Scene set. This crashes every time I attempt to use it in the scene with animated volumetrics.
- 'Full scene reload' does NOT cause a crash.
- I will send an email with a sample scene later today.

I'v installed the Octane 3.04 .50 in my lightwave 2015.3 but no way to see the button of th etool of thematerial conversion.
I have cleaned the menu branch and reloaded thenew one but no way...

Any sugestion?

Ok fixed...it was my fault!

juanjgon wrote:

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

I'm only rendering using the Full scene reload, since that's the only way I can get it to work without crashing.
However, the issue with texture sequence/animated texture problem was caused by me. When I created the texture sequence in After Effects, I did not pad the sequence numbers correctly.

cyborgty wrote:- I get a crash only when performing an F10 render with Update Scene set. This crashes every time I attempt to use it in the scene with animated volumetrics.
- 'Full scene reload' does NOT cause a crash.
- I will send an email with a sample scene later today.

Can you send me a sample scene with this crash? The log file can also help, please enable it in the plugin options panel and attach the log that you get after the crash.

Thanks,
-Juanjo

Nice update Great work!
I love the textures converter, really helpful. Have you ever considered making a tool that converts an orbx into a LightWave surface 'Compound Node'?

It seems I am not able to control the reflection amount on a surface with a displaced specular material on it. It is always 255 !





This was because displacement was applied on a big N-Gon, if subdivided and converted to quads/tris it worked.

Eeks! Juanjo, it happened again. That damn Texture from file field got me again! (fortunately this time I caught it before it was buried deep in a project) I understand you can't do anything about making it read only and populated only by path from button -- but could you at least make it so it does not get focus automatically when we double-click a Texture Image node? Is that possible pal? I really think it would make this mistake very rare for most.

Also, have you been privy to any of the new OSL stuff coming, so that you could determine if we will indeed be able to span displacements across instances using World Coordinates? (we talked about this before - where folks like me want to be able to make displaced instances be completely unique)

BorisGoreta wrote:It seems I am not able to control the reflection amount on a surface with a displaced specular material on it. It is always 255 !
This was because displacement was applied on a big N-Gon, if subdivided and converted to quads/tris it worked.

Hmm, weird issue. Can be a problem with the plugin internal n-gons tessellation algorithms. Anyway subdivide/triple big N-Gons with a lot of edges in the modeler to use it in Octane is always a good idea.

Thanks,
-Juanjo

FrankPooleFloating wrote:Eeks! Juanjo, it happened again. That damn Texture from file field got me again! (fortunately this time I caught it before it was buried deep in a project) I understand you can't do anything about making it read only and populated only by path from button -- but could you at least make it so it does not get focus automatically when we double-click a Texture Image node? Is that possible pal? I really think it would make this mistake very rare for most.

Sorry, I can't reproduce this behavior here. The texture from file parameter is only in focus to write on it if you click in the string GUI. Do you get it in focus double clicking the node?

Thanks,
-Juanjo