Wiki Page - Endless Ocean - [edit]
[color=#ff0000][color=#006600]i5 3570K @ 4.5GHz/GTX 660 Ti/RAM 4GB/Win7 x64[/color][/color]
[Wii] Endless Ocean
|
11-14-2012, 03:00 AM
Wiki Page - Endless Ocean - [edit]
[color=#ff0000][color=#006600]i5 3570K @ 4.5GHz/GTX 660 Ti/RAM 4GB/Win7 x64[/color][/color]
09-21-2015, 07:59 AM
I don't have permissions to post a new thread, but my question is pertinent to this title, so I apologize if this is a pretty good necro.
I am having this same issue on two different systems and I am hoping someone can assist in debugging. System 1: (I recognize this system will not come close to full frame - but I am using it as a comparison) Core i5-4200U (intel HD4400) 4GB DDR3 Mem (shared) Win 10 dolphin build 4.0-7781/ Direct3D System 2: Core i7-4970K Nvidia 960 4GB (evga) 16 GB DDR3 Mem Xubuntu dolphin (most recent - git pull origin every two days or so) OpenGL renderer I dumped Endless Ocean with CleanRip (2.0.0 I think), and have combined the chunks and verified the MD5 (720c5020b8603fea7bfdb623fb5d3bdb) so that the chunks match what CleanRip reported. So that looks good. In both Linux and Win, I use dolphin to check the integrity of the partitions (there is a Partition 0 and a Partition 1 of the dumps), and in both Linux and Win, the partitions are good. When I load the ISO and start emulation all I get is a black screen with the following logging: Code: 38:49:607 ConfigManager.cpp:85 N[BOOT]: Saving settings to C:/Users/Michael/Documents/Dolphin Emulator/Config/Dolphin.ini Can anyone verify my MD5? - or offer any other suggestions? Something looks screwy at the PowerPC\SignatureDB calls but I have no clue what those mean or how to correct the cause. 09-21-2015, 09:44 AM
The SignatureDB messages appear in debug builds of Dolphin. Are you compiling a debug build? If so, try compiling and running a release build.
09-21-2015, 10:14 AM
Yes. Windows was a "nightly" precompiled build and Linux was pulled from github and compiled.
I tried again with 4.0.2 release build and 5.0.rc27 only on windows and it appeared to work. I'm not a git expert, so how do I specify that the rc27 tag to test in linux? 4.0.2 Windows Code: 02:28:214 Src\ConfigManager.cpp:140 N[BOOT]: Saving settings to C:/Users/Michael/Documents/Dolphin Emulator/Config/Dolphin.ini 5.0-rc-27 Windows Code: 08:28:415 ConfigManager.cpp:42 N[BOOT]: Saving settings to C:/Users/Michael/Documents/Dolphin Emulator/Config/Dolphin.ini 09-21-2015, 11:02 AM
Quick googling got my git tag to 5.0-rc on my Linux build, and that resolved the issue. So is the issue I am seeing just an issue is in the trunk code and not on those particular tagged branches?
09-22-2015, 08:35 AM
It seems so. If you could bisect it down to the commit responsible, we can look at it further.
09-22-2015, 11:49 AM
While watching MNF I just narrowed it down on windows to somewhere between 4.0-7506(last working) to 4.0-7517(not working).
The in-between dev builds (via the dolphin download page) trip up Windows Defender as including virus. 09-23-2015, 10:46 AM
Don't worry, we already know how to fix this. There's a vbeam inaccuracy, that's all, and it's known and being debugged.
09-24-2015, 01:22 PM
|
« Next Oldest | Next Newest »
|