Does vray for rhino work for the 64 bit version of the Rhino 5 beta?
I’ve been having issues with Rhino 4 and very complicated models (3gb memory limit). Rhino 5 64 bit has unlimited memory usage! Yippee! But if the Vray plugin doesn’t work with Rhino 5, I cannot render the model.
The first V5 WIP was released a day or so ago, and there is a native 64 bit version. I’m very busy the end of this week, so I won’t be able to actually install and play around with things until the beginning of next week. According to McNeel V4 plugins should be able to be loaded and used with V5 since there were no breaks made to the SDK. I am assuming that V-Ray will work on a 64 bit machine, although there’s a slight possibility that it won’t (because it wasn’t compiled for 64 bit). I’m not sure what the memory capabilities of V-Ray compiled for 32 bit Rhino being used with v5 64 bit would be.
Long term, we will be fully supporting 64 bit. Chances are you won’t see any 64 bit builds of V-Ray until we start having betas of the next full version though.
As a note 64 bit systems do not offer unlimited memory…just 128 gbs. Obviously, you’d be hard pressed to find a motherboard with that many mem slots on it though
I was referencing the first WIP builds of Rhino for their next version, not ours. McNeel has both a 32 bit and 64 bit version of the WIP. We have not done anything with V-Ray in terms of “responding” to the Rhino WIPs coming out, but this isn’t a problem as Rhino4 plugins should work just fine in the v5 WIP.
The only “gotcha” to this is the 64 bit build of Rhino v5 WIP. There is no reason that is RHINO SPECIFIC as to why a Rhino4 plugin won’t work in Rhino 5 64 bit. However, if a plugin was compiled against x86 libraries (which I’m almost sure V-Ray is), then it appears as though that plugin will not load because all of the other dependencies are not setup to run on 64 bit windows.
I still have not tried this, but a few other plugins have run up against this issue. Right now, I don’t forsee V-Ray working natively with 64 bit Rhino v5, until we release a build that is specifically compiled for 64 bit machines.
You still can use a 64 bit system by using the 32 bit version of Rhino (v4 or v5 WIP) and V-Ray will work fine. This will allow you to use about 3.8 gbs of memory, so that will still be better than using a 32 bit os.
Im sorry to be so impatient but I’m nearing the end of a project and being able to use all my memory would allow me to render the entire model at once which would be great and so I cant wait for the development to follow!
I very much appreciate you wasting your time to answer such impatient questions.
V-Ray does not work natively with the V5 64-bit betas. 64 bit programs require recompiling to be able to work with them, and we will not be in a position to do that until we begin our own beta cycle for the next full version of V-Ray. If you have a 64 bit system and would like to test V-Ray with Rhino 5, you can do so by using the 32 bit version. For the record, a 64 bit version of Rhino only allows for the use of additional memory. There really won’t be any noticeable difference in the actual working with or rendering process itself.
I haven’t really had a good go with it yet either but the main improvement is the fact that you can really take advantage of a 64 bit system. Correct me if im wrong though. Is there any news about a compatible 64 bit plugin for R5?
No news, as I posted previously we have to get to beta version of VfR2 before we’ll see a native 64 bit version
Long term, we will be fully supporting 64 bit. Chances are you won’t see any 64 bit builds of V-Ray until we start having betas of the next full version though.
There has not been any update on this for at least 7 months. Considering even McNeel comments that Rhino 5 is more stable than Rhino 4, we are moving most of our office to Rhino 5. The only barrier right now is Vray for Rhino.
Any luck with this? Specifically the 64 bit version? We’re running everyone at 64bit (why install two versions?), so a version compiled with that would be ideal.
Is it your experience too? My Rhino 5 tests ends with display problems often, so that I stopped to test v5. Is is stable now?
Could be nice to get the old VfR as 64bit version. Maybe it’s one day of work for the developer, but it could be a big help for the users.
ha! not even if Devin and Joe had Dual xeon Cores in their heads and multiple arms…people knoked it off, they are developers with a schedule. By the way how many here in the forum have a purchased license?
I would say, the developing team is to small. If something like a VfR plugin need years to get it implemented at it’s best, than maybe it’s time to think about the reasons. Vray is a pro tool and a well developed plugin should be a very good sellable product. Laublab got it for Cinema, why not ASGvis for Rhino?
I really can’t wait to put out the new core and start pumping out updates so you’ll stop making comments like this. It’ll get better man, I’m telling you. The SketchUp guys have gotten 3 public releases since 1.48.66 was released in April, it’s a lot easier to put out updates with the new rewrite. It’ll be a little bit longer before we put out a beta, but hang in there!