[Wine] How to run KITModelViewer and IFCCheckingTool on Linux?

Oh so Boxes do provide GPU passthrough now. Cool.

No, I am using now Wine (Staging) native on my optimus laptop. This time, no boxes and no bottles. I got an intel GPU and an nvidia dGPU and the command nvidia-run-mx is a wrapper from MX Linux for the environmental variable that needed to set, if one wants to start the program with NVIDIA support.

What if you tried now changing renderer to vulkan? WINEPREFIX=/home/USER/Wine/KIT winetricks renderer=vulkan?

Still the same behaviour, the bottom half has no problem, only the upper half. Perplexing. I also switched from X11 (KDE) to Wayland (KDE) Session, no change.

If you can downgrade packages on MX Linux maybe try different combinations of previous versions of wine-stable/wine-staging, wine-dxvk and nvidia drivers?

There is the possibitly to download the wine version package by debian stable instead from MX Linux:

➤ wine --version

wine-8.0 (Debian 8.0~repack-4)

And when i start the programm, there is nothing in the 3D Vew:

So wine version 8.0 is not the way.

There is a way to install newer stuff from the MX Linux Test Repo

Now i got:

➤ wine --version

wine-8.20

There is the cube like in the version 8.12 in the 3D View.

But the issue of flickering is not solved. Do I need to delete my old WINEPREFIX and install it new, since my WINEPREFIX was installed with the older version of wine (Version 8.12)? Would there be any difference?

No, I am using now Wine native on my optimus laptop

Oops sorry, I read "now" as "not"...

I got an intel GPU and an nvidia dGPU and the command nvidia-run-mx is a wrapper from MX Linux for the environmental variable

Thanks, that's interesting, there used to be a prime-run command wrapper in some nvidia-utils packages, which added environmental variables that I've modified into:


DRI_PRIME=pci-0000_01_00_0 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia

to offload rendering to the Nvidia card (I'm also on an Optimus laptop - 81YT Lenovo Legion 7 15IMH05 ). The first variable is the pci number of your nvidia card (which you can get with the lspci -nnk -d 10de: command for example). You may want to try and add the first two variables along the ones you already have and maybe that would help with the flickering.

Have you considered running it on Intel's iGPU? Although it's slower it may be more stable.

Could you share the output from your wine command now? Specifically does it print anything when you orbit the viewport (when it flickers)? If not, how about adding either one of the WINEDEBUG=+wgl,+d3d again?

I also switched from X11 (KDE) to Wayland (KDE) Session

I would recommend testing first on X11 - Wayland's support for wine and nvidia prime is still under development.

If you do try later running it on Wayland try something else than KDE - I've never managed to run wine on KDE Wayland with Nvidia prime render offload. It did work out-of-the-box though on wlroots-based compositors. It worked on Hyprland at least (without nvidia's patch). KDE6 is coming out soon and they were developing wlroots-backend as well, so it may change.

wine-8.0 (Debian 8.0~repack-4)

Hmm, I was thinking of switching to something closer to wine-staging 8.20, like 8.19 or even the latest 8.21 (if available). You could also consider compiling from source, but that can get much much more tricky for uncertain benefit, especially if you say that...

There is the cube like in the version 8.12 in the 3D View. But the issue of flickering is not solved.

In terms of:

Do I need to delete my old WINEPREFIX and install it new, since my WINEPREFIX was installed with the older version of wine (Version 8.12)? Would there be any difference?

I'm not 100% sure, so I would recommend starting from scratch. You definitely shouldn't have wineserver running from different version than the one starting the application (that's why it's good to run kill -9 $(ps aux |grep -i '\.exe' |awk '{print $2}'|tr '\n' ' ') after each test), but obviously I've been hopping from version to version for the past few months (from wine 8.14 to 8.21) on the same prefix and it's been running fine (once initially configured).