[Xenoblade Chronicles X] [Vulkan] Graphical Corruption/Flickering in certain menus #1011
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
log.txt
When in the Game Options menu in Xenoblade X (in-game, not sure if this happens on the title screen as well), there is inconsistent but fast graphical corruption/flickering occuring. The corruption would also very in intensity at random, sometimes weak and only affecting small parts of the screen, and sometimes affecting all of it. The flickering was too fast for me to take a screenshot of. Moving around the options menu might amplify the issue, but I'm not sure.
When in the Skell menu (the terminal in the BLADE Barracks) and customizing the Skell's equipment, there is full screen flickering black and white, also affecting the UI (This is what the attached screenshot shows). I've also seen it occur isolated to just the Skell, flickering between fullbright white and black.
I have not tested Skell submenus other than equipment, but it seems to not happen in the main Skell menu, only when in the equipment submenu.
Detailed system specs are in the log, but I am using:
Ryzen 9 5900X
Radeon RX 6700 XT
32GB DDR4 RAM
KUbuntu 22.04.3 LTS
Cemu 2.0-59 AppImage
Vulkan Renderer/Asyc Compile on/Accurate Barriers on
Vsync is off
I played some more of the game and found 2 more scenarios in which this bug occurs:
Specifically when opening the Yes/No prompt for upgrading an Art
When going to the Shop menu for Skells and browsing purchasable equipment
Edit: I have found another instance, that being when in the character equipment menu and browsing your equipment.
Edit 2: I've found a fourth instance that occurs in the pop up that shows whenever an Arms Manufacturer levels up.
I’m also having this issue (flickering in the equipment select screen). I’ve tried changing graphics pack settings (change resolution to default, 30fps, revert to default) and nothing has worked so far.
I’m using:
AMD Ryzen 7 7800X3D
Radeon RX 7800 XT
64GB DDR4 RAM
Arch Linux
Cemu built from GitHub
Vulcan Renderer/Async Compile On/Accurate Barriers On
V-sync Triple Buffering (issue still occurs with V-sync off)
This could be an issue with the graphics card as we are both using the same card.
I am having the same issue "flickering in the equipment select screen" I have also tried changing graphics pack settings and more nothing has worked.
AMD Ryzen 5 1600 6-core
Windows 10 Home 64bit
Cemu version 2.0.4.9
16GB Ram
Vulcan Renderer/Async Compile On/Accurate Barriers On
V-sync Triple Buffering "issue still occurs with V-sync off"
DX 12
Nvidia Geforce GTX 1050ti 4GB
I do not think it is the video cards as we do not have the same and I am having the exact same issues.
Good to know that it's not just isolated to a single configuration. In the mean time I've found another instance of the bug, which occurs in the menu where you can change around/view your soul voices. I've also found this to occur on the Flatpak version of Cemu as well.
Thank you for that info, I just tried the latest test build of cemu 2.0-59 and I have not ran into this problem with it yet, But I only tested it for a min. I will do more testing now.
https://github.com/cemu-project/Cemu/assets/127622115/43d0a7e2-6e25-43f4-96c6-da65e264432e
I've recorded a video to present to demonstrate some of these issues.
Ironically enough however, my recordings seem to be having graphical issues of their own that show up through the whole video, and I'm not sure how to fix them. They may or may not show up for you, but it's just some black flickering that comes from the bottom of the screen. Other than that the video should be perfectly watchable.
Edit: They seem to be gone when watching the video after posting it, so it is probably an issue on my end. The video works perfectly otherwise.
The problem is still there for me also after more testing.
I get this as well, the shop menu especially is epilepsy inducing - a workaround I've found is switching to OpenGL instead of Vulkan (which is annoying, Vulkan gets me much more stable framerates with FPS++ but oh well). The problem was evident before I started using FPS++ or any other graphics pack, so that's not the cause.
Specs:
Windows 11 Home
AMD Ryzen 5800H
Nvidia GeForce RTX 3060 (laptop version)
16GB RAM
cemu 2.0-59 with Vulkan, tested multiple settings and it's there
Just tested on the recently-released Cemu 2.0-60, and I can confirm that the issue is still present.
I just tested its the same for me also. I hope it can be fixed soon if possible.
I found this thread on google and made an account to say I have the same issue. In the menu to change weapons it gradually flickers and in the shop menu it flickers intensely. *It happens in weapon menus but not armour. I don't have a skell yet but it also happens in the skell frame shop menu.
Thanks to a tip from someone on the discord, I was asked to test this on 2.0-51 and can confirm it does not occur there on the AppImage version. It is still an issue on latest (2.0-61) however.
I was having the same problem using a Lenovo Legion Go. I also confirm that going from 2.0-61 to 2.0-51 solved the issue for 11. I forgot to mention the Legion Go is on Windows 11.
Same problem
Ryzen 5 3600
Rx 5600 Xt
Confirmed working for me now by going back to 2.0-51
Yes 2.0-51 working but from that its a mess.
Was getting intense flickering even in the settings menu on the title screen, but rolling back to 2.0-51 fixed all Vulkan flickering issues (including the inventory flickering in BOTW). Hope the devs look into this sooner rather than later.
I'm going to try with this version, I come from 2.0-65 and it is impossible to play the game like this.
Can confirm 2.0-51 doesn't have the flickering issue while other versions do. Running on a ryzen 5500 cpu and an amd rx6600.
For me its seams fixed on lastest version.
Yes, looks like it's fixed as of 2.0-66.
I'll test it out on latest Cemu later today and see if it's fixed
Test on Cemu 2.0-66 (Flatpak), this issue does seem to have been resolved!