Octane Render 1.022 beta2.2 RC1 available [obsolete]

[kubo]

definitly bumps are not working on my side either, I can only add float 1-3 and daylight float to the bump, normal or opacity channels as default.
If I do create a new material node, then add a texture node and attach it to the material, I can use a texture in that material and any other in the scene without attaching it, they suddenly show again, but it doesn't matter cause they wont work, no matter what texture I use I get no bump, same goes for old scenes with bumps working in 1.21.
Also If I minimize, say, the diffuse channel, then play with the bump one, the material expands again and opens all channels.
Besides that, it seems to give the same speed on 1.21 scenes but of course no bump atm.
Testing with 1.22 RC1 windows x64 on the machine in my sig

[kubo]

'm off to bed guys, worked 14 hours on this today.
need to sleep some times...

Hehehe, yeap, same here, I had a project due today (yesterday... whatever day today is) 18 hr up after a 3 hour sleep the day before (let's call it nap), but luckly for me, after getting in my project, and a larger nap this time, I woke with the nice surprise of having a new toy to play with. So totally worth it
So thanks a lot guys, I can't say it enough times, you do a great job, and thanks for the effort, time and support you give us.
Have a good night sleep!

[SamPage]

I am noticing a speed loss when using two cards. On the Octane_benchmark with one GTX 285, I am getting 1.6-1.7 megasamples/sec, with two GTX 285s, I am getting 0.80 - 1.25.

Rhino Materials are not imported.

Are you by chance exporting out of Rhino v5 beta on an older Rhino file? I am finding that materials will work coming from Rhino, but with the v5 beta they have changed a lot of things with the material editor, so if you are working with an older file, all the materials look good in Rhino, but if you actually try and edit that material in Rhino, the material doesn't exist. After going back and recreating all my materials in the Rhino 5 material editor, they come into Octane OK. If you notice some of your texture maps not working, you may want to resize them to a power of two (both width and height, 512x512 etc, Rhino will do this behind the scenes anyway so you shouldn't notice any stretching). I had a few that were refusing to come in and this cleared it up (although I am having trouble reproducing the texture maps not coming in now that I have redone my materials in Rhino).

[cgbeige]

I'm getting those weird vertical waves but they disappear eventually. Right click for panning still doesn't work on the Mac version.

[efioramonti]

I'm on Linux (Ubuntu 9.10) and have several issues. Whem importing .obj files or .ocx some or all textures are black and stay black. Or some strange checkboard artifacts (see picture) I tried other files too. There's always one or several black materials. Can't test further since basic functionality is missing. I have a GeForce GTX 260 which works ok under 1.021 b21.

[efioramonti]

forgot to mention that I use to export .obj through blender, and pathtracing fixes the checkerboard thing but smoothing turns it black. Materials stay black whatever I do....

[acc24ex]

so far on the benchmark scene i get 3.8 Msamples/s with 2 GPU setup 480gtx and 260gtx
on a single 480gtx 3.5 Msamples/s
wel it's doing something faster, I feel like I need a 2nd 480gtx now , good thing they're expensive, and what if a 6GB version of 480s start to became available

[kubo]

ok, further testing.
I got this scene (it's in the wip gallery) and I changed totally the mesh, add some things, etc.
If I opened it in 1.22 and then reloaded the obj file, at first it went fine about (plain mesh in the 340mb range), but as I reattached the material nodes memory useage went sky high till it finally collapsed and crashed big time with lots of errors about not having enough ram.
Same scenario, now in 1.21, it all went well, and memory usage stayed well in the 380Mb range with all the materials.
So when I had all working on 1.21 I went back to 1.22, I loaded the scene, it stayed in the 380 range, fine, no prob, but if I tried to touch anything, boom, memory went up again and it crashed.
Also funny thing, the materials that had bump applied on the 1.21 worked fine in the 1.22, but if I did a new material and added bump it wouldn't show.

[evo]

Hi everyone, this is my first post, I'm alan from rome italy.
anyway for first i like to say sorry for my bad english and thanks to randiance and his team!! i really like octane and your job.

here some test i've made with rc1
first problem i've got was this. a sunlight error. just changing day value in daylight parameters and it disappears. came back in that position and appear again.
pathtracing and even directlighting.



second one is memory problem i got 2 gtx 260. to active both i've got to disable sli option in nvidia control pannel. (is it normal?). then i just import a mesh used also with beta 2.1
memory goes up every time i apply a glossy mat. and in a couple of settings memory was satureted!! (thats a very bad english i think)



any way this is the same scene with a couple o material more.



so i've try to open the scene done with beta2.1, with the rc1. and memory was the same with the 2.1!! (about 245 mb)
so maybe could be a memorymanager problem with material...

hope to have been helpful, and thanks again for the wonderful work done so far.

Alan

[DavidT]

definitly bumps are not working on my side either, I can only add float 1-3 and daylight float to the bump, normal or opacity channels as default.

The same for me. Specular is only allowing float values also, no option to load an image for specular. If I load an ocs saved from 1.021, the image option is there for materials that already have an image assigned to them for specular.