I think I need some help with Octane in understanding it.
below is a render of a modo scene, beside it is the octane scene.
I created an override for the 2 area lights that are in the scene.
I have one UV map on the chair and one for the floor, they are two separate objects.
On the octane scene the bump map on the wood frame has gone haywire. I added an override to the front arm supports and noticed the power of the greyscale image for the bump was at 1.0 I reduced it to .1 to get the bump under control. I would of thought the plugin would read the bump value from modo. Is this not the case?
The fabric on the chair is a pattern that gets repeated 65 times in the horizontal and vertical. In the Octane scene the pattern is not repeated. If I add an override to the material I see no way to repeat the pattern.
Why is the plugin not getting the values from modo for the pattern.
The wood texture on the legs and vertical arms does not go the right way. In modo it's rotated 90 degrees which Octane is ignoring and I have been unable to get it to rotate in octane.
On the floor I added a material override so I could use the checker texture. It is always giving me this weird effect on the texture, also how do you change the color of the checks?
My greyscale checker in the modo scene is correct but in the octane scene it's messed up.
Now I'm pretty sure that this is all my doing, but it's got me stumped. I just can't seem to get to look right.
Anyone know what I doing wrong.
Thanks
OctaneRender for Modo (Windows) 1.52 [STABLE]
Moderator: face_off
At this stage the bump map power from Modo is not converted to Octane - however this would be a reasonably easy enhancement to make. How are you setting the strength of the bump map in Modo? Low Value/High Value?On the octane scene the bump map on the wood frame has gone haywire. I added an override to the front arm supports and noticed the power of the greyscale image for the bump was at 1.0 I reduced it to .1 to get the bump under control. I would of thought the plugin would read the bump value from modo. Is this not the case?
The plugin should pick this up automatically - however I just checked, and there seems to be an issue with some projections that has been introduced with the latest version, which I will investigate (and hopefully fix) today.The fabric on the chair is a pattern that gets repeated 65 times in the horizontal and vertical. In the Octane scene the pattern is not repeated. If I add an override to the material I see no way to repeat the pattern.
See above.The wood texture on the legs and vertical arms does not go the right way. In modo it's rotated 90 degrees which Octane is ignoring and I have been unable to get it to rotate in octane.
Yes - this is due to the Octane Checks node not working if the source geometry is at the origin on the scene. Raise it a tiny amount in the Y axis to fix.On the floor I added a material override so I could use the checker texture. It is always giving me this weird effect on the texture, also how do you change the color of the checks?
My greyscale checker in the modo scene is correct but in the octane scene it's messed up.
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
I'm having a strange problem with the octane plugin enabled. I notice this mainly if I'm in the model tab. If I load an octane scene (like my spectest scene) then close it and reload it or a different scene (using file > open recent), some of the mesh layers will be invisible. The 3d view shows no geometry. At first I thought I accidentally deleted the geometry but I discovered if you enable "show vertices", the vertices are there!
If I close the scene and reload it again, it loads fine. I wonder what happens if you accidentally save while in this state?
If I disable the octane plugin I dont have this issue
If I close the scene and reload it again, it loads fine. I wonder what happens if you accidentally save while in this state?
If I disable the octane plugin I dont have this issue
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
I haven't been able to reproduce this. Are you able to PM or Skype me some more details pls, and I will investigate.I'm having a strange problem with the octane plugin enabled. I notice this mainly if I'm in the model tab. If I load an octane scene (like my spectest scene) then close it and reload it or a different scene (using file > open recent), some of the mesh layers will be invisible. The 3d view shows no geometry. At first I thought I accidentally deleted the geometry but I discovered if you enable "show vertices", the vertices are there!
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
I have refreshed the installer at the top of this thread with:
1.52.0.57
- Compiled against Octane 1.52
- Fixed issue where material picking was not working on materials without a sub-group in the Shader Tree
- IMPORTANT: Fixed issue where Texture Locators attached to an Octane Override were not being applied (problem introduced 1.50.0.55)
- IMPORTANT: Fixed an issue where processing an emtpy mesh would result in all other meshes not loading
If you updated to 1.50.0.55, is it important to download and install this new version.
Paul
1.52.0.57
- Compiled against Octane 1.52
- Fixed issue where material picking was not working on materials without a sub-group in the Shader Tree
- IMPORTANT: Fixed issue where Texture Locators attached to an Octane Override were not being applied (problem introduced 1.50.0.55)
- IMPORTANT: Fixed an issue where processing an emtpy mesh would result in all other meshes not loading
If you updated to 1.50.0.55, is it important to download and install this new version.
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Thanks Paul
The latest build corrected a few things.
UV maps now are tiling properly, but the UV rotation is not being applied. However I can now put a transform on the texture and rotate it. Would it be possible to have that applied automatically?
Bump maps are still being applied at full strength. I'm just using a image map applied to a UV. The material gets it's bump strength from the bump amplitude on the material Ref tab. Low and High values are 0 and 100 percent on the texture layers tab.
I just found an interesting problem.
I made a change to the scene and needed to see the objects better in ogl. I put a material at the top of the tree above the base shader to make all the objects in the scene grey in ogl, modo still sees the scene ok for a render as in the all the materials still came through. Octane went black in it's output and did not render anything until I went to the texture environment in Octane and unchecked use RGB color or switched to daylight mode. The area lights in the scene were not been seen anymore in Octane.
As I forgot to turn the material off above the baseshader in the tree. Modo was ok with it, Octane was not. It threw me for a loop trying to figure out what went wrong.
I don't know if there is a way around that, I know it's user error but if the modo ouput is looking ok it can throw you off if Octane is showing something different.
Keith
The latest build corrected a few things.
UV maps now are tiling properly, but the UV rotation is not being applied. However I can now put a transform on the texture and rotate it. Would it be possible to have that applied automatically?
Bump maps are still being applied at full strength. I'm just using a image map applied to a UV. The material gets it's bump strength from the bump amplitude on the material Ref tab. Low and High values are 0 and 100 percent on the texture layers tab.
I just found an interesting problem.
I made a change to the scene and needed to see the objects better in ogl. I put a material at the top of the tree above the base shader to make all the objects in the scene grey in ogl, modo still sees the scene ok for a render as in the all the materials still came through. Octane went black in it's output and did not render anything until I went to the texture environment in Octane and unchecked use RGB color or switched to daylight mode. The area lights in the scene were not been seen anymore in Octane.
As I forgot to turn the material off above the baseshader in the tree. Modo was ok with it, Octane was not. It threw me for a loop trying to figure out what went wrong.
I don't know if there is a way around that, I know it's user error but if the modo ouput is looking ok it can throw you off if Octane is showing something different.
Keith
Windows 10 | 1950x threadripper |64gb Ram | EVGA GTX1080 ti x3 |
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04
I just realised that when you rotate the texture in Octane for your UV maps that if Modo has a 90° rotation on the UV map you have to do a -90° transformation in Octane to get the same result in Modo.
Can that be made to be the same rotation as with modo?
Keith
Can that be made to be the same rotation as with modo?
Keith
Windows 10 | 1950x threadripper |64gb Ram | EVGA GTX1080 ti x3 |
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04
I just got this error after rendering for 20 minutes
Started logging on 08.04.14 08:44:08
OctaneRender version 1.52 (1520000)
CUDA error 702 on device 0: The device kernel took too long to execute. This can only occur if timeouts are enabled. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Kernel execution failed (pt)
CUDA device 0: Path tracing failed
CUDA error 702 on device 0: The device kernel took too long to execute. This can only occur if timeouts are enabled. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Failed to deallocate device memory
Started logging on 08.04.14 08:44:08
OctaneRender version 1.52 (1520000)
CUDA error 702 on device 0: The device kernel took too long to execute. This can only occur if timeouts are enabled. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Kernel execution failed (pt)
CUDA device 0: Path tracing failed
CUDA error 702 on device 0: The device kernel took too long to execute. This can only occur if timeouts are enabled. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> Failed to deallocate device memory
Windows 10 | 1950x threadripper |64gb Ram | EVGA GTX1080 ti x3 |
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04
I just shut down Modo, restarted and loaded the scene I was rendering from before.
I now get this error
Started logging on 08.04.14 12:07:27
OctaneRender version 1.52 (1520000)
CUDA error 716 on device 0: Error code unknown.
-> Kernel execution failed (pt)
CUDA device 0: Path tracing failed
CUDA error 716 on device 0: Error code unknown.
-> Failed to copy memory to device.
CUDA device 0: Failed to load data of data texture 20 of context 0 onto device
CUDA error 716 on device 0: Error code unknown.
-> Failed to deallocate device memory
CUDA error 716 on device 0: Error code unknown.
-> Could not get memory info
CUDA error 716 on device 0: Error code unknown.
-> Failed to launch kernel (clear)
CUDA error 716 on device 0: Error code unknown.
-> Failed to allocated device memory
CUDA device 0: Failed to reallocate data texture 20 of context 0
CUDA error 716 on device 0: Error code unknown.
-> Failed to load symbol data to the device (camera data)
CUDA error 716 on device 0: Error code unknown.
-> Failed to allocated device memory
CUDA device 0: Failed to reallocate data texture 20 of context 0
CUDA error 716 on device 0: Error code unknown.
-> Failed to load symbol data to the device (camera data)
I now get this error
Started logging on 08.04.14 12:07:27
OctaneRender version 1.52 (1520000)
CUDA error 716 on device 0: Error code unknown.
-> Kernel execution failed (pt)
CUDA device 0: Path tracing failed
CUDA error 716 on device 0: Error code unknown.
-> Failed to copy memory to device.
CUDA device 0: Failed to load data of data texture 20 of context 0 onto device
CUDA error 716 on device 0: Error code unknown.
-> Failed to deallocate device memory
CUDA error 716 on device 0: Error code unknown.
-> Could not get memory info
CUDA error 716 on device 0: Error code unknown.
-> Failed to launch kernel (clear)
CUDA error 716 on device 0: Error code unknown.
-> Failed to allocated device memory
CUDA device 0: Failed to reallocate data texture 20 of context 0
CUDA error 716 on device 0: Error code unknown.
-> Failed to load symbol data to the device (camera data)
CUDA error 716 on device 0: Error code unknown.
-> Failed to allocated device memory
CUDA device 0: Failed to reallocate data texture 20 of context 0
CUDA error 716 on device 0: Error code unknown.
-> Failed to load symbol data to the device (camera data)
Windows 10 | 1950x threadripper |64gb Ram | EVGA GTX1080 ti x3 |
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04
Modo 13 64bit
Lightwave 2018
Nvidia driver 419.67
Octane modo plugin version 4.04.0.145
Octane lightwave plugin version 4.04