2017 PC Screenshot Thread

*snip fantastic tutorial*

Thanks so much for that. Really easy to understand.

The only snag I've run into is... none of the shaders disable the vignette.

wtf?

I've tried it on 4 different maps, 4 different locations, and can't find the vignette shader at all. It has to be accessible somewhere, because activating Ansel's freecam disables the vignette. Maybe I can try to find it while Ansel is activated? I didn't try that.

I am, however, going to put your tutorial to good use to create a toggle to hide weapons, and a couple of other things, so it's not all bad news! And I'll keep investigating this curious vignette thing. So frustrating!

(Found rim lighting though - woo!)
 
Thanks so much for that. Really easy to understand.

The only snag I've run into is... none of the shaders disable the vignette.

wtf?

I've tried it on 4 different maps, 4 different locations, and can't find the vignette shader at all. It has to be accessible somewhere, because activating Ansel's freecam disables the vignette. Maybe I can try to find it while Ansel is activated? I didn't try that.

I am, however, going to put your tutorial to good use to create a toggle to hide weapons, and a couple of other things, so it's not all bad news! And I'll keep investigating this curious vignette thing. So frustrating!

(Found rim lighting though - woo!)
Weird! Well at least you solved one problem :) Btw, you can create multiple toggles at once: the 'x' here in this code:
Code:
float4 params = IniParams.Load(0);
  if (params.x == 0)
  {
is the variable you set to 0 under '[keys]' in the ini file. So you can use 'y' or 'z' or whatever you want with different keys and test on it instead of x. So you can e.g. use 'x' for one shader and y for another. If I look at PhilGPT's phone shots from ME:A here https://twitter.com/PhilGPT/status/848820555038031873 I don't see a vignette in some shots and see it in one but I think that's because of AO (caused by a spotlight behind the camera it seems). Which might be the reason why you don't see it with ansel. Wild guess tho...
 
If I look at PhilGPT's phone shots from ME:A here https://twitter.com/PhilGPT/status/848820555038031873 I don't see a vignette in some shots and see it in one but I think that's because of AO (caused by a spotlight behind the camera it seems). Which might be the reason why you don't see it with ansel. Wild guess tho...

The vignette seems to vary in strength depending on the scene - it is generally quite mild (nowhere on a par with the vignette in the original trilogy - more like the one in DA:I - which could be toggled using the Cinematic Tools), but I can see it in 3 of those shots but that's perhaps because I know what I'm looking for and have seen the difference it makes when Ansel is activated.

That's interesting about the AO, though. I didn't realise that was a possibility. I'll turn AO off and see if it makes a difference.

On the 3Dmigoto toggle: if I was to share the rim lighting toggle with others, what files do they need in order to make it work? Do they need to install 3Dmigoto first, and then I give them the dxgi.ini and the shader inside ShaderFixes?

Thanks a lot for all the help on this. You're always very helpful, and it's appreciated :)

Edit: turning off HBAO+ doesn't seem to affect the vignette. Not sure what's going on. I guess I'll wait and see if hattiwatti cracks the conundrum.
 
What's funny with MEA's HUD is that the default FB's UI toggle variable leads to game's options menu disappearing after its use - and they only re-appear after the game's restart.

This game is probably the buggiest game I've seen in years.
 
What's funny with MEA's HUD is that the default FB's UI toggle variable leads to game's options menu disappearing after its use - and they only re-appear after the game's restart.

This game is probably the buggiest game I've seen in years.

You don't need to use the console command if you use hattiwatti's tools.

But... I don't know what you're talking about. I just turned the ui off and on again via the console and all my menus are there just fine.

Edit: no, you're right. It's just the video/graphics options etc that are missing - the rest of all the menus work fine. That's very odd.

Still, it's entirely avoidable by using hattiwatti's tools.
 
33779972056_241e9f297b_o.png
 
On the 3Dmigoto toggle: if I was to share the rim lighting toggle with others, what files do they need in order to make it work? Do they need to install 3Dmigoto first, and then I give them the dxgi.ini and the shader inside ShaderFixes?
that's a possibility, but the easiest is to grab one of the hud toggles (e.g. this one) https://mega.nz/#!FQQShJyS!Ipg4CycflblD2LvZdlfQMgl29ptx_yqPX_HA03u5hoU, then change the readme.txt, dxgi.ini and shaderfixes folder contents with yours and you're good to go :) The ppl you share it with then just have to copy everything into the game bin folder and it should work

Thanks a lot for all the help on this. You're always very helpful, and it's appreciated :)
No problem :) sharing knowledge is how everyone learns, right :)
 
You don't need to use the console command if you use hattiwatti's tools.

But... I don't know what you're talking about. I just turned the ui off and on again via the console and all my menus are there just fine.

Edit: no, you're right. It's just the video/graphics options etc that are missing - the rest of all the menus work fine. That's very odd.

Still, it's entirely avoidable by using hattiwatti's tools.

Sure, but I generally try to avoid running more injectors than absolutely necessary as this is a solid recipe for major instability, which is bad as I generally take my screenshots while playing the game.

That being said, HattiWatti's CT for MEA work absolutely fine with MSI AB so yes, this solves the issue. Still funny that the issue is even occurring.
 
Sure, but I generally try to avoid running more injectors than absolutely necessary as this is a solid recipe for major instability, which is bad as I generally take my screenshots while playing the game.

That being said, HattiWatti's CT for MEA work absolutely fine with MSI AB so yes, this solves the issue. Still funny that the issue is even occurring.

hattiwatti's tools are usually as stable as you can get. The only problems arise if you try to do something with them that isn't supported yet. For example, in ME:A you can't currently use them to pause during a cutscene, because the game will crash.

But then, if you're pushing your game to get the very best screenshots you possibly can you have to expect there will be instability along the way. Either you push the hotsampling too far, or you try to do too much all at once, or you start doing weird things with cheat engine... it's all par for the course, and it's what can lead to some of the best shots too. I lost my character's entire body model yesterday, she was just a floating head for a while ¯\_(ツ)_/¯
 
33683865702_cd0f6c224e_o.jpg


32996296314_246c8763b2_o.jpg

Weee! (4 shot panorama)

The motorcross minigame is such fun :) 12 minutes endurance across the whole bay area. So many different landscapes. They put so much effort in tiny details. Hats off to the WD2 team.
 
These ME:A shots are amazing! I'm going to hold off on playing it anymore until I get a better GPU and/or upgrade my PC so I can really push it.
 
I dunno why people complain that this game runs like an ass? I mean i get 40+FPS all maxed out but AA which i run at 2xMSAA and still runs like a champ at 8k res...and that's all of a single GPU!

33016489734_e1127e6b9c_o.jpg


33046790513_57867440ee_o.jpg
 
Top Bottom