yuzu
yuzu copied to clipboard
yuzu-emu
Artifacts in Xenoblade Chronicles 3 with vulkan, a section of the game its impossible to see (Pentelas region).
Build: Yuzu EA 2888 Game version : 1.1.0 CPU : AMD Ryzen 5 5600X 6-Core Processor GPU : Rx 5700 VRAM : 8GB RAM : 32GB OS : Windows 11 Version 21H2 (Build 22000.832) Driver : 22.7.1
Inside uraya in chapter 3 there's a graphical glitch with the water using vulkan.
Log: yuzu_log.txt.old.txt
Save game: bf3game00a.zip
https://user-images.githubusercontent.com/110557543/182666527-ea2febf9-2d03-47f4-a423-eb6cf6456b84.mp4
I'm getting this exact same issue as well in the same area. It occurs zone-wide within the Pentelas region, but it's particularly pronounced around the Great Cotte Falls area where no matter which direction you look the game blinds you with those artifacts, likely from the waterfalls. It occurs with or without any mods and regardless of any settings I've tried (including adjusting resolution scaling, disabling the asynchronous shader building option, and changing accuracy levels from normal through extreme), though only in Vulkan - OpenGL doesn't have this issue.
If it weren't for this issue the game would probably be perfectly playable from start to finish in Vulkan for me given how the game runs and looks outside of this zone.
Build: Yuzu EA 2888 Game Version: 1.1.0 CPU: AMD Ryzen 9 3900X 12-Core Processor GPU: AMD Radeon RX 6700 XT VRAM: 12GB RAM: 32GB OS: Windows 10 Version 21H2 (Build 19044.1865) Driver: 31.0.12015.2001
Example screenshots (though the above video is also representative of what I see in motion):
I made a post on this as well, I uploaded my saves and logs, seems to be getting some traction. Is this on PC or Steamdeck
Same experience. When I start the area at the top the textures only glitch when I'm looking at a particular direction (generally east-ward) but the further down I get the more pronounced it gets until I'm at the bottom where it happens regardless of what direction I'm looking at.
Build: Yuzu EA 2890 Game version : 1.1.0 CPU : Intel Core i5-9400F GPU : RX580 VRAM : 8GB RAM : 16GB OS : Windows 10 21H2 (Build 19044.1826) Driver : 22.7.1
it seems that this artifact its not only happening in pantelas region, just before destroying the clock of colony gamma the artifact was present for a couple of seconds. There was no water around the artifact, maybe is not the waterfall or the water around colony lambda thats causing this error.
apparently yfc2 is the fix for this, same issue happened in xb2
What is yfc2 ?
Happening with me too, the entire region close to the waterfall is unplayable.
Build: Yuzu EA 2890 Game version : 1.1.0 CPU : Ryzen 5 3600 GPU : 5700 XT VRAM : 8GB RAM : 16GB OS : Windows 10 latest build Driver : 22.2.3
Just to confirm that this is happening on my side as well (AMD Vulkan, 6700XT, latest Yuzu build). I encountered this extreme epilepsy inducing flickering in a few cutscenes before, but now seems very prevalent in the Urayan Tunnels area and probably the upcoming Pantelas region as well. Hard to give up on Yuzu, though - the AMD FSR filter is just THAT good :)
If this happened in Xenoblade Chronicles 2 as well let's hope we can get a fix soon. Keep up the great work, Yuzu devs!
Exact same problem in the Urayan Tunnels when the camera is facing eastward. I'm 60 hours in. I hope they can fix it soon.
Build: Yuzu EA 2895 / VULKAN Game version: 1.1.0 + DLC and not Ad-ons CPU: Ryzen 7 3700x GPU: Radeon RX 5700XT / 8GB RAM: 32Gb DDR4 OS: Windows 11 Driver: 22.7.1
Exact same problem in the Urayan Tunnels when the camera is facing eastward. I'm 60 hours in. I hope they can fix it soon.
Particle issue submitted 12 days ago - so far no official update on that. This game breaking issue has almost a week and there's not even an acknowledgement from the dev team. I want to believe like you, but the situation is not looking too bright for us right now :(
Exact same problem in the Urayan Tunnels when the camera is facing eastward. I'm 60 hours in. I hope they can fix it soon.
Particle issue submitted 12 days ago - so far no official update on that. This game breaking issue has almost a week and there's not even an acknowledgement from the dev team. I want to believe like you, but the situation is not looking too bright for us right now :(
I'm new here.
If Yuze dev know about an issue they will post here? Or they will stealth fix and release in a new build and we have to download every new build and test it ourself?
Well. from the look of it. It seem dev just don't know or actually don't care. I mean if it hard to fix maybe dev should come in and tell us it hard and should take a long time to fix or something.
Some 'd say just use Opengl. Well I use amd and lastest driver will crash the game if I start any battle. If I roll back then it tank Vulkan performant hard. 10 fps in town and 20 fps outside. Right now my work around is use opengl for travel in this map and swap to Vulkan if I have to fight. Then I fight blind. Only thing I see is ui. I also see blind cutscene. I can still read text box and subtitle. It is a pain to did all this but what else I can do?
Exact same problem in the Urayan Tunnels when the camera is facing eastward. I'm 60 hours in. I hope they can fix it soon.
Particle issue submitted 12 days ago - so far no official update on that. This game breaking issue has almost a week and there's not even an acknowledgement from the dev team. I want to believe like you, but the situation is not looking too bright for us right now :(
I'm new here.
If Yuze dev know about an issue they will post here? Or they will stealth fix and release in a new build and we have to download every new build and test it ourself?
Well. from the look of it. It seem dev just don't know or actually don't care. I mean if it hard to fix maybe dev should come in and tell us it hard and should take a long time to fix or something.
Some 'd say just use Opengl. Well I use amd and lastest driver will crash the game if I start any battle. If I roll back then it tank Vulkan performant hard. 10 fps in town and 20 fps outside. Right now my work around is use opengl for travel in this map and swap to Vulkan if I have to fight. Then I fight blind. Only thing I see is ui. I also see blind cutscene. I can still read text box and subtitle. It is a pain to did all this but what else I can do?
I went through the hassle of going through Pentelas region with OpenGL, I have a save file right after the region.
Exact same problem in the Urayan Tunnels when the camera is facing eastward. I'm 60 hours in. I hope they can fix it soon.
Particle issue submitted 12 days ago - so far no official update on that. This game breaking issue has almost a week and there's not even an acknowledgement from the dev team. I want to believe like you, but the situation is not looking too bright for us right now :(
I'm new here.
If Yuze dev know about an issue they will post here? Or they will stealth fix and release in a new build and we have to download every new build and test it ourself?
Well. from the look of it. It seem dev just don't know or actually don't care. I mean if it hard to fix maybe dev should come in and tell us it hard and should take a long time to fix or something.
Some 'd say just use Opengl. Well I use amd and lastest driver will crash the game if I start any battle. If I roll back then it tank Vulkan performant hard. 10 fps in town and 20 fps outside. Right now my work around is use opengl for travel in this map and swap to Vulkan if I have to fight. Then I fight blind. Only thing I see is ui. I also see blind cutscene. I can still read text box and subtitle. It is a pain to did all this but what else I can do?
I went through the hassle of going through Pentelas region with OpenGL, I have a save file right after the region.
What settings are you using with OpenGL? Because I've tried to use it but Yuzu crashes and closes when the camera is facing eastward (where the glitch occurs with Vulkan). My hardware:
Build: Yuzu EA 2895 Game version: 1.1.0 + DLC and not Ad-ons CPU: Ryzen 7 3700x GPU: Radeon RX 5700XT / 8GB RAM: 32Gb DDR4 OS: Windows 11 Driver: 22.7.1
The only alternatives for AMD users are:
-
Buy an Nvidia GPU.
-
Roll back to 22.6.1 drivers and play the entire Pentelas region in 3-15 FPS - but that's rather miserable.
-
AMD releasing a new driver that fixes OpenGL crashes in 22.7.1 and brings us improved performance - although considering latest driver was released on 25th of July it's going to be at least a month before the next one.
-
Wait for the Yuzu devs to save us.
The only alternatives for AMD users are:
- Buy an Nvidia GPU.
- Roll back to 22.6.1 drivers and play the entire Pentelas region in 3-15 FPS - but that's rather miserable.
- AMD releasing a new driver that fixes OpenGL crashes in 22.7.1 and brings us improved performance - although considering latest driver was released on 25th of July it's going to be at least a month before the next one.
- Wait for the Yuzu devs to save us.
Well, I rolled back the drivers to 22.6.1 and tried to play with OpenGL but it was an awful experience. Constantly jumping from 0 to 20fps and very blurry graphics compared to Vulkan. I don't think I can go this way.
Well, I rolled back the drivers to 22.6.1 and tried to play with OpenGL but it was an awful experience. Constantly jumping from 0 to 20fps and very blurry graphics compared to Vulkan. I don't think I can go this way.
Same. Someone mentioned they played for 4 hours at 10FPS to get through the area, but I'm not really sure that's worth it.
The devs are aware of this issue, but there's no ETA. It depends on their priorities. I recommend everyone joining the Yuzu discord server where you can follow the #yuzu-updates channel which lists all the fixes and improvement coming in every released version. That way you no longer have to guess what is coming :) And of course, support their cause if your wallet allows it.
Running on Linux for the OpenGL performance is probably the best bet until this is fixed. There's a few glitchy shadows and plants, but otherwise it makes Pentelas playable 30fps. The big thing is to keep an eye on swap, since Yuzu seems to have a memory leak running OpenGL with this game. Save and close and reopen Yuzu when swap fills up before the OOM killer takes it out unexpectedly.
Running on Linux for the OpenGL performance is probably the best bet until this is fixed. There's a few glitchy shadows and plants, but otherwise it makes Pentelas playable 30fps. The big thing is to keep an eye on swap, since Yuzu seems to have a memory leak running OpenGL with this game. Save and close and reopen Yuzu when swap fills up before the OOM killer takes it out unexpectedly.
That's interesting. I tried looking into that earlier and the posts I've found mentioned that it wasn't really worth it to try Linux with AMD cards. I imagine getting Linux set up is quite a lengthy process and you can't do it on an USB stick for example... :/
You could use a Live ISO from a linux distribution. My experience with XC3 on Linux (Until begin of Chapter 4) using EA:
- Playable with Vulkan until the middle of Chapter 3, then you need to switch to OpenGL for the Pentelas Region and play it with OpenGL. I heard that you can switch to Vulkan again after leaving that region, but i am still in that region.
And the OpenGL Performance: 30 FPS with some stutters when the shaders getting built and some graphic glitches (AMD RX 6900 XT)
That's interesting. I tried looking into that earlier and the posts I've found mentioned that it wasn't really worth it to try Linux with AMD cards. I imagine getting Linux set up is quite a lengthy process and you can't do it on an USB stick for example... :/
I tried Ubuntu 22.04, Pop OS, Manjaro and Fedora. Only Ubuntu gave me issues. Pop and Manjaro worked out of the box, but OpenGL with SPIR-V resulted in an immediate crash. Fedora ran Yuzu with OpenGL/SPIR-V just fine. At least for me. All with a 5700 xt. Installation of all them was really simple, although I installed them to a partition. 22-30fps, the only real choppiness was building shaders.
So I wanted to come back with an update for future stragglers reaching this location. As of now:
- 22.8.1 drivers still crash with OpenGL (haven't tried 22.8.2 but pretty sure nothing major changed)
- This issue is not occurring on Nvidia cards.
- It will take months, if not more for this issue to be fixed in Yuzu for AMD cards. So don't hold your breath for a fix anytime soon. Most likely applies for the missing flute particles issue as well.
- As confirmed by above posters, Linux is the savior of AMD users with a caveat - OpenGL suffers from a memory leak which will result in a crash after some time. I personally used the Manjaro plasma desktop version. Setting up a 16GB swap file on your Linux installation will allow you to extend the duration of your playtime from 20-30 mins to maybe an hour if you already have 16GB of RAM so just save and close Yuzu from time to time (you can monitor memory and swap file usage with "free -h" command). Or you can play on your Switch for the area with issues, but "switching" saves between Windows and Linux turned out to be more convenient for me. Keep in mind that graphical mods also work on Yuzu OpenGL Linux version, even if it's going to look more washed out due to missing AMD GPU features like sharpening, FSR, saturation, etc).
Very important existential notes for AMD users:
- Make sure to use Radeon Image Sharpening (I use it at 60%) - this combined with AMD FSR filter on Yuzu will bring you fantastic clarity on character and environment details.
- Make sure to use GPU EXTREME accuracy when playing on Vulkan (Windows). This will grant you smooth 30 FPS most of the time (tested on a 6700XT)
- theboy181 has made some LIFE CHANGING mods that I recommend: 2K resolution mod, disable scaling mod(required for 2k mod), improved LOD mod, improved DOF mod. Make sure to get these mods as they will transform your XC3 game into a breathtaking visual experience. No more poor quality textures - now you can spend additional time just gazing at your favorite characters and landscapes.
What a great adventure this was. AMD users need to suffer a bit but in the end I can say it's well worth it.
Remember to continue supporting your favorite companies Nintendo and Monolithsoft, your favorite emulator - Yuzu - you can support their cause on Patreon while ensuring they can hire more GPU devs to bring us even faster fixes and of course theboy181 for bringing us so much joy with his mods.
* Make sure to use GPU EXTREME accuracy when playing on Vulkan (Windows). This will grant you smooth 30 FPS most of the time (tested on a 6700XT)
For me Normal is the best performing option (FPS drops significantly for me on High and Extreme completely kills performance and makes the game virtually unplayable) even with a 6700XT, in Vulkan or OpenGL on Windows 10. I've seen people suggest that tweak for Xenoblade games constantly but until now I just assumed it was some odd Nvidia quirk but now that I'm seeing someone mention that it actually helped them with an AMD card I just had to chime in and say it's not like this for everyone.
Actually, related to this, I'm noticing an issue where randomly the volumetric clouds in the sky and such will disappear when playing on Normal accuracy. You can bring them back by switching to High or Extreme accuracy, however FPS then drops again. When this happens I need to restart the game for the clouds to show once more on Normal accuracy without the FPS penalty that the higher accuracy settings inflict on me.
Finally, I've noticed that the vertex explosion or.. whatever you want to call it that destroys the experience on Vulkan in the third zone also occurs elsewhere in the game randomly. I can play for hours without any issues and then suddenly characters will explode (often during cutscenes). Restarting the game helps to clear that up when it happens there at least.
For me Normal is the best performing option (FPS drops significantly for me on High and Extreme completely kills performance and makes the game virtually unplayable) even with a 6700XT, in Vulkan or OpenGL on Windows 10. I've seen people suggest that tweak for Xenoblade games constantly but until now I just assumed it was some odd Nvidia quirk but now that I'm seeing someone mention that it actually helped them with an AMD card I just had to chime in and say it's not like this for everyone.
If you have a 6700XT with latest drivers you should have the same experience assuming that:
- You're using one of the latest Yuzu versions
- Multicore CPU emulation is enabled. CPU accuracy is set to AUTO. Resolution is set to 1x (!). All graphics and advanced graphics settings (checkbox ones) are enabled in Yuzu except VSYNC. NVDEC emulation is set to your GPU and not your CPU.
- You have "Instant replay" and "Record desktop" enabled in AMD software for maximum performance as described here, scroll towards the bottom section: https://yuzu-emu.org/entry/yuzu-progress-report-jul-2022/
GPU accuracy seems to have an additional impact on CPU (the emulation heavy lifting is mainly done by the CPU as far as I understand), so it's possible that you're being bottlenecked by your CPU. There's literally no reason why Extreme would work different on the same GPU, except improper Yuzu configuration parameters and/or a lacking CPU. OR... Yuzu using your integrated GPU instead of your dedicated one :) Characters exploding all of a sudden sounds... kind of scary.
For me Normal is the best performing option (FPS drops significantly for me on High and Extreme completely kills performance and makes the game virtually unplayable) even with a 6700XT, in Vulkan or OpenGL on Windows 10. I've seen people suggest that tweak for Xenoblade games constantly but until now I just assumed it was some odd Nvidia quirk but now that I'm seeing someone mention that it actually helped them with an AMD card I just had to chime in and say it's not like this for everyone.
If you have a 6700XT with latest drivers you should have the same experience assuming that:
* You're using one of the latest Yuzu versions * Multicore CPU emulation is enabled. CPU accuracy is set to AUTO. Resolution is set to 1x (!). All graphics and advanced graphics settings (checkbox ones) are enabled in Yuzu except VSYNC. NVDEC emulation is set to your GPU and not your CPU. * You have "Instant replay" and "Record desktop" enabled in AMD software for maximum performance as described here, scroll towards the bottom section: https://yuzu-emu.org/entry/yuzu-progress-report-jul-2022/GPU accuracy seems to have an additional impact on CPU (the emulation heavy lifting is mainly done by the CPU as far as I understand), so it's possible that you're being bottlenecked by your CPU. There's literally no reason why Extreme would work different on the same GPU, except improper Yuzu configuration parameters and/or a lacking CPU. OR... Yuzu using your integrated GPU instead of your dedicated one :) Characters exploding all of a sudden sounds... kind of scary.
This happens with the latest versions of Yuzu and regardless of any of the other settings. I'm also manually raising my minimum frequency for the extra performance so I don't need the instant replay workaround, and I'm using 22.8.1.
As for my CPU, it's a 3900x so it's not exactly a complete slouch even if it's not top-of-the-line (and doesn't have integrated graphics to even bother with). I would assume that higher GPU accuracy would shift more of the load towards the 6700XT though, so I don't exactly see how this would be the CPU's fault. I mean the game runs fine on normal accuracy for me otherwise, well above 30FPS most of the time, but higher accuracy does nothing to boost performance like people claim, at least for me.
In fact as of testing right now after double checking all of the above settings and standing at the Eternal Canopy in Erythia Sea with only a 60FPS mod enabled (merely to get past the default 30FPS limit for the purposes of comparison), I'm getting 55 FPS with GPU Accuracy set to Normal, 45 with High, and around 4 FPS most of the time which is clearly unplayable (if you don't move the camera or do anything then eventually it raises back up to similar FPS to what High gets but that's definitely not what I'd consider 'playable').
I noticed that my clock speeds were dropping hard with the higher accuracy settings (especially when set to Extreme) so I applied the Instant Replay/Record Desktop tweak to see if that helped. It definitely raised my GPU clock even further by a slight amount but it did nothing to stop the drops in frequency and performance.
All in all, even if it weren't for the odd clock fluctuations there's a definite and noticeable performance hit for me using anything above Normal GPU Accuracy. I suppose it really could just be some weird quirk of my CPU and GPU combination but nothing else I can think of seems to help to make the higher accuracy settings faster than Normal.
Sorry to hear about your special situation. As a fellow AMD GPU user I know how painful it can be to troubleshoot certain issues. Your CPU should be up to the task. They way you're describing it, there is something that causes that drop to 4 FPS when moving on extreme. Should you install Linux and test OpenGL on High accuracy (and be able to get mostly 30FPS when shaders are not loading) you could confirm that it's not a potential issue with your PSU/GPU/RAM. I'm guessing you already tried to factory reset the AMD drivers (also disable Anti-Lag and Enhanced Sync features).
Anyway, since you mentioned "some weird quirk of my CPU and GPU combination" this popped into my mind (as I have an Intel I9 CPU and can't use this feature anyway): https://community.amd.com/t5/drivers-software/performance-issues-with-smart-memory-access-on-pci-express-3-0/td-p/514505
Sorry I couldn't help more. Maybe you can join the Yuzu Discord and see if anyone has better ideas. Yuzu supporters on Patreon benefit from better live tech support, so if you can afford that it might help you get closer to a resolution (you don't need to be a supporter to join DS though).
Good luck!
@skill-face
I noticed that my clock speeds were dropping hard with the higher accuracy settings (especially when set to Extreme) so I applied the Instant Replay/Record Desktop tweak to see if that helped. It definitely raised my GPU clock even further by a slight amount but it did nothing to stop the drops in frequency and performance.
Sounds like a throttling problem.
Check with XTU if supported or ThrottleStop (on throttlestop click on "limit" to see who is going to limit performance).
If something limits, what it is is written there
Exact same problem in the Urayan Tunnels when the camera is facing eastward. I'm 60 hours in. I hope they can fix it soon.
Particle issue submitted 12 days ago - so far no official update on that. This game breaking issue has almost a week and there's not even an acknowledgement from the dev team. I want to believe like you, but the situation is not looking too bright for us right now :(
I'm new here. If Yuze dev know about an issue they will post here? Or they will stealth fix and release in a new build and we have to download every new build and test it ourself? Well. from the look of it. It seem dev just don't know or actually don't care. I mean if it hard to fix maybe dev should come in and tell us it hard and should take a long time to fix or something. Some 'd say just use Opengl. Well I use amd and lastest driver will crash the game if I start any battle. If I roll back then it tank Vulkan performant hard. 10 fps in town and 20 fps outside. Right now my work around is use opengl for travel in this map and swap to Vulkan if I have to fight. Then I fight blind. Only thing I see is ui. I also see blind cutscene. I can still read text box and subtitle. It is a pain to did all this but what else I can do?
I went through the hassle of going through Pentelas region with OpenGL, I have a save file right after the region.
link for the safe would be appreciated
