vinegarhq / vinegar

An open-source, minimal, configurable, fast bootstrapper for running Roblox on Linux.
https://vinegarhq.org
GNU General Public License v3.0
425 stars 30 forks source link

Vulkan no datamodel shown #444

Open OverHash opened 1 month ago

OverHash commented 1 month ago

Acknowledgement of preliminary instructions

What problem did you encounter?

Opening Roblox Studio on the latest version (v1.7.6) on version-4a428ded4f244e64 produces nothing but a white screen once you open a game. About once per frame the console is filled with errors of

2024-10-05T10:21:31.698Z,18.698793,0024,6 [FLog::Graphics] VULKAN ERROR: vkAcquireNextImageKHR(device, windowData->swapChain, UINT64_MAX, acquireSemaphore, VK_NULL_HANDLE, &windowData->imageIndex) returned -1000001004 (VK_ERROR_OUT_OF_DATE_KHR)
2024-10-05T10:21:31.704Z,18.704840,0024,6 [FLog::Graphics] VULKAN ERROR: vkAcquireNextImageKHR(device, windowData->swapChain, UINT64_MAX, acquireSemaphore, VK_NULL_HANDLE, &windowData->imageIndex) returned -1000001004 (VK_ERROR_OUT_OF_DATE_KHR)
2024-10-05T10:21:31.705Z,18.705849,0024,6 [FLog::Graphics] VULKAN ERROR: vkAcquireNextImageKHR(device, windowData->swapChain, UINT64_MAX, acquireSemaphore, VK_NULL_HANDLE, &windowData->imageIndex) returned -1000001004 (VK_ERROR_OUT_OF_DATE_KHR)
2024-10-05T10:21:31.713Z,18.713911,0024,6 [FLog::Graphics] VULKAN ERROR: vkAcquireNextImageKHR(device, windowData->swapChain, UINT64_MAX, acquireSemaphore, VK_NULL_HANDLE, &windowData->imageIndex) returned -1000001004 (VK_ERROR_OUT_OF_DATE_KHR)

The datamodel looks like (just a white screen): image

Notably you can click on items in the datamodel, it just appears white (the explorer and properties tab will update to the part you have clicked on)

This is a regression from v1.7.5 where everything was stable.

System information

$ flatpak run org.vinegarhq.Vinegar sysinfo
* Vinegar: v1.7.6 
* Distro: Freedesktop SDK 23.08 (Flatpak runtime)
* Processor: 13th Gen Intel(R) Core(TM) i7-13700KF
  * Supports AVX: true
  * Supports split lock detection: true
* Kernel: 6.8.0-45-generic
* Wine (Player): wine-9.18 (Staging)
* Wine (Studio): wine-9.18 (Staging)
* Flatpak: [x]
* Cards:
  * Card 0: simple-framebuffer simple-framebuffer.0 /sys/class/drm/card0
  * Card 1: nvidia 0000:01:00.0 /sys/class/drm/card1

Configuration

# See how to configure Vinegar on the documentation website:
# https://vinegarhq.org/Configuration
multiple_instances = true

[env]
WINEESYNC = "0"

[studio]
renderer = "Vulkan"
dxvk = false

[studio.fflags]
DFIntTaskSchedulerTargetFps = 143
DFFlagDisableDPIScale = true
0x13479 commented 1 month ago

I can confirm this (Vulkan)

* Vinegar: v1.7.6
* Distro: Freedesktop SDK 23.08 (Flatpak runtime)
* Processor: AMD Ryzen 5 5600X 6-Core Processor
  * Supports AVX: true
  * Supports split lock detection: false
* Kernel: 6.10.12-hardened1-1-hardened
* Wine (Player): wine-9.18 (Staging)
* Wine (Studio): wine-9.18 (Staging)
* Flatpak: [x]
* Cards:
  * Card 0: nvidia 0000:0a:00.0 /sys/class/drm/card1

1728147927

xXHaloEpicXx commented 1 month ago

can also confirm this happens regardless of studio version, i attempted to roll back to version-ea7c4a2d814e4dc6 and was met with the same error

apprehensions commented 1 month ago

This is due to the recent updated Wine builds used in the Flatpak to use the merged 'childwindow' implementation rather than a patched one, giving different behavior as a result and causing Roblox to behave differently. Please try using DXVK instead.

OverHash commented 1 month ago

This is due to the recent updated Wine builds used in the Flatpak to use the merged 'childwindow' implementation rather than a patched one, giving different behavior as a result and causing Roblox to behave differently. Please try using DXVK instead.

Thanks for your investigation. Shall I close this issue and open one at flathub/org.vinegarhq.Vinegar for this problem?

wayzaction commented 1 month ago

I have the same issue, but choosing d3d11 + dxvk or opengl + dxvk is not an option because I have literally 4 to 5 fps with them. Is there anything we can do to make Vulkan work again?

UPD: And by the way, my vinegar is build by source, not from flatpak, I tried flatpak as well, but no luck

UPD2: I used official proton 9.0.2 and the problem was resolved. https://github.com/Kron4ek/Wine-Builds/releases?page=2

wayzaction commented 1 month ago

Okay, so, basically:

Use non-flatpak version Use Proton 9.0.2 from https://github.com/Kron4ek/Wine-Builds/releases?page=2 (use wineroot command)

and you can use vulkan

gresm commented 1 month ago

@wayzaction How? The proton builds are for 32 bit... Am I missing something?

Some-O-ne commented 1 month ago

@gresm Well, i downloaded the amd64 version and it works perfectly

wayzaction commented 1 month ago

@wayzaction How? The proton builds are for 32 bit... Am I missing something? image

This one is 64 bit. https://github.com/Kron4ek/Wine-Builds/releases?page=2

r3dm1 commented 1 week ago

@wayzaction How? The proton builds are for 32 bit... Am I missing something? This one is 64 bit. https://github.com/Kron4ek/Wine-Builds/releases?page=2 How do I set the wineroot to it? It always tells me wine64 is not present when setting it to bin