OctaneRender™ Standalone 1.50

[stratified]

There's no pdf manual anymore, it's online here: http://render.otoy.com/manuals/Standalone_1_5/.

cheers,
Thomas

[Synthercat]

Thank you stratified. I prefer to have it offline but since it's got that search feature I will get used to it fast Bookmared!

[ROUBAL]

There is a problem with numeration of frames rendered with the Script animation feature :
When rendering an animation, the files are named File_0001.png, File_0002.png...
If everything works well, it is fine. But I encountered a script error in my last animation of 1000 frames, and the animation stopped after 48 frames.
So, when I noticed it I started a new animation render from frame 49 to the end (frame 1000)... But I discovered too late that this new render named the new images
File_0001.png, File_0002.png... instead of File_0049.png, File_0050.png ! So, the already rendered images have been overwritten and I lost much time.

So, I think that there is something to fix in the script to avoid this trouble.

Thanks in advance !

[roeland]

I see. We can add a check to skip frames if the image already exists.

Do you remember which error you got?

--
Roeland

[ROUBAL]

I see. We can add a check to skip frames if the image already exists.

I think that making the script actually respect the input values would be more useful and flexible. I mean : if I chose Start at 49, end at 150, I want the script to actually write image_0049.png to image_0150.png even if there are images with same name. I can really need to re-render some already existing images if I notice some errors on them. I want the bad images to be overwritten, without loosing time to remove these images by hand in the output folder. What I don't want is the script writing numbers different than the frame numbers in the animation.

Do you remember which error you got?

No, Octane was frozen, I clicked the little "Kill" button in the low left corner. I didn't understood the message about the script error and as I was very busy having to relaunch my animation, I closed the pop up window by reflex. Sorry !

[gordonrobb]

So this may have been reported already, but it's my first real go at reporting a bug, there are two problems with the Matte object when used for shadow catcher.

Firstly, it reflects like it's normal material and secondly, when viewed through a spec material, it shows as a normal material.

It's the same in the LW plugin.

[dionysiusmarquis]

So this may have been reported already, but it's my first real go at reporting a bug, there are two problems with the Matte object when used for shadow catcher.

Firstly, it reflects like it's normal material and secondly, when viewed through a spec material, it shows as a normal material.

It's the same in the LW plugin.

try this:
http://render.otoy.com/forum/viewtopic.php?f=9&t=38911

[gordonrobb]

Ah, superb. I'll take a look.

That will solve the reflection problem, but presumably not the 'through the specular material' problem.

[Seekerfinder]

Guys,

Which is the best Nvidia driver for 1.5? Face-Off suggested 227 a while ago when I was using 332 and had some problems with the Revit plugin. 332 Apparently caused some issues with then release candidate 1.27.

Your 1.5 help file suggests merely an "Nvidia driver supporting CUDA 5.5" (http://render.otoy.com/manuals/Standalo ... page_id=26)

Are there no stability issues any longer with the latest Nvidia driver releases?

Cheers,
Seeker

ANYONE...? PLEASE.

[Seekerfinder]

1.5 WASHED OUT RENDERS...& MTL link?

Hi guys,
ISSUE 1
My first observation with 1.5 vs 1.2 is a washed out render appearance... All settings are the same to my knowledge. In both bases I simply opened Octane, imported geometry mesh, tweaked camera, ensured daylight settings the same and rendered... 1.5 is visibly (and quite unacceptably) more washed out.

What am I missing?

OCTANE RENDER 1.2.jpg

OCTANE RENDER 1.5.jpg

ISSUE 2
Though I imported the exact same OBJ, R1.5 seemed not to be able to find one .png image file, while 1.2 has no such hangups. Why?

Seeker