• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

2016 PC Screenshot Thread of No Compromises

Nick Pal

Member
Those latest portraits, 2 of them are at 84% and 1 is at about 90% whereas your previous page shots were all 100%.
Maybe there's something funky going on with your faststone settings.

Where can I get that info? I can't see it under file properties. Yeah I think the issue is my Faststone settings. I've been posting from work and didn't realize I had it set to default at 90% lossless where as the one I use at home is 100%. I guess that 10% makes a noticeable difference..

What are you using to actually take the shots? MSI AB, etc? If you're not using an external program but just printscreen or some UWP screenshot function that's probably what's causing the "Super JPEG-y" shots.

I always use Afterburner. I downloaded a newer version last week but forgot to check to see what the default lossless percentage is there. It's probably at 90 too I'm guessing.
Edit: No, Afterburner is at 100% Jpg quality. Faststone settings apart from 90% quality were all okay, Smooth and Lanczos filter. ColorSubsampling disabled..so I'll try some shots again I guess.
 
30410787953_b4a7edbcaf_o.png


31074622342_cff750ed9a_o.png


Album
 

Parsnip

Member
Where can I get that info? I can't see it under file properties. Yeah I think the issue is my Faststone settings. I've been posting from work and didn't realize I had it set to default at 90% lossless where as the one I use at home is 100%. I guess that 10% makes a noticeable difference..
You can use JpegSnoop to get a good idea about chrominance and luminance quality of a jpg (and bunch of other tech info too).
 

NattyDread

Neo Member
Those don't look like freecam shots but I could be wrong. If they are, great! Means I don't have to update my table this weekend =)

Aww Yiss! :p
Didn't wanna beg but since you offered...
Been holding off the playthrough until the final episode and some working cam tools.
 
Aww Yiss! :p
Didn't wanna beg but since you offered...
Been holding off the playthrough until the final episode and some working cam tools.

https://drive.google.com/open?id=0B5GvHRzSYX08VC01dnNQTmV0M3c

Updated Camera + FOV.

Also updated the camera lock for you hotsamplers out there. If you alt-tab outside of the game, the mouse inputs are still being read so when you alt-tab back in for a screenshot, the camera is usually pointed somewhere else. And you have to do that for the new resolution to kick in. So pressing F5 before alt-tabbing will prevent that.

Timestop didn't need to be updated.
 

NattyDread

Neo Member
https://drive.google.com/open?id=0B5GvHRzSYX08VC01dnNQTmV0M3c

Updated Camera + FOV.

Also updated the camera lock for you hotsamplers out there. If you alt-tab outside of the game, the mouse inputs are still being read so when you alt-tab back in for a screenshot, the camera is usually pointed somewhere else. And you have to do that for the new resolution to kick in. So pressing F5 before alt-tabbing will prevent that.

Timestop didn't need to be updated.


Hmm... :D
It's the Bangkok lvl. Freecam moves random boats.
Only tested here and on Marrakesh. Works fine there.
 

OtisInf

Member
https://drive.google.com/open?id=0B5GvHRzSYX08VC01dnNQTmV0M3c

Updated Camera + FOV.

Also updated the camera lock for you hotsamplers out there. If you alt-tab outside of the game, the mouse inputs are still being read so when you alt-tab back in for a screenshot, the camera is usually pointed somewhere else. And you have to do that for the new resolution to kick in. So pressing F5 before alt-tabbing will prevent that.

Timestop didn't need to be updated.

LOL I just spend a few hours writing my own! ;) http://www.deadendthrills.com/forum/discussion/comment/10552/#Comment_10552 Check your own forums too man ;)

Learned a lot so it was no time wasted. Will see if you use different addresses than I do :) Anyway, yours looks better so I'll see if I can update that one with lookvector movement tomorrow.

(edit) you seem to use different addresses. Interesting.
 
Both Paris and Sapienza worked good for me on Ultra settings. 30-60. But around 40-45 most of the time.
But once i started playing Marrakesh fps tanked to 18-20. Market and Protests are the worst because there are a lot of NPCs, so i had to lower some setting. But other than that, it's fine. I am on DX11 tho.

R9 280x
i5-4460
8GB
W7

That's rough. I have min 45fps mins with a 290x, i7 @4.0ghz, 16gb, W10.
 
Check your own forums too man ;)

The only time I had to work on it was while my daughter was taking a nap. So I didn't do a tour of all da forums :p

If you look at my script, you'll see that my camera lock (for hotsampling) is just killing the opcode that writes to the rotation matrix. Typically when you find the camera coordiantes, the rotation matrix is directly adjacent (either before or after). For hitman it's before:


Good luck getting that to work :)

EDIT: Got the boat thing fixed. Let me do some testing and then I'll upload.
 

OtisInf

Member

Thank you kind, sir! :D

The only time I had to work on it was while my daughter was taking a nap. So I didn't do a tour of all da forums :p
That's a good excuse :) No worries :)

If you look at my script, you'll see that my camera lock (for hotsampling) is just killing the opcode that writes to the rotation matrix. Typically when you find the camera coordiantes, the rotation matrix is directly adjacent (either before or after). For hitman it's before:
Good luck getting that to work :)
Matrix is bigger than that though (4x4 floats). I think what you have there is the lookat vector, which is obviously the one you want (as the projection matrix is calculated from that + the camera coords) :) Will look at it tomorrow, thanks a million! :)
 

OtisInf

Member
Some shots from the overflow bin

30450445973_6980218e2b_o.jpg


Spent a lot of time fighting with x64 calling conventions in the Hitman CT table to make the camera move related to the view direction, but finally have it working, hopefully I can fix the vector misalignment tomorrow so the CT table (with Jim's camera interception) can be released :)
 
Top Bottom