erbkaiser
Modder (CK2)
Taking a long break from modding
Posts: 693 
|
Post by erbkaiser on Sept 20, 2019 13:54:17 GMT
Having the same issue as Visi. Crashes on the 7th or the 9th of the first month no matter what start I use. Interestingly, if I use More Bloodlines and the MB version of this mod there's no crashes. That only makes it more strange. There is no difference between the two versions other than the map data. |
|
|
|
Post by hafhdrn on Sept 20, 2019 14:05:58 GMT
Having the same issue as Visi. Crashes on the 7th or the 9th of the first month no matter what start I use. Interestingly, if I use More Bloodlines and the MB version of this mod there's no crashes. That only makes it more strange. There is no difference between the two versions other than the map data.
I'm about as lost as you are. I don't see anything in the error file that stands out. Maybe there's an issue in the map data for the standard edition of the mod?
|
|
|
|
Post by derianstark on Sept 20, 2019 14:40:10 GMT
Hello, I am running into an odd issue. I am running More Bloodlines compatible version of the mod, tested with disabling all other mods but this and the more bloodlines version. Whenever I launch the game with this running, the new colonies that were added, Skane and Hoare Castle on the iron Islands, as well as the new provinces, are unable to be colonized, and those that are supposed to have lords already, are just greyed out. Any idea what is causing this? I would assume it is something to do with the history files, but I do not know enough about modding to figure this out. Still can't figure out a work around the new provinces not allowing colonization (Skane, Hoare Castle) or those that should have characters already as lords are just spaces (the new setup for kings landing, the bloody gate, the 4 new lands in the iron islands amongst others). Any ideas to fix this would be appreciated. I love playing with Colonizable valyria, but as a progress towards, or look at westeros for future conquest it really messes up game play. |
|
erbkaiser
Modder (CK2)
Taking a long break from modding
Posts: 693
|
Post by erbkaiser on Sept 20, 2019 14:46:18 GMT
Hello, I am running into an odd issue. I am running More Bloodlines compatible version of the mod, tested with disabling all other mods but this and the more bloodlines version. Whenever I launch the game with this running, the new colonies that were added, Skane and Hoare Castle on the iron Islands, as well as the new provinces, are unable to be colonized, and those that are supposed to have lords already, are just greyed out. Any idea what is causing this? I would assume it is something to do with the history files, but I do not know enough about modding to figure this out. Still can't figure out a work around the new provinces not allowing colonization (Skane, Hoare Castle) or those that should have characters already as lords are just spaces (the new setup for kings landing, the bloody gate, the 4 new lands in the iron islands amongst others). Any ideas to fix this would be appreciated. I love playing with Colonizable valyria, but as a progress towards, or look at westeros for future conquest it really messes up game play.Li List ALL the mods you're using for CK2 and maybe I can figure out what the issue is. |
|
|
|
Post by derianstark on Sept 20, 2019 16:38:35 GMT
The issue occurred when I was just running AGOT 2.0, More Bloodlines Submod (AGOT 2.0 compatible), and More Bloodlines compatible version (2.0 only). I had originally thought it was another mod conflict, so I had already disabled all other submobs but those. No issue when launching the game with just more bloodlines and the base mod, but as soon as I tried using Colonizable Valyria MB the areas show up, but no longer are able to be colonized, and the areas that are already established have no lords, etc but the names, etc all show. Currently at work, but I can try to grab screen shots later.
I even tried deleting all the mods, reinstalling, and turning on each one by one, and this only happens when I turn this mod on.
|
|
|
|
Post by gotchristian on Sept 20, 2019 16:47:33 GMT
The issue occurred when I was just running AGOT 2.0, More Bloodlines Submod (AGOT 2.0 compatible), and More Bloodlines compatible version (2.0 only). I had originally thought it was another mod conflict, so I had already disabled all other submobs but those. No issue when launching the game with just more bloodlines and the base mod, but as soon as I tried using Colonizable Valyria MB the areas show up, but no longer are able to be colonized, and the areas that are already established have no lords, etc but the names, etc all show. Currently at work, but I can try to grab screen shots later. I even tried deleting all the mods, reinstalling, and turning on each one by one, and this only happens when I turn this mod on. The mod isn't save-game compatible. This could possibly be the issue. I experienced similar glitches/errors when I loaded into a save-game. |
|
|
|
Post by derianstark on Sept 20, 2019 17:24:39 GMT
Yeah, I also have tried it on multiple new games also knowing that. Only dates in the main mod, same issue no matter whom I start with. Even purged all my saved games to ensure that there wasn't an issue with it trying to pull old data from somewhere also.
|
|
|
|
Post by steamdriventurkishstateopera on Sept 20, 2019 23:07:45 GMT
It crashes afew days after setting up the ai management events. Whit any mod combo.
|
|
|
|
Post by Visi on Sept 21, 2019 0:29:41 GMT
That only makes it more strange. There is no difference between the two versions other than the map data.
I'm about as lost as you are. I don't see anything in the error file that stands out. Maybe there's an issue in the map data for the standard edition of the mod?
Can confirm, switching to the MB version, along with the MB version of the the Bugfixes mod and MB itself, does indeed stop my game from crashing on the same day. I don't really have any interest in using the MB mod, but it seems like I don't have any choice. EDIT: Well, it seems that I can still use the MB versions of the Colonizable Valyria and Bugfixes mod without enabling the More Bloodlines mod itself, so maybe I'll do that and just hope that no conflicts arise. Thank you for the help, hafhdrn. EDIT #2: Well I don't think I'll try playing without the MB mod enabled. It changes some of the map and there are several provinces that are kind of wonky without the mod activated. What a mess... I just want to play in Valyria for God's sake...  EDIT #3: Well I've been playing with the MB mod since I had no other choice, and now the activating the Religion tab crashes my game. IDK what triggers it, as it didn't happen when I started another new game, but it is happening on one a few years in and it seems isolated to the Valyrian religion. FML. I guess I just can't freaking play the mod until the next big update. =/ |
|
|
|
Post by hafhdrn on Sept 26, 2019 6:19:20 GMT
Belated update: I might have fixed the crash. I've been able to play for a few generations with the standard Colonizable Valyria mod without issue. I diffchecked the working (MB) version with the standard version, ignoring the differences in the map (because of course that would be different) and isolated one file. In the MB version the 'valyria-unoccopied.txt' looks like this: #c_port_of_sighs
19790001 = {
name = " "
religion="ruin_rel"
culture="ruin"
7860.1.1 = {
birth=yes
In the standard Colonizable Valyria mod it looks like this:
#c_port_of_sighs
19790001 = {
name = " "
religion="ruin_rel"
culture="ruin"
7860.1.1 = {
birth=yes
effect = {
if = {
limit = { is_ruler = no }
death = yes
}
if = {
limit = { is_ruler = yes }
add_trait = ruin
set_defacto_liege = THIS
c_port_of_sighs = {
location = {
set_province_flag = ca_colony_3
set_province_flag = ruined_province
}
}
character_event = { id = unoccupied.101 }
create_character = {
name = ""
religion="ruin_rel"
culture="ruin"
dynasty=none
attributes = {
martial = 0
diplomacy = 0
intrigue = 0
stewardship = 0
learning = 0
}
trait = ruin
}
new_character = {
b_port_of_sighs = { gain_title = PREV }
}
create_character = {
name = ""
religion="ruin_rel"
culture="ruin"
dynasty=none
attributes = {
martial = 0
diplomacy = 0
intrigue = 0
stewardship = 0
learning = 0
}
trait = ruin
}
new_character = {
b_port_of_sighs2 = { gain_title = PREV }
}
create_character = {
name = ""
religion="ruin_rel"
culture="ruin"
dynasty=none
attributes = {
martial = 0
diplomacy = 0
intrigue = 0
stewardship = 0
learning = 0
}
trait = ruin
}
new_character = {
b_port_of_sighs3 = { gain_title = PREV }
}
}
}
}
}
}
}
I did a quick bit of looking around the mod files and couldn't find any particular issue with removing everything under "birth=yes". I did so, and since, I've been able to play just fine with the standard version.
|
|
erbkaiser
Modder (CK2)
Taking a long break from modding
Posts: 693
|
Post by erbkaiser on Sept 26, 2019 6:36:53 GMT
Belated update: I might have fixed the crash. Oh man... that would be it. I moved the ruin setup to another place, seems I overlooked the change in that file...
I'll fix the upload later today. Thanks for letting me know and awesome troubleshooting.
|
|
|
|
Post by hafhdrn on Sept 26, 2019 7:25:47 GMT
Belated update: I might have fixed the crash. Oh man... that would be it. I moved the ruin setup to another place, seems I overlooked the change in that file...
I'll fix the upload later today. Thanks for letting me know and awesome troubleshooting.
No worries. Glad to help. c:
|
|
|
|
Post by hafhdrn on Sept 27, 2019 14:39:29 GMT
Womp womp. Back to square one. It was working (reasonably) well for a while with the modification I made (and I see you reflected in the main download), but now, for some reason unbeknownst to me? It's scuffed. I haven't made any other edits, using the same configuration I used previous, and now it's either crashing on the 9th of the month or the 16th no matter which start I use. I've diffchecked the map files and unfortunately I'm not confident enough to go messing around with those by myself, but as far as I can tell they're the only other option here. I did notice that there are SOME differences between the files but seeing as it worked previous I'm sort of at a loss. It's like it's just decided to, uh, break. AGOT + CV? Crash. AGOT + Bugfixes + CV? Crash AGOT + Bugfixes + CV + Traderoutes? Crash etc. Doing a reinstall of CK2 to see if that helps, I've cleared the map caches to see if THAT would help. Nothin'.
EDIT: Brainblast. Removed all reference to the Port of Sighs from the history files (it's the only province in there in the first place?) and I can get it to run at full speed with no issues, seemingly indefinitely. Additionally, it doesn't seem to mess up Port of Sighs as a province. Might that had been the issue?
EDIT 2: Doesn't seem like that was a permanent solution. It worked maybe twice? And now it crashes on either the 9th or 18th of the first month of any new game, as usual.
EDIT 3: I need to get some rest, but I did some more tinkering and found the following: with the change mentioned in the first edit, with no other mods it seems to work... decently reliably, although it can still crash due to some bugs from the base AGOT mod. HOWEVER! If I enable your Bugfixes mod, I start to experience instability that I can't pin down.
|
|
erbkaiser
Modder (CK2)
Taking a long break from modding
Posts: 693
|
Post by erbkaiser on Sept 27, 2019 15:48:53 GMT
The only thing that still comes to mind is make sure you have the bugfix (or MB version of it) set as a dependency for the CV mod(s). It's set in the download but if you're manually updating you'll need to add the dependencies yourself.
|
|
|
|
Post by hafhdrn on Sept 27, 2019 15:52:49 GMT
The only thing that still comes to mind is make sure you have the bugfix (or MB version of it) set as a dependency for the CV mod(s). It's set in the download but if you're manually updating you'll need to add the dependencies yourself.
Checked and double checked! Downloaded the new versions of everything to make sure they were unified.
I'm finding that if I run CV without Bugfix and TRR+V I'm not getting the 9th/18th crashes.
EDIT: Don't know what happened but it's working again, haha. Frick.
EDIT 2: And now it's not again? This is doing my head in.
|
|
