Resolved: [Bug Report] [Silent Hill 2] GSdx Screenshots have wrong height.
#11
(02-07-2016, 05:18 PM)refraction Wrote: I'd like to direct people to this post http://forums.pcsx2.net/Thread-Removal-o...#pid470787

I don't think the F8 screenshot function captures the physical display dimensions, rather the rescaled resolution which it's currently rendering as that's how it always worked whenever I had used it.

Quote:I checked out this issue with the PAL version and didn't manage to reproduce it. I tried a slightly newer dev build than the one in the OP from late 2014 and one of the latest 2016 dev builds , but all screenshots were saved at the height I selected in-game.

I'd guess it's fixed then, better wait for Ryudo to move it to the resolved subforums.

Sponsored links

#12
Could I just use this thread to mention that I never managed to open the .bmp snaps done with pcsx2 in Adobe Photoshop?
It gives me a 'missing module' error every time... (regular .bmp and other files don't have this problem...)

I dunno... maybe the files are wrongly signed or something...
(and yes, they open OK in Paint... Strange, isn't it...?)
_____
Intel Core i7-5820K/16GB DDR4/GeForce RTX 2070 Super/MSI X99A Gaming 7 motherboard
...some of my PS2 games videos...
#13
(02-07-2016, 06:48 PM)ssakash Wrote: I don't think the F8 screenshot function captures the physical display dimensions, rather the rescaled resolution which it's currently rendering as that's how it always worked whenever I had used it.

Yep. That's correct.


My monitor only supports up to 1920x1200 normally. But setting the internal resolution to 2560x1440 for example, allowed me to take screenshots at THOSE dimensions. Which is why I love custom resolutions.

Scaling is nice and more stable, but you sometimes get weird results when used in conjunction with widescreen hacks, etc when taking screenshots with F8.


I haven't tested the game in recent revisions yet. I'll test it later and will post the results to see if it's fixed or not.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 32 GB (2x16GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Samsung 980 1TB | Windows 10 Pro x64 (22H2)
#14
Having set a Custom Resolution of 2560x1440 -- The screenshots ended up being 2560x1260.
So for custom resolution it still doesn't seem to be saving at the correct dimensions.

[Image: gsdx_20160208013357.png]


Meanwhile I tested Kingdom Hearts II with the exact same thing - The screenshots were at the correct dimensions (2560x1440).

[Image: gsdx_20160208013641.png]


@Parotaku - The screenshots open fine in Photoshop for me. That's how I converted them to PNG. Both CS5 and CC-2015 work for me.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 32 GB (2x16GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Samsung 980 1TB | Windows 10 Pro x64 (22H2)
#15
What version of SH2 are you using and do you have any patches enabled? I tried the same custom resolution and got all 2560x1440 snaps.
#16
NTSC version. And no patches are applied to it.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 32 GB (2x16GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Samsung 980 1TB | Windows 10 Pro x64 (22H2)
#17
What's the resolution of the captured screenshot when you set the custom resolution to 2560 X 1646 ?

I think I got a little grasp of the issue (It's probably related to the SetScale function on Texture cache), I'll try to patch up a build to fix the issue. (It might most likely cause other issues with the game though)
#18
Using that custom res does save it in a correct output.

Also, using that resolution you mentioned causes a horizontal line to be visible in exactly the middle of the screen. (This is likely again related to the old bug where only half of the game was being displayed).




Meanwhile I ran into another issue with this game that I'll be making a topic about in the near future after doing some further research on it. (Completely unrelated, but somewhat more important).

[Edit] Disregard the new issue mentioned that I was gonna make a new topic for. It was my own fault.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 32 GB (2x16GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Samsung 980 1TB | Windows 10 Pro x64 (22H2)
#19
@Ryudo

Could you provide a GS dump of the issue ? I'd like to fix this issue ASAP.
#20
Nevermind, Refraction gave me one dump. Build is now live at #1365.




Users browsing this thread: 1 Guest(s)