Calendar causes Warlords to crash to desktop

[InvisibleStalke]

With the Warlords expansion, I get a crash to desktop as soon as I get calendar - presumably it is trying and failing to centre the map. It happens consistently - I reload a save, get immediately prompted with a trade to get calendar, accept the trade, exit the trading screen and bang - the screen goes black and I'm sent back to the desktop.

My configuration was fine for running vanilla civ4 - with low graphics settings and movies disabled. Now with warlords it appears unusable.

Anyone else have this problem? Any suggestions on a workaround?

 

[crunch]

You could edit some xml file .. let me check. Go to C:\Program Files\FiraxisGames\SidMeiersCiv4\Warlords\Assets\XML\Technologies. Edit the file CIV4TechInfos.xml e.g. via notepad. Search for "calendar". Set the bMapCentering value to 0.

Spoiler :

		<TechInfo>
			<Type>TECH_CALENDAR</Type>
			<Description>TXT_KEY_TECH_CALENDAR</Description>
			<Civilopedia>TXT_KEY_TECH_CALENDAR_PEDIA</Civilopedia>
			<Help/>
			<Strategy>TXT_KEY_TECH_CALENDAR_STRATEGY</Strategy>
			<Advisor>ADVISOR_ECONOMY</Advisor>
			<iAIWeight>0</iAIWeight>
			<iAITradeModifier>0</iAITradeModifier>
			<iCost>350</iCost>
			<Era>ERA_CLASSICAL</Era>
			<FirstFreeUnitClass>NONE</FirstFreeUnitClass>
			<iFeatureProductionModifier>0</iFeatureProductionModifier>
			<iWorkerSpeedModifier>0</iWorkerSpeedModifier>
			<iTradeRoutes>0</iTradeRoutes>
			<iHealth>0</iHealth>
			<iHappiness>0</iHappiness>
			<iFirstFreeTechs>0</iFirstFreeTechs>
			<iAsset>16</iAsset>
			<iPower>0</iPower>
			<bRepeat>0</bRepeat>
			<bTrade>1</bTrade>
			<bDisable>0</bDisable>
			<bGoodyTech>1</bGoodyTech>
			<bExtraWaterSeeFrom>0</bExtraWaterSeeFrom>
			[COLOR="Red"]<bMapCentering>1</bMapCentering>[/COLOR]
			<bMapVisible>0</bMapVisible>
...

 

[InvisibleStalke]

Played through again from an earlier savegame running in a window instead of full screen. This time it didn't trigger on calendar, so I don't know if thats truly the cause or its related to time or something else at that time. Unfortunately in my experimenting I lost the save game that reproduces the problem consistently.

Thanks Crunch for your suggestion. I'll try it if (when) it recurs.