[Bug ORAS] Pokemon Omega Ruby was crashed at Victory Road

Hi, everyone
I have a problem when i play pokemon ORAS. I can’t go next on Victory Road.
How to complete ORAS without bug. Pls help me ToT
Thank so much.

System Information

  • Operating System: Windows 10
  • CPU: Intel Core i7-4700MQ CPU @ 2.40Ghz 2.40 Ghz
  • GPU: Nvidia GeForce 750M
  • Citra Version (found in titlebar): Citra | HEAD-AVX2-30-JAN-2017
  • Game: Pokemon Omega Rupy
  • Screenshot of Issue (include the full Citra window including titlebar):

You’re using an unofficial build, we do not provide support for such builds.

  1. Don’t post personal emails here.
  2. No support for unofficial builds. Please restest this with the latest nightly from the official website.
  3. Post the full log by following this guide.

Sorry, i have tried the other Citra but still be same problem.
Citra Nightly | HEAD-ea53d60
Can u help me :slight_smile:

Need the full log please. Also, provide a save file and steps to reproduce this.

This is my log.
Thank for your help :smile:

This is my save file. Do i need to do anything else, bro?

Moderator Edit: Removed infringing link.

your save includes font file and system archives which are illegal to share, please remove this link and post the save file only instead of the entire user folder.

can you also be more specific about where it is crashing?

edit: i just reached the pokemon league with your save so something might be on your end

The way the log goes from 0 to 71 seconds make it look like it’s incomplete. Also this line looks weird as it should only show if your ROM is encrypted which shouldn’t even boot with CItra.

[ 0.546344] Loader core\loader\ncch.cpp:Loader::AppLoader_NCCH::LoadExeFS:295: ExHeader Program ID mismatch: the ROM is probably encrypted.

This and what RavenHome said about not encountering this issue might be because of a bad ROM dump. Please redump your game and retest.

I made it!
You’re very kind and friendly.
Thank for your help. I wish the community will develop more in the future. :blush:

So did redumping your ROM fix the issue as others who might have encountered this will be able to resolve it.

1 Like