Emulator Issues #13128
openXenoblade Chronicles bloom on title screen is much stronger than console
0%
Description
Xenoblade Chronicles (SX4E01, USA, Good dump, ISO/RVZ)
What's the problem? Describe what went wrong.
During the sunset part of the title screen sequence, bloom is way too large. On console you can see nice dramatic clouds in the sunset, but on Dolphin that whole part of the screen is basically a solid orange color.
Dolphin is accurate here with the software renderer, but all other backends have this issue no matter what settings I try to change. I mainly tested things at native Internal Resolution, but this setting is odd as the title screen is part of the EFB or something, so increasing resolution only works with Scaled EFB Copy enabled. When that setting is enabled, changing IR does nothing to the bloom, everything just becomes HD as it should. However if Scaled EFB Copy is disabled, increasing the resolution slightly reduces bloom, but only on even numbered IR scales? Some settings do decrease the bloom a little bit, like 8xMSAA or Disable EFB VRAM Copies, but none of these are real solutions.
Using a bloom gecko code is helpful, but they're all slightly off and tend to mute the pink sunset colors a bit.
Please note I've looked at nothing but the title screen, and have no idea about the state of things like torches or lamps
What steps will reproduce the problem?
Just boot up the game and fast forward a bit. Once the sun starts setting, you'll soon see an orange color fill up the top right of the screen. The sunset lasts a while, so you can easily make a save state to check out the scene in the software renderer.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
I tested most things on the beta build 5.0-17995, but I updated to the latest dev version 5.0-18078 and its still there
Is the issue present in the latest stable version?
Yeah, 5.0 has it. So does 4.0 and 3.5, but 3.0 is strange.
Stable 3.0 is the only version I tested that doesn't completely mess up the scene at default settings. The bloom is still wrong, but at least its not covering the entire top right of the screen. Something else I only saw on 3.0 is that the graphics get very blurry right when the sunset starts, like the game has just changed something, then when sunset turns to night, the game goes back to the normal blocky low res graphics.
The earliest dev build I could find on the website was 3.0-749, but at default settings it does the heavy bloom like every other Dolphin version. However if you change the EFB Copies setting to RAM, you still get bad bloom but its a unique form of bad. This EFB Copies thing worked on 3.0-749, 3.0-936, and 3.0-937 aka 3.5-0, but I couldn't get stable 3.5 to do this.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
I've got a three frame fifolog but I don't know if it'll help anything. It was recorded in either 5.0-17995 or 5.0-18078.
I've also got some screenshots, plus I made some comparison images because I've got nothing better to do
What are your PC specifications? (CPU, GPU, Operating System, more)
AMD R5 3600
Nvidia 1050 (driver 516.94)
Windows 10 Home 21H2 Build 19044.2364
I've also tested it on someone else's computer with a R7 3700x and 3060 ti (unknown drivers / windows 10). I haven't tried any AMD or Intel GPUs.
Android 5.0-17269 (from F-Droid) also has the issue.
Is there anything else that can help developers narrow down the issue?
This probably doesn't help, but you can easily find old youtube videos that show title screen on Wii or Dolphin
Here's an old Wii video, check out the right side starting around 1:45: https://youtu.be/3OZoockxQmY
Even this classic 2011 Dolphin video has the error in it starting around 1:37: https://youtu.be/wgPcl1WJ98Y
Files