Some users experience extreme screen tearing, while the game itself runs perfectly well otherwise. In such cases, some have solved this issue by editing the user.cfg file in the game directory C:\Program Files (x86)\Steam\SteamApps\common\metro 2033 and change “r_vsync off” to “r_vsync on”.
However many users prefer not to have V-sync enabled, and have found the solution in third party software. Please view this forum thread for further detail:
Black Vertical Lines in DX11
As depicted here: http://www.youtube.com/watch?v=_ABNwfEp9L0&feature=youtu.be
These black vertical lines seem to only occur with DX11, switching to DX9/10 is the simple way to avoid this issue. It seems that the common screen resolution that would see this issue is 1366x768, so in some cases, switching resolutions is another possible solution. Some users have reported that they fix this issue by deactivating the advance DOF in the advanced DX11 options.
PhysXloader.dll is missing
After installing the game, an error message appears when trying to launch it that says the program can’t continue because PhysXloader.dll is missing from the computer. Various users have found different fixes work for them:
- Restart Steam first, then see if it will launch. If that doesn’t work, restart the computer.
- Locate the PhysX file in the following location: C:\Program Files (x86)\Steam\steamapps\common\metro 2033\install and run it.
It may need to be uninstalled before being installed again manually. (It can also be uninstalled via Add/Remove Programs).
- If not, uninstall it manually as mentioned in the above step, and launch the game by running the executable in the game folder rather than from Steam. If that worked, restart the computer and then afterwards the game should run from Steam directly.
- If the user cannot find the file located in the above location, typing in “PhysXloader.dll” in a search engine should lead them to a downloadable link for that file. Paste it in either the Metro 2033 game folder, or place it in the C:/Windows/system folder.
X3DAudio1_7.dll is missing
This is part of the DirectX install. Locate the DirectX folder in the following location: C:\Program Files (x86)\Steam\steamapps\common\metro 2033\install\D3D11Install and manually install the D3D11Install file there.
Game not starting (including crash on launch)
Most launch issues could be a result of one of the above mentioned packages not having been installed correctly. Go to the install folder in the Metro 2033 folder and try uninstalling (if needed) then reinstalling each of these packages separately: D3D11Install and DirectX, Phys X, and vcredist (C++ redistributables).
With all crashes, the user should attempt each fix in the following order:
- Restart Steam.
- Restart computer.
- Uninstall/Reinstall PhysX.
If none of the above work, the save files could be corrupted. Delete the game profile from C:\Users\”username”\My Documents\4a games\metro 2033
Widescreen and Multi-Monitors
Many users reported problems with multi-monitor setups like Eyefinity, and widescreen resolutions. Certain users experienced extreme stretching in many widescreen resolutions. A patch for this went out in March 2010 and corrected this, however some users still report that in the 16:10 aspect ratio the issue still occurs. Users suggested changing the FOV in the .cfg files. Though it will improve the issue slightly, it does not fully fix the image stretching. To attempt a fix, begin with changing the resolution in both .cfg files to the monitor’s native resolution. If that doesn’t work, change the FOV in the .cfg files to “fov 60”. The two user.cfg files should be in the following locations:
- C:\Program Files (x86)\Steam\userdata\”username”\43110\remote
- C:\Program Files (x86)\Steam\steamapps\common\metro2033
Another suggestion was that if the user has a VGA cable, switching it for a DVI/HDMI cable should solve the issue.
Other solutions can be found here:
Unable to install Metro 2033
A common complaint from users recently has been that they are completely unable to install the game. When a ticket was logged, the following response was given, though unfortunately has not been a fix for all users who experienced this issue:
- Exit Steam and go to the Steam folder (default C:\Program Files (x86)\Steam)
- Delete all contents in the folder except the Steam.exe and the Steamapps folder.
- Restart the computer.
- Launch Steam.exe from within the Steam folder (not from any previously made shortcut).
- With Steam running again, try installing the game.
Note: This process will not affect any currently installed games and save files.
Common Gameplay Issues
- Accidentally switching to firing Military-Grade Rounds instead of the dirty ammo in a gun. The Controls section is missing a note on switching between the ammo types so it has caused some confusion in the forums. Hold the reload key (PC default: [R]) to switch between dirty rounds and MGRs.
- A lot of users report lag after finding a child crying over a man’s dead body. However, what they describe as lag is actually because the child is on Artyom’s back and has slowed down his movements. This greatly affects Mouse sensitivity and causes slowed reaction time. The “problem” goes away once the boy is no longer being carried by Artyom.
- Loss of inventory functionality. Reload last checkpoint or restart the chapter. If that doesn’t work, reload a save from a previous chapter and try again. In some cases
- It was suggested that this issue was a result of entering a QTE or a cutscene while using a Medkit. Load the last checkpoint and try to avoid such a combination.
- If the user has reached the limit in Filters/air, they won’t be able to pick up any more Filters until they start using up what’s already in their inventory. Also, not all Filters can be picked up as some are considered to be used up. Same with Gasmasks, if the Gasmask on the ground is cracked, the user won’t be able to swap it for their own.
- A common progression block has been mentioned often, in which the NPC, Bourban, becomes frozen and will not speak to the player anymore making it impossible to progress. This is believed to be caused by running ahead of Bourban before he is finished talking to the player upon arrival at the Market.