Vray For Rhino Mac Download

[Shari Alvine]

Im trying to render an interior scene using Rhino + Vray. Vray supposedly is compatible with the lights you can create from Rhino (ie. Spotlight, Point Light, Rectangular Light...etc). I've had success with the Rectangular light but for some reason no matter what I do to the settings of the Spotlight, it refuses to produce any light.

So, I'm just wondering if there are any Vray gurus out there that can throw some advice my way about spotlights in vray.

Thanks

use Vray lights with IES files

VISIesLight

but ya i have found regular lights to be compatible, so maybe it is settings or you could ask at the support newsgroup and get your support from the source.

if you are using physical camera settings or the vray sun you will have to crank the multiplier on the spotlight WAY up. The rectangular light is best however. Check out the ASGVis forums for more help.

I uploaded a sample with two instances of the same block, one with vray material and the other with Rhino material.

It should also be noted that the mapping coords established before making the block become lost when switching to Rhino renderer but they are respected when switching to Vray renderer.

I make a separate object file and using Texture and Texture mapping then Insert that in my main file!! But When I want to make a render in Main file, more Clamps Apear on my Block textures!!!

WHAT IS WRONG??

Imagine having a job where placing spotlights and other directional lights is something you do alot - and then imagine you are designing a tradeshow stand with a rig and 50 spotligts attached to that rig. The spotlights are imported as blocks - which is good - but now you have to manually insert 50 vray ies spotligts. This is time consuming and the solution seems so simple yet it is not possible.

Having lights as an ordinary object i Rhino to work in blocks has been requested since 2014 and I can see that there is no development on this. What is the forecast of this feature being implemented in R8?

Yes, the main problem is that Rhino does not allow lights in blocks as a whole. V-Ray lights are simply Rhino lights + some extra data. The reason for that is to be able to see them in the viewport. Certain lights have 100% match - Rectangular, Point, Directional and Spot lights are exactly the same, so we use them directly. This is important in order to be able to visually modify their properties in the viewport - like cone angle, penumbra, etc. That also includes the intensity, color, attenuation (coming soon)

As @tay.othman said - there are number of ways to overcome the issue with the automation. It basically means some sort of scripting - Python, Basic, C# or Grasshopper (which is just very inefficient C#). You just need to link up your BIM data (lights locations) with a couple of lines of python code.

V-Ray will also benefit from having lights in blocks. We have a very efficient light instancing in the renderer, so having 1 block with 100 lights instanced 100 times will render fast and efficient. However Rhino does not have that feature

@Jacob_Thuesen @Nikolay

How about exporting the tradeshow lighting fixtures geometry along with the associated lights as a .vrayscene and then embedding the ,vrayscene into a block. I have tested the .vrayscene ability to save lighting information and it should work.

Hi @rene1, 700+ meg sounds like alot for Vray to be responsible for.

You could also try one of the test commands that one of the Mcneel guys mentioned somewhere else on the forum to remove embedded images from old pictureframes etc.:

TestPurgeBitmapTable

And then save as another file name to be safe, and see if that has an effect on your file size. Michael VS

The latest stable VRayForRhino is Nov 14, 20142.00.25251. You can check your version under the menu V-Ray->Debug Window. In the latest release we did everything we could to reduce duplicate materials being saved in files, which was a known problem in earlier releases.

if you still think VRayForRhino is causing this bloated file size can email the file to vray...@chaosgroup.com and have them take a look, as @mvyess said, it could be embedded images and/or any other plugin causing these issues.

The latest stable VRayForRhino is Nov 14, 2014 2.00.25251. You can check your version under the menu V-Ray->Debug Window. In the latest release we did everything we could to reduce duplicate materials being saved in files, which was a known problem in earlier releases.

if you still think VRayForRhino is causing this bloated file size can email the file to mailto:vray...@chaosgroup.com vray...@chaosgroup.com and have them take a look, as @mvyess said, it could be embedded images and/or any other plugin causing these issues.

If my assumption is correct, then that actually sounds about normal. Rhino can use up a lot of RAM, especially if you do a lot of complicated operations (even copy and paste) which causes that data to be stored in RAM for future UN-dos. I have commonly seen a 100 MB file use up 3GB or more of RAM, depending on what I am doing.

It is not about RAM use but the real file size that is shown in my computer. It was solved by installing the latest build of V-ray. The file size is now 130 mbs which is quit right in my opinion. Problem solved!

On a Machine B, we open the same file produced by machine A from the server, to do the simplest thing on earth, just pressing the render command and see exactly the same results as in Machine A. It looks like this is not possible. Lights do not even appear in the vray asset editor, although they do appear in the scene.

We then try to export a VRScene from Machine A, importing it back to Machine B, but what we get is a duplication of the objects from the original file, also badly meshed on the screen, showed as a block. The program asks even for a proxy position insertion point. Therefore we have, effectively, two identical objects and the result look similar.

This is exactly how it is designed to work. Basically you can add a complete render ready scene file into another file or render it directly using the batch render tool. The mesh is just a preview mesh to keep viewport speed high. In general the insertion point is just 0

Are we saying that a rhino file with vray lights, materials and settings can only be rendered/edited by the same machine which created it, otherwise, if opened on another machine, you have to recreate the entire scene from scratch??

First: Make sure you have enabled + loaded + set V-Ray as current renderer on the target machine BEFORE opening the file. If the V-Ray plugin is not loaded, Rhino will not call our deserialization code

just a couple more ideas I would try:

de-install and then re-install latest V-Ray on both machines (4.10.02)

Start a new scene on both computers and add the same assets in both, then try to open up scene created on A on B and vice versa to see if it makes a difference.

That is a bit confusing. V-Ray 6 for Rhino is still in beta, and there is no way you can install that on Rhino 5.

It would be best if you can screenshot the About window, where the full version is shown

It is almost certain now, that you have downloaded the latest V-Ray that supports Rhino 5, which is a very old version. You shall upgrade to Rhino 7 (Rhino 6 is almost out of support as well), and use latest V-Ray 5. V-Ray 6 is almost out of the door

Thank you. I just want to clarify: If I update my Rhino to version 7, would I be able to utilize VRay with the same user interface I find in online tutorials and examples? Do I get fewer options because my version is outdated?

I checked with our IT department and they said they reinstalled my vray, but unfortnatelly with a very outdated version. . . (I am using Rhino 7) I asked for Vray 6 now - i look forwart to those functionalities

So I'm new to enscape and fairly new to rendering in general. I am using Rhino 6, with Enscape as the render export/video maker. However I have been using vray for materials, and they all have a very high reflection/glossiness when rendering out in enscape. I saw a post somewhere saying that vray materials don't work well with enscape but no solution/workaround for somebody who like me has all the materials already set, and mapped. I was hoping somebody might have some advice on how to either get the vray materials into materials that render better with enscape or a potential tweak to the materials in vray that would remove the gloss/make the two plugins work better together. Thanks for any advice.

3a8082e126