OctaneRender™ Standalone 1.50

[face_off]

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

I'm no expert in this, but I haven't had any issues reported from people using 334 or 335 - so go with one of those.

Paul

[abstrax]

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

I guess, why everything is grey is because none of the image textures are loaded. Although a lot of things changed internally since 1.20, the MTL import should still work like before. Could you post the OBJ, MTL and image files or send them to me via PM, so we can have a look? Thank you.

[Seekerfinder]

Hi Marcus,
Thanks for the reply. The textures are there... Again, if nothing changed, why the difference? It's a copyrighted OBJ and so I can't send it out. Perhaps I could chop it up a bit but like I say, it seems as though all textures are there (even the one it asked for was in the folder).

OCTANE RENDER 1.5 - textures are there.jpg

Could it be a driver issue? I got no reply from Otoy yet on my previous driver query.

Hope you can help...

Seeker

[abstrax]

Hi Marcus,
Thanks for the reply. The textures are there... Again, if nothing changed, why the difference?

I didn't say nothing changed, but it should still work the same. In fact, we had to touch about 80-90% of the code base due to the node system refactoring. So maybe something got broken here. I did a quick test with C4D exporter and in general it seems to work.

It's a copyrighted OBJ and so I can't send it out. Perhaps I could chop it up a bit but like I say, it seems as though all textures are there (even the one it asked for was in the folder).

OCTANE RENDER 1.5 - textures are there.jpg

It doesn't have to be this scene, any scene (the simpler the better) that shows the problem and which does work in 1.20 is fine. Without a scene it's really hard to say anything.

Could it be a driver issue? I got no reply from Otoy yet on my previous driver query.

Hope you can help...

Seeker

No, it's not a driver issue. Definitely either something dodgy with the MTL file or a bug in the OBJ/MTL import.

[Seekerfinder]

No, it's not a driver issue. Definitely either something dodgy with the MTL file or a bug in the OBJ/MTL import.

Marcus,
It seems to be a [edit: INDEX] FLOAT VALUE issue in 1.5. Default float value in 1.2 was a value of 1.3. In 1.5 the float value default is 3.

Incidentally, a float value of 1.000 returns a zero image. 1.001 brings the image back. Is that intended behaviour?

OCTANE RENDER 1.5 - FLOAT VALUE ISSUE.jpg

Seeker

[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

I'm no expert in this, but I haven't had any issues reported from people using 334 or 335 - so go with one of those.

Paul

Thanks Paul!
So I should upgrade then. This is one I really thought the Octane core team would have responded to...

Best,
Seeker

[abstrax]

No, it's not a driver issue. Definitely either something dodgy with the MTL file or a bug in the OBJ/MTL import.

Marcus,
It seems to be a [edit: BUMP INDEX] FLOAT VALUE issue in 1.5. Default float value in 1.2 was a value of 1.3. In 1.5 the float value default is 3.

Incidentally, a float value of 1.000 returns a zero image. 1.001 brings the image back. Is that intended behaviour?

OCTANE RENDER 1.5 - FLOAT VALUE ISSUE.jpg

Seeker

Yes, an index of refraction of <= 1.000 disables the fresnel effect, i.e. the amount of reflection is solely controlled by the specular channel. But this behaviour was introduced before 1.00, so it's nothing new.

-> I still would like to find out what exactly is causing the difference in the import. Could you post the MTL file that you used and maybe a screenshot of the trunk material node in 1.20 and 1.50? Thanks.

[SimonJM]

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 !

Very much a +1 for the naming to follow frame numbers!

[dionysiusmarquis]

Ah, superb. I'll take a look.

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

You should get the right color Informations from your Shadow Catcher diffuse color for refractions as well.

[FrankPooleFloating]

Yo - Thanks for 1.5 Octane Team!

Marcus/Roeland, now that you mad scientists are going to be in your evil lair, making the next batch of diabolical weapons, I am very curious how things will work in regard to future release candidates and 2.0 - which presumably we will be paying for an upgrade... I mean, those of us that like to be on the bleeding edge with RCs will get to test new features as you add them, right?.. but will need to pay after 2.0 is released? Please do tell... unless you haven't thought that far ahead...