Thank you very much for testing and reporting - that’s really helpful! Is there any chance that you could share terminal output when you try to run rhino 8 (pastebin.com?)
The output of my last run, with some additional debug logs enabled, is attached to Wine bug #57272.
Fantastic and sorry for missing that.
I’m wondering about this line:
0154:err:winediag:wined3d_dll_init Disabling 3D support.
seemingly indicating an issue with graphics instead - perhaps running it with WINEDEBUG=+wined3d,+d3d,+opengl debug flags might confirm that?
alternatively: LIBGL_ALWAYS_SOFTWARE=1 wine or WINEDLLOVERRIDES="dxgi,d3d11=n" wine or if you are running nvidia and proprietary driver maybe render-offload: DRI_PRIME=pci-0000_01_00_0 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia wine
I’ll try when I have a chance, but I think the crash is not related to 3D rendering at all, but probably some incompatibility with NET Desktop 7.
That message probably appears because on that run I was setting renderer=no3d. It’s the same message for Rhino 7, where it seems to run just fine with both renderer=no3d and renderer=vulkan.
1 Like
oh okay, false positive then
Microsoft Recall is now integrated in FileExplorer as a dependency (as of 24H2).
4 Likes
I’ve seen this also yesterday. Quite terrifying that somebody will watch and record even the smallest thing you do on your machine.
3 Likes
I just thought I’d give you guys an update. Between the mention of fixing black tooltips with the windows theme change, and the previous docs I’ve had as a github gist, I can say that I’ve now been using rhino for a few projects without major problems. Cycles still isn’t right but that’s ok.
Here’s the docs site here: Running Rhino3D on Linux | rhino-wine
And the github site here:
I’m working on some installation wrappers for this nowdays. please feel free to contribute or offer a pull request!
6 Likes
I was contemplating working out a git installer on the Arch repository, so it might be possible to just run “yay rhino7”, which would be pretty cool
2 Likes
Looks like a nice guide, and useful scripts. Perhaps you could make a small change to the guide by first telling the user to download the Rhino 7 installer. Also change the script to take the path to the downloaded Rhino installer as input to the script, that should make it easier for users, especially for those who aren’t too familiar with shell scripting.
1 Like
Thanks for initial feedback. I wanted to just get anything up there rather than a manual guide.
I’ll need to spend some more time working out something nicer - maybe a couple different recipes for users who use bottles or vanilla wine etc.
I am looking to migrate from windows to linux. Since Rhino3D is a major part of my workflow, I was excited to see the recent progress in getting it to work on wine. Many thanks for publishing installation instructions for Ubuntu!
However, being only a casual linux user and being new to wine, I had no luck following the instructions on a new Ubuntu 22.04 LTS based Pop! OS installation. Here are some notes and issues I ran into:
-
“apt install wine wine32” installs old versions of wine/wine32
(v6.03) on Ubuntu 22.04 so I installed winehq-staging (v9.22) from
winehq repo per instructions at
Debian/Ubuntu · Wiki · wine / wine · GitLab -
after running “sudo dpkg --add-architecture i386”, I believe “sudo
apt install --install-recommends winehq-staging” installs both
64-bit and 32-bit binaries, so no separate wine32 package is needed
(or available) -
created new WINPREFIX for rhino-3d (default 64-bit architecture)
before running “wineboot -u”:export WINEPREFIX=~/wine/wpfx_rh3d_64
-
had to run “winetricks allfonts” 3 times for it to complete successfully
without a core dump (maybe needed to update winetricks first - see below) -
saw many warnings from winetricks like this: “warning: You are using
a 64-bit WINEPREFIX. Note that many verbs only install 32-bit
versions of packages. If you encounter problems, please retest in a
clean 32-bit WINEPREFIX before reporting a bug.” -
had to run “sudo winetricks --self-update” to install vkd3d
-
repeated killing of wine processes was not needed (no such processes found)
-
finally, when I tried running the rhino_en-us_7.37.24107.15001.exe
installer, the installer window popped up, but then wine crashed
when I clicked “Install Now”. -
after trying running the installer multiple times, one time it
didn’t crash wine, but ended installation with an error code (which
alas, I didn’t record) -
I also noticed that two instances of the Rhino3D installer
would open with a single command, and there seemed to be another
instance of the rhino installer “waiting in the queue” which opened
as soon as wine was started (e.g. if I ran winecfg without any
arguments). -
I then uninstalled everything, installed winehq-stable (v9.0), and
repeated the process. This time, running the installer resulted in
an unhandled memory exception (std::bad_alloc) from libc++abi
without the installer window ever showing up.
Any thoughts on what might be going wrong? Reading the forum, it seems others have had much better luck (at least getting past the installer).
Thanks!
1 Like
I also just tried installing Rhino (v7.37.24107.15001) via Crossover per Santiago’s suggestion. The installation process went flawlessly. However, when trying to run Rhino, I get a Rhinoceros License Not Found message box with “Rhino requires a license to run. Rhino will now exit.” despite being logged into the Zoo from the same machine with a valid license for v.7. Seems like I’m doing something dumb, hoping for better luck tomorrow. So close! 
As it stands, Rhino is the only thing that’s holding me back from migrating my workflow to linux (other windows software I rely on can be run in a VM without native GPU access), and even if the renderer doesn’t work yet in wine, it’s not a big deal for me.
1 Like
hi @Interstellar_Vagabon and congratulations on giving linux and rhino on wine a try. Have you looked already at aaronsb’s excellent guide and his latest script for debian (ubuntu’s base distro). Would running these command lead to the same errors?
Also worth noting if you ever get stuck you can always run rhino in a virtual machine, which is always guaranteed to work, although won’t integrate as neatly into your desktop as wine.
Hi, I did try aaronsb’s guide (which as far as I can tell is the same as the script), however I ran into problems (see 2 messages above). The issue with running Rhino in a VM, at lleast with VirtualBox, is that it does not provide direct access to the GPU, which is essential for me. It looks like it’s possible to do GPU passthrough with KVM, so I’ll have to look into that, but still holding out hope for getting Rhino to work via wine/Crossover. The license error I’m seeing doesn’t seem to be occurring for others, so maybe easily solvable.
ok, that makes sense. I’m running a different distro and haven’t encountered most of these issues, but here are packages
wine vkd3d lib32-vkd3d wine-gecko wine-mono dxvk-bin winetricks
and winetricks
winetricks -q corefonts pptfonts dotnet48 vcrun2005 vcrun2010 vcrun2013 vcrun2019 vcrun6 vcrun6sp6 gdiplus dxvk
wine winecfg -v win10
wine Downloads/rhino_en-us_7.32.23221.10241.exe
that worked for me - are they any different from what you’ve tried? If not, could you share console output that wine prints for you (when you run WINEPREFIX=<PREFIX> wine Rhino.exe, so we can troubleshoot further?
The issue with running Rhino in a VM, at lleast with VirtualBox, is that it does not provide direct access to the GPU
that is correct, KVM is able to perform GPU passthrough - are you on a laptop or PC?
Thanks! Which version of wine do you have installed? My distro (and I think the latest Ubuntu LTS) installs 6.0.3 with apt. I can install the latest stable (v9.0) or development (v9.22) version via winehq repo. Or perhaps I could try another version via playonlinux. I’ve only tried with rhino_en-us_7.37.24107.15001.exe, which is the latest version downloadable from McNeel. I’m not sure where I can download an older version. It looks like this license error message I’m getting is an issue others have reported running Rhino from a VM without a clear solution. Perhaps it has to do with network passthrough/settings? I followed the exact steps in Santiago’s post 598 with the same Rhino installer and Crossover verion, and wonder what’s different on my machine (a laptop with an Nvidia GPU).
6.0.3 is quite old, I don’t think you need the absolute latest, but anything past v9.0 should help. I’m on wine-9.22 (Staging) right now.
I’m not sure where I can download an older version.
I don’t think older versions are officially available, I used to scrape dates and versions from builds that referenced youtrack tickets on the release page and put them in url in format https://files.mcneel.com/dujour/exe/YYYYMMDD/rhino_en-us_X.XX.XXXXX.XXXXX.exe, but can’t reproduce this anymore (all are 404 now). If you don’t want to wait I’ve shared the exact versions of my past installers here (link expires in a week - in general running executables from strangers on the internet is a bad idea, but can’t think of any other way).
Regarding license error do you have gecko installed on your machine? I recall that it was required by the license manager, I think it used it to render html form required for license dialog. Also Rhino 8 since about beginning of this year moved to webview2 windows framework, which still doesn’t work on wine - I wonder if that might have been added to latest Rhino 7 as well.
You’re definitely going to need to run a newer wine version. Latest and greatest is what’s going to be needed here.
Ubuntu 22 on an LTS are going to give you lots of trouble with dependencies.
I’ve switched to arch in the last year - I know that’s not for everyone but it has essentially solved my out of date package problems.
You’re going to likely need to use a newer ubuntu (24+) and use packagelock to prevent apt sources from ubuntu for wine and instead install from their sources and packages to get a much newer version.
yep, packages above were from Arch (by the way). It makes wine much easier.