• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Metro: Last Light update: AMD fixes and FOV

C

csbin

Senior member
http://steamcommunity.com/app/43160/discussions/0/810924774395015649/

A patch has been released on Steam to fix issues with AMD hardware, and improve performance for these cards. It's live now, but might take a few minutes to reach everyone. Restart your client or verify local files if it doesn't download automatically.

It also fixes a shadow visual corruption bug on AMD 7xxx cards, and fixes an issue with the game starting only in 3:1 resolution on some TVs.

In addition, you can now customize the FOV this way:

After starting the game up, the user.cfg will be updated with the r_base_fov attribute. You can find this in %LOCALAPPDATA%\4A Games\Metro LL\. Tweak it at your leisure!
 
This again illustrates the annoying part of games being backed by either nVidia or AMD. Last light was nVidia, so AMD then has to rush to get fixed drivers out because they are not given early access. On Tomb Raider is was the opposite, nVidia had to rush to get out updated drivers.
 
AMD didn't have to release drivers to fix the shadow issues, that required a fix from the developers, 4A. Given this and the piece from someone who seemed to have some insight into 4A's practices, it seems they just weren't able to thoroughly test AMD configurations due to budget constraints.

http://www.pcgamer.com/2013/05/15/4...el=ref&ns_source=steam&ns_linkname=0&ns_fee=0

Edit: The point being that I don't see the launch issues on AMD cards a sign of Nvidia's TWIMTBP program getting in the way, but more of a small team not being able to properly conduct the test needed to properly insure compatibility over a wide range of hardware.
 
Last edited:
A FOV adjustment was really needed. Hopefully it doesn't break anything. The game is a system killer though, so more FOV is going to make it even harder to run. I can't hold 60fps as much as I'd like, in some scenes it's dropping to the 30s.
 
(sic)Klown12 said:
AMD didn't have to release drivers to fix the shadow issues, that required a fix from the developers, 4A. Given this and the piece from someone who seemed to have some insight into 4A's practices, it seems they just weren't able to thoroughly test AMD configurations due to budget constraints.

http://www.pcgamer.com/2013/05/15/4...el=ref&ns_source=steam&ns_linkname=0&ns_fee=0

Edit: The point being that I don't see the launch issues on AMD cards a sign of Nvidia's TWIMTBP program getting in the way, but more of a small team not being able to properly conduct the test needed to properly insure compatibility over a wide range of hardware.
Click to expand...

I have the same feeling. The patch came out 24 hours after the launch. It's for european people a zero-day patch. So i guess it was on their agenda to fix AMD's problem as soon as possible.
 
Guru3D benchmarks: http://www.guru3d.com/articles_pages/metro_last_light_graphics_performance_review_benchmark,6.html

index.php

index.php
 
Stuka87 said:
This again illustrates the annoying part of games being backed by either nVidia or AMD. Last light was nVidia, so AMD then has to rush to get fixed drivers out because they are not given early access. On Tomb Raider is was the opposite, nVidia had to rush to get out updated drivers.
Click to expand...


Well once the PS4/Xbox720 come out everything, console port, will be made for AMD. 😉
 
With the new patch, my Gigabyte 7950 (stock clock 1Ghz ), jumped from 37fps average to 47fps average (1080p, No physx, No SSAA). 27% increase is not bad at all.

Waiting for new drivers as well, before doing some proper testing.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top