As usual: When we are ready and as soon as possible. Maybe tomorrow, maybe beginning of next week. Should be only days, not weeks or months.Refracty wrote:1.1.1 will be fun
Any ideas when the new good stuff will be released as a beta,Marcus?
OctaneRender™ Standalone 1.10
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Also nach Karneval
Kölle Alaaf.
Sounds great

Sounds great
Just downloaded the 1.1 version and fired up my previous project to see how it performs. To my surprise I see 40% speed drop, but even bigger issue is the look change. The whole glass tile wall is now a busy mess. I clocked 2 minute renders to illustrate the issue. The whole scene is illuminated with a single 4000x2000px HDR image. I tried to enable and disable importance samping from the environment and smoothing from the glass material. Disabling importance samping gives back most of the performance, but neither fixes the look. Seems to affect all kernels. Stats for the images below.
Octane Render 1.0 RC 3
198 s/px , 3.38 Ms/sec, 00:02:01
27 Textures, 2096553 Tris, 5 Meshes, 2 GPUs, 785.8/983/2560 MB
Octane Render 1.1
120 s/px , 2.06 Ms/sec, 00:02:01
27 Textures, 2096553 Tris, 5 Meshes, 2 GPUs, 816.2/905/2560 MB
Rendered with two 570GTX cards and Nvidia driver version 310.70.
Edit: Just noting that Houdini's Mantra also produces the smoother look of the tiles with that mesh and environment map.
Octane Render 1.0 RC 3
198 s/px , 3.38 Ms/sec, 00:02:01
27 Textures, 2096553 Tris, 5 Meshes, 2 GPUs, 785.8/983/2560 MB
Octane Render 1.1
120 s/px , 2.06 Ms/sec, 00:02:01
27 Textures, 2096553 Tris, 5 Meshes, 2 GPUs, 816.2/905/2560 MB
Rendered with two 570GTX cards and Nvidia driver version 310.70.
Edit: Just noting that Houdini's Mantra also produces the smoother look of the tiles with that mesh and environment map.
You do not have the required permissions to view the files attached to this post.
CPU: i5-2400 | RAM: 8GB | GPU: 2x GTX 570 (2560MB) | Drivers: 310.70 | OS: Win7 Pro 64bit SP1
Found the problem. Obj mesh exported from Houdini lacks normal (vn) definitions. Re-saving the file from Modo adds the normals (and rounds other values a bit) and the mesh behaves as expected in Octane 1.1. Version 1.0 and prior seem to work fine without normal definitions. I guess I have to rethink my workflow a bit if this is permanent change. I can upload example files a bit later if needed.
Edit: Here you go. https://dl.dropbox.com/u/76294644/forum ... e_test.zip
Edit: Here you go. https://dl.dropbox.com/u/76294644/forum ... e_test.zip
CPU: i5-2400 | RAM: 8GB | GPU: 2x GTX 570 (2560MB) | Drivers: 310.70 | OS: Win7 Pro 64bit SP1
This is a problem with the new OBJ parser, it's not calculating shading normals for certain OBJ files. It will be fixed in a later release.
Check if Houdini can export vertex normals or smoothing groups. If it can export smoothing groups you can do so and enable using smooth groups in the OBJ import settings (You can add everything to one smoothing group). If this isn't possible, enable using smoothing groups in Octane, and at the top of the OBJ file insert a line "s 1" (open it with notepad). In any case if Octane has to calculate vertex normals, set the maximum smoothing angle to 89, so it doesn't smooth straight angles.
--
Roeland
Check if Houdini can export vertex normals or smoothing groups. If it can export smoothing groups you can do so and enable using smooth groups in the OBJ import settings (You can add everything to one smoothing group). If this isn't possible, enable using smoothing groups in Octane, and at the top of the OBJ file insert a line "s 1" (open it with notepad). In any case if Octane has to calculate vertex normals, set the maximum smoothing angle to 89, so it doesn't smooth straight angles.
--
Roeland
I use RAM Drive (4Gb space is enough in most cases) for OBJ file and textures placement... so there is no more I/O bottleneckpixelrush wrote:Well then after that there's SSD....~275mb/s for SATA2 and ~550 mb/s for SATA3 effectively.


AMD R7-2700/64Gb/RTX2080Ti 11Gb + RTX2080 8Gb/Win10 Pro x64/nV driver 451.67/Poser10, DS4.12, Blender2.79, Octane 4.05 Standalone
> Using RAM Disk with Octane <
> Using RAM Disk with Octane <
- mauricesteenbergen
- Posts: 31
- Joined: Tue Dec 04, 2012 9:37 am
andw wrote: I use RAM Drive (4Gb space is enough in most cases) for OBJ file and textures placement... so there is no more I/O bottleneckTypical transfer rate is about 6..7 Gb/s... and without any wearing out
Wow, thanks for the tip on this RAM disk thing.
I found one here that's free up onto 4GB: http://memory.dataram.com/products-and- ... e/ramdisk/
which I found more than enough for my scenes. Everything is much faster now!
Render: Geforce GTX480 (EVGA) (1.5GB) | OC @ 1.0V / 750Mhz
Display: Geforce 8800GT (NVIDIA) (512MB)
OS: Win 7 x64 | CPU: Quad Intel Xeon 2.66GHz (12GB)
Display: Geforce 8800GT (NVIDIA) (512MB)
OS: Win 7 x64 | CPU: Quad Intel Xeon 2.66GHz (12GB)
mauricesteenbergen wrote:andw wrote: I use RAM Drive (4Gb space is enough in most cases) for OBJ file and textures placement... so there is no more I/O bottleneckTypical transfer rate is about 6..7 Gb/s... and without any wearing out
Wow, thanks for the tip on this RAM disk thing.
I found one here that's free up onto 4GB: http://memory.dataram.com/products-and- ... e/ramdisk/
which I found more than enough for my scenes. Everything is much faster now!
Wait, how does this work? It speeds up import time? If this is true, i need to try it to speed up my animations. import/export is 30 sec a frame right now...
Intel quad core i5 @ 4.0 ghz | 8 gigs of Ram | Geforce GTX 470 - 1.25 gigs of Ram
- mauricesteenbergen
- Posts: 31
- Joined: Tue Dec 04, 2012 9:37 am
I created a RAM disk, and I've put the Octane executable, the project file and the assets (textures, objects) in there. Feels like the software is responding faster now too while navigating a scene.kavorka wrote:
Wait, how does this work? It speeds up import time? If this is true, i need to try it to speed up my animations. import/export is 30 sec a frame right now...
I've setup the C4D export script to read the Octane Executable from RAM disk, and to write the objects there too. Finished renders are written elsewhere. Really worth a try.
EDIT: Tutorial is here: http://blog.laptopmag.com/faster-than-a ... a-ram-disk
Render: Geforce GTX480 (EVGA) (1.5GB) | OC @ 1.0V / 750Mhz
Display: Geforce 8800GT (NVIDIA) (512MB)
OS: Win 7 x64 | CPU: Quad Intel Xeon 2.66GHz (12GB)
Display: Geforce 8800GT (NVIDIA) (512MB)
OS: Win 7 x64 | CPU: Quad Intel Xeon 2.66GHz (12GB)