(10-19-2014, 02:28 AM)shadowlink Wrote: [ -> ] (10-19-2014, 02:07 AM)Link_to_the_past Wrote: [ -> ] (10-19-2014, 12:39 AM)shadowlink Wrote: [ -> ]Hi all!
I was playing the game and, when I arrived for first time to the Refugee Camp, my Dolphin was crashed. I can´t go beyond that point. Any Idea? I use the last build. The rest of the game runs smooth and perfect but...
If it happens to you no matter the dolphin version and always on the same spot, it is possible you have a bad dump. Backtrack to dolphin 4.0.2 or older to check.
I tried with 4.0.2 and 3.5. Always the same situation.
Then probably a bad dump, i have finished this game with no game breaking bug in the past. What is the size of the iso? Try checking the partition integrity in the file browser in game properties, by right clicking the game partition and checking integrity.
(10-19-2014, 02:39 AM)Link_to_the_past Wrote: [ -> ] (10-19-2014, 02:28 AM)shadowlink Wrote: [ -> ] (10-19-2014, 02:07 AM)Link_to_the_past Wrote: [ -> ] (10-19-2014, 12:39 AM)shadowlink Wrote: [ -> ]Hi all!
I was playing the game and, when I arrived for first time to the Refugee Camp, my Dolphin was crashed. I can´t go beyond that point. Any Idea? I use the last build. The rest of the game runs smooth and perfect but...
If it happens to you no matter the dolphin version and always on the same spot, it is possible you have a bad dump. Backtrack to dolphin 4.0.2 or older to check.
I tried with 4.0.2 and 3.5. Always the same situation.
Then probably a bad dump, i have finished this game with no game breaking bug in the past. What is the size of the iso? Try checking the partition integrity in the file browser in game properties, by right clicking the game partition and checking integrity.
Integrity check for partition 0 failed!
Seems that I really need another dump. Thanks for the info
Hello everyone.
I'm sure this thread has seen innumerable questions regarding what one should do to play this game at full speed, but I seem to be having a somewhat different issue that I'd like to get help on.
For starters, here's my specs:
OS: Windows 8.1 x64
CPU: Intel Core i7-4770K 3.5GHz (OC'd to 4.5GHz)
GPU: NVIDIA GeForce GTX 780 (EVGA Superclocked, 3GB VRAM)
RAM: 8GB (2 x 4GB) DDR3-1600
Dolphin: 4.0-3743 x64
(Note that both the emulator and the game file are both stored on my SSD)
The issue is that the game will randomly stutter at random points in the game for unknown reasons. It can handle most everything at a constant 30FPS with ease, including some pretty demanding cutscenes with a lot of things to render. Even so, the game will still occasionally stutter for a split second, specifically during a battle when an enemy gets hit. It sometimes happens when opening a menu as well, however this is much less frequent. Messing with the settings and testing different things didn't seem to help me very much, and I still can't figure out exactly what may be causing this. One thing I noticed is that it doesn't matter what the internal resolution is, what anti-aliasing level I have checked, or anything like that; I'll have a random 1-second freeze (sometimes longer) during a battle with one small enemy, even if the internal resolution is 1x native, the game is running in a window (rather than fullscreen), and AA is off.
Most of the settings have been left to their default values, although I am using OpenGL as a backend. The wiki suggests using OpenGL to reduce stuttering, and it actually did end up helping as the stuttering was more frequent and noticeable when using Direct3D.
I've tried a few different versions of Dolphin that were compiled over the last few days/weeks, and while I have had varying results, I can't seem to get the stuttering issue to go away.
If anyone can provide some insight on this issue, it would be much appreciated.
That's the good old shader cache complilation. There's nothing you can do about that at this point.
You won't have that issue with the option "Full async shader compilation" in the Ishiiruka build, however, that is an unofficial build, so don't ask for any support outside of the Ishiiruka thread.
(10-21-2014, 07:06 PM)StripTheSoul Wrote: [ -> ]That's the good old shader cache complilation. There's nothing you can do about that at this point.
You won't have that issue with the option "Full async shader compilation" in the Ishiiruka build, however, that is an unofficial build, so don't ask for any support outside of the Ishiiruka thread.
Wow. The difference in speed is actually pretty impressive. I'm getting 100% smooth gameplay now, and despite the warnings on using async shader compilation, no graphical hiccups. Thanks for the tip!
Just finally got around to starting this game up, and after fiddling with settings and options for the past week or so, finally managed to get the game running almost flawlessly on my rig (info is on my profile for that, except HDD info, which is a recent 1TB WD Black drive). I thought I would chime in with some findings, since initially, I'd had many of the same issues many people reported, but once I found a specific set of settings, I achieved this nearly flawless state I'm currently in.
So, what fixed the slowdowns and lag during battles and scenes of high motion/activity was BorderlessFullscreen. The moment I set that, my FPS stayed at 30 throughout the entire intro sequence. Prior to setting this, the tutorial battle would drop into the mid- to low-20s, particularly when the camera moved around to face the opposite direction you start facing. I suppose there is a lot more activity going on on that side of the battlefield as opposed to the side you start out viewing.
As for the issues of slight blips in framerate when opening menus and exiting them, manually setting the framelimit from Auto to 60 (presumably 50 for PAL versions), fixed that as well. Seems like the game tries to ramp up the FPS during the swap between in-game display and the menu screens. The only hiccough I've encountered in 4 hours of play was during the first flashback sequence, upon initial loading, the frames dropped for perhaps a second at the most, but that's likely due to loading, and was perfectly acceptable, at least for me.
I did a quick search of the thread on these particular settings, and found nobody happened to mention them previously, so I thought I would share what worked for me, and hope it helps anyone else achieve nirvana for this particularly excellent game.
Hello, fine folks of Dolphin! Forgive me for registering to a forum and asking for help straightaway, but like so many others I am having rather baffling performance issues with Xenoblade Chronicles in the latest development build (and numerous other builds, both experimental and official). No matter what I do the game refuses to go over 15 FPS. I have Googled all sorts of configurations and tried them all. The VBeam Speed Hack and D3D gives the 'best' performance, but we're talking 15-20FPS instead of 10-15. On my system, that just ain't right. Specs:
Windows 8.1 x64
CPU: AMD Phenom II X4 965BE 3.5GHz
GPU: NVIDIA GeForce GTX 770 (4GB edition)
RAM: 12GB Kingston DDR3
I have an SSD and two HDDs, but the performance difference is minimal no matter which I run the game off of.
Now here's the strange thing.
This old custom build runs the game flawlessly, almost no FPS drops at all, and I haven't even carefully tweaked it yet. So I know it's not my hardware that's the problem. While I'll certainly run an old build if that's what it takes to get the game going, I'd much rather use a more recent version if possible. Any advice, or am I stuck on a 3.x HLE-hacked version of the emulator?
Thanks in advance! (and I'll try to stick around and be helpful on these forums now that I'm signed up, I'm not totally clueless on emulation
)
Your hardware is the problem. The old build is highly inaccurate and emulates much less of the console. Your processor is exceedingly old and weak at this point, which is why the game doesn't run as well as you'd expect.
I wondered about that, but I've seen YouTube videos of people with Core i3s running the game just fine. That's on par with what my CPU can handle :\
no, your computer is much weaker than most i3s. I guess the exception would be the early laptop ones from the first generation.