Civ4 crashes on "graphics init"

[Trokkin]

So, I have installed Civ4 Complete 3.19, it works on high graphics options perfectly, don't lag and don't crash even when I play the biggest maps.
I installed C2C and Dawn of Civilization of latest avaiable versions, loaded them, set up a game... And it crashed after a second of graphics init.
Other mods that are less heavy than this two works normally too.

Reinstalling DoC without additional modules made it work...
I have just one idea if this could be because of blue marble.

Any ideas what's happening?

 

[Dancing Hoskuld]

C2C has different terrains to Blue Marble so you should not use them together.

 

[Trokkin]

You mean, DoC with BM installed can conflict with other mods?

After I uninstalled DoC entirely C2C still crashes - but I'm not sure if the problem is still in graphics: the last text I see before crash is just "Initialization".

Also, the end of PythonErr2.log seems questionably to me.
13:42:58 DEBUG: BugInit - init() called
13:42:58 DEBUG: BugInit - game not fully initialized
PY:OnInit

 

[Trokkin]

After several reinstalls I assume DoC works without Varietas Delectat and Ethnic City Styles and C2C crashes on graphics init with any of DoC modules installed exept Carbon HUD. Without them C2C crashes exactly on initialization.

 

[Trokkin]

The crashes always occurs while I'm trying to start a game with map size more than standart, smaller sizes loads and works properly but meets memory allocation error soon. Sadly, it seems that my computer or OS can't handle this mod.

Is there any ways to reduce memory usage of C2C?

 

[Dancing Hoskuld]

You mean, DoC with BM installed can conflict with other mods?

After I uninstalled DoC entirely C2C still crashes - but I'm not sure if the problem is still in graphics: the last text I see before crash is just "Initialization".

Also, the end of PythonErr2.log seems questionably to me.
13:42:58 DEBUG: BugInit - init() called
13:42:58 DEBUG: BugInit - game not fully initialized
PY:OnInit

That is normal. The PythonErr2.log is where programmers put all their trace prints. It rarely has anything interesting for non modders or useful for finding problems.

C2C has a totally different terrain set to most other mods so having Blue Marble active may cause conflicts some how. I thought the C2C ini file turned off other modules to stop such conflicts. I am running a temperature at the moment so don't feel confident getting into details, that an I don't have my normal computer with everything on it here.

 

[Nightinggale]

My experience tells me that 32 bit systems have issues with graphcis while 64 bit systems can handle the very same mod just fine. The first sign of 32 bit issues is graphics and packed graphic files. Unpacking the graphics have helped my poor old (now disused) 32 bit computer to load mods it would otherwise crash on during startup. You can unpack using Civ4 PakBuild.

I don't know if that is your problem, but at this point it is as good a guess as any other and it's the only thing I can come up with, which might make a difference.

 

[Trokkin]

My experience tells me that 32 bit systems have issues with graphcis while 64 bit systems can handle the very same mod just fine. The first sign of 32 bit issues is graphics and packed graphic files. Unpacking the graphics have helped my poor old (now disused) 32 bit computer to load mods it would otherwise crash on during startup. You can unpack using Civ4 PakBuild.

I don't know if that is your problem, but at this point it is as good a guess as any other and it's the only thing I can come up with, which might make a difference.

Yes, I have 32 bit WinXP (I'd have Win7 64bit, but it lags a lot ). My computer does have more than 4gb RAM, but since it's 32bit it can't handle all.

What exactly should I do with this program? Extract what to where, I mean.

 

[Dancing Hoskuld]

The FPK files are Firaxis PacKed files. You find them in the assets folder. Unpacking them into that same folder will put the art where is should be. Remove the FPK files afterwards.

Warning when using PakBuild to unpack a file the bar that would normally show progress fills up/finishes way before the process is finished.

 

[Lib.Spi't]

I would suggest that if you are running 32bit then C2C working for you is pretty much a non-starter. You probably won't get very far into a game before it explodes with memory failures.

 

[Nightinggale]

It should be pointed out that FPK files makes the game start faster. This mean unpacking the files and using your dated computer is not a good combo for a quick startup. 5 minutes is not unrealistic for an uncached start. Just be patient even if it seems to have stalled. Luckily it's a startup delay and the speed will be as good as your computer can provide once you reach the main menu. A slow startup could be a bit annoying, but it beats the alternative of not being able to play at all.