Metro 2033 - Ranger Hardcore Walkthrough Part 9 - Outpost + Black Station
Here's a tougher level to remain fully hidden all the way... I use stealth on the first few but then go combat heavy on the rest. Grenading all the soldiers as they form a circle is probably the easiest way to take them out.
Alternatively, you can wait until they enter the metro station entrance and once again grenade/ambush them from behind. Throwing knives tend to bounce off a lot from their armour unless you can get a good clear aim at their sides.
At Black Station I pick up the unscoped VSV simply because not much sniping will be required from that point onwards. Also, the scope is near useless in dark underground levels due to the glare on the lens.
Two deaths in this video, I get auto-shotgunned immediately after I land near the hole at 9:52 and then in the 'car graveyard'... by chance I managed to join the two videos at a point where the transition is nearly unnoticable at 12:34.
I also realize now that I forgot to cut off the loading screen at the end of 'Outpost'... that's why you see the loading screen twice in a row before the next level.
This is played on Ranger Hardcore difficulty. PLAYLIST: • Metro 2033 Walkthrough HD
I edited the user.cfg with notepad in order to increase the FOV.
To do this you must edit the SICK_FOV value in the THREE user.cfg files located here:
C:\Users\[your username]\AppData\Local\4A Games\Metro 2033
C:\Program Files (x86)\Steam\steamapps\common\metro 2033
C:\Program Files (x86)\Steam\userdata\[random set of numbers]\43110\remote
Important: You need to keep the fullstop. I set it to "SICK_FOV 65." Remember that Metro uses vertical FOV measurement rather than the common horizontal measure. A vertical FOV of 65 is a horizontal FOV of 90 on a 16:10 1920x1200 resolution. Setting it any higher might make some errors appear like seeing the 'end' of your arms during reload animations or cutscene animations. You can try to see what you like best.
I just think the default FOV is ridiculous... and unfortunately, this is becoming way to common an issue for console ports nowadays.