Metal Gear Solid 2: Substance: Difference between revisions
Jump to navigation
Jump to search
m
Cleaning up Known Issues section... No need to add who found it and when. Regarding the pressure sensitivity - that's not an emulator issue, that's just a limitation of controllers. Added a workaround.
BreadBread (talk | contribs) |
m (Cleaning up Known Issues section... No need to add who found it and when. Regarding the pressure sensitivity - that's not an emulator issue, that's just a limitation of controllers. Added a workaround.) |
||
| Line 186: | Line 186: | ||
== Known Issues == | == Known Issues == | ||
{{Issue | {{Issue | ||
|IssueName=Pressure Sensitivity Long-Term Issue(PCSX2) | |IssueName=Pressure Sensitivity Long-Term Issue(PCSX2) | ||
|IsFixed=0 | |IsFixed=0 | ||
|IssueLevel=1 | |IssueLevel=-1 | ||
|Description=PCSX2's plugin-to-core merge on 1.7 development builds uses LilyPad for handling gamepad inputs. The problem with this is that the version of LilyPad used doesn't contain pressure sensitivity for anything other than L2 and R2 if you're not using a DualShock 3 controller. | |Description=PCSX2's plugin-to-core merge on 1.7 development builds uses LilyPad for handling gamepad inputs. The problem with this is that the version of LilyPad used doesn't contain pressure sensitivity for anything other than L2 and R2 if you're not using a DualShock 3 controller. | ||
This is a problem because you can't even rebind the left or right trigger to the square button to access pressure-sensitivity functionalities like lowering your weapon, and may become a BIG problem in the future. I would overall suggest to the devs to fix it sooner rather than later so that this feature isn't outright *lost to time* whenever DualShock 3's become difficult to find. | This is a problem because you can't even rebind the left or right trigger to the square button to access pressure-sensitivity functionalities like lowering your weapon, and may become a BIG problem in the future. I would overall suggest to the devs to fix it sooner rather than later so that this feature isn't outright *lost to time* whenever DualShock 3's become difficult to find. | ||
|Workaround=You can manually change the sensitivity of button inputs to get around this issue if you don't have a DS3 controller. | |||
}} | }} | ||
{{Issue | {{Issue | ||
|IssueName=Left Side Pixel Artifacts | |IssueName=Left Side Pixel Artifacts | ||
|IsFixed=0 | |IsFixed=0 | ||
| Line 204: | Line 202: | ||
|Description=Alongside the left side of the screen, there are artifacting pixels that are 1 pixel wide. Easiest to see at native resolution. Happens across pretty much the entire game. | |Description=Alongside the left side of the screen, there are artifacting pixels that are 1 pixel wide. Easiest to see at native resolution. Happens across pretty much the entire game. | ||
|Workaround=No known solution. | |Workaround=No known solution. | ||
}} | |||
{{Issue | {{Issue | ||
|IssueName=Vamp Stop VFX Bug | |IssueName=Vamp Stop VFX Bug | ||
|IsFixed=0 | |IsFixed=0 | ||
|IssueLevel=0 | |IssueLevel=0 | ||
|Description=[Minor spoilers] | |Description=[Minor spoilers] | ||
During the Vamp boss fight, Vamp throws traps to stop you from moving. If the center of the trap is located inside one of the railings at the edge of the map, the effect doesn't render at all | During the Vamp boss fight, Vamp throws traps to stop you from moving. If the center of the trap is located inside one of the railings at the edge of the map, the effect doesn't render at all | ||
}} | |||
{{Issue | {{Issue | ||
|IssueName=Eavesdrop Cutscene Olga Movement Error | |IssueName=Eavesdrop Cutscene Olga Movement Error | ||
|IsFixed=0 | |IsFixed=0 | ||
| Line 227: | Line 220: | ||
[reason for "Serious" below contains minor spoilers] | [reason for "Serious" below contains minor spoilers] | ||
Pretty big deal because it skips the part that explains how Revolver Ocelot has both of his arms for this point in the game. This isn't your average cutscene glitch. | Pretty big deal because it skips the part that explains how Revolver Ocelot has both of his arms for this point in the game. This isn't your average cutscene glitch. | ||
|Workaround=No known solution. | |Workaround=No known solution. | ||
}} | |||
{{Issue | {{Issue | ||
|IssueName=Big Shell Map ID Text Error | |IssueName=Big Shell Map ID Text Error | ||
|IsFixed=0 | |IsFixed=0 | ||
| Line 241: | Line 231: | ||
|Description=When paused and looking at the Big Shell map, later sections of the title do not display unless it's the frame after you hit START to unpause. Does not happen with every title like "Shell 1 Core" but most of them do have this issue. | |Description=When paused and looking at the Big Shell map, later sections of the title do not display unless it's the frame after you hit START to unpause. Does not happen with every title like "Shell 1 Core" but most of them do have this issue. | ||
|Workaround=No known solution. | |Workaround=No known solution. | ||
}} | |||
{{Issue | {{Issue | ||
|IssueName=Fortune First Cutscene Flickering | |IssueName=Fortune First Cutscene Flickering | ||
|IsFixed=0 | |IsFixed=0 | ||
| Line 252: | Line 240: | ||
|Workaround=No known solution. | |Workaround=No known solution. | ||
Was tested with both OpenGL and DX11 Software modes. DX11 performed noticeably better but still bottlenecked a GTX 1660 Super paired with a Ryzen 7 3700X. | Was tested with both OpenGL and DX11 Software modes. DX11 performed noticeably better but still bottlenecked a GTX 1660 Super paired with a Ryzen 7 3700X. | ||
}} | |||
{{Issue | {{Issue | ||
|IssueName=Weapon Laser Issue | |IssueName=Weapon Laser Issue | ||
|IsFixed=0 | |IsFixed=0 | ||
| Line 262: | Line 248: | ||
|Description=Weapon lasers appear significantly darker than on original hardware in the tanker. | |Description=Weapon lasers appear significantly darker than on original hardware in the tanker. | ||
|Workaround=Use dev build 1.7.2234 instead of the stable release. | |Workaround=Use dev build 1.7.2234 instead of the stable release. | ||
}} | |||
{{Issue | {{Issue | ||
|IssueName=Infrared Sensors Issue | |IssueName=Infrared Sensors Issue | ||
| Line 271: | Line 256: | ||
|Description=In the tanker, the infrared sensors are visible without the need to shoot a fire extinguisher. Appears as black lines that turn red while the extinguisher is active. | |Description=In the tanker, the infrared sensors are visible without the need to shoot a fire extinguisher. Appears as black lines that turn red while the extinguisher is active. | ||
|Workaround=Use dev build 1.7.2234. | |Workaround=Use dev build 1.7.2234. | ||
}} | }} | ||
| Line 279: | Line 262: | ||
|IsFixed=0 | |IsFixed=0 | ||
|IssueLevel=0 | |IssueLevel=0 | ||
|Description= Some cutscenes are rendered at 10fps with motion blur to give a dramatic slow-motion effect but the effect is only shown on a small portion at the left side of the screen. | |Description= Some cutscenes are rendered at 10fps with motion blur to give a dramatic slow-motion effect but the effect is only shown on a small portion at the left side of the screen. A great place for testing this is Solidus Snake's introduction, right before the Harrier fight. | ||
|Workaround=Use Software mode. | |Workaround=Use Software mode. | ||
}} | }} | ||