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


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 ... 341 342 343 344 345 ... 1196 Next »

Ocarina of Time Screenshoting crashes the game!
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Ocarina of Time Screenshoting crashes the game!
03-16-2017, 06:38 PM
#1
Ripdime
Unregistered
 
Hello Dolphin folks!

I've been using Dolphin on and off over the years, but I never had a computer good enough to really make much use until fairly recently. I got the itch to play some old games and went ahead and got the newest Dolphin, my games, and even discovered texture packs, widescreen hacks, etc. I've never seen these games look so good, it's amazing...with one slight complication.

As the thread title says, taking a screenshot in both versions of Ocarina of Time that I have - the Master Quest disc (D43E01) and the Collector's Edition Disc (PZLE01) - crashes the game, giving me a read error (0xdbb266c0, PC = 0x8071aaac). It's worth noting it does manage to actually save a SS in spite of crashing the emu!

To try and pinpoint the problem, I've tried:

∙ turning off all the additions (hacks/codes/textures)
∙ lowering internal resolution
∙ disabling the CPU clock override
∙ turning off AA
∙ setting AF to 1x
∙ removing all post-effects
∙ Unchecking "Store EFB copies to Texture"
∙ Moving the Texture Cache slider in both directions
∙ Checking "Full Resolution Frame Dumps"

I'll add that I'm using the (atm newest) Ishiruuka version of Dolphin as well.

The only thing that has made any difference is that with "Full Resolution Frame Dumps" disabled, I get a slightly different error message:

"0xdbb266c0, PC = 0x8071aeac"

Those errors are from the Ishiruuka build. When on the master Dolphin, the error is "0xdbb266c0, PC = 0x8071a33b"

I've only tested a few other games (Twilight Princess, Mario Sunshine, Wind Waker), but screenshots work fine with them. Both versions of the Master quest disc crash, I have not tried other games on the CE disc.

I can't make sense of the error codes, any direction would be appreciated

Thanks guys!

-Rip
Reply
03-17-2017, 12:08 AM (This post was last modified: 03-17-2017, 12:10 AM by envisaged0ne.)
#2
envisaged0ne Offline
The Force Is Strong With This One
*****
Posts: 759
Threads: 15
Joined: Mar 2009
Just tried taking a screenshot of Ocarina Of Time.  Playing the Collectors Edition on the latest Dev build.  Worked just fine.  No errors.  Since it lets you take the screenshot anyway, doesn't sound like an emergency. I'm using the OGL backend, in case that makes a difference. Also, there is no support for the Ishiruuka here. Just 5.0 or one of the latest dev builds
Windows 11 Home x64
Intel Core i7-10700
Nvidia Rtx 2060 6GB
32.0 GB DDR4 RAM
Find
Reply
03-17-2017, 12:35 AM
#3
degasus Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 1,828
Threads: 10
Joined: May 2012
Sounds like GPU desync. May you try single core and check if "SyncOnSkipIdle" is enabled in the ini?
Find
Reply
03-17-2017, 09:47 AM
#4
Ripdime
Unregistered
 
(03-17-2017, 12:35 AM)degasus Wrote: Sounds like GPU desync. May you try single core and check if "SyncOnSkipIdle" is enabled in the ini?

Disabling the Dualcore setting indeed fixed it! - but (not surprisingly) the game is struggling to stay at 100% speed now. I'm not sure where to get to the ini to check that setting. I tried the games' ini's and there wasn't any sync entries there, show me where to go and I'll check it!

Thanks for the help so far!

@envis
I understand Ishiruuka is a custom build that can't officially be supported by anybody except I assume, Tino; but since this issue was happening on the regular Dolphin 5.0, it seemed to me that the issue wasn't specifically with Ishiruuka, and therefore would be better placed here. Since you're not having troubles that further points to there being a driver compatibility issue or something more specific to my hardware, it looks like you've got a different GPU, CPU and even Windows version Blush .


FWIW, I forgot to mention in the original post, but I did try the D3D9/11/12, and OGL backends and the issue still happened, sorry I forgot.

Is there any recourse for long-term use? The game dips to 80% and less atm.

Thanks guys.
Reply
« Next Oldest | Next Newest »


  • 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