Custom Textures + Texture Filter = swapped texture bug

Whenever I use custom textures with texture filter, it loads fine, but when I change maps (playing Fantasy Life) the textures bug out. If I save state and load state, it resets fine, but when I change maps again, or even open the menu, the textures bug again.

System Information

  • Operating System: Windows 10
  • CPU: Ryzen 5 3600x
  • GPU: RX 580
  • Citra Version (found in title bar): Nightly1727/Canary 1997
  • Game: Fantasy Life
  • Screenshot of Issue (include the full Citra window including titlebar):

Diagnostic Log
Upload your log file as an attachment by dragging & dropping.
citra_log.txt (2.0 MB)

System Information for Support

Client Version                                Nightly 1727 HEAD-6183b5d
Operating System                              Windows 10 (10.0)
CPU                                           AMD Ryzen 5 3600X 6-Core Processor              | AVX2 | FMA
Graphics API                                  OpenGL 3.3.1
Graphics Renderer                             Radeon RX 580 Series
GPU Driver Version                            21.10.1 30.0.13025.1000
CPU JIT                                       [x]
Hardware Renderer                             [x]
Hardware Shader                               [x]
Hardware Shader, Accurate Multiplication      [x]
Shader JIT                                    [x]
System Region                                 -1
Shader Disk Cache                             [x]

Here’s some issues I found with your log that might help.

  • Due to AMD’s poorly optimized OpenGL driver, you may experience slowdowns.

This is a known issue that was introduced a while ago. The developer that introduced the issue was unable to figure out what’s causing it. Currently, you can only use either custom textures or a texture filter. Using both results in the behavior you’ve experienced.

Yeah, I’ve had the issue for a long time. Do I have access to old citra builds when the bug hadn’t been introduced yet? (I remember playing FL fine back then) If so, do you know what was the last build without the bug?
Edit: I know where to download old builds from (github). Now I just have to find a build without the bug.
Edit2: Found it! The last version without the bug is 1691 (nightly). I’ll leave this here for anyone interested.

1 Like

Thanks for coming back to post your find on build 1691. I too am having the same issue and rolling back to 1691 solves it without other issues that I can find.