From: svenster
Hi Forum. I've had very issues with this over many versions, but my arch host just upgraded to wine-10.12 and now there are definately problems with the viewports as shown below. I reset the configuratrion just in case. Wonder if I should post something on winehq about this or just wait for 10.13 ?
Sven
Image Attachments:
Screenshot From 2025-07-15 11-02-29.png
From: Michael Gibson
Hi Sven, the viewports are pretty tightly connected to the GPU so one thing
you might try to see if it has any effect is go to Options > General > "Edit .ini file" button.
Find the setting GraphicsAPI=Auto inside the [View] section and try with these:
GraphicsAPI=Direct3D11
Then try:
GraphicsAPI=OpenGL
And also:
GraphicsAPI=Direct3D9
I think it's possible to have the older wine-10.11 build set up in a separate wine prefix if that version works better.
- Michael
From: svenster
Hi Michael. Thanks for replying...
-Direct3D11 = same result
-OpenGL = looks correct, but viewports disappear with activation of single viewports when returning to split view
-Direct3D9 = worst of all
I can still use in Windows until Wine resolves.
Sven
From: svenster
Hi Everybody. Wine-10.13 on Arch Linux behaving the same with all the possible GraphicsAPI settings. wine-stable ( wine 10) is available on Arch, but wants to install install 101 dependencies many looking like some 32 compatible libraries so I'm trying to avoid. Is there anybody that is succussfully using Moi3D on wine 10.13 ? Between my Moi3D archive being on Arch and my lack of need for Windows I would really like to get this working on Linux. Is it worthwhile reporting to winehq and if so, what should be mentioned ?
Thanks, Sven
From: Michael Gibson
Hi Sven, it's working fine for me on Linux Mint 22.1 , with wine version wine-9.0 .
I'm not able to try with Arch Linux right now, looks like their web site is down.
- Michael
From: Michael Gibson
Hi Sven, so Arch Linux does not have a graphical/windowed environment set up by default.
What Window Manager or Desktop Environment are you using with it?
Since it looks like the problem is something with child windows not being located as expected it might have more to do with the particular window manager you're running as well as the wine version.
- Michael
From: svenster
Hi Michael. I've been using Gnome desktop environment. After your reply I did try KDE Plasma desktop environment with the same results. Specific window managers seem to require configurations so I was unable to easily launch moi when trying them ( e.g. Hyprland, sway). I just installed wine-stable ( wine 10.0 ) which pulled in an incredible number of dependencies, but it does work so I can use until hopefully the development branch resolves this. So don't report something like this to winehq ?
Thank you, Sven
From: Michael Gibson
Hi Sven, I'm glad wine 10.0 is working for you.
re:
> So don't report something like this to winehq ?
I'm not sure... Maybe it would be good to look for any already open bugs first.
Maybe it's possible the development branch build is set up to use the newer Wayland driver instead of winex11.drv .
- Michael
From: svenster
just had a look and found this ?
https://bugs.winehq.org/show_bug.cgi?id=56285
From: Michael Gibson
It might be related to that one but it's hard to know for sure.
- Michael
