Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
You *can* play with the Rimtech tracks if you rip them from the disk, convert them into .ogg and put them in the proper folder with the proper filename, but then Mil-Agro will play the Rimtech tracks too because the game is hardcoded to look for track numbers, not filenames, so you can't mix and match.
The best option available is to put the Rimtech tracks into the folder under different names, then write a batch file that swaps their names with those of the Mil-Agro tracks, executes the game, then restores the original filenames once the game exits. It's not perfect, but it should work.
Anyone know a fix for this?
1- You need to run regedit.exe, then go to
Equipo\HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Psygnosis\Metal Fatigue (or search "Metal Fatigue" if you can't find it).
Look for "Driver" key and make sure it's set to 1. (Glide)
2- Install NGlide from Zeus: http://www.zeus-software.com/downloads/nglide
3- Download this dgvoodoo2 patch and paste contents in main game folder: https://drive.google.com/open?id=1umSij0jVcyxUbK71PokY4I9gfUt5iSQi
Password is 1234
I included a Reshade preset for it but it's optional.
4- (Recommended) Set in-game HUD resolution to 800x600 so the camera is not too far. Make sure "Enhance Pointer Precision" is set to OFF in Windows.
It does NOT seem to be the heap crash. At least, I installed the fix for it and it still crashes a few seconds after loading the above save. If I don't touch anything between loading and crashing, the fault offset remains the same but if I switch map layers, it still crashes with a different offset. Memory usage during these few seconds starts at 197 MB and rises to 204 MB before crashing.
Over the years and across three PCs, this particular map has always crashed for me while the others pretty much never did. I have no idea what's up with it.