Rhino on Linux – Gathering users who want (or seed) to switch to Linux

Rhino
,
123

Agreed !!

Here’s MY case for needing to migrate:

Currently - still on Windows 10, I use external programs to bridge gaps or shortcomings presented by Rhino, like a favored AutoCAD Clone - BricsCAD - for creating Shop and Technical drawings of my designs, and SimLABS’ excellent 3D-PDF generator Rhino Plugin, and Rhino’s OWN “BONGO” decent Animation Plugin.

I’m hearing some really GREAT things about Plasticity on Linux, so IF it comes to that, I AM prepared to replace Rhino.

I HEAR that Rhino 7 will run under Wine in Linux, but depending on the viability of

  1. GPU Pass-thru and CUDA, well tuned in Rhino for maximum value of the new “Raytraced” native RTR-rendering solution that replaced the ABSOLUTELY CAPABLE “NEON” plugin that did NOT require the added CUDA burden, but DID make effective use of it if it was available.

  2. viability of CRITICAL Plugins,

I may not be able to make effective use of my FAVORITE standalone program -

Rhino,

so MAY be forced to move my Surface Modeling to Linux-Native “Plasticity” instead.

The migration TO Linux is fast becoming a NECESSITY for ANY Rhino user whose CLIENT or Artistic Work, or Client or internal Engineering or Architectural work, is PROPRIETARY - as Windows (in Win-11) NOW makes EXTENSIVE use of mining YOUR critical PROPREITARY content for IT’s OWN use.

If Rhino developers aren’t interested in mitigating this THREAT that their users face, Rhino’s users who have SIGNED CONFIDENTIALITY AGREEMENTS may be forced to pass along any indemnity for breach of Confidentiality, as a DIRECT result of NEGLIGENCE, to McNeel. If you have EVER been a defendant in such a lawsuit OR been tasked with supporting such a Defendant, YOU well KNOW that Transfer of Liability SURVIVES all Indemnity firewalls, no matter HOW it’s worded in clicked-past Software “User Agreements”.

Because we as CAD Designers, Engineers, Artists and Architects can NOT afford to take on the BURDEN of such potential liability, the forced migration to Linux also forces abandonment of the originating intermediate THREAT itself - Rhino.

This is something I hope to AVOID at almost ALL COST.

Any Rhino user NOT willing to make the change away from the Data-Mining Operation that Windows has become, takes upon HIMself/HERself/Corporation that exact potential LIABILITY, as a PERSONAL Business decision.

This is NOT a matter of opinion.

Lawsuits on THIS EXACT TOPIC have been won or lost (depending on which side you’re on) and companies have closed down, and this will CONTINUE to be Litigated on THIS very basis. THIS is how China Copyright and theft of Copyright and Industry & Government Intellectual Property and Military and Engineering Data espionage prosecutions in Europe AND The U.S., have been SO successful .

“But its held on SECURE Microsoft Servers ?” Have YOU ever heard of successful server hacking ? I have.

“But it’s never uploaded off of the User system (MS Recall) ??” Well, first- you can’t have BOTH - or you’re dealing with POPAGANDA, and this is Now known to be ACTIVELY FALSE, with recent disclosures of unauthorized UPLOAD of PROPRIETARY DATA to M.S. “OneDrive”.

I don’t know whether YOUR work is “Client Confidential” or not, but if it IS - you and I BOTH share the same exposure, as LONG as we’re on an O-S whose primary new “Killer APP” Feature is designed to UPLOAD YOUR data to your REQUIRED Microsoft Account ON “The Cloud” (again - M.S. OneDrive).

THIS is why there’s now widely growing SUCH a compelling case for finally making the MOVE to Linux. Yeah, we don’t want “our STUFF” to not be private, but FAR more importantly, we face a very REAL Indemnity threat, one that is ONLY mitigated by migrating.

Some Insurance companies won’t EVEN cover you OR YOUR CORPORATION (rendering your ability to even ENTER INTO Contracts non-viable) if you don’t address this liability, which is the basis of EVERY CORPORATE I-T contract and Corporate Client Contract in PLACE, World-WIDE !

