![]() ![]() In my last efforts, when I play MGS I've usually set the clockspeed at 45 - merely as a compromise, so that cutscenes could benefit from some more frames while gameplay hopefully won't suffer too badly due to the decrease of only 5. At 50, cutscenes have tons of slowdowns (I often benchmark the opening submarine sequence), and in-game segments (meaning when you actually get to control Snake) also suffer from slowdowns when the game gets demanding. ![]() For example, Spider-Man 1 is very volatile when set at 50: less demanding segments would run very smoothly but the drops and slowdowns are way too noticeable when the game gets really demanding when set somewhere in the range 37-41, the framerate becomes much more stable and uniform, and the game much more playable, though naturally also a bit more janky (but still tolerable for me.)Īccording to my experience MGS is one of the more difficult 3D or graphically intensive games to get to run in a stable manner. Normally when I tinker with clockspeed at all, I would try to find one particular value I can settle with so that the game could run in a most stable or uniform manner possible fps-wise when compared to how it runs at the default 50 (naturally, this would only happen if 50 is not good enough). Also, I'm currently on a one week old nightly (I think). Normally, I'm on a very performance/speed-friendly configuration (with all relevant settings either enabled or disabled accordingly - except for audio, blending and lighting, which are always enabled). I guess some of you might already know this but for discussion's sake I'll be posting anyways. I made some new findings yesterday regarding how CPU clockspeed values affect performance in MGS (which I one of the games I've chosen for benchmarking). Other options like sound interpolation may make a difference but I haven’t noticed a significant change with those. No idea why, but it seemed to make a noticeable difference in my tests. You may also get a small boost by keeping the 3D slider off. The newest nightlies have an extra Unai Advanced option to downscale hi-res modes to the 3DS resolution which can be a big boost in games that use those modes. Dithering off (because there are a lot of optimizations that don't work when it's on) CD Read Method: async (this also helps avoid the slow read problem, by trying to read stuff in advance and not pausing the emulator while doing it) Other settings that work very well for most games: I would guess this is probably the biggest problem, because frameskip won't help much if it's slow because of reads. The extra compression helps a lot with the 3DS's slow read speeds. bin/.cue, the biggest boost will come from switching to. I haven't tried any of those specific games so I don't know what to expect from them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |