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
Running Rome and Barbarian Invasion through Alexander was always the first class in modding Total War games for which I was the designer of how through a hint from another modder now employed by CA from before he was employed.
My apologies qualifying myself as that is just so you will understand. 90% of that list is bunk and untrue.
Make sure RTW is using your NVIDIA graphics card and not your integrated intel GPU. True if you are running an INTEL laptop, but it wont stop the lag in Rome because the problem is the presence of that chip and not the use of that chip.
Set your maximum pre rendered frames to 1 on RTW and 2 for BI and Alex. That is ONLY if you have a NVIDIA card and both Rome and BI are set to 1. Do not do anything to Alexander.
Run RTW in compatibility mode with windows XP service pack 2. True.
Run RTW as admin by default. True.
All the rest of that has not applied ever or either since Windows 10's second primary patch where my fault list was repaired.
Just to note, using a Large Address Aware enabler on an exe file is NOT a problem to recommend on Steam or on the CA support site (which CA runs this forum also) when it applies like to Empire, but to use it on Rome you will lock up your computer unless you reload often because that sets the memory leak loose in Rome and BI. It will completely blockade your page file access running data back and forth because the platform engine upon which Rome and Medieval 2 were built did not have the instructions to permanently hold in page file ordering shifting as needed. It will get caught in the loop constantly writing and deleting game files to page memory. It is normally then followed by a BSOD with a memory fault when Windows cannot write a file in page it needs.