If you can get the name of the POI it would let others see how it works in their games. The admin can get this by typing dm in the console and then pressing F3 after closing the console. Among all the info shown will be the name of the POI. I know I've driven all over the place in my 20.6 game after updating to 20.7 and never had any errors. But it's possible I just haven't seen that particular POI.
Well, it would affect anyone playing that same save. Whether it is a corruption in the save or a problem with that POI in 20.7 is something that would have to be looked into. With the POI name, someone may be able to verify if it works fine for them or if they see the same problem.Looks like it's farm_03. I know everyone else on the server I play on is having the same issue with the same POI - the screenshots I posted were from two other players on the same server. I get the same errors.
Well, it would affect anyone playing that same save. Whether it is a corruption in the save or a problem with that POI in 20.7 is something that would have to be looked into. With the POI name, someone may be able to verify if it works fine for them or if they see the same problem.
You could try resetting the poi using shift-F6Hopefully someone will look into it.
Are you running any mods?
Edit: The reason I asked is because I saw this happened in a world of mine after I uploaded a new mod into the game that I was playing. The mod had nothing to do with POIs, but it did turn one of the POIs into something similar in your picture.
Not saying that this is your issue, but it was something that struck out at me this morning when I read the post and saw your pictures.
I've also seen it happen when the server/host doesn't have enough system resources available when it is drawing in the POI. There are three or four POI's that this seems to affect more than others.
You could try resetting the poi using shift-F6
Depending where it is located, you could consider deleting the region file and see if that helps or trying a chunk reset, though everyone seems to consider using a chunk reset to be risky. I personally haven't run into any issues using it but that is just me own experience. Don't delete the region if any bases or storage are in the region or they will be lost.
Or even going into the world editor and removing it and placing it back or using a different POI there.
Have you looked to see where else that POI is on the map and see if the same thing is occurring there?
You can give yourself the quest for that poi. I'm not sure what is offhand but if you type 'help quest' in the console the commands will come up.If I can get a quest for that specific POI
If you have a land claim that overlaps that poi, you won't be able to reset it. You could temporarily remove your claim if that's the case.something related to our base, due to the close proximity.
Keep in mind that you can get corruption from a number of different sources and it is possible that it is coincidence the corruption and the update happened at the same time. Perhaps the game didn't properly close prior to the update and that caused the corruption in the region where your base is because that's where the players were. It may not really be a 20.7 issue, especially considering from what they said, that update only changes how the header of the save is read. So there's really no reason it should affect your save.I'm now thinking after 20.7, it's not liking something related to our base, due to the close proximity.
You can give yourself the quest for that poi. I'm not sure what is offhand but if you type 'help quest' in the console the commands will come up.
If you have a land claim that overlaps that poi, you won't be able to reset it. You could temporarily remove your claim if that's the case.