Project

General

Profile

Actions

Emulator Issues #10454

closed

Go Vacation Crashes on Character Creation Menu (AArch64 JIT) on cmpi

Added by JMC4789 over 6 years ago. Updated over 6 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-5135

Description

Game Name?

Go Vacation - SGVEAF

What's the problem? Describe what went wrong.

When you startup the game, you're given the ability to either choose a Mii (lame) or create a cute/cool/etc. anime character desu that totally represents your inner beauty (good.) Unfortunately, when you go to fulfill your anime destiny, the game will crash on all CPU backends except JIT64. This means our poor Android users cannot create their anime avatar for Go Vacation, leaving their lives incomplete. Also, it's probably not good for the game to crash on our interpreters and work on the JIT.

What steps will reproduce the problem?

1: Startup Go Vacation
2: Choose a new file
3: Ignore the shitty use Mii option to create the avatar of your dreams.
4: Game Will Crash if not using JIT.

Is the issue present in the latest development version?

Yes

Is the issue present in the latest stable version?

Shit, I didn't realize my new guidelines would apply to me. After an extra five minutes to verify, it does indeed happen in Dolphin 5.0.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

Yay I can ignore this step.

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

This isn't a fifolog but it's a log. Get rekt whoever wrote this.

01:17:631 HW\DVD\FileMonitor.cpp:109 W[FileMon]: 5,834 kB Sound/StreamData/ALL/ID000_BGM_MENU_US.nub
01:39:276 PowerPC\CachedInterpreter\CachedInterpreter.cpp:187 W[PowerPC]: ISI exception at 0x00000000
01:39:276 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Unhandled Exception 3
01:39:277 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ------------------------- Context 0x801879f8 -------------------------
01:39:278 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r0 = 0xffffffe0 ( -32) r16 = 0x00000000 ( 0)
01:39:278 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r1 = 0x80200d98 ( -2145383016) r17 = 0x00000000 ( 0)
01:39:279 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r2 = 0x80186820 ( -2145884128) r18 = 0x00000000 ( 0)
01:39:279 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r3 = 0x90ea02f4 ( -1863712012) r19 = 0x00000000 ( 0)
01:39:280 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r4 = 0x00000001 ( 1) r20 = 0x9054a028 ( -1873502168)
01:39:280 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r5 = 0x00000000 ( 0) r21 = 0x80201598 ( -2145380968)
01:39:281 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r6 = 0x40000017 ( 1073741847) r22 = 0x00000000 ( 0)
01:39:281 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r7 = 0x00004000 ( 16384) r23 = 0x00000000 ( 0)
01:39:282 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r8 = 0x00000000 ( 0) r24 = 0x00000021 ( 33)
01:39:283 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r9 = 0x0000000b ( 11) r25 = 0x00000000 ( 0)
01:39:283 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r10 = 0x00000008 ( 8) r26 = 0x92d32ce0 ( -1831654176)
01:39:284 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r11 = 0x80200e28 ( -2145382872) r27 = 0x80200e50 ( -2145382832)
01:39:284 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r12 = 0x00000000 ( 0) r28 = 0x80650000 ( -2140864512)
01:39:285 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r13 = 0x801852c0 ( -2145889600) r29 = 0x90ea02f4 ( -1863712012)
01:39:285 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r14 = 0x00000000 ( 0) r30 = 0x90ea02f4 ( -1863712012)
01:39:286 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: r15 = 0x00000000 ( 0) r31 = 0x8064aec8 ( -2140885304)
01:39:286 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: LR = 0x80242640 CR = 0x28000488
01:39:286 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: SRR0 = 0x00000000 SRR1 = 0x4000a032
01:39:286 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:287 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: GQRs----------
01:39:287 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: gqr0 = 0x00000000 gqr4 = 0x00060006
01:39:287 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: gqr1 = 0x00000000 gqr5 = 0x00070007
01:39:287 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: gqr2 = 0x00040004 gqr6 = 0x0c070c07
01:39:288 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: gqr3 = 0x00050005 gqr7 = 0x08040804
01:39:288 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:288 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:288 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: FPRs----------
01:39:288 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr0 = 0 fr1 = 0
01:39:289 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr2 = 0 fr3 = 0
01:39:289 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr4 = 0 fr5 = 0
01:39:289 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr6 = 0 fr7 = 0
01:39:289 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr8 = 0 fr9 = 0
01:39:289 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr10 = 0 fr11 = 0
01:39:290 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr12 = 0 fr13 = 0
01:39:290 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr14 = 0 fr15 = 0
01:39:290 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr16 = 0 fr17 = 0
01:39:290 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr18 = 0 fr19 = 0
01:39:290 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr20 = 0 fr21 = 0
01:39:291 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr22 = 0 fr23 = 0
01:39:291 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr24 = 0 fr25 = 0
01:39:291 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr26 = 0 fr27 = 0
01:39:291 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr28 = 0 fr29 = 0
01:39:291 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: fr30 = 0 fr31 = 0
01:39:292 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:292 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:292 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: PSFs----------
01:39:292 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps0 = 0x0 ps1 = 0x0
01:39:292 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps2 = 0x0 ps3 = 0x0
01:39:292 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps4 = 0x0 ps5 = 0x0
01:39:293 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps6 = 0x0 ps7 = 0x0
01:39:293 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps8 = 0x0 ps9 = 0x0
01:39:293 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps10 = 0x0 ps11 = 0x0
01:39:293 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps12 = 0x0 ps13 = 0x0
01:39:293 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps14 = 0x0 ps15 = 0x0
01:39:294 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps16 = 0x0 ps17 = 0x0
01:39:294 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps18 = 0x0 ps19 = 0x0
01:39:294 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps20 = 0x0 ps21 = 0x0
01:39:294 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps22 = 0x0 ps23 = 0x0
01:39:295 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps24 = 0x0 ps25 = 0x0
01:39:295 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps26 = 0x0 ps27 = 0x0
01:39:295 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps28 = 0x0 ps29 = 0x0
01:39:295 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ps30 = 0x0 ps31 = 0x0
01:39:296 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:296 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Address: Back Chain LR Save
01:39:296 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200d98: 0x80200da8 0x8023a560
01:39:296 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200da8: 0x80200e28 0x8024499c
01:39:297 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200e28: 0x80200e48 0x8025a2b4
01:39:297 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200e48: 0x80200e98 0x8025f960
01:39:297 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200e98: 0x80200eb8 0x8025d21c
01:39:298 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200eb8: 0x80200ec8 0x8025c9f0
01:39:298 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200ec8: 0x80200ed8 0x8023e014
01:39:298 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200ed8: 0x80200ee8 0x802d0ff4
01:39:298 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200ee8: 0x80200ef8 0x802c9fec
01:39:299 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80200ef8: 0x80201048 0x802bb654
01:39:299 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80201048: 0x802010a8 0x80338e30
01:39:299 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x802010a8: 0x80201128 0x8038d0f4
01:39:300 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80201128: 0x80201188 0x80338e30
01:39:300 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80201188: 0x80201208 0x8038d0f4
01:39:300 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80201208: 0x80201268 0x80338e30
01:39:300 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 0x80201268: 0x802012e8 0x8038d0f4
01:39:301 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:301 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: DSISR = 0x00000000 DAR = 0x00000000
01:39:302 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: TB = 0x0077f06747ea0dbb
01:39:302 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:302 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Attempted to fetch instruction from invalid address 0x0 (read from SRR0)
01:39:303 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
01:39:303 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Last interrupt (17): SRR0 = 0x8013b324 TB = 0x0077f06747e99b7c

What are your PC specifications? (CPU, GPU, Operating System, more)

Intel Core i5-3570K, GTX 760, Windows 10

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

I love Go Vacation and any poking fun at it I did in this issue report is purely to entertain any poor soul who stumbles upon it.


Related issues 1 (0 open1 closed)

Has duplicate Emulator - Emulator Issues #10138: (android) Go Vacation crashes on character loadDuplicate

Actions
Actions #1

Updated by JMC4789 over 6 years ago

Actions #2

Updated by JMC4789 over 6 years ago

I was able to successfully get through the thing falling back everything EXCEPT Jit Integer. Falling back JIT Integer caused an unknown opcode on startup.

Actions #3

Updated by JMC4789 over 6 years ago

  • Status changed from New to Accepted
  • Assignee set to degasus
  • Priority changed from Normal to High

Fallingback addi causes the game to crash immediately, which is a separate crash from the character select crash. I'll make a second issue eventually about that.

Actions #4

Updated by JMC4789 over 6 years ago

THE CULPRIT IS: cmpi

degasus plz fix

Actions #5

Updated by JMC4789 over 6 years ago

  • Subject changed from Go Vacation Crashes on Character Creation Menu (Interpreter, Cached Interpreter, AArch64 JIT) to Go Vacation Crashes on Character Creation Menu (Interpreter, Cached Interpreter, AArch64 JIT) on cmpi
Actions #6

Updated by JMC4789 over 6 years ago

  • Subject changed from Go Vacation Crashes on Character Creation Menu (Interpreter, Cached Interpreter, AArch64 JIT) on cmpi to Go Vacation Crashes on Character Creation Menu (AArch64 JIT) on cmpi
  • Priority changed from High to Normal

Interpreter + Cached Interpreter fixed by 5.0-5130 - https://dolphin-emu.org/download/dev/0a8e1bd864947fdd67c7d7fcd006917cf98b3267/

Actions #7

Updated by JMC4789 over 6 years ago

  • Status changed from Accepted to Fixed
  • Fixed in set to 5.0-5135
Actions

Also available in: Atom PDF