
OctaneRender® pre-Beta 2.3 v5 (win/lin/mac) [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.
- Jaberwocky
- Posts: 976
- Joined: Tue Sep 07, 2010 3:03 pm
Please ignore my earlier comment about the max plugin 1.022F causing Octane to crash out.I had the Specify GPU box ticked.I only have 1 GPU in my machine.Once i unticked the box ,Octane opened up OK.Could this however be seen as an error trapping bug ? 

CPU:-AMD 1055T 6 core, Motherboard:-Gigabyte 990FXA-UD3 AM3+, Gigabyte GTX 460-1GB, RAM:-8GB Kingston hyper X Genesis DDR3 1600Mhz D/Ch, Hard Disk:-500GB samsung F3 , OS:-Win7 64bit
- Synthercat
- Posts: 284
- Joined: Mon Aug 30, 2010 11:12 am
- Location: Thessaloniki Greece
I had such an issue since v4. Strange was that after a while even the software I use for pic browsing (faststone) didn't display that gif's thumbnailJaberwocky wrote:Ok I think i've found a bug.I can use JPGS & TIFF maps in the scene ok.However I have just tried a test with a Gif file and it displays it in black and white as you can see from the uploaded images.Replacing the GIF with a JPG and your back to colour again.I think this must constitue a bug.
Linux Mint 19.3 | GTX-1080Ti | AMD FX-8320 (OCed 4.4GHz) | 16GB RAM
- martin.hedin
- Posts: 14
- Joined: Sat Sep 25, 2010 10:22 am
I cant change the resolution for the rendering with this one...
Nothing happens, stays with the initial 1024 x 580 (?)

Nothing happens, stays with the initial 1024 x 580 (?)
Martin
Win 7 x64 & Super Ubuntu 10.04 | ENGTX465 1Gb | i7 870 2,93 Ghz | 8GB | Microstation V8i Select 2
Win 7 x64 & Super Ubuntu 10.04 | ENGTX465 1Gb | i7 870 2,93 Ghz | 8GB | Microstation V8i Select 2
Right I'm testing with the benchmark in pathtracing and I have 2.06 Megasamples compared to the intermediate pre 2.3 v4 running 2.44 Megasamples, is that normal or should I look
into something? (2.69 with 10.22b)
into something? (2.69 with 10.22b)
Win 7 64 | 2 X MSI AERO GtX 1070| Intel I7-6850K| 32 GB DDR4 RAM | Asus X99 II-A
v4 has pathtracing maxdepth default 8, v5 16. Check if this is the cause.justix wrote:Right I'm testing with the benchmark in pathtracing and I have 2.06 Megasamples compared to the intermediate pre 2.3 v4 running 2.44 Megasamples, is that normal or should I look
into something? (2.69 with 10.22b)
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
Hi guys,
THE SPEED DIFFERENCE is due to more intelligent decisions while tracing rays.
This takes a bit more computation so the speed is slower, but the render converges faster (eg less noise/fireflies), which is what counts when using pathtracing for your finals
we raised the maxdepth to 16 as this gives more indirect light, but you can puit it on 2048 too if you like,
it just creates more fireflies, but now you can easily remove them
Radiance
THE SPEED DIFFERENCE is due to more intelligent decisions while tracing rays.
This takes a bit more computation so the speed is slower, but the render converges faster (eg less noise/fireflies), which is what counts when using pathtracing for your finals

we raised the maxdepth to 16 as this gives more indirect light, but you can puit it on 2048 too if you like,
it just creates more fireflies, but now you can easily remove them

Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
Well that makes sense.
Before: More megasamples, but more fireflies = render time of say 10 minutes.
After: Less megasamples, but less fireflies = render time of something faster than 10 minutes, hopefully.
Before: More megasamples, but more fireflies = render time of say 10 minutes.
After: Less megasamples, but less fireflies = render time of something faster than 10 minutes, hopefully.
Core i7 950 @3.07GHz | GTX 460 2GB | 12GB RAM | Window 7 x64
I love it, light efficiency is great, and the new manual is superb, much more complete, with lot's of things that get asked time and again there clearly explained.
The firefly killer works flawless following the instructions. I'm having lot's of fun, I'll post some test later on.
Thanks
The firefly killer works flawless following the instructions. I'm having lot's of fun, I'll post some test later on.
Thanks
windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB
- marchermitte
- Posts: 283
- Joined: Sat May 29, 2010 9:25 pm
- Location: Geneva
- Contact: