PCSX2 Wiki

Metal Gear Solid 3: Subsistence: Difference between revisions

Page Discussion

Metal Gear Solid 3: Subsistence (view source)

Revision as of 19:08, 19 June 2018

1,970 bytes removed ,  19 June 2018
m
Way too much text, really. I'm moving this text to a Discussion page.
(added another game profile)
m (Way too much text, really. I'm moving this text to a Discussion page.)
Line 160: Line 160:
|Comments=BIOS: USA 2.30, Finally got my DS3 controller to work properly with this game. The game runs fine aside from the few known issues with graphics. Requires a powerful computer to run at full speed. I used Skipdraw 1 to deal with a massive drop in frame rates whenever 'Stealth Camouflage' was being used. Using Skipdraw 1 did not cause any further weird side-effects in the rest of the game. As mentioned, the DS3 controller is pretty much a must-have for this game. Using the SCPToolkit, the pressure sensitive buttons worked perfectly fine after some minor adjustments to the sensitivity itself in LilyPad's configuration page. (I set the Circle button to 0.600, because it was still a bit too sensitive and I ended up killing soldiers whom were taken in a chokehold. After setting it to 0.600 it worked perfect). Each controller has different calibration ranges for the buttons, so always check and see which sensitivity works best for your controller.
|Comments=BIOS: USA 2.30, Finally got my DS3 controller to work properly with this game. The game runs fine aside from the few known issues with graphics. Requires a powerful computer to run at full speed. I used Skipdraw 1 to deal with a massive drop in frame rates whenever 'Stealth Camouflage' was being used. Using Skipdraw 1 did not cause any further weird side-effects in the rest of the game. As mentioned, the DS3 controller is pretty much a must-have for this game. Using the SCPToolkit, the pressure sensitive buttons worked perfectly fine after some minor adjustments to the sensitivity itself in LilyPad's configuration page. (I set the Circle button to 0.600, because it was still a bit too sensitive and I ended up killing soldiers whom were taken in a chokehold. After setting it to 0.600 it worked perfect). Each controller has different calibration ranges for the buttons, so always check and see which sensitivity works best for your controller.
|Tester=Ryudo
|Tester=Ryudo
}}
{{TestingFooter}}
<!--
{{TestingHeader|OS=Linux}}
{{TestingEntry
|Status=?
|Region=?
|OS=?
|CPU=?
|GPU=?
|Revision=?
|Graphics=?
|Sound=?
|Comments=?
|Tester=?
}}
}}
{{TestingEntry
{{TestingEntry
Line 201: Line 185:
* Anisotropic Filtering: 16x
* Anisotropic Filtering: 16x
* CRC Hack Level: Automatic
* CRC Hack Level: Automatic
* '''Shader Configuration:'''
* '''Shader Configuration:'''
** FXAA: no
** FXAA: no
Line 213: Line 195:
* SPU2-X 2.0.0
* SPU2-X 2.0.0
* LilyPad 0.11.0 SCP (r5875)
* LilyPad 0.11.0 SCP (r5875)
|Comments=BIOS: USA. Note that playing using 1.4 gave _much_ worse performance. Used a pressure-sensitive-r2/l2-only controller, made palatable by reducing the 'o' sensitivity to .470--this means you can't slit throats, but are able to interrogate. Some weapons (AK, other similar rifles) you can't do the 'aim by half pressing square' function, but handguns and sniper rifles and most every other weapon is fine, which is an ok trade-off. The game runs reasonably, considering this is not a gaming rig, but the videos sometimes slow down to 60% (or even lower). To get around this, I also set up the 'tab for auto' functionality, but set auto to be at 100% speed (so it isn't turbo), but enabled the setting for frame skipping while doing turbo (the default 2 per 2 is the only one I found to work); then, during some slow video scenes, hitting tab would speed it up nicely. Some video scenes get frozen, however (audio continues), so you have to keep clicking tab until you jump back into the correct frame stream. Skipdraw 1 and 2 worked pretty well, I went for 2 to be a bit more aggressive, I think I remember 3 creating issues. Most of the game played perfectly smoothly, but after you get to groznjy grad, many sections start going more like 90%... You will notice, however, that turning the camera to face away from the huge base, or away from the shagohod, or to the ground, will cause the speed to go back up to 100% (fewer polygons being rendered to your screen, less trig being thrown at the processor I guess). But it's playable. For the videos... You can get most of them to work well enough, but the slow mo effect really kills the cinematic sense of the game for videos, so I'd switch over to youtube and watch the scene there if that starts happening, honestly. (I had a first time watcher, girlfriend, and wished I'd done that for the intro, which is particularly demanding and nice--I absolutely switched to youtube for the end of the game, because I'll be damned if I'd let that be ruined, and it was definitely the right call). This laptop is almost able to pull it off, and/or pcsx2 is almost able to pull it off. Just as a note, though, MGS V (native PC) runs perfectly on this laptop on low settings and is gorgeous, so if you get too frustrated, switch over to that!
|Comments=BIOS: USA. Note that playing using 1.4 gave _much_ worse performance. The game runs reasonably, considering this is not a gaming rig, but the videos sometimes slow down to 60% (or even lower). Skipdraw 1 and 2 worked pretty well. See [[Talk:Metal Gear Solid 3: Subsistence#Additional information|my config info]].
|Tester=fintip
|Tester=fintip
}}
{{TestingFooter}}
<!--
{{TestingHeader|OS=Linux}}
{{TestingEntry
|Status=?
|Region=?
|OS=?
|CPU=?
|GPU=?
|Revision=?
|Graphics=?
|Sound=?
|Comments=?
|Tester=?
}}
}}
{{TestingFooter}}
{{TestingFooter}}
Ngng
Bureaucrats, ninja, Administrators
67,564

edits

Retrieved from "https://wiki.pcsx2.net/Special:MobileDiff/92162"