OctaneRender for Rhino Beta 1.20.1 [OBSOLETE]

[Vernon]

One observation,

I cannot get LiveDB materials work if they have textures,
other values seems to work all right. Also, if you apply a
material to a object, there is no way to delete it afterwards?


-V-

[face_off]

My only major suggestion is to make a propriety tab for materials,
where you could gather your materials, and edit them,
and then assign them either by object, by layer or by group,
with possibility to drag and drop. I think Maxwell render
plugin for Rhino has it perfected, it is so easy to browse
and assign materials and edit them with that. Rhinos own material tab,
not so great...

You can do this at the moment. Simply assign the relevant Rhino material to by layer, group, etc by drag and dropping, and the matching Octane material will be assigned. This is covered in the manual at http://render.otoy.com/manuals/Rhino/?page_id=85. There are disadvantages in having the separate property tab for materials - the main one being the it would not be possible to support the LiveDb materials.

I cannot get LiveDB materials work if they have textures,
other values seems to work all right.

Textures are working but I think your problem might be that they are being scaled incorrectly (to the point where they are way too big or small) - and the plugin is adjusting the scale according to your scene units - which is probably incorrect behaviour. A texturemap in Octane will go from UV 0,0 to UV 1,1 and in Rhino you might have 2 planes - one is 1mm x 1mm and one is 100m x 100m and Octane will stretch the same texturemap to cover each area separately (as per the image below). So to get both "bricks" texturemaps appearing the same size, the UV mapping needs to be changed (in the case below, set UVW repeat to 0.15 for the small plane in Rhino).

Also, if you apply a material to a object, there is no way to delete it afterwards?

Can you be more specific on this one pls? Are you trying to delete the object or the material? If the later, the Rhino or the Octane material?

Paul

[maxwater]

Hi,

first of all great plugin !

Is there a way to keep the actual viewpoint in render window and work
in the ortho-views like top/front/side to move objects ?

The X-button on octane renderview is not the perfect solution for it.
There should be something like "lock view" which still allows to move
objects around in the different views and see them updating. ( right now
it either doesnt update the objects, when X-button activated or it instantly changes
to the view where i am working in, you have to deactivate the X, click into
a different view, after that click in the view you like to see.... kind of complicated.


greets,
Johannes

[Vernon]

Thanks Paul for your answer,
I got it working now and I think I now understand
the parallel systems in the works, it works pretty
much the same when exporting to standalone.

Still I cannot help thinking,
that it is cumbersome and takes too many steps
and clicks to assign materials from live DB.

It would really help if there would be a separate tab/window,
in where to access the DB, collect and edit the materials while
they are all visible and then drag and drop them to layers tab or
to geometry, without need to have a rhino material to replace.

I know it is early days and I appreciate your work for real,
and I hope you would consider to make using materials as straight forward
as possible, it is so time consuming anyway. Making complex multible mix materials
is a strong point of standalone, here it is very hard if not impossible.

On the other hand, I just love how you guys have done the settings tab and
rendertarget, it is sooo fast and convenient to make and have presets and edit them
while it is all there in one place, brilliant!

Cheers,

Vernon

[face_off]

Is there a way to keep the actual viewpoint in render window and work
in the ortho-views like top/front/side to move objects ?

Not currently - but it is a great idea. I'll add a new button in the Viewport that just locks the current Viewport you are rendering, so only changes to that Rhino Viewport camera propagate to the Octane camera, and you can work freely in the other Viewports. Really good idea. It will be in the next version (available sometime this week).

Paul

[face_off]

Still I cannot help thinking,
that it is cumbersome and takes too many steps
and clicks to assign materials from live DB.

I simply load a LiveDB material once, and then Export it or add it to the Favourites, and also "Save as Default" so that LiveDb material is always then used for that Rhino material. Rhino is an app where the LiveDb materials get used a lot more than with other host apps (like ArchiCAD/Revit), and the download time from the LiveDb is such then saving each material afer downloading will save you a lot of time.

It would really help if there would be a separate tab/window,
in where to access the DB, collect and edit the materials while
they are all visible and then drag and drop them to layers tab or
to geometry, without need to have a rhino material to replace.

Yes, in order to edit the Octane material the corresponding Rhino material needs to be assigned to some geometry. This is a limitation with the Rhino API. I spoke to McNeel about this, but it is not possible to get the currently selected material without recompiling the Rhino rhinocommon dll. So it's theoretically possible, but opens up a lot of potential support issues, so it's not something I've implemented at this point.

The other way to approach this was to edit the Octane material in the Rhino Material window, but that imposed way too many limitations on the Octane materials (no LiveDB, no nodes connected to nodes, etc), and users do not want that.

Paul

[newske]

Is it (or could it be) possible to render static animations (ie. flythroughs with no altering geometry) without voxelising the scene each time? So just move camera, wait for #samples, save frame, repeat. Not sure if this is in and I'm just missing it or it's not currently possible.

Is there any chance of this (http://render.otoy.com/forum/viewtopic. ... 22#p151423) or does Rhino make it overly difficult?

Newske

[face_off]

Sorry - I missed responding to this one...

An actually important question/suggestion:
Is it (or could it be) possible to render static animations (ie. flythroughs with no altering geometry) without voxelising the scene each time? So just move camera, wait for #samples, save frame, repeat. Not sure if this is in and I'm just missing it or it's not currently possible.

By this, I mean the same way that the Standalone does Turntable and Sun Animations (for which Rhino also currently seems to very inefficiently re-voxelise every frame in Rhino).

It is a very necessary feature given that Rhino is popular for industrial design / architecture, where modifying geometry during animations isn't overly necessary in our basic animations, but quick sun-studies and flythroughs are.

Yes, this will be in the version after the next one. There will be an option in the configuration to progress to the next frame without reloading the scene into Octane IF the Viewport is open. This is how it works in the ArchiCAD plugin and it works very well.

Paul

[face_off]

I think the easy workaround for what I was suggesting would just be to make a nested block.

Perhaps. Someone also mentioned there was a Rhino script to save all instances of a block as a CSV transform file, which you could load into a proxy into the plugin. I haven't tried it myself though.

EDIT: Thread is here....http://render.otoy.com/forum/viewtopic.php?f=41&t=23430.

Paul

[jitendra]

Octane has been famous for its Node Graph Tree.

What if the Rhino plugin for Octane have Grasshopper components? It would be a win-win plugin.

Maxwell already has this as available here: http://www.food4rhino.com/project/scarab

Thank you. Keep the good work up, Paul.