D'you mean the Mongol Empire start date or something? Hmm. That's curious... I'll look into that.
Indeed. Ol' Temujin himself.
D'you mean the Mongol Empire start date or something? Hmm. That's curious... I'll look into that.
Indeed. Ol' Temujin himself.
Do you remember approximately how long it took you to get to a CTD? (i.e. one week in, three months in, one year in, etc.) I've tried starting at the Mongol start date as Temujin and I've gone by one year without any CTDs.
However long it takes to start marching your event troops to Esfahan and gather your levies together. Month or two, I guess?
Is it intended in the duel module for your own army commander to charge you across the battlefield???
I have had quite a few family members [often the commanders controlling the flanks] die in this way. it gets reported as `died in personal combat to x`. As I often have my sons commanding the flanks...well its an honorable death.Does anyone know the answer to this? Since it resulted in the death of my ruler this is going to determine whether I load from a prior save or not.If it's WAD then I'm just going to go with what the gods (oh wait, God; I'm playing a Catholic) have dealt me.
Is it WAD for Magyars to retain claims on the lands they "migrate" from in lower Ukraine?
It kind of defies the point of having them discard them, also they tend to reconquer those if they can. At least they did for me 3 times on 4 tries, but just because the fourth time I was playing as them and noticed it.
Seems to have just been a one-off thing.
I played a game with the 'no ahistorical empires' decision, but after reloading the game those empires came back, just like Raineh Daze reported. I followed the instruction to type "event meneth.512", the decision fired again and all was well again. Then when I reloaded a second time, everything has been removed. First I thought the save was corrupted so I just loaded an old save (prior to firing the event), played for a few years and saved twice to be sure it got saved properly, yet it still happened again to both of the saves. The save file themselves are proper size and look right on the inside as well, so I don't know what's going on.
Frankly to be honest I dunno how that could happen due to the no ahistorical empires decision (maybe one of the other HIP guys knows better than me). I know you tried two, but did you try that with another game or a few just to be sure?
Sorry if this one has already been fixed, or if there might just be something I am missing with the install, and if I did, please feel free to mock me openly, but...
I just installed the latest version of HIP on Friday. The game was loading a bit slowly, but nothing really unusual for a none vanilla... anyway, I'm playing my game, and I start saving... again, it is taking a while for the save screen to load, but at least from my experience, nothing odd. I manually save once. Fine. I manually save the game again... I get a runtime error notification. It happened again a few other times. I figured, fine I have auto save, and I'll make sure to only do one manual save each time I load the game. Played like that for a hundred years. Soon, it starts to crash any time I do a manual save, otherwise the game is working fine otherwise, no problems. But then around the year 970 AD, the game crashed when it goes to autosave into the next year. I reload. Same thing happens. I reload again same thing happens. I reload a third time... and I star tot notice something odd, all my old autosaves are disappearing, and I am on my last one for the game I am playing (my last manual save from several decades ago, because of the issue). I reload the game, it crashes... reboot... all my autosaves are gone.
Anyone have this issue before? Is there a known fix?
Edit: Sorry, should have said, it is always a C++ Runtime Error.
I have had quite a few family members [often the commanders controlling the flanks] die in this way. it gets reported as `died in personal combat to x`. As I often have my sons commanding the flanks...well its an honorable death.
Fighting your own side sounds like a bug.
Though it would be cool to allow assassination attempts if you are both in the same combat on the same side - disguising it as a "friendly fire" incident or just stabbing the guy during all the confusion.
There's a thread in Tech Support regarding a C++ Runtime error while starting the game and appears to be connected with ram, so maybe it has the same cause? Their fix was to turn off some DLCs to lower the demand for ram. Go read it and hopefully you'll find a solution.