OctaneRender for Rhino 1.20.1 [OBSOLETE] (RhinoSR7 31213)

[face_off]

Hi Nathan - I will include this in the next release, which I'll do once some more people have provided feedback on the new material integration in this release.

Paul

[nardo]

http://render.otoy.com/forum/viewtopic.php?f=30&t=36774

Hi Paul,
Can this function be integrated with rhino?
Thank you.

[face_off]

Can this function be integrated with rhino?

The new material integration in this release makes this sort of functionality possible. One way this could be implemented would be to have all the LiveDb materials as rmtl (Rhino material) files, so from the Material panel you would "Import Material from File", and then select the appropriate LiveDb material (the materials would be in subdirectories as per their categories). You could then drag that material from the material panel onto the relevant geometry. There are some complications (like you wouldn't be able to move the texturemaps to a different folder, because the LiveDb material would have a reference to the texture in it's original folder).

The other way to implement this would be with a separate screen (as the C4D plugin does). This may not allow the drag-dropping of materials onto geometry though.

I would be interested to hear other users thoughts on this.

Paul

[Ndawg]

Hi Nathan - I will include this in the next release, which I'll do once some more people have provided feedback on the new material integration in this release.

Paul

Excellent! Thank you, Paul!

Best,
Nathan

[face_off]

Quick note to say, pls avoid installing Nvidia driver version 331.65. Otoy have reported that there are issues with this release for some installations. 327.23 is the preferred driver release.

Paul

[Bendbox]

Hi Paul,

So far, so good with all the test scenes I've done with the latest version. Love the material integration, so nice! And, the Rhino displacement working in Octane is just in time for a project I'm starting too. Great work on this version Paul!

I do have a couple of comments.

1) Regarding Ndawg's comments on the image map being used in the Rhino viewport. I think, if possible, it would be very useful if there was a drop down menu showing a list of each image map used within each material if multiple image maps were used in a single material. For example, if you had an image map in both the diffuse slot and the bump slot, it would be very nice if there was a drop down menu within that material allowing the user to pick which image map to show within the Rhino viewport. The plugin for Thea Render does this, and it's very handy. On a mixed material with a birch wood, and a scratchs map, you could chose whether you wanted the Rhino viewport to show the birch or the scratch map. If this is possible to do and others want this as well, I do think it would be important to make Octane use the default of showing the diffuse image map in the Rhino viewport however, just so the user does not have to manually pick each time, but only when they want to change what's showing in the viewport.

2) Also, I was wondering if there is any Rhino command line entries to tell Rhino to pull up the Octane Render Window, and also to Save that image to disk from that window? I'm working on a Batch Render script and I can only tell it to pull up the Rhino Render Window. I know that Octane will render in the Rhino render window just fine, but there seams to be an issue with using the background Alpha Channel and the Rhino render window -- the Rhino render window shows very pixelated edges around objects when the Alpha Channel is being used. If this wasn't an issue I wouldn't have any need to be able to pull up the Octane Render window via the command line, the batch would run fine on just the Rhino window. But, the image the batch will save is from the Rhino Render Window on the Right, and obviously, looks bad.

[face_off]

Hi Bendbox.

1) The Rhino viewport will support displaying a different diffuse map to the bump map (should do so already). I code it so that if there are 2 diffuse maps (in an Octane mix) - it will always display the first in the Rhino viewport (then you could set their order to pick which to display in the Rhino viewport). OR I can add a dropdown box which lists all the texturemaps (diffuse, bump, trans, etc) using by that Octane material and allows you to select which one is displayed in the Rhino Viewport as the diffuse map. In this case, it may be difficult to save this setting to the rhino file - would that be a problem?

2) You should be able to use the Rhino renderer in your script. The "quality" issue you are seeing is due to the way the Rhino render panel is presenting the alpha background of the image - and I think when this file is saved as png, the image will then match the quality of the Octane Viewport. If this is NOT the case, then there is an issue I need to fix. IMO it is better for people to use the Rhino render panel to script their rendering, because that is compatible with all the other rhino rendering tools (like animation, etc). If needed, yes I can add new commands, but I would rather fix to root cause of the issue.

Hope that helps.

Paul

[Bendbox]

Hi Paul,

1) Not being able to save that setting wouldn't be a probelm at all as long as the primary diffuse slot was the default, which I think would be used most of the time by most people. Having a drop down menu helps when you are using multiple mapping chanels, or need to go back into photoshop and revise a different map within a material. Being able to see these maps within the viewport saves time since you don't have to wait on a rendering. I think this would be a very useful feature.

2) Changing the batch to save as PNG solved the problem! Saved images look exactly like the Octane viewport now. Thank you!

Thanks Paul.

[Bendbox]

Hi Paul,

I did find a couple of issues this morning that are strange.

1) The first is that when making ANY change to a material, any texture mapping in the viewport darkens to any assigned objects. This includes just changing the name of the material. Please see the image below. The first image shows the viewport immediately after the material was created an assigned. The second shows what the viewport looks like after the name of the material was changed. I also replicated this across multiple types of material setting changes. Changing the glossy levels, reflection levels, etc, does this "darkening" effect as well.



2) The second issue is that a glossy material does not show the texture map in the material sphere, but it DOES show up correctly in the rendered viewport. A diffuse materials does show up correctly in the materials list. Both of the materials below have the birch texture map assigned in the diffuse slot. Please see the image below.

[face_off]

I did find a couple of issues this morning that are strange.

I have a new release ready to go - just waiting to hear back from McNeel on one issue. This new release should address both these points. I will hopefully post it in the next 24hrs.