OctaneRender for Rhino Beta 1.20.1 [OBSOLETE]

[Vernon]

Hello,

those who are playing with instancing with Geometry and CVS,
I managed to make it work, except the external .obj comes
without materials. There finds a .mtl file in the same folder,
and there was X in the "export material definitions" box.
How must I do the exporting .obj from rhino to make sure the
materials do follow?

Thanks!


-V-

[Refracty]

Is it possible to step into "open file dialog" directly when selecting an image node?

[face_off]

Yes, for two reasons. It's faster (for me at least) to set up texture mapping using the Rhino Rendered Viewport than rendering in Octane. The second and main reason, is that I often send clients screenshots of the Rhino Rendered viewport for pre-rendering approval (this is mainly so they can check they will have the views they, want, graphics are in the correct positions, etc.) -- if the colors and texture maps don't show up, this is not possible to do. My work involves tons of graphics on surfaces and right now, I've got to change the Octane material and the Rhino material to get them to show in the Rhino viewport. Having to change both materials (octane and basic Rhino) seems like an extra step. I'm always working right next to (or over web connection with clients) and being able to see changes to material colors and textures in the Rhino Rendered viewport is very quick and informative. Much faster than during actual rendering. Then the Octane rendered viewport is used for material fine tweaking and lighting.

If this is how you are using it - it's probably worth investigating the "Reconvert Materials Automatically" option (not sure if it's in the version you are running - or the next, available later today).

Paul

[face_off]

those who are playing with instancing with Geometry and CVS,
I managed to make it work, except the external .obj comes
without materials. There finds a .mtl file in the same folder,
and there was X in the "export material definitions" box.
How must I do the exporting .obj from rhino to make sure the
materials do follow?

Just to confirm - the MTL file must be in the same folder as the OBJ file in order for Octane to be able to pick up the material definitions.

Paul

[face_off]

Is it possible to step into "open file dialog" directly when selecting an image node?

Maybe - let me look into it....

Paul

[newske]

For your 1000 tree blocks - how did they get there? If you copy/pasted a block instance, then simply copy/paste the block instance after you assign the tree proxy OBJ to it. If you are generating 1000 block instances automatically (can that process replicate the already assigned proxy block instance?
Paul

Hi Paul,
There seems to be an issue with retaining the proxy properties when copying in instance. See attached images. In this case, I had one block with a proxy assigned which seems to work fine, and then copied it, and the copied blocks don't seem to have a proxy assigned, and (after viewport refresh) do not show up in the viewport. It seems that it doesn't work for nested blocks, either, as it clears the proxy file when nesting.

It would also be nice if the CSV file was also interchangeable with a .txt (since it's much easier to generate) - as this is what happens in Octane Standalone.

It would also be very useful to have a 'apply proxy obj file to selection' rather than necessarily doing it one by one (for things like fauna, and anything on mass really).

Thanks
Newske

One block proxy works fine

Copies of the block don't seem to work

[face_off]

There seems to be an issue with retaining the proxy properties when copying in instance. See attached images. In this case, I had one block with a proxy assigned which seems to work fine, and then copied it, and the copied blocks don't seem to have a proxy assigned, and (after viewport refresh) do not show up in the viewport. It seems that it doesn't work for nested blocks, either, as it clears the proxy file when nesting.

I have reported a bug to McNeel where Rhino is not copying the instances attached info (ie. proxy data) when you use the Rhino "copy" command, but it is working if you do a copy/paste. I have not heard back yet from them on this.

It would also be nice if the CSV file was also interchangeable with a .txt (since it's much easier to generate) - as this is what happens in Octane Standalone.

I will add this to the todo list.

It would also be very useful to have a 'apply proxy obj file to selection' rather than necessarily doing it one by one (for things like fauna, and anything on mass really).

I agree - you can select multiple scene elements to assign the Live Geometry status, so a similar thing can probably be done for assigning proxies. I will look into it.

Paul

[Bendbox]

quote]
If this is how you are using it - it's probably worth investigating the "Reconvert Materials Automatically" option (not sure if it's in the version you are running - or the next, available later today).

Paul

Hi Paul,

Thanks for the reply -- I'm honestly open to using this however it was intended, It's just different than other plugin's so I'm trying to understand it. Is your opinion and intention that the "rendered viewport" in Rhino should be not used, and for us to use the Octane Render window only instead? Just wondering what workflow you reccomend?

Also, correct me if I'm wrong, but is the intended process, to create a Rhino Material, name it, assign it to geometry, and then tweak the Octane material settings from that point forward?

Thanks for the help!

Ryan

[Bendbox]

I just noticed that when copying geometry from one file to another that the Octane material settings do not transfer over. So, in file "A", I have an aluminum can, and then I copy it. I then open a new file, file, "B" and past the aluminum can into file B. The Octane material settings to not read in. Can it be made so this will work?

Thanks,
Ryan

[face_off]

I just noticed that when copying geometry from one file to another that the Octane material settings do not transfer over. So, in file "A", I have an aluminum can, and then I copy it. I then open a new file, file, "B" and past the aluminum can into file B. The Octane material settings to not read in. Can it be made so this will work?

Hi Ryan - in file A, select the aluminium can and in the plugin Materials tab, right click the can material and "Save as Default". Then whenever that Rhino material name is used (in file B for example), the Octane material you saved will be applied. This is covered in the manual http://render.otoy.com/manuals/Rhino/?page_id=35.

Paul