So that is MY case FOR migrating.

I can no longer stay on Windows now, any longer than is absolutely necessary, and this is why I’m seeking ANYTHING that will help me successfully migrate my Rhino implementation along with my O-S migration .

Any thoughts ANYONE might offer will be deeply and SINCERELY appreciated !

Thanks !

- C .

ps. - Sorry I went long !

Thanks !

124

Hello @cfee , I’m curious, do you have concrete examples?

125

I’m pretty close to a dead end here. I went to download WIP 9 and it came up as “requiring” Windows 11. I will never be using any version of Windows beyond 10 and only keep that to run my Rhino3D Ver.8. Everything else I do on a computer is done in Linux now.
Apparently, when Ver.9 is released, I’ll just have to stay with Ver.8 and start looking for another CAD option. I’m really disappointed that I have to do that.

126 
As it sits, and to the best of my current understanding- Microsoft has stopped supporting windows 10, so we cannot officially support windows 10 for ongoing versions of Rhino either.

Will Rhino 9 run on windows 10? Very likely and also very likely without issue.

If problems arise we will do our best to address them, cuz that’s how we try to roll, but as an *official support policy* v9 will most likely be win 11 only.
127

If R9 might run on linux, does that also mean Rhinolands and Visual Arq might also run on Linux?

Thanks

128

Probably not without effort from the vendors, unless they are pure C# plugins that do not use Windows specific APIs. If they have any C/C++ code then that likely needs to be recompiled for Linux.

129

Jesterking-

Hi ! Are you a Rhino developer or support tech ? Or are you a fellow user ?

I share the challenge re: Win-11, and will NOT be “upgrading” to Win-11 for ANY reason, Rhino or NOT, altho it will GENUINELY cause important follow-on work-flow CHALLENGES, moving forward.

It’s frustrating that with the HUGE market interest in Linux, that there seems to be NO interest in moving Rhino forward with us .

I plan to move to Rh-8 as soon as I get paid on this project, but it’s LOOKING like I’ll have to “Legacy-Load” at Rh-7 even tho I’ll have to pay for Rh-8 at Upgrade, as others elsewhere here on “The Forum” are reporting that Rh-7 seems to RUN in a Linux/Win-10 Virtual portal, but Rh-8 does NOT !

ANYTHING of substance you can offer to that end will be DEEPLY and gratefully APPRECIATED !!

Thanks -
and GOOD LUCK ! -
- C .

130

Daavid - If you’re not associated directly with McNeel/Rhino, please accept my MOST SINCERE apologies in advance -

If you ARE -
It SEEMS that while you aren’t DIRECTLY supporting Rh-9 on Win-10,
that you COULD possibly “emphasize” it still RUNNING on Win-10, even IF you can’t “OFFICIALLY SUPPORT” it.
There shouldn’t be any SUBSTANTIVE REASON for it NOT running, as Win-11 itself offers NO NEW CRITICAL CODE that Rhino SHOULD be “depending” on to successfully EXECUTE .

Seriously.
This REALLY IS something SERIOUS, and with an unexplainable refusal to branch forward to Linux (something like what you already do with MAC), this really does create a GENUINE problem for the Rhino User Community.

Blaming the Add-on or other Developers doesn’t wash, as THEY look to Rhino for IT’S direction. This is inarguable, yet that seems to be the most CONSISTENT REASON GIVEN for NOT adding a Linux fork, to match the MAC fork, which we can NOT cross-adapt, as our systems do NOT run MAC but DO run LINUX, as an alternative to ANYTHING Microsoft uses for it’s MASSIVE and intentional Data-Mining SECURITY breaching.

My projects are PROPRIETARY, and having them FORCIBLY uploaded to “The Cloud” for ANYONE to hack into (China!!) is NOT a valid option, no matter WHAT Nation a Designer runs their Rhino in.

So-
Q: Is there ANY SUBSTANTIVE insight you could offer, that would help us successfully DEAL with his very REAL problem, besides recommending we DROP RHINO which we do NOT want to do ?

SINCERELY ASKING ,
Thanks ! -
- C .

131

No association with McNeel other than a customer and forum participant.