• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Game Support › GameCube v
« Previous 1 2 3 4 5 36 Next »

[GC] Baten Kaitos: Eternal Wings and the Lost Ocean
View New Posts | View Today's Posts

Pages (13): « Previous 1 ... 8 9 10 11 12 13 Next »
Jump to page 
Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
[GC] Baten Kaitos: Eternal Wings and the Lost Ocean
05-19-2018, 09:42 AM (This post was last modified: 05-19-2018, 09:45 AM by GranteedEV.)
#91
GranteedEV Offline
Junior Member
**
Posts: 30
Threads: 3
Joined: Dec 2013
(10-22-2017, 12:50 PM)Spamzilla Wrote: Sorry for the bump.. I've been playing this game and no problems until a weird graphics glitch in the Lava Caves on Disc 2 in both DirectX11 and OpenGL.. Using version 5.0-5667...



Here is a link to a save-state if anybody is interested..

https://1drv.ms/u/s!Ap4KZFMds2L1hCiz7macyFYPkEqA

I came across this issue today (on Vulkan).   I tried playing around with settings and couldn't seem to nix it so I did a bit of revision-testing to see when this first popped up. 

Revision 5.0-1471:

 [Image: pIVJMBQ.jpg]


Revision 5.0-1473 ( [color=#333333]PixelShaderGen: Fix incorrect indexing of tevLerpBias ([/color][color=#428bca]PR #4514[/color][color=#333333] from [/color][color=#428bca]stenzek[/color][color=#333333])[/color] ):

[Image: iiwaitw.jpg]
Find
Reply
01-12-2019, 07:24 AM
#92
thechaindog
Unregistered
 
Bug 
I've been encountering an issue with the second disc on Dolphin 5.0(x64). Basically at one point you fight a boss named Kalas, but as soon as you beat him, it crashes almost immediately after. Specifically a message box pops up, he has one line of dialogue, and then his wings are supposed to fade away, and cut to another camera shot. It basically freezes in the middle of the wings disappearing. The screen gets stuck and a single note keeps repeating.

I've updated to 5.0.9331 to see if it helped, but it did not. I double checked if something maybe went wrong with the dump, but the md5 hash says it should be fine. It's about the NTSC version specifically, but I some Googling tells me that the PAL version also suffered from this same issue at some point.


I tried a couple of times with Dual Core enables and disabled, since I read that used to be an issue at one point, but this also made no difference. The last time I tried, I turned on the logger, and I can indeed see an unhandled exception trigger right when the thing is locks up. Not sure if this is entirely useful information, but here it is:

Code:
58:13:052 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:   3,110 kB FILE_300042AB
58:13:211 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:   5,225 kB FILE_70004FBA
58:13:503 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:   3,110 kB FILE_300042AB
58:13:633 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:   5,225 kB FILE_70004FBA
58:13:936 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:   3,110 kB FILE_300042AB
58:14:052 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:   5,225 kB FILE_70004FBA
58:14:343 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:   3,110 kB FILE_300042AB
58:15:704 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:     247 kB FILE_60002030
58:16:007 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:     259 kB FILE_60002031
58:16:211 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:     236 kB FILE_60002034
58:16:450 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:      20 kB FILE_60005E02
58:17:055 core\hw\dvd\filemonitor.cpp:83 W[FileMon]:      23 kB FILE_60005E46
58:22:628 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: Unhandled Exception 2
58:22:628 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ------------------------- Context 0x80263470 -------------------------
58:22:629 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r0   = 0xfeedface (     -17958194)  r16  = 0x3f800000 (    1065353216)
58:22:630 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r1   = 0x80296440 (   -2144771008)  r17  = 0x00000000 (             0)
58:22:630 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r2   = 0x8028c1e0 (   -2144812576)  r18  = 0x00000001 (             1)
58:22:630 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r3   = 0x81c0b161 (   -2118078111)  r19  = 0x00000000 (             0)
58:22:630 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r4   = 0xfeee0000 (     -17956864)  r20  = 0x00000000 (             0)
58:22:630 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r5   = 0x81c0b141 (   -2118078143)  r21  = 0x00000000 (             0)
58:22:630 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r6   = 0x802964d0 (   -2144770864)  r22  = 0x00000000 (             0)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r7   = 0x80e8df40 (   -2132222144)  r23  = 0x80253358 (   -2145045672)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r8   = 0x00000000 (             0)  r24  = 0x00000000 (             0)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r9   = 0x00000000 (             0)  r25  = 0x00000000 (             0)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r10  = 0x80296440 (   -2144771008)  r26  = 0xffffffff (            -1)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r11  = 0xbce14efe (   -1126084866)  r27  = 0x00000001 (             1)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r12  = 0x8001d204 (   -2147364348)  r28  = 0x00000c68 (          3176)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r13  = 0x8028aa80 (   -2144818560)  r29  = 0x00000000 (             0)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r14  = 0x00000000 (             0)  r30  = 0x80bfb020 (   -2134921184)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: r15  = 0x00000006 (             6)  r31  = 0x00000c80 (          3200)
58:22:631 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: LR   = 0x800262f0                   CR   = 0x40000088
58:22:632 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: SRR0 = 0x80026324                   SRR1 = 0x0000b032
58:22:632 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:632 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: GQRs----------
58:22:633 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: gqr0 = 0x00000000 gqr4 = 0x00060006
58:22:633 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: gqr1 = 0x00000000 gqr5 = 0x00070007
58:22:633 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: gqr2 = 0x00040004 gqr6 = 0x08070807
58:22:633 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: gqr3 = 0x00050005 gqr7 = 0x0c070c07
58:22:634 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:634 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:634 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: FPRs----------
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr0 = 0 fr1 = 1
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr2 = 2 fr3 = -1
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr4 = 0 fr5 = 0
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr6 = 1 fr7 = 0
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr8 = 0 fr9 = 0
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr10 = 0 fr11 = 0
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr12 = 1 fr13 = 0
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr14 = 0 fr15 = 0
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr16 = 0 fr17 = 0
58:22:635 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr18 = 0 fr19 = 0
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr20 = 0 fr21 = 0
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr22 = 0 fr23 = 0
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr24 = 0 fr25 = 0
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr26 = 0 fr27 = 0
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr28 = 0 fr29 = 0
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: fr30 = 0 fr31 = 1
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:636 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: PSFs----------
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps0 = 0x0 ps1 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps2 = 0x2 ps3 = 0xffffffff
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps4 = 0x0 ps5 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps6 = 0x1 ps7 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps8 = 0x0 ps9 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps10 = 0x0 ps11 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps12 = 0x0 ps13 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps14 = 0x0 ps15 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps16 = 0x0 ps17 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps18 = 0x0 ps19 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps20 = 0x0 ps21 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps22 = 0x0 ps23 = 0x0
58:22:637 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps24 = 0x0 ps25 = 0x0
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps26 = 0x0 ps27 = 0x0
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps28 = 0x0 ps29 = 0x0
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ps30 = 0x0 ps31 = 0x0
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: Address:      Back Chain    LR Save
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x80296440:   0x80296460    0x8017a91c
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x80296460:   0x802964d0    0x80019ef0
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x802964d0:   0x80296550    0x80030aac
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x80296550:   0x80296560    0x800bc144
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x80296560:   0x80296570    0x800ad1fc
58:22:638 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x80296570:   0x802965b0    0x8009ead8
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x802965b0:   0x802965c0    0x8013aec8
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x802965c0:   0x802965e0    0x8013d290
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x802965e0:   0x80296600    0x8013b9d0
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x80296600:   0x802966c0    0x800a635c
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x802966c0:   0x802966d0    0x80033ac0
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x802966d0:   0x802966e0    0x8003c228
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x802966e0:   0xffffffff    0x800032ac
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:639 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: DSISR = 0x42000000                   DAR  = 0x81c0b141
58:22:641 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: TB = 0x00565331e82093f0
58:22:641 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:641 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: Instruction at 0x80026324 (read from SRR0) attempted to access invalid address 0x81c0b141 (read from DAR)
58:22:641 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]:
58:22:641 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: Last interrupt (6): SRR0 = 0x8018522c  TB = 0x00565331e8203220
Reply
03-12-2019, 05:21 AM
#93
Mydude
Unregistered
 
[attachment=17864]
(01-12-2019, 07:24 AM)thechaindog Wrote: I've been encountering an issue with the second disc on Dolphin 5.0(x64). Basically at one point you fight a boss named Kalas, but as soon as you beat him, it crashes almost immediately after. Specifically a message box pops up, he has one line of dialogue, and then his wings are supposed to fade away, and cut to another camera shot. It basically freezes in the middle of the wings disappearing. The screen gets stuck and a single note keeps repeating.

I've updated to 5.0.9331 to see if it helped, but it did not. I double checked if something maybe went wrong with the dump, but the md5 hash says it should be fine. It's about the NTSC version specifically, but I some Googling tells me that the PAL version also suffered from this same issue at some point.


I tried a couple of times with Dual Core enables and disabled, since I read that used to be an issue at one point, but this also made no difference. The last time I tried, I turned on the logger, and I can indeed see an unhandled exception trigger right when the thing is locks up. Not sure if this is entirely useful information, but here it is:











Did you ever find a solution for this? My game also crashes at this point.

Currently running version 5.0-9727. Tried multiple settings. Ran on two different PCs, but the game crashes at the same point.

EDIT:

Fixed the crash. Switched to an older Dolphin build, then transferred save.
Reply
04-02-2019, 12:42 AM
#94
Tormento
Unregistered
 
(03-12-2019, 05:21 AM)Mydude Wrote: Fixed the crash. Switched to an older Dolphin build, then transferred save.

What version did you switch to?

I'm having the exact same issue after the Kallas fight...
I've tried many version but my memory card or my savestates aren't recognised by any other version... after 30hrs+ playing the game i'm kinda out of idea...
Thanks!
Reply
04-02-2019, 08:56 AM
#95
mimimi Offline
Senior Member
****
Posts: 720
Threads: 1
Joined: May 2014
Please use savestates as little as possible. If your save file from the memory card can't be used in another version of Dolphin, that's a big problem.

Can you upload your save file? If it's PAL, maybe i could test this myself.

One thing i noticed is that Dolphin now forces cpu efb access to be disabled, while it used it for force it on in the past. At least some effect in the menus requires it. Could you load your save file and then enable efb efb access, while the game is running? I'm curious if that fixes the issue. Also make sure to run the game with dual core disabled, it's one of the games that is supposedly unstable with it on.
Find
Reply
04-04-2019, 04:00 AM
#96
Tormento
Unregistered
 
(04-02-2019, 08:56 AM)mimimi Wrote: Please use savestates as little as possible. If your save file from the memory card can't be used in another version of Dolphin, that's a big problem.

Can you upload your save file? If it's PAL, maybe i could test this myself.

One thing i noticed is that Dolphin now forces cpu efb access to be disabled, while it used it for force it on in the past. At least some effect in the menus requires it. Could you load your save file and then enable efb efb access, while the game is running? I'm curious if that fixes the issue. Also make sure to run the game with dual core disabled, it's one of the games that is supposedly unstable with it on.

Thanks for your advices, it's not pal it's NTSC US.

I'll try a couple of thins when i have the time, probably Friday - I'll try and upload the save file Smile

Savestates are a last resort for me, but with a child and very little time to play sometimes you just can't play until there's a savepoint Smile
Reply
04-06-2019, 01:11 AM
#97
Tormento
Unregistered
 
IT WORKED!

Thanks a lot mimimi!

I don't exactly know what did it, but i can now continue the game Smile

For those who had the problem, here's what i tried

- Disables dual core
- Unchecked "skip EFB access from CPU", then re-enabled it once the game was launched.
- DIsabled V-SYNC (surely didn't resolved the issue, but i needed a little more cpu ressource since the game wasn't running perfectly with dual-core disabled)
Dolphin v. 5.0-9896

Thanks again!
Reply
04-18-2019, 11:52 AM
#98
Botulix
Unregistered
 
Hello !

I'm having the same issue : the game crashes right after I defeat Kalas. I've tried what was said but it didn't work for me... I'm using version 5.0-9620 (x64) on Romstation 2.0, so I tried to use 5.0 instead, but i cannot use my save, it says it's corrupted... I can only use it with v. 5.0.
I've never used savestates, only the regular savepoints and it's a PAL game.
Any ideas?...
Reply
04-19-2019, 01:29 AM
#99
mimimi Offline
Senior Member
****
Posts: 720
Threads: 1
Joined: May 2014
(04-18-2019, 11:52 AM)Botulix Wrote: Hello !

I'm having the same issue : the game crashes right after I defeat Kalas. I've tried what was said but it didn't work for me... I'm using version 5.0-9620 (x64) on Romstation 2.0, so I tried to use 5.0 instead, but i cannot use my save, it says it's corrupted... I can only use it with v. 5.0.
I've never used savestates, only the regular savepoints and it's a PAL game.
Any ideas?...

Can you please upload your savegame?
Find
Reply
04-20-2019, 06:35 AM
#100
Botulix
Unregistered
 
(04-19-2019, 01:29 AM)mimimi Wrote: Can you please upload your savegame?

Here you go!
Thank you for your help!


Attached Files
.zip   AF-GKBP-BKData-001.zip (Size: 18.6 KB / Downloads: 80)
Reply
« Next Oldest | Next Newest »
Pages (13): « Previous 1 ... 8 9 10 11 12 13 Next »
Jump to page 


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode