Hi octane team, may the treaded voxelizing to fall into oblivion because working on other features.
It would be a huge improvement for rendering stills an animations to speed up octane.
Cheers, mib.
Feature Request: Multitreaded Voxelizing
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
- mib2berlin
- Posts: 1194
- Joined: Wed Jan 27, 2010 7:18 pm
- Location: Germany
Opensuse Leap 42.3/64 i5-3570K 16 GB
GTX 760 4 GB Driver: 430.31
Octane 3.08 Blender Octane
GTX 760 4 GB Driver: 430.31
Octane 3.08 Blender Octane
It also eats memory. I have maxed out my 16 quite often recently which results in Octane just falling over.
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
I thought it was !
+1 obviously !
+1 obviously !
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.
not sure if voxelizing is done in the builtin octane plugin for 3dmax or others on a single core also - it doesnt eveb show the time it takes to voxelize - but its a lot quicker, seems like at least 50-70% speed up, and a smoother workflow really brings it to another level - so if nothing else that's the solution to wait out
- it is a waste of resources with no multithreading in any case, I thought they knew better than that, hope it does not require a complete rewrite of octane code - which they already done a few times..
so if you have a 4xHT CPU, you end up with 8 virtual cores, and then you use a single virtual core to do the processing - that has the 1/2 power of a single core - ends up a 12.5% CPU usage doing it on a single core, (and I wanted to upgrade to 6 cores in some time - not worth it still)
- did anyone test if the speed goes up if you disable hyperthreading in BIOS?
..also check out this Arion has voxelization disk cache - reuses same info on camera animations - thats a good trick
- it is a waste of resources with no multithreading in any case, I thought they knew better than that, hope it does not require a complete rewrite of octane code - which they already done a few times..
so if you have a 4xHT CPU, you end up with 8 virtual cores, and then you use a single virtual core to do the processing - that has the 1/2 power of a single core - ends up a 12.5% CPU usage doing it on a single core, (and I wanted to upgrade to 6 cores in some time - not worth it still)
- did anyone test if the speed goes up if you disable hyperthreading in BIOS?
..also check out this Arion has voxelization disk cache - reuses same info on camera animations - thats a good trick
3dmax, zbrush, UE
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
+1 to multi threaded voxelizing, 6 cores ready to do something.
Maya 2013 / W7 64bit / Intel i7 980 / 24GB / Gigabyte gtx 580 3GB + 2*EVGA gtx 680 4gb / MB Gigabyte X58A-UD3R / NZXT Phantom - white/black case
Maya 2013/W7 64bit/Intel i7 3820/16GB/ MB Gigabyte GA-X79-UD3 /4*EVGA gtx 680 4gb/SSD 6Gb.s /CM HAF X case
Maya 2013/W7 64bit/Intel i7 3820/16GB/ MB Gigabyte GA-X79-UD3 /4*EVGA gtx 680 4gb/SSD 6Gb.s /CM HAF X case