OctaneRender™ Standalone v1.0 RC 1 [obsolete]

[MOSFET]

@abstrax: Regarding a new file format, have you taken a look at Alembic?

http://code.google.com/p/alembic/

Also, would it be possible to add support for OpenSubDiv surfaces at some point? The big three packages (Maya, Max & Soft in addition to Mudbox) will ship with OpenSubDiv integrated in the future.

https://github.com/PixarAnimationStudios/OpenSubdiv

Demonstration video:

http://www.youtube.com/watch?v=Y-3L9BOTEtw

/edit: Video demonstrates realtime displacement on a GPU of a OpenSubDiv surface using a PTEX file as the displacement map.

[gabrielefx]

• Added caustic blur parameter to the kernel settings to approximate caustics on rough surfaces.

That is how it works.
It can significantly reduce caustic noise in case caustic details are not very important.
Here is PT with 1000 samples.

can't wait to use it with Max

[bepeg4d]

hi, first of all a big thanks for the rc version, the caustic blur effect seems really promising for speed up pt animation rendering
it seems like almost all the promised features are already here
about the mac version, the performance are very similar to the win version, ungortunately it's more unstable, expecially with pt and pmc (crash report attached).
the comma- point in the numpad doesn't work in this version also.
p.s. what about an histogram graph in the image node for a fast verification of the exposition?
ciao beppe

[pixelrush]

A quick look through the pdf manual leads to the following observations -
p11 mac install cuda toolkit not needed for latest version.
p13 same for linux
p8, 20 and 25 mentions this too.
p12 mentions older obsolete beta versions.
p14 refers to GTX295 which is a little dated, add 590 and 690.
p14 graphic of pc case (to right) is a bit truncated at the top, doesnt really look like one.
p14 should probably mention backward compatibility of pci-e 3.0 slots (this might be better to go on p33 though). Should also mention potential driver issues with Quadro and Geforce together.
p15 mentions matching gpu models but this isnt so necessary now the code has been changed, but min common ram size is worth a mention. Note cuda as being backward compatible.
p23 refers to demo suite 2.46 needs updating..
p49 refers to scripts for *only* 2.4x
p48 there is a rhino script as well I think. Should also mention the availability of the dedicated Octane versions.
p56 blender screen shot from 2.49, blender 2.6xx is where its at these days.
p116 refers to 2.58d which is probably not relevant to v1.0 final manual.
p120 seems to be out of place here. Probably should come in the earlier hardware section.
p134 refers to beta versions.
p143 not really relevant to standalone. Might mention it in passing as advertising in regard of dedicated Octane.
Manual generally needs more discussion/fleshed out, of appropriate sys ram, vram, sizes and number of cores and referring to Fermi/Kepler differences. Might mention case of paging to disk. General recommendations for the type of work you do might be useful eg. archviz rig. Possibly add this stuff to p24.
No mention of texture number allocations/limitations for Kepler and previous generations.

more stuff when I do some more looking and thinking

[abstrax]

hi, on this version pmc works not correctly at my gtx280 card, render speed very high, but the picture doesn't appear. camera settings don't work. cuda driver 5.0.1, because of it?
at gtx680 works fine.

I had a look and the problem is that Octane picks the wrong CUDA code for GPUs with compute model 1.1, 1.2 and 1.3. We will fix it on Tuesday and update the archives in this thread.

Thanks again for the heads up and apologies for the bug...
Marcus

[manalokos]

There is a bug in the Saturation combined with Camera Response.

Try this:

Open any test scene, render in PMC or Pathtracing
Change the camera response to Kodachrome 64CD,
Set the saturation slider to 0
Change the camera response to another film.

You will see that the desaturated image now has a brownish tint that will affect the render permanently even when setting the saturation back to 1...

Can you replicate this issue?

Best regards
Filipe

[abstrax]

@abstrax: Regarding a new file format, have you taken a look at Alembic?

http://code.google.com/p/alembic/

No, I haven't seen it yet (I'm living under some rock in NZ...), but on the first glance it looks excellent. I tried it in C4D and the geometry part would probably be cover all our needs for geometry export. I would have to dive a bit deeper into it but it seems that materials are only exported as placeholders, which isn't necessarily a deal-breaker, but may be a problem. We will see.

What I like is it's speed, compactness (binary unlike COLLADA) and openness (unlike FBX). Thanks for the heads up.

Cheers,
Marcus

[abstrax]

A quick look through the pdf manual leads to the following observations -
p11 mac install cuda toolkit not needed for latest version.
p13 same for linux
p8, 20 and 25 mentions this too.
p12 mentions older obsolete beta versions.
p14 refers to GTX295 which is a little dated, add 590 and 690.
p14 graphic of pc case (to right) is a bit truncated at the top, doesnt really look like one.
p14 should probably mention backward compatibility of pci-e 3.0 slots (this might be better to go on p33 though). Should also mention potential driver issues with Quadro and Geforce together.
p15 mentions matching gpu models but this isnt so necessary now the code has been changed, but min common ram size is worth a mention. Note cuda as being backward compatible.
p23 refers to demo suite 2.46 needs updating..
p49 refers to scripts for *only* 2.4x
p48 there is a rhino script as well I think. Should also mention the availability of the dedicated Octane versions.
p56 blender screen shot from 2.49, blender 2.6xx is where its at these days.
p116 refers to 2.58d which is probably not relevant to v1.0 final manual.
p120 seems to be out of place here. Probably should come in the earlier hardware section.
p134 refers to beta versions.
p143 not really relevant to standalone. Might mention it in passing as advertising in regard of dedicated Octane.
Manual generally needs more discussion/fleshed out, of appropriate sys ram, vram, sizes and number of cores and referring to Fermi/Kepler differences. Might mention case of paging to disk. General recommendations for the type of work you do might be useful eg. archviz rig. Possibly add this stuff to p24.
No mention of texture number allocations/limitations for Kepler and previous generations.

more stuff when I do some more looking and thinking

Wow, thanks for your feedback - very much appreciated.

Marcus

[Elvissuperstar007]

@abstrax: Regarding a new file format, have you taken a look at Alembic?

http://code.google.com/p/alembic/

No, I haven't seen it yet (I'm living under some rock in NZ...), but on the first glance it looks excellent. I tried it in C4D and the geometry part would probably be cover all our needs for geometry export. I would have to dive a bit deeper into it but it seems that materials are only exported as placeholders, which isn't necessarily a deal-breaker, but may be a problem. We will see.

What I like is it's speed, compactness (binary unlike COLLADA) and openness (unlike FBX). Thanks for the heads up.

Cheers,
Marcus

++++1111111 yes new exporter needed! Alembic cool

[matej]

Regarding the file format; whatever you guys decide, it will be ok, just please stay away from closed proprietary formats like FBX.