D3D9On12 VS wayvnc

No Intel is not using dxvk but https://github.com/microsoft/D3D9On12, the DXVK is just a reimplementation and not a WDDM compatible UMD driver, because of this the DXVK will never be accepted a part of Wine project, the DXVK not use the same D3D9 and D3Dcompiler from Microsoft, the DXVK replaces this and not give a UMD D3D9 adapter with WDDM component, because this the DXVK never be used to replace a driver.

When Intel first shipped Arc, D3D9 games all ran via a layer called D3D9On12 which isn't very performance optimized. Last week's driver adds two additional modes - DXVK (an open source equivalent to D3D9On12 which targets Vulkan, used widely as part of Steam on Linux) and a port of their old D3D9 driver for Intel HD Graphics. The driver decides which of the three drivers to use based on the app name, which is based on their internal benchmarking of which works best per-game (e.g. you can force any game to run via DXVK by renaming the .exe to csgo.exe)

Intel has officially declared they are providing full DirectX 9 support via D3D9on12 .

> rewrite d3d9.dll to emulate the API in user mode on top of D3D12.

There seem to be such a project actually, just released to open source:

https://github.com/microsoft/D3D9On12

https://devblogs.microsoft.com/directx/open-sourcing-direct3...

You can run remote applications with Wayland now: https://access.redhat.com/documentation/en-us/red_hat_enterp...

There is also a VNC server for fullscreen sessions (only supports wlroots compositors for now): https://github.com/any1/wayvnc

There's wayvnc.

It says on their GitHub page that "Gnome, KDE, and Weston are not supported". What does that mean?

I thought this existed in the form of wayvnc but from their README it seems they don't support the popular desktop environments (GNOME, KDE).

Not sure if I would call it hassle free, but wayvnc isn't that hard to set up.

And wayvnc

There is however a fresh issue on the wayvnc github with what looks like your problem. https://github.com/any1/wayvnc/issues/206

On wayvnc git master and sway 1.8 (or git master), you can script things so that a "virtual" display gets created automatically when someone connects to VNC, and removed when they disconnect.

See https://github.com/any1/wayvnc/pull/200/files

The script in the PR does something a bit different, but it's only an example and can be modified to do what I described in the first paragraph.

No - it's not X, it's doesn't share a screen in the way X does.

That said... if this is a shoddy attempt at a "gotcha" style question - Screen sharing and remote desktop are both supported.

Ex - for Gnome:

https://wiki.gnome.org/Projects/Mutter/RemoteDesktop

LibVNCServer for VNC support, FreeRDP for remote desktop protocol.

For KDE:

https://userbase.kde.org/Krfb

Which mostly just works as long as you have Pipewire and xdg-desktop-portal-kde installed (the base plasma-wayland session usually includes them)

This one is a bit less polished - some users still have problems with keyboard input, depending on the distro and other installed packages.

For Sway:

xdg-desktop-portal-wlr works just fine for screen sharing, and you can use https://github.com/any1/wayvnc for VNC access (including having a completely headless machine).

Ah right, looks like the VNC server you're using is xorg only. You can try WayVNC for gaming mode https://github.com/any1/wayvnc .