@pixelrush: your results seems correct to me, they are roughly the same of my 560 under mac. anyway you could make a direct comperison with the same results with beta 3.01 on your system
ciao beppe
OctaneRender™ Standalone v1.0 beta3.03 [obsolete]
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
i have noticed a big speed improvement in the clay render mode... have you reduced the reflectance of the default material or you have found a way to speed up the rendering of diffuse material in general?
@pixelrush: your results seems correct to me, they are roughly the same of my 560 under mac. anyway you could make a direct comperison with the same results with beta 3.01 on your system
ciao beppe
@pixelrush: your results seems correct to me, they are roughly the same of my 560 under mac. anyway you could make a direct comperison with the same results with beta 3.01 on your system
ciao beppe
Yes the brightness of the diffuse material got reduced to something more reasonable, which is why you see this speed improvement.bepeg4d wrote:i have noticed a big speed improvement in the clay render mode... have you reduced the reflectance of the default material or you have found a way to speed up the rendering of diffuse material in general?
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
ok, thanks marcus for the clarification
i see also a much better result for the smoothing problem on low poly meshes, great
ciao beppe
i see also a much better result for the smoothing problem on low poly meshes, great
ciao beppe
- Attachments
-
- 3.01
-
- 3.03
Greetings to all, this is my first post.
I've only had Octane for less than a week and I'm slowly getting into things - it's my first renderer and was pretty overwhelmed with things at first and also because I was struggling to bring in more than one material from my CAD program. However, since trying the 3.03 release, the import now seems to be OK, so please don't make any changes that'll spoil it for me. Thanks very much for the very rapid updates to this cool renderer, I do hope to have some fun with it
Martin.
I've only had Octane for less than a week and I'm slowly getting into things - it's my first renderer and was pretty overwhelmed with things at first and also because I was struggling to bring in more than one material from my CAD program. However, since trying the 3.03 release, the import now seems to be OK, so please don't make any changes that'll spoil it for me. Thanks very much for the very rapid updates to this cool renderer, I do hope to have some fun with it
Martin.
Thanks guys, it keeps getting better and better. But I'm still having issues. 
I removed the libGLEW link and Octane started up with out complaints. Yay. Here is how I tested it and the results, maybe they will help determine why my system is having problems.
I started Octane and loaded the benchmark ocs. Octane started the render and then died very quickly, only 2 samples per pixel. I went to file menu and selected new, and then reloaded the benchmark. Before clicking on the node I selected the PMC renderer. This time it worked but the render time was much slower then I'm used to (.72 Ms/sec). I was able to pan the camera and the kernel still continued to work. I then changed the renderer to pathtracing and that worked as well, just again at a slower speed then usual (.74 Ms/sec). Next I changed to direct lighting and instantly the kernel died. Every test I did by starting fresh (by using file/new and then reloading the benchmark) and using direct lighting would kill the kernel. The errors were all the same as the others I have already posted. Hope this helps,
Jason
But I'm still having issues. I removed the libGLEW link and Octane started up with out complaints. Yay. Here is how I tested it and the results, maybe they will help determine why my system is having problems. I started Octane and loaded the benchmark ocs. Octane started the render and then died very quickly, only 2 samples per pixel. I went to file menu and selected new, and then reloaded the benchmark. Before clicking on the node I selected the PMC renderer. This time it worked but the render time was much slower then I'm used to (.72 Ms/sec). I was able to pan the camera and the kernel still continued to work. I then changed the renderer to pathtracing and that worked as well, just again at a slower speed then usual (.74 Ms/sec). Next I changed to direct lighting and instantly the kernel died. Every test I did by starting fresh (by using file/new and then reloading the benchmark) and using direct lighting would kill the kernel. The errors were all the same as the others I have already posted. Hope this helps,
Jason
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
A little bit more info. I just tried to load the benchmark, set it to pathtracing and select the node. The kernel died. It looks like the kernel will only work if I select and run PMC first, then pathtracing will work. Direct lighting still fails either way. BTW the interface seems faster on this build then the last few, not as laggy.
Jason
Jason
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
Hmmm, well, I put another card in my system for the display and left my gtx460 to do the rendering and all my problems went away. It certainly looks like the use of graphic effects in the new desktops like Gnome 3, Cinnamon, Unity (not sure about this one), etc. will conflict with Octane. I may be wrong but it appears they don't get along very well.
Jason
Jason
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
Im finding this release almost 2x slower than 2.58 on my setup
PT
3.03 = 0.29 Ms/sec
2.58e = 0.56 Ms/Sec
PT
3.03 = 0.29 Ms/sec
2.58e = 0.56 Ms/Sec
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
Hello, I fear that I have found a bug that was already present in previous versions.
The attached Zip file contains the ocs saved with v1.0 beta3.03.
In the node graph, please disconnect one of the two materials nodes, and try to connect the material node again : it is not possible until you disconnect one of the two purple links going out of the obj node.
I have tested with a geometry node with more inputs, as well as several geometry nodes.
In fact, the problem occurs each time there is more than one link connected in output of the obj node.
The attached Zip file contains the ocs saved with v1.0 beta3.03.
In the node graph, please disconnect one of the two materials nodes, and try to connect the material node again : it is not possible until you disconnect one of the two purple links going out of the obj node.
I have tested with a geometry node with more inputs, as well as several geometry nodes.
In fact, the problem occurs each time there is more than one link connected in output of the obj node.- Attachments
-
- NodeConnectBug.zip
- (166.75 KiB) Downloaded 286 times
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.