CK III - Map gets bright, random, permanent borders

[GodofBlades]

Short summary of your issue Map gets bright, random, permanent borders

Game Version 1.1.1

What OS are you playing on?
Windows

What platform are you using?
Steam

Do you have mods enabled? No

Have you tried verifying your game files (Steam only)?
No

How much "pain" is this causing you?
3

Please explain the issue you experienced in the most condensed way possible
After some time, the game map keeps random, bright borders, regardless of map mode

Please explain how to reproduce the issue
Simply playing

Is there anything else you think could help us identify/replicate the issue?
It is a cloud save started on a patch previous to 1.1.1. Maybe the conversion did something.

I have attached a save game
Yes

Upload Attachment
File(s) attached

 

[UndefinedT]

It also does the same with internal borders, borders seem to update sporadically if at all in all cases.

 

[Kardo]

I've also noticed the same thing, but for me it's stuck as a glowing red/blue as if the areas were at war but aren't.

 

[theJSeffect]

Exact same problem for me since the patch. Red borders with kingdoms I'm no longer at war with, white borders with other kingdoms I just selected to look at the top liege, and a confusing mess of white borders within my kingdom from clicking vassals. Unplayable at this point because I can't tell where anything is.

 

[GodofBlades]

I've also noticed the same thing, but for me it's stuck as a glowing red/blue as if the areas were at war but aren't.

It hadn't happened by when I made the bug report, but recently it happened to me too

 

[DomShadow]

I've also noticed the same thing, but for me it's stuck as a glowing red/blue as if the areas were at war but aren't.

Same here. Please fix, its super annoying!

 

[UndefinedT]

Wasn't fixed in 1.1.2 - Super irritating to play with, basically requires me to close to desktop periodically and reload until it gets too much to bear again.
It looks like internal borders just don't update at all and war borders don't update occasionally.

 

[Yes please]

Hi, GodofBlades and others in the thread,

Thank you for the report!
We are aware of the issue, it has already been added to our bug database.

Cheers,
Yes, please!

 

[DomShadow]

Hotfix!? I dont want to wait for the next bigger patch for this to be fixed....

i cant play like this! Its super irritating and aynnoing af!

 

[M22413751]

What the heck is going on with the borders? It's impossible to play like this.

 

[DomShadow]

HELLO!? FIX!? Whats wrong with you!? Its been 2 weeks! And all you've done is added it to your bug database!? Wow! So we do have indeed to wait a couple of weeks until you fix a bug which could have been spotted easily in the 1st place!? Only by looking at the error.log and so, no QA was done - nice.

If such a problem would aoccur from an indie game, the indie dev would have fixed it immediately. But we all now pdx handling with such things, especially your great QA!

 

[GodofBlades]

HELLO!? FIX!? Whats wrong with you!? Its been 2 weeks! And all you've done is added it to your bug database!? Wow! So we do have indeed to wait a couple of weeks until you fix a bug which could have been spotted easily in the 1st place!? Only by looking at the error.log and so, no QA was done - nice.

If such a problem would aoccur from an indie game, the indie dev would have fixed it immediately. But we all now pdx handling with such things, especially your great QA!

Dude, chill. Do you have any idea how hard it is to develop and fix a game? The game, and by extension its code and assets, are enormous, and there could be a thousand things which could cause this issue. They have to find and assess what causes the bug, and then make sure that the fix doesn't break something else. A few weeks would be lightning fast in my opinion, let alone fucking immediately. You need to learn to appreciate what you have and what others do for you

 

[DomShadow]

Dude, chill. Do you have any idea how hard it is to develop and fix a game?

I know, yes. Hence my posting.

 

[Chalkcs]

So... Is this going to be fixed soon? It's been a hot minute.

 

[alcoholv]

I think it's a very serious critical AAA+ bug. Hotfix is urgent.

 

[M22413751]

Kinda ridiculous that they just left it like this since September

 

[Johann7]

Kinda ridiculous that they just left it like this since September

Not really. It's an intermittent bug, not something that e.g. always occurs any time the border view updates, so tracking down all of the causes is more difficult than some other bugs might be. They actually haven't just left it the same since launch - some, but not all, of the causes were found and fixed in one of the patches. Further, what a lot of people seem to fail to consider is that changing code to fix one bug can break other things that were set up based on the bugged code. Sometimes a bug is easy to identify and fix, but the subsequent problems caused by the fix are worse than the original problem, so the bug is left unpatched (or reverted) until the entire chain of bug->fix->bug->fix->etc. can be identified and fixed, which is more complicated and takes longer than just finding and fixing the initial bug (especially if a given fix causes multiple subsequent bugs). Finally, despite some reactions like DomShadows's, this is a minor interface bug, not a serious mechanical bug. I do find it annoying to not be able to see war/peace status at a glance and to have to restart the game to clear it, but since there is actually a workaround (re-launch the application), it's going to be a lower priority than e.g. a bug that affects a core mechanic or doesn't have a workaround.

 

[alcoholv]

Not really. It's an intermittent bug, not something that e.g. always occurs any time the border view updates, so tracking down all of the causes is more difficult than some other bugs might be. They actually haven't just left it the same since launch - some, but not all, of the causes were found and fixed in one of the patches. Further, what a lot of people seem to fail to consider is that changing code to fix one bug can break other things that were set up based on the bugged code. Sometimes a bug is easy to identify and fix, but the subsequent problems caused by the fix are worse than the original problem, so the bug is left unpatched (or reverted) until the entire chain of bug->fix->bug->fix->etc. can be identified and fixed, which is more complicated and takes longer than just finding and fixing the initial bug (especially if a given fix causes multiple subsequent bugs). Finally, despite some reactions like DomShadows's, this is a minor interface bug, not a serious mechanical bug. I do find it annoying to not be able to see war/peace status at a glance and to have to restart the game to clear it, but since there is actually a workaround (re-launch the application), it's going to be a lower priority than e.g. a bug that affects a core mechanic or doesn't have a workaround.

Intermittent? LOL