MHXX crashes after choosing character and entering village

Citra Support
1

Issue:
Game loads fine until after choosing character and loading first village. Then drops to 3fps and freezes while maxing out gpu.

  • Operating System: Windows 10

  • CPU: Ryzen 2600X

  • GPU: RX550 4GB

  • Citra Version : Nightly 1887
    citra_log.txt.old.txt (329.8 KB)

  • Game: Monster Hunter XX 1.4 English Patch V5:

2

Your log file is showing several unmapped errors. This is usually caused by a corrupt ROM. You will have to redump your game (hopefully that fixes it)

3

I will try that now thanks

4

citra_log.txt.old.txt (101.0 KB)
this is with a different ROM but same patch

5

Same result from the log file again. Unmapping errors are being shown in your log file.

6

hmm any idea why it works when hardware shader is disabled?

7

Unsure, as the Hardware Shader setting deals with shaders. At least its fixed now :slight_smile:

1 Like
8

I have previously used these ROMs around a year ago on an older version with hardware shader enabled so i am confused at why it would break now. maybe something to do with openGL

9

Disable all cheats, then restart the emulation (important, otherwise they remain active. Now try your game again with hardware shaders.

Also, set your Citra Region back to auto-select in Citra’s general settings. You shouldn’t be touching this unless you know what you’re doing.

10

Unmapped reads/writes can be caused by a lot of different things. Not just a corrupt ROM. A few of the most common ones are:

  1. Incompatible cheat codes (when a cheat code isn’t meant for the game, game’s version, or game’s region).
  2. A region mismatch. If the user has set their own region that is different from the one that the game requires, it will crash with unmapped reads/writes.

An easy way to check that is to look for this setting:

[   0.000115] Config <Info> common/settings.cpp:operator():128: System_RegionValue:

If it is set to -1, it means Region selection is set to Auto-select. So a region mismatch isn’t the problem. However, if it’s set to anything else (0, 1, 2, ect.), followed by unmapped reads/writes, there’s likely to be a region mismatch.

  1. Corrupted files. Updates, DLC, Texture packs, mods, ROMs. If any of these are corrupted, or incompatible, Citra tends to run into unmapped reads.
  2. An emulation incompatibility. This is probably the most unlikely of them all.
1 Like