Announcement

**joe_b** · 16-01-2006, 02:51 PM

Features question

Distrubuted Rendering will definately not make this release
Displacement Mapping probably won't make this release
Toon renderer probably won't make this release
I'm not sure about area lights
Some procedural textures might make it in
Bump mapping willl absolutely be in the final release

I'm not sure about the VRay 1.5 stuff, I'll let Corey answer that one. Right now we have 1.49.10 or 1.49.11 so I think the switch over to 1.5 won't be too much different for VRay for Rhino.

**Micha_cg** · 16-01-2006, 03:03 PM

Features question

I miss an ambient occlusion mode. Is it planed?

**andreas** · 17-01-2006, 03:43 AM

Features question

Hello Joeb,

thank you for your answers, actually I forget to ask two more, probably important, question:

- Since as far as I understood it, Rhino 4 is supposed to solve many of the actual shortcomings of Rhino concerning textures. I would like to know how easy / fast you could convert vray4rhino to work with Rhino 4, or will there be an in-between solution for Rhino 3, which will enable us to see the textures exactly in the view port ?

- In your post you referred to features which will not be part of the first release (1.0.0) and to future releases, so I suppose that the first nonbeta version will have a basic set of the features and will be updated by later releases to complete the initial feature list?

Best regards

Andy

**joe_b** · 17-01-2006, 07:31 AM

Features question

Originally posted by vcube

- Since as far as I understood it, Rhino 4 is supposed to solve many of the actual shortcomings of Rhino concerning textures. I would like to know how easy / fast you could convert vray4rhino to work with Rhino 4, or will there be an in-between solution for Rhino 3, which will enable us to see the textures exactly in the view port ?

I am not 100% on all the differences between Rhino3 and Rhino4 as far as plugin development goes. However, I am sure that all Rhino4 plugins must be Unicode builds. As of this very moment the VRaySDK does not have a unicode build, and I am not sure if there is a way for us to link the current VRaySDK properly in a unicode build. So this might take a little time in and of itself, then I need to make sure that all of my own existing codebase is unicode compliant. So I cannot really give you a completely definitive answer on this right away, but I am sure we will be very interested in keeping all the Rhino users happy, and as such, I'm sure we will be looking into this as soon as it is possible for us to do so. Sorry if this doesn't fully answer your question.

Originally posted by vcube

- In your post you referred to features which will not be part of the first release (1.0.0) and to future releases, so I suppose that the first nonbeta version will have a basic set of the features and will be updated by later releases to complete the initial feature list?

I believe we are pretty close to the feature list we said we would have. But there are definately a lot of things for us to continue porting from VRay for Max to VRay for Rhino. I am not sure how it will all work out as far as pricing and release dates, but we will continue adding features to VRay for Rhino as long as there is a demand to do so. This is a good question, and one I will have to talk with Corey about.

**broozee** · 23-03-2006, 08:12 PM

Features question

Originally posted by joeb

Toon renderer probably won't make this release.

Has the status of this feature changed any since this was posted in Jan? I use AIR a great deal for its toon line capabilites.

It helps me bring out the details of my white models.

Bill

**corey** · 23-03-2006, 09:08 PM

Features question

V-RayToon will not be a part of the feature set for the 1.0 release. It's on the wishlist for our next official release.

Best regards,

Corey

**Micha_cg** · 23-03-2006, 10:12 PM

Features question

Bill, some weeks befor I have post some suggestions at the old rhinoman forum, how you can get outline without to change your vray materials. Do you know it?

**broozee** · 23-03-2006, 11:45 PM

Features question

@ Corey - thanks for the update!

@ Micha - sorry I missed that post. Brian changed forums and lost many of the previous posts. If I understand your english

are you saying there is a way to make toon lines in vray without using vray materials?

Bill

**Micha_cg** · 24-03-2006, 02:48 AM

Features question

Bill, I mean you can switch to Rhinoman|AIR without that you destroy all Vray settings. Here my workflow (I hope I don't forget something):

- enable Rhinoman as renderer
- set custom command for outline mode
- set pixel sampling (AA) at 12
- set shading rate to a horrible value like 32
- disable raytrace
- enbale GI without bleeding
- set indirect light intensity to 100
- use horrible GI settings like samples4-distance10-error0.5, no prepass

The idea behind it is: the quality of the outlines depends on the pixel sampling only. So we must try to kill the different default colors of the object. Best way: burn out the whole scene with extrem much light. Now you can use low surface quality settings, because surface are burned out white.

You only must multiply your Outline image to the Vray image in photoshop.

You can switch back to Vray everytime and anything work like befor. If you reopen your scene after saving later, all Vray and Rhinoman settings should work.

Cool or?

-Micha

**broozee** · 24-03-2006, 01:43 PM

Features question

Ahh! I remember this now. Its like the poor mans hidden line using AIR. I understand you now.

It's no big deal - I just thought if the toon feature was upcoming, I would use it.

Thanks Micha! I will try your approach.

Bill

Announcement

Features question

Features question

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment