[Bug 52283] New: After loading roblox studio, some menus are shifted and blinking
https://bugs.winehq.org/show_bug.cgi?id=52283 Bug ID: 52283 Summary: After loading roblox studio, some menus are shifted and blinking Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: waldirio(a)gmail.com Distribution: --- Hi, After loading the roblox studio via wine, I can see the main screen, all templates, resize the window and no issue at all. However, when loading any project, and here I'm using the Baseplate as example, some menus will be shifted and blinking all the time, for example "Toolbox" or "Asset Manager". The version in question wine-6.21-1.fc34.x86_64 over Fedora 34 --- $ cat /etc/redhat-release Fedora release 34 (Thirty Four) --- Attached I'm going to add some screenshots, via winecfg, I set "Windows 10" as windows version and also added some different versions of direct. I'm also adding the dxdiag screen, I can see some dll's are missing. I'm not sure if they could be the root cause of this behavior. Thank you in advance for your help. Waldirio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #1 from Waldirio <waldirio(a)gmail.com> --- Created attachment 71411 --> https://bugs.winehq.org/attachment.cgi?id=71411 pdf file with some pictures -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #2 from Waldirio <waldirio(a)gmail.com> --- Also, I tried some additional tests - Updating fedora (getting the latest updates available) - Changing the X server (Xorg and Wayland), similar behavior Not sure what can be at this moment. Thank you Waldirio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #3 from Waldirio <waldirio(a)gmail.com> --- Created attachment 71412 --> https://bugs.winehq.org/attachment.cgi?id=71412 the list of wine packages and the complate output when loading roblox studio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #4 from Waldirio <waldirio(a)gmail.com> --- Created attachment 71413 --> https://bugs.winehq.org/attachment.cgi?id=71413 opening roblox and presenting the issue -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 Josesk Volpe <joseskvolpe(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joseskvolpe(a)gmail.com --- Comment #5 from Josesk Volpe <joseskvolpe(a)gmail.com> --- I'm afraid DXVK is not supported by the Wine team. Please retest it using plain Wine D3D implementation. Please report this DXVK bug to their developers: https://github.com/doitsujin/dxvk/ I can confirm issues with DXVK. On my hardware, Roblox Studio don't open at all and presents that my Video card is "too old" However, on my experimentation Roblox Studio is usable on Plain WineD3D, with minor flickering issues that stops at time and doesn't affects usability like in the video. Using Wine 6.20 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #6 from Waldirio <waldirio(a)gmail.com> --- Hello Josesk, Thank you for your quick response. I'm not using DXVK, in fact, when trying it, the roblox studio didn't start. In your libraries, could you share what is your current setup? Also, when adding the Toolbox, I believe you are not facing the same behavior as I'm. Is that right? Thank you! Waldirio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #7 from Waldirio <waldirio(a)gmail.com> --- Hi, I just added the missing dll's under `~/.wine/drive_c/windows/syswow64`, now, dxdiag.exe is no more presenting missing DLLs. However, the roblox studio is still presenting the same behavior. Thank you Waldirio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #8 from Waldirio <waldirio(a)gmail.com> --- Created attachment 71414 --> https://bugs.winehq.org/attachment.cgi?id=71414 dlls in dxdiag.exe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #9 from joaopa <jeremielapuree(a)yahoo.fr> --- It is always better to report a bug without using any native dll. Usually, configuration with native dlls are not supported in this bugzilla. Anyway, if your software does not work with a builtin dll, wine must be fixed. So remove your .wine folder and report back. rm -fR .wine Lauch your software And attach the console output. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #10 from Waldirio <waldirio(a)gmail.com> --- Created attachment 71417 --> https://bugs.winehq.org/attachment.cgi?id=71417 new log with no .wine dir -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #11 from Waldirio <waldirio(a)gmail.com> --- Hello Joao, Thank you for your response. ~/.wine removed and the app was loaded once again. Same behavior, just FYI. Thank you Waldirio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #12 from Josesk Volpe <joseskvolpe(a)gmail.com> --- (In reply to Waldirio from comment #6)
Hello Josesk,
Thank you for your quick response. I'm not using DXVK, in fact, when trying it, the roblox studio didn't start.
In your libraries, could you share what is your current setup? Also, when adding the Toolbox, I believe you are not facing the same behavior as I'm. Is that right?
Thank you! Waldirio
¡Sure! I'm running Roblox Studio in a separate clean wineprefix without DLL overwrites. So the libraries settings are empty Yeah, i'm not facing the same behavior as you're. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #13 from Waldirio <waldirio(a)gmail.com> --- Hello friends, good morning I can confirm that in version 7.0.rc3-1.2 it's working as expected. --- $ rpm -qa | grep wine wine-staging64-7.0.rc3-1.2.x86_64 wine-staging-common-7.0.rc3-1.2.i686 winehq-staging-7.0.rc3-1.2.x86_64 --- Attached is the picture. No more flicking or issues. I believe we can archive this BZ, please, feel free to add a tag to mention that it was fixed on this specific version. Thank you Waldirio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #14 from Waldirio <waldirio(a)gmail.com> --- Created attachment 71442 --> https://bugs.winehq.org/attachment.cgi?id=71442 menu in the correct place and no more flicking -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #15 from joaopa <jeremielapuree(a)yahoo.fr> --- If the bug is fixed, you can close it as FIXED. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 Waldirio <waldirio(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #16 from Waldirio <waldirio(a)gmail.com> --- Fixed/Tested in the below version --- $ rpm -qa | grep wine wine-staging64-7.0.rc3-1.2.x86_64 wine-staging-common-7.0.rc3-1.2.i686 winehq-staging-7.0.rc3-1.2.x86_64 --- Thank you Waldirio -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #17 from joaopa <jeremielapuree(a)yahoo.fr> --- It is better to test with plain wine (not staging) Can you confirm that all is fine with plain wine-7.0-rc3. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 Waldirio <waldirio(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED |--- --- Comment #18 from Waldirio <waldirio(a)gmail.com> --- Hi, I'm checking on the current wine repos and this is what I can see --- # grep 7.0.rc3 /tmp/all.txt | grep ^wine wine-devel.i686 1:7.0.rc3-1.1 WineHQ wine-devel.src 1:7.0.rc3-1.1 WineHQ wine-devel-common.i686 1:7.0.rc3-1.1 WineHQ wine-devel-common-debuginfo.i686 1:7.0.rc3-1.1 WineHQ wine-devel-debuginfo.i686 1:7.0.rc3-1.1 WineHQ wine-devel-debugsource.i686 1:7.0.rc3-1.1 WineHQ wine-devel-debugsource.x86_64 1:7.0.rc3-1.1 WineHQ wine-devel-devel.i686 1:7.0.rc3-1.1 WineHQ wine-devel64.x86_64 1:7.0.rc3-1.1 WineHQ wine-devel64-debuginfo.x86_64 1:7.0.rc3-1.1 WineHQ wine-devel64-devel.x86_64 1:7.0.rc3-1.1 WineHQ wine-staging.i686 1:7.0.rc3-1.2 WineHQ wine-staging.src 1:7.0.rc3-1.2 WineHQ wine-staging-common.i686 1:7.0.rc3-1.2 WineHQ wine-staging-common-debuginfo.i686 1:7.0.rc3-1.2 WineHQ wine-staging-debuginfo.i686 1:7.0.rc3-1.2 WineHQ wine-staging-debugsource.i686 1:7.0.rc3-1.2 WineHQ wine-staging-debugsource.x86_64 1:7.0.rc3-1.2 WineHQ wine-staging-devel.i686 1:7.0.rc3-1.2 WineHQ wine-staging64.x86_64 1:7.0.rc3-1.2 WineHQ wine-staging64-debuginfo.x86_64 1:7.0.rc3-1.2 WineHQ wine-staging64-devel.x86_64 1:7.0.rc3-1.2 WineHQ winehq-devel.i686 1:7.0.rc3-1.1 WineHQ winehq-devel.x86_64 1:7.0.rc3-1.1 WineHQ winehq-staging.i686 1:7.0.rc3-1.2 WineHQ winehq-staging.x86_64 1:7.0.rc3-1.2 WineHQ --- Only devel and staging at this moment. I'm not sure if you have already some plain 7.0 available. Please, let me know and for sure I can test. Thank you! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 Waldirio <waldirio(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #19 from Waldirio <waldirio(a)gmail.com> --- Hi, Updating here --- # grep winehq /tmp/all.txt winehq-devel.i686 1:7.0.rc3-1.1 WineHQ winehq-devel.x86_64 1:7.0.rc3-1.1 WineHQ winehq-stable.i686 1:6.0.2-2.1 WineHQ winehq-stable.x86_64 1:6.0.2-2.1 WineHQ winehq-staging.i686 1:7.0.rc3-1.2 WineHQ winehq-staging.x86_64 1:7.0.rc3-1.2 WineHQ --- So, when installing the stable version, as below, the issue is not around also. --- # rpm -qa | grep wine wine-stable64-6.0.2-2.1.x86_64 wine-stable-common-6.0.2-2.1.i686 winehq-stable-6.0.2-2.1.x86_64 --- I'll keep moving on this version from now. Ps.: One behavior that I noticed, when clicking on "Terrain Editor", the menu was not opening on the left menu, the workaround was just proceed with the right click on the top menu and click over "Terrain Editor". For any reason that I'm not aware, after closing/reopening, the button on the top menu is working ..., I removed the .wine, reinstall the app and the behavior it's working now ... maybe some cache .. I'm not sure. Thank you all for your help. Just to keep on track, below you can see the steps to put the stable version on Fedore 34 https://wiki.winehq.org/Fedora --- # dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/34/winehq.repo # yum install winehq-stable --- I hope this helps. Waldirio // Archiving this BZ from now. Happy New Year!!! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #20 from joaopa <jeremielapuree(a)yahoo.fr> --- It is always better to report a bug against the latest devel version of wine, because stable can be far behind. When you report a bug again the stable version, usually, one requests you try with the latest devel version to be sure the bug is not already fixed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #21 from Waldirio <waldirio(a)gmail.com> --- Hello Jeremie, Thanks for your help and explanation. Indeed, normally, I try to fill the bz in the latest version. Once I'm using Fedora, I was "believing" that the Fedora was delivering the latest version ... I'm not confident anymore on that. :-) Anyway, based on the page [1], I believe we are talking about the latest version for Fedora 34 and 35 Stable branch - I believe to be the stable and latest version Development branch - Some are with some new features/testing/nightly maybe Staging branch - No idea :-) Thank you!! Waldirio [1]. https://wiki.winehq.org/Fedora -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #22 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 7.0-rc4. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 jrelvas(a)proton.me changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrelvas(a)proton.me --- Comment #23 from jrelvas(a)proton.me --- Good afternoon. I wish to reopen this report as I can confirm that it happens with the latest staging release, 8.16, with both WineD3D and Roblox Studio's own OpenGL renderer. (Note: It was not reintroduced in 8.16, it also happens with other versions, afaik, every single 8.x release is affected.) This flickering isn't just the only problem; the widgets that are flickering also slow down the program's performance to a crawl, for some reason. The only solution is to close the offending widgets. FYI, this is likely caused by the fact that many widgets in Roblox Studio are not rendered by QT, but rather by the engine itself. Evidently, all such widgets are guilty of the flickering and slowdown issue. I work with the program's internals (I use their developer SDK), so I'm aware of which widgets are rendered natively by the engine and which ones are actual QT UI. If I should make a new report instead of commenting here, please let me know. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #24 from jrelvas(a)proton.me --- Some additional information I was able to discover: If I offload rendering to my NVIDIA gpu, the widgets have no flickering, but all engine-rendered widgets and the main (game) view turn pitch black instead. Closing all offending widgets restores the game view's image. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 CC| |z.figura12(a)gmail.com --- Comment #25 from Zeb Figura <z.figura12(a)gmail.com> --- Reopening. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52283 --- Comment #26 from jrelvas(a)proton.me --- Another status update: This bug does not seem to be present with wine's Vulkan renderer (via DXVK or native vulkan), but the lack of childwindow support means that said renderer cannot be used unless an external patch is applied. (I think this pretty much confirms the issue is within d3d) For anyone running mainline Wine, Roblox Studio is practically impossible to use unless you don't use the majority of its tools. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla