V-Ray for Mac Studio

Licensing General
1

Hello Guys!
Does everyone know when should be able V-Ray for Apple M1 chip?
Thank you in advance

Best regards

Max

2

V-Ray is natively supported on M1/M2.

3

Vray runs natively on M1 for over a year.

4

Hi guys!
Thanks a lot for the quite answer…some technical says otherwise

Max

5

Maybe they are not so technical then :wink:

6

I need another answer/confirmation. If I buy an Apple Mac Studio, works good with Rhinoceros and Vray?
Sorry for my stupid question, I’m not a computer technician, and on that point I don’t trust on our technician.
Thank you in advance

Max

7

The problem is not M1 compatibility, the problem is that there is no MacOS version of Vray for Rhino.
https://forums.chaos.com/forum/chaos…or-rhino-6-mac

On other supported platform works well though, Cinema4D, Sketchup etc

8

Thank you Sirio76 for your reply.
Did you know if Chaos is still working on that point?

9

Dear rainhard_kompatscher, hello.

The topic was discussed at different places, but please refer to this post which explains the situation quite well.
Since it is at V-Ray 6 beta forum, will paste the text also here to be sure that it will be visible to all users.

The answer is from Nikolay Bakalov, the Lead Developer of V-Ray for Rhino:

Originally posted by jason_vayanos View Post
From what I understand, the V-Ray for Rhino and V-Ray for SketchUp are similar applications
yes, but not in terms of host application APIs. They are completely different things. V-Ray for SketchUp and V-Ray for Rhino share all the cide, except the hostapp SDK dependant part

Originally posted by jason_vayanos View Post
Would love to hear what Chaos thinks, and if there are plans for support.
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​

10

Dear Tsvetomira Girginov,
thanks a lot for the answer and the advice about the Topic!
Thanks also to everybody for the support!
Have a nice day!

M

11

You are welcome!

Contact us again if needed.
Wishing you all the best.