|
Post by meiilee on Dec 8, 2017 16:05:07 GMT
about a hundred in-game years in theres a new year point wherein during an autosave it ctd. This has happened to me in all my agot games for the past 3 years and ive only now thought to ask this in the forums. What causes this and if you guys can help me with a solution, am i able to play a game indefinitely?
I have tried playing it without autosaves and risk manually saving after a couple of years. 5 hours wasted after I just dont know what to do. This playthrough has been one of the best ive played for a long time.
|
|
|
Post by syntax on Dec 9, 2017 15:04:59 GMT
You can make a quick save on dec 31st of the last working year. From there you can open the quick save in notepad or notepad++ and change the date in the file from Dec 31st to the following year and January 2nd. I've been able to run game for 600 years that way before deciding to move on (game still worked). The bug does eventually go away, but periodically comes back. You have to do it every year, though - at least until the bug goes away.
Depopulaton scripts run on January 1st so you may need to learn how to edit the saves manually if that bothers you.
I havn't seen any comments on the bug from the devs despite numerous reports, hopefully it gets fixed one day!
|
|
|
Post by trent520 on Dec 10, 2017 7:58:41 GMT
Thats why Im not even going to bother reinstalling the mod until this issue is addressed. Every time it gets reported the response is either:
1. "Check your submods" Issue happens even with no submods
2. "Post your save game" Many users over the past year have done that and never heard back
3. "Its a vanilla bug" Bullshit, I've never had this problem with a vanilla game or any other mod for that matter. Yes, Ive tried the whole edit the date in the save file thing. It works for a couple more years then the problem starts again and editing won't fix it that time around. Its like the team is reluctant to admit that this is a problem WITH THE MOD and not with how the game saves or whatever other excuse they can come up with. I'm glad I saw this before I got deep into another campaign only to have to start from scratch yet again.
|
|
|
Post by ballerz on Dec 10, 2017 14:00:17 GMT
Thats why Im not even going to bother reinstalling the mod until this issue is addressed. Every time it gets reported the response is either: 1. "Check your submods" Issue happens even with no submods 2. "Post your save game" Many users over the past year have done that and never heard back 3. "Its a vanilla bug" Bullshit, I've never had this problem with a vanilla game or any other mod for that matter. Yes, Ive tried the whole edit the date in the save file thing. It works for a couple more years then the problem starts again and editing won't fix it that time around. Its like the team is reluctant to admit that this is a problem WITH THE MOD and not with how the game saves or whatever other excuse they can come up with. I'm glad I saw this before I got deep into another campaign only to have to start from scratch yet again. I mean, it's definitely not a universal problem bc I run a ton of submods and play long saves all the time. No such crashes in 4+ years of AGOT.
|
|
|
Post by syntax on Dec 10, 2017 14:41:54 GMT
Ballerz - that is interesting. How long do you let your saves run for? I have two computers, both modern and decently powerful (one with 18gb of ram the other with 24gb) computers. Both have the same problem, but it usually takes at least 100+ years to develop, and usually more than 150 years.
I don't use any submods except for the AGOT music mod.
In any case, while the fix is annoying, it does seem to reliably work for me. A 600+ year game is testament to that I believe.
|
|
|
Post by ballerz on Dec 10, 2017 16:05:31 GMT
Ballerz - that is interesting. How long do you let your saves run for? I have two computers, both modern and decently powerful (one with 18gb of ram the other with 24gb) computers. Both have the same problem, but it usually takes at least 100+ years to develop, and usually more than 150 years. I don't use any submods except for the AGOT music mod. In any case, while the fix is annoying, it does seem to reliably work for me. A 600+ year game is testament to that I believe. I'm pretty reliably running saves arou d 400-500 years each version. In the past 1.5 years, on a laptop with 16gb RAM and an oldish (4th gen?) i7. No slowdown either, though I don't play much on the highest speed.
|
|
|
Post by meiilee on Dec 28, 2017 20:06:29 GMT
Can I bump this thread? No dev actually responded.
|
|
|
Post by knuckey on Jan 2, 2018 10:12:07 GMT
If you can upload a save we can certainly try find the problem. Unfortunately with these sort of CTDs it is often impossible for us to tell what the problem is, as the error logs give nothing useful.
|
|
|
Post by Ogron on Feb 20, 2018 0:08:24 GMT
I am definitely having this same issue for about the past 3 years. I will try to get the save uploaded.
|
|
|
Post by Ogron on Feb 21, 2018 1:33:33 GMT
Hey Knucky, heres my situation. I have tried playing this mod over the last couple years and every time I get into it I hit a date that I cannot get passed as it does a CTD every time I save after that date. I usually start over and the same thing happens. There doesn't seem to be a specific time frame at least that I noticed. I usually then just quit after a few games and try a few months down the line in the hopes it has been fixed. I finally decided to post to see if I can get this resolved. I love this mod and really appreciate all the work you all have put into it. I cannot imagine the time it would take to set all this up. Superb. Please let me know if there is anything I can do to help. To encounter the bug, let the game pass the 1st of the year and then try to save. www.dropbox.com/s/j0jlvshzccm1w1x/The_Vale8471_12_31.ck2?dl=0
|
|
|
Post by Kash on Apr 4, 2018 22:19:12 GMT
I've run into the same problem. After just 80 years or so game starts crashing every January 4th, when it is doing the autosave. I can't save on any date in the new year either. I did the save-file editing to skip 6 days and resume on January 5th, and it worked for another year, but then crashes again on January 4th of the next year. I use the better faces and westerosi traderoutes restored, but the problem stays even if I disable them.
|
|