I tried this simple test
Did a 300530tris scene in 512samples and it took :
156sec
239sec (Instacsing X2)
Did the same scene X2 but in editing to be EXACT like the instancing scene (601060tris instead of 300530 X 2meshes)
223 sec!!! (6.7% improvment)
-----------
Wasn't the "Placement + geometrygroup" method suppoed to be faster to render? If not then why use it?
Why not control the duplicate obj from WHITHIN the editor to have better control?
Instacing prob?
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.
-
Synthercat
- Posts: 284
- Joined: Mon Aug 30, 2010 11:12 am
- Location: Thessaloniki Greece
Linux Mint 19.3 | GTX-1080Ti | AMD FX-8320 (OCed 4.4GHz) | 16GB RAM
No, it's not supposed to be faster. As you find out it's the other way around.Synthercat wrote: Wasn't the "Placement + geometrygroup" method suppoed to be faster to render? If not then why use it?
Instancing is there just to save VRAM for massive scenes, with lots of duplicating objects. Don't use it, if you don't really need it.
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net