-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] MGS2 | MGS3: Vector rain doesn't get scaled up #90
Comments
$275 bounty to whoever resolves this issue. |
Is the bounty still up? I have an idea of what's going on but this game is hard to debug lol |
Curious, does the upscaling settings from the 2.0.0 version present this issue? If not, it might be a good idea to "support" this new upscaling setting to prevent stuff like this, if desired. Tho I know the new version of MGSHDFix is currently being made. |
The issue is still present with 2.0.0 with upscaling. I would presume it's even the reason that Konami opt'd to limit the games' max native resolution to 1080p & have all the extended resolutions be through pure FSR upscaling. |
It is still up - my share ($175) would have to be paid out in a few months at the earliest as I've been out of work due to immigration bureaucracy, but the remaining pot is payable as other have chipped in. |
A little more background on this bug - this issue is not unique to the MC & has actually been present since the 2002 Xbox port of Substance. My running theory has been that something about all these vector effects likely didn't get implemented right when they moved from PS2 Renderer -> DirectX, and then that messed up version of the code has been used as a base for every version since. The 2002 Xbox port, 2003 PC Port, & the 2011 PS3 & 360 HD Collection versions all have these same exact scaling issues. |
These aren't textures/sprites, but actual vector lines that aren't being scaled up with resolution changes.
PC Version:




The same areas in PCSX2 set to 1440 internal resolution, which DOES scale those vectors:




Similar issue is also present with #104 & #96
The text was updated successfully, but these errors were encountered: