I'm trying to run a program, Switch Toolbox, which requires .NET Framework 4.6. I have had luck running this with no issue in the past on Ubuntu, however I'm currently using Arch with Wine 10.1 (also tested with 10.0)
In a clean 32-bit wine prefix, I ran `winetricks dotnet46 corefonts` and upon booting the tool which I placed inside of the Wine prefix itself, certain panels such as the 3d view and the UV editor show up as completely black.
If I unset the `DISPLAY` variable and ran it in Wayland, it works and shows everything properly.
I initially thought this could be xWayland or my desktop environment, however testing it on native x11 KDE Plasma the same issue persisted
The viewport uses OpenGL, and running a windows port of glxgears through the same wine prefix worked just fine. In the settings of the app, both x11 and wayland report the same Open GL and GLSL version, and the output to the console looks identical with no errors.
I rebuilt the app with only 32bit support, which still worked on my windows machine, but contained the same issue through wine.
I saw someone say to use winetricks to install gdiplus, but no luck. I would use the native Wayland version but as you can see from the screenshot the bottom timeline is missing (consistently shows up in x11 and doesn't in Wayland), the window decorations are there no matter what options I do to remove them, and just an assortment of other bugs which will likely be fixed in time with development, but it hasn't yet.
Issue exists using both an intel iGPU and Nvidia dGPU. mesa and nvidia-utils are installed, along with the lib32- versions of each.
Is there any idea what could be causing this? I can provide more information on request
Certain panes in .NET Framework apps are completely black in X11, fine on Wayland
-
- Newbie
- Posts: 2
- Joined: Sat Feb 08, 2025 3:52 pm
-
- Newbie
- Posts: 2
- Joined: Sat Feb 08, 2025 3:52 pm
Re: Certain panes in .NET Framework apps are completely black in X11, fine on Wayland
Found it out! Seems to work just fine with a 64bit wine prefix. Not sure what's up with that, but that's solved