Bug: Broken Hammer model browser in Wine Wayland

[Arenovas]

Describe the bug

The model browser renders white and is unusable when running Hammer using Wine in native Wayland instead of x11 or xWayland. However if the model browser is opened as soon as possible upon Hammer loading and making a map, it will appear properly but sometimes after being closed it'll be broken again.

Here it is broken.

And here it is when it briefly works.

I could just keep using x11/xWayland but setting it to run in native Wayland fixes some other bugs like frame delay in viewport updating when -nowinecompat is used. And running without -nonwinecompat results in horrible lag from the 2d viewports as reported in #1665 And since Wine 11 fixes the issue -nowinecompat was made for, it isn't necessary in Wayland at all.

Only thing I can notice between when the model browser loads and doesn't is that when it successfully loads, this little snippet appears in the console, same as x11/xWayland.

Binding uncached material "vgui_white", artificially incrementing refcount info: Presenter: Actual swapchain properties: info: Format: VK_FORMAT_R8G8B8A8_UNORM info: Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR info: Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR (dynamic: yes) info: Buffer size: 1912x1002 info: Image count: 3 Binding uncached material "potterywheelpanelwireframe", artificially incrementing refcount ConVarRef cl_custom_material_override doesn't point to an existing ConVar 0024:err:seh:user_callback_handler ignoring exception c0000005

So it seems like something at some point prevents Hammer from binding to that vgui_white material after a certain period of time has passed when running in Wayland and just just renders that material directly?
And that final line also doesn't seem to appear in x11/xWayland but appears regardless in Wayland, so not sure if that has anything to do with it.

To Reproduce

1. Open the Hammer editor when Wine is set to use Wayland for rendering as opposed to x11 or xWayland. You can tell if it's running in Wayland if the window decorations don't match the system's
2. Open/make a new map
3. Let it sit for a few seconds or so and open the model browser
4. If the model browser opens successfully, close it and try again, sometimes it might work a bit longer but it will break

Issue Map

Any map both from a fresh start and an existing one.

Expected Behavior

For the model browser to work properly and load in as it does in x11/xWayland.

Operating System

Fedora 43