There is another feature in the standalone that I miss in the lightwave plugin.
With the standalone, I can save an image at any time as OpenEXR Tonemapped, OpenEXR untonemapped, PNG 8bpc or PNG 16bpc.
In the lightwave plugin I can only save jpg or tga from the IPR. Also, if I need a tonemapped and untonemapped render, I need to F9 render twice.
Is it possible to add this?
OctaneRender™ for LightWave™ build 1.13.1 released
Moderator: juanjgon
I will think about this issue. Perhaps could be possible add a button to the IPR to enable/disable tone mapping.funk wrote:There is another feature in the standalone that I miss in the lightwave plugin.
With the standalone, I can save an image at any time as OpenEXR Tonemapped, OpenEXR untonemapped, PNG 8bpc or PNG 16bpc.
In the lightwave plugin I can only save jpg or tga from the IPR. Also, if I need a tonemapped and untonemapped render, I need to F9 render twice.
Is it possible to add this?
-Juanjo
Another bug report: Shift+clicking instances doesnt bring up the material editor. It probably has something to do with the fact that it isnt real geometry. Hopefully there is a workaround
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Currently there is no workaround for this issue. Plugin use a custom ray casting code to pick the object's surfaces because neither Octane or LW APIs have surface picking, but this custom code is not compatible with instancing. Perhaps in the the future Octane could have it's own native surface picking to allow instancing surfaces picking.funk wrote:Another bug report: Shift+clicking instances doesnt bring up the material editor. It probably has something to do with the fact that it isnt real geometry. Hopefully there is a workaround
-Juanjo
Probably small bug with UVMAP node.
When render engine is set to LW Native renderer and change parameter in UVMAP node lightwave crashes.
I know it sounds unlogic changing something in octane node when in LW mode. But not crashing would be better i think.
Anyway, again great release and fast work! I really love the material picker.
When render engine is set to LW Native renderer and change parameter in UVMAP node lightwave crashes.
I know it sounds unlogic changing something in octane node when in LW mode. But not crashing would be better i think.
Anyway, again great release and fast work! I really love the material picker.
Thanks, I will test it to see if I can avoid the crash.desarts wrote:Probably small bug with UVMAP node.
When render engine is set to LW Native renderer and change parameter in UVMAP node lightwave crashes.
I know it sounds unlogic changing something in octane node when in LW mode. But not crashing would be better i think.
Anyway, again great release and fast work! I really love the material picker.
-Juanjo
Another issue.
Follow steps to test:
- New Scene
- Enable Octane
- Add new sphere
- Add difuse material with Turbulence texture
- Open IPR
- Move Sphere.
The texture is static in world space. So it glides over the sphere surface. I dono if this is bug or it can be disabled? I didn't have this in previous version.
Thx for looking at this.
Follow steps to test:
- New Scene
- Enable Octane
- Add new sphere
- Add difuse material with Turbulence texture
- Open IPR
- Move Sphere.
The texture is static in world space. So it glides over the sphere surface. I dono if this is bug or it can be disabled? I didn't have this in previous version.
Thx for looking at this.
Octane procedurals always work in world space, so if you move the sphere texture is going to slide over the object's surface. There is no Octane version with local space procedural textures.desarts wrote:Another issue.
Follow steps to test:
- New Scene
- Enable Octane
- Add new sphere
- Add difuse material with Turbulence texture
- Open IPR
- Move Sphere.
The texture is static in world space. So it glides over the sphere surface. I dono if this is bug or it can be disabled? I didn't have this in previous version.
Thx for looking at this.
But it is easy to make a node tree setup to fix a texture to the object using the object info node. You have a sample scene in the plugin .zip file.
-Juanjo
- Attachments
-
Question:
I like to create an texture offset based on Item ID.
I managed to do this with Procedural Textures. I also tried with Image textures but that didn't work.
Do you know any kind of setup to do this with image textures?
See attached images below for node setup.
It could be very usefull to do lots of objects with the same material. This break repetition in the textures. I think of tiles on the ground. In this case wooden panels. Etc.
Hopefully there is a solution to this.
I like to create an texture offset based on Item ID.
I managed to do this with Procedural Textures. I also tried with Image textures but that didn't work.
Do you know any kind of setup to do this with image textures?
See attached images below for node setup.
It could be very usefull to do lots of objects with the same material. This break repetition in the textures. I think of tiles on the ground. In this case wooden panels. Etc.
Hopefully there is a solution to this.
- Attachments
-
- This is the node setup with procedural texture and offset based on Item ID.
-
- This is the result with procedural texture and offset based on Item ID.
-
- This is the node setup with image texture and offset based on Item ID.
-
- This is the result with image texture en offset based on Item ID.