No unfortunately not. Archaalens save was deleted but I hope Basileios II will send his to me. It might a real bug that has escaped us so for, since it's later in the game.Count Six said:
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Mnorrefeldt, I just sent you an email with the bugged savegame. This error definatly didn't occur in EEP 1.4.1 and Im'm rather sure that it didn't happen in EEP 1.4.2.
Hapsburg (Austria) Flavor Events file missing?
Correct me if I'm wrong but it was missing after I installed EEP. I copied the one over from the Vanilla GC.
Correct me if I'm wrong but it was missing after I installed EEP. I copied the one over from the Vanilla GC.
Ami Hund said:
You don't need to copy it. If there is no file in the EEP folder it will look for the file in the default folder. So it's the same as what you've done.
The Manchu Flu (CTD bug)
A little experiment:
My consistent CTD is shortly after Manchu inherits CHI, between Jan 25 and Jan 30 1683.
Looking at the eep_mch and major_mch files, it appears there are two events which change MCH into CHI after the inheritance: major_mch 10024 and eep_mch 221000.
I edited out 10024 and ran the saved game several times - no CTD.
I conclude that something is wrong with 10024, but I can't see what - the event script looks fine to me.
I thought that perhaps the problem was both events firing simultaneously, both trying to change MCH to CHI at the same time. However, it appears that the eep event 221000 will not fire in any case because it is lacking a date statement.
So I'm no closer to a true solution, but I do think 10024 is the problem.
Anyone wants the savegame, just PM me.
A little experiment:
My consistent CTD is shortly after Manchu inherits CHI, between Jan 25 and Jan 30 1683.
Looking at the eep_mch and major_mch files, it appears there are two events which change MCH into CHI after the inheritance: major_mch 10024 and eep_mch 221000.
I edited out 10024 and ran the saved game several times - no CTD.
I conclude that something is wrong with 10024, but I can't see what - the event script looks fine to me.
I thought that perhaps the problem was both events firing simultaneously, both trying to change MCH to CHI at the same time. However, it appears that the eep event 221000 will not fire in any case because it is lacking a date statement.
So I'm no closer to a true solution, but I do think 10024 is the problem.
Anyone wants the savegame, just PM me.
mnorrefeldt said:
settings : normal/weakling
it happened nearly always (4/5)...possibly the pb is with Daywalker AI's (?). i removed cores (french and burgundian on Lorraine, french on Maine) and PRO and LOR in the hitlists, and then it seems to be better...but there's a thing that's the cause of the pb : since Lorraine and Provence can't military challenge France, i think the AI decided to strike his weak neighbours
If you use other AI files you can get a very different behaviour. Might be why it works well for plain EEP?Duc de Guise said:
Nice experiment Count Six! I cannot recieve the game right now, unless you have ICQ? I have only hotmail here. But it might very well be that these two event fire at the same time and cause the game to CTD. Could you try loading you game as MCH and manually trigger both the events before they actually trigger, to see if they work one by one? I don't know if 221000 will trigger without the date command, but my guess is that it will. At least it's not triggered by another event. (I think the solution is right here.Count Six said:
)
More Manchu CTD experiments:
I'm begining to doubt my original theory that eep_mch 221000 and major_mch 10024 conflict. When I deleted 10024 and left 221000, the game did not CTD, but then 221000 didn't fire either. When I delete 221000 and leave 10024, the game does *usually* CTD. However, the CTD comes only several days after 10024 fires. Hence, the event fired Jan 28, 1683, but the CTD comes on Feb 1.
One thing I noticed playing as Manchu - in several tests, as soon as I became China, a new Manchu revolted. This is because the revolt file gives 1820 as the MCH deathdate - this should probably be changed so that once the Manchus have taken over China, they will no longer revolt. A deathdate of 1682, for instance.
However, I can't explain the CTD this way - why a CTD because a revolter appears?
Unless, that is, the sudden & unexpected reappearance of Manchu triggers an event which was not written with this possibility in mind.
Now, I've gone through both the MCH and CHI event files and I haven't found an event which would trigger on exists = mch at the wrong time. So I'm begining to wonder if the real problem isn't in another country's events - a neighbor maybe, with an event triggering on exists = mch which fires when the "Neo-Manchu" revolter appears and causes a CTD.
An event triggering on this revolter's appearance would explain why the CTD comes frequently but not always: the revolter is a contingent possibility, followed perhaps by an event choice which creates another contingency, leaving some chance that the CTD will not occur.
Nevertheless, to test this theory one would have to comb through all the Far Eastern countries' event files. I'm afraid I am not the one - I don't know these files at all, and I don't have the time to educate myself.
However, perhaps the people who have worked on the Far East set-up can remember if there are events for other countries which trigger on MCH or might otherwise be the culprit.
One last point - virtually the only solid conclusion I can offer is that the problem stems from Manchu becoming China. 10024/221000 are not the cause directly, but clearly the CTD problem begins with these events, especially 10024.
I'm begining to doubt my original theory that eep_mch 221000 and major_mch 10024 conflict. When I deleted 10024 and left 221000, the game did not CTD, but then 221000 didn't fire either. When I delete 221000 and leave 10024, the game does *usually* CTD. However, the CTD comes only several days after 10024 fires. Hence, the event fired Jan 28, 1683, but the CTD comes on Feb 1.
One thing I noticed playing as Manchu - in several tests, as soon as I became China, a new Manchu revolted. This is because the revolt file gives 1820 as the MCH deathdate - this should probably be changed so that once the Manchus have taken over China, they will no longer revolt. A deathdate of 1682, for instance.
However, I can't explain the CTD this way - why a CTD because a revolter appears?
Unless, that is, the sudden & unexpected reappearance of Manchu triggers an event which was not written with this possibility in mind.
Now, I've gone through both the MCH and CHI event files and I haven't found an event which would trigger on exists = mch at the wrong time. So I'm begining to wonder if the real problem isn't in another country's events - a neighbor maybe, with an event triggering on exists = mch which fires when the "Neo-Manchu" revolter appears and causes a CTD.
An event triggering on this revolter's appearance would explain why the CTD comes frequently but not always: the revolter is a contingent possibility, followed perhaps by an event choice which creates another contingency, leaving some chance that the CTD will not occur.
Nevertheless, to test this theory one would have to comb through all the Far Eastern countries' event files. I'm afraid I am not the one - I don't know these files at all, and I don't have the time to educate myself.
However, perhaps the people who have worked on the Far East set-up can remember if there are events for other countries which trigger on MCH or might otherwise be the culprit.
One last point - virtually the only solid conclusion I can offer is that the problem stems from Manchu becoming China. 10024/221000 are not the cause directly, but clearly the CTD problem begins with these events, especially 10024.
Count Six said:
This could make sense as the cause of a CTD as its basically the same as what is happening with Saxony. The game still thinks of the player as the MCH tag, so it has a problem when MCH revolts from MCH.
But if he's working from a save game the tag problem would go away IF the save is after MCH has become CHI.
Isaac Brock said:
Working with several, in fact - some before, some after. I'll have to experiment - stay tuned.
Isaac Brock said:
Oh, I was only trying to suggest that, that is one of the possible errors. Not the ultimate cause of the inevitable CTD, but just an awful side effect that doesn't help.
i found solution
After this post, i started a game as the Byzantine Empire; and it crash also somewhen about 1486. I noticed, that also in this game Saxony and Meißen had some events (god knows what happens there). So, I ereased the events eep_sac, major_sac and U16 (left empty eventfiles in the directory)
and ...................................
It works! No more CTD wheter with BYZ nor with PRO!
The only thing what makes me fuzzy: all other games past without problems the year 1486.
May be the events for Saxony must to be corrected.
Thanks anyway!
Rene II said:
After this post, i started a game as the Byzantine Empire; and it crash also somewhen about 1486. I noticed, that also in this game Saxony and Meißen had some events (god knows what happens there). So, I ereased the events eep_sac, major_sac and U16 (left empty eventfiles in the directory)
and ...................................
It works! No more CTD wheter with BYZ nor with PRO!
The only thing what makes me fuzzy: all other games past without problems the year 1486.
May be the events for Saxony must to be corrected.
Thanks anyway!
mnorrefeldt said:
Sorry, I was wrong about the line.
Here's the fix :
Change 65154 in line 111-112 to 65155
Change 65154A in line 114 to 65152A
Please check if I make a mistake again.
3 typos
First sorry if I repeat some others bug
I'm playin moscovy and I'm using one not so honest tactics to check if my cultural conversion will be ok.
province SaratoW has "capital" - SaratoV(this is the right writing)
provinces Ufa and Samara - have switched capitals
Ufa - capital Samara
Samara - capital Ufa.
I guess this is wrong
Johny Cage
First sorry if I repeat some others bug
I'm playin moscovy and I'm using one not so honest tactics to check if my cultural conversion will be ok.
province SaratoW has "capital" - SaratoV(this is the right writing)
provinces Ufa and Samara - have switched capitals
Ufa - capital Samara
Samara - capital Ufa.
I guess this is wrong
Johny Cage
JCage said:First sorry if I repeat some others bug
I'm playin moscovy and I'm using one not so honest tactics to check if my cultural conversion will be ok.
province SaratoW has "capital" - SaratoV(this is the right writing)
provinces Ufa and Samara - have switched capitals
Ufa - capital Samara
Samara - capital Ufa.
I guess this is wrong
Johny Cage
I think someone changed the capital names to make them correct. In reality, Ufa and Samara are swapped from their positions on the Eu2 map. It is confusing however, so it should be changed back.
mnorrefeldt said:
Apologies if this is noted elsewhere in this thread. I believe I know why this event is not firing. Event #179101, Protect Ladislaus' claim, does not contain a setflag command Wladislaw, which is a trigger condition for both the Victory of Ladislaus' Supporters and Elizabeth's death event.
I have not tested this from Austria's side, but editing in the setflag command allows the civil war to end properly in 1443 (Ladislaus' claims fail with the death of his mother) if you are playing Hungary.
I assume the problem is the same for event 188102 considering that the Wladislaw flag is cleared and Ladislaus flag is set when Postumus' supporters win the civil war.
Cheers,
MM
I think the flags for the whole sequence need to be reworked. As I understand it Twoflower hadn't realized that the flags are country specific when he scripted them.
I checked ...\EEP\db folder and cannot find the new colonynames.csv file. Was this forgotten for EEP 1.4.2a installation?