Vray For Rhino 6 Mac

[artPen]

Hey guys,
Any plans for Beta ? Are you working on it?
We haven’t heard from you in a while.
Rhino 6 for Mac is already well developed and stable

[artPen]

Anyone from ChaosGroup?

[Peter.Chaushev]

Hello, and thank you for expressing your interest in V-Ray for Rhino. I understand the lack of new info has been going on for quite a while regardless of McNeel's product development.
Allow me to quote my most recent response of Chaos Group's stance in regards to the commercially available Rhino 6 on macOS.

It is our desire to have V-Ray accessible to all Rhino users.
Development of V-Ray for Rhino on MacOS is entirely possible right now, however, the decision to pursue it also relies on other factors outside of its technical scope. Once its evaluation as a business product comes to a conclusion an announcement will be made. For now though, I’m afraid I have no further info to share.
Be advised that if the project receives green light it will still be a while before it is completed as for this purpose V-Ray for Rhino will have to be almost entirely rewritten.

Kind regards,
Peter

[artPen]

Thank you Peter

[rudiwave]

Hey guys,

hope this message finds you well!

I just wanted to share that a lot of other people (myself included) are also hopefully waiting for a Mac version of V-Ray for Rhino. There are many posts on the McNeel forum on this topic, as for example this quite large thread, which is going on since 2014 and still active:

https://discourse.mcneel.com/t/vray-...dy-knows/10347

Surely it is not a quick and easy thing to develop a new V-Ray plugin, but I thought it would make sense if you guys had some more information regarding the demand for V-Ray for Rhino on Mac.

Hope this is helpful!

Stay healthy and greeting from Vienna,

Rudi

[enjoystick]

Hi ChaosGroup!
I can concur! I think V-Ray on Mac would be total gamechanger for many people working in different industries!!!

Petr

[alex_brosh]

Development of V-Ray for Rhino on MacOS is entirely possible right now, however, the decision to pursue it also relies on other factors outside of its technical scope. Once its evaluation as a business product comes to a conclusion an announcement will be made. For now though, I’m afraid I have no further info to share.

Any update available from ChaosGroup on this yet? I know it's something that I'd love to see come to fruition. It's encouraging to see that V-Ray for SketchUp has made it to Mac, looking forward to the same with V-Ray for Rhino.

[Peter.Chaushev]

Hello, Alex,

There is currently no active development yet.
Here is a more detailed explanation by my colleague Konstantin:

Hi guys,

The development of V-Ray for Rhino for MacOS is still on hold.
There are both technical and business decisions that need to be made before we push forward with it.

"You have SketchUp version for Mac and I assume you probably have the same source , so why not compile for Rhino Mac ?"

The task is not at all that easy.
We are currently using Rhino's C/C++ SDK for the V-Ray integration (this was the only good option for a long time and the one recommended by McNeel).
It gives us both performance and flexibility but unfortunately it's Windows only (you can read more in the Rhino SDK Docs).
If we want to build a MacOS version of V-Ray we'll basically have to use the RhinoCommon (The cross-platform .NET plugin SDK for Rhino).
This means rewriting almost everything on the integration side.
If we go in that direction we would have to rewrite the windows version as well in order to share the codebase and avoid duplicated effort.

I hope that the technical details will help you understand why we haven't made that move still.

Regards,
Konstantin

[nigel_patale]

Hello, Alex,

There is currently no active development yet.
Here is a more detailed explanation by my colleague Konstantin:

Hello Peter,
Has there been any new developments on this topic? May are itching to switch to the new apple silicon given performance to energy consumption ratio.
Been using Rhino for more than a decade with vray. Any chance that there has been a development of Vray for rhino for Apple Silicon/MacOS?

[Peter.Chaushev]

Hello, Nigel,
We have developers dedicated on porting V-Ray to native ARM code.
A V-Ray integration for Rhino on macOS, however, is still not in development, I'm afraid.
Once the situation changes an announcement will be published.

Kind regards,
Peter

[Robert]

Yeah, not even continue on delivering Modo versions. At least Chaos response. Wonder how many plugin will die next.. simple ignore users seem to work. I know a lot people with a Vray license in Modo and being extremely unhappy

[miruna_vecerdi]

Hi there!

Has there been any developments on this issue?

i am a avid user of Vray for Rhino - and I totally love it!

im about to transition from Windows to macOS - and it would be a huge pity if there is no future to using Vray for Rhino on Mac

would be nice to know the status

cheers
Miru

[rudiwave]

Would be amazing to have a V-Ray for Rhino implementation on macOS, especially with the M3 chips with hardware accelerated raytracing... the benchmarks seem to be very primising.

Best wishes,
Rudi

[sirio76]

Would be amazing to have a V-Ray for Rhino implementation on macOS, especially with the M3 chips with hardware accelerated raytracing... the benchmarks seem to be very primising.

Best wishes,
Rudi

Even if available Vray wouldn’t use M3 hardware acceleration since ther’s no support for a real Vray GPU engine for MacOS. Vray CPU should be plenty fast though.

[tsvetomira.girginova]

Dear rudiwave, hello.

Please refer to the answer of Nikolay Bakalov (previously posted in V-Ray 6 beta forum) - V-Ray for Rhino leading developer:

V-Ray itself supports Apple Arm chips, which is evident - C4D sketchup, maya, houdini...they all run natively on the M1/M2. Our plans of Rhino on Mac exist since 3-4 years ago. However the problem is the Rhino API. Historically V-Ray for Rhino is written on C++, using the Rhino C++ SDK on Windows. On Mac, however, McNeel do not offer a C++ SDK, but only .NET/Mono one. Hence the language we must use is C#. None of the already existing C++ code could be reused, and both SDKs have absolutely nothing in common. This means we need to rewrite everything on another language and against differnt SDK, that could potentially have fewer features. Then we need to support both implementations.

this is not quite feasible.

We know that McNeel have written their own Mac plugins on C++, hence such SDK exists. We have asked McNeel several times about publishing the SDK one way or another. The answer has always been 'No'

As you can see, if is not that we don't want, quite the opposite, however on these condirions, we don't really have a choice

This is our official statement.

Best regards,
TS