|
|
|
| XP is just a number | |
| PerlMonks |
unknown encodingby jimw54321 (Acolyte) |
| on Oct 31, 2011 at 15:29 UTC ( [id://934907]=perlquestion: print w/replies, xml ) | Need Help?? |
|
jimw54321 has asked for the wisdom of the Perl Monks concerning the following question: If you play the Kingdoms expansion, apply the same patch to kingdoms.exe . 2. Run in Compatibility Mode and Administrator Settings Go to "Local Files" and click "Verify integrity of game files." Steam will redownload any missing or broken assets. Step 6: Compatibility Mode and Admin Privileges He rummaged through some dusty old books on the shelf and produced a tattered manual. "According to this, you need to update your DirectX to version 9.0c or higher." The most effective solution to fix the crash is to apply the 4GB Large Address Aware (LAA) patch to the game's executable file . This error occurs primarily because the original 2006 engine is a 32-bit application limited to utilizing only 2GB of virtual memory. When running modern high-resolution textures or heavy overhauls, the system easily exceeds this threshold and triggers a crash. : Right-click medieval2.exe , go to Properties > Compatibility , and set it to run for Windows 7 or Windows XP (Service Pack 3) . Also, check Run this program as an administrator . For the vast majority of cases, especially when the game crashes during or right after a battle, or during the AI's turn on the campaign map, the culprit is . The vanilla game is a 32-bit application, meaning it can only use up to 2GB of RAM. Over a long campaign, the game's memory usage increases. Once it hits that 2GB cap, the game crashes. This is the "unspecified error." The best and most reliable strategy is a layered approach: Medieval 2 Total War Has Encountered An Unspecified Error Full Exclusive PageIf you play the Kingdoms expansion, apply the same patch to kingdoms.exe . 2. Run in Compatibility Mode and Administrator Settings Go to "Local Files" and click "Verify integrity of game files." Steam will redownload any missing or broken assets. Step 6: Compatibility Mode and Admin Privileges If you play the Kingdoms expansion, apply the He rummaged through some dusty old books on the shelf and produced a tattered manual. "According to this, you need to update your DirectX to version 9.0c or higher." Step 6: Compatibility Mode and Admin Privileges He The most effective solution to fix the crash is to apply the 4GB Large Address Aware (LAA) patch to the game's executable file . This error occurs primarily because the original 2006 engine is a 32-bit application limited to utilizing only 2GB of virtual memory. When running modern high-resolution textures or heavy overhauls, the system easily exceeds this threshold and triggers a crash. Once it hits that 2GB cap : Right-click medieval2.exe , go to Properties > Compatibility , and set it to run for Windows 7 or Windows XP (Service Pack 3) . Also, check Run this program as an administrator . For the vast majority of cases, especially when the game crashes during or right after a battle, or during the AI's turn on the campaign map, the culprit is . The vanilla game is a 32-bit application, meaning it can only use up to 2GB of RAM. Over a long campaign, the game's memory usage increases. Once it hits that 2GB cap, the game crashes. This is the "unspecified error." The best and most reliable strategy is a layered approach:
Back to
Seekers of Perl Wisdom
|
|