Mod getting stuck at "init uncached" then crashing

[Sword_Of_Geddon]

This started recently, before when I made a change to the mod, it would reload just fine, now, it gets stuck at "init" uncached". Until yesterday I was able to get it to load(though its been taking longer than normal, like 35 minutes, it was never this slow) by clearing the cache.

Now however, these methods don't work. The graphics are fine, the XML is fine, the only thing is I moved some civilizations back to being modular as they were orginally.

Well the mod noticed the change, and now it won't load.

PLEASE HELP ME...over five years of work I don't want it to end like this....

 

[PPQ_Purple]

You should check all your XML. All of it. Not just the modular part. And look for places where one file is calling on another (like say the art style calling on art defines). The way I get such crashes is if I have an XML tag being called that either does not exist or is not loaded. So like if you have say an art style file in the base mod calling on an art define in the modular part. Stuff like that is what crashes silently in my experience.

 

[Sword_Of_Geddon]

I did doublecheck, it turns out xml was not the issue. I tried reinstalling the game, the mod loaded fine. I changed a line of civilopedia, suddenly it stopped working.

this all started when i upgraded my RAM from 16gb to 24. mod used to load every time with no quirks, I could load up my media player, or browse the internet, even play other games while the mod loaded.

After going to 24 gb, its like it has less memory not more. The mod tends to only load when the computer is left undisturbed, even checking the task manager can cause it to fail.

 

[Nightinggale]

First you talk about really long loading times, then you complain about crashes while loading. It sounds like there is something seriously wrong with either your computer or mod. First of all, try testing your memory. I would be a bit surprised if you have bad ram and it only affects civ4, but at the same timeit's not impossible. I have tried having to replace brand new ram due to stability issues and failing the test (warranty paid, but still).

The only other thing I can think of would be to test the mod myself to see if I can figure out something. Do you have a git repository with the newest version I can clone? You know one where all I have to do is to compile and then run the game.

Last, but not least, "Init uncached" is triggered by the DLL, meaning not only can we debug what it is doing when something goes wrong, we have the ability to modify the code and perhaps avoid the issue entirely.

 

[Sword_Of_Geddon]

Hello Nightingale. Yes, the long boot times have long been a problem, which I've tried(for players more or less) to fix. However since the RAM has changed, the mod has been very quirky, doesn't let you do anything while it is loading otherwise it crashes, and has increased the load times even further.

As for the latest current version, I have no uploaded it(Because of everything going on), but an older(current release version) is available for download in my mod's thread.

So I've gone back down to 16mgs of ram, its not back to acting like it was before, with relyable, 20 minute loading and the ability to browse the internet and such whil the mod loaded. I think it has to do with which RAM is installed. I need the old RAM back.

And thankyou for helping...

 

[Sword_Of_Geddon]

Thought I'd add this oddity as an afterthought as well: If the mod does load(and lately this only happens if I uninstall Civ4, Warlords, Beyond the Sword etc), it will work, but loading times have jumped to 40 minutes(was 20 just a week or so ago), moreover, if ANY changes are made to the mod, the mod will go back to not loading, getting stuck on Init Uncached, then crashing to desktop.

 

[PPQ_Purple]

Are you having loading problems with any other software? Or like OS boot issues? Because this sounds like a serious issue mechanically on your end.

 

[Sword_Of_Geddon]

It started when I switched out my memory for some new memory, I looked into it, the old memory is optimal for the motherboard, where the new memory is not. I just hope switching it back fixes the issue.