POIs lods bug???

[org_256]

Hello there!

I'm playing on 19.2 (b4) on the map I created under 18.*

It's 49 day now ( approx 12 day of game experience, i.e. 12-15 game loads )
I'm starting experiencing strange bug I've never see before.
It seems like many closest chunks loads with wrong POIs lods. 
I know /pois console command can "solve' that.
But I wonder is there any way to fix it, so I'll be still able to see distant POI lods? Thanks!

 

 

[SylenThunder]

a18 maps are NOT compatible with a19. You must wipe all the things.

 

[org_256]

I get used to that map ;(

oh, My fault. It wasn't 18.*.... it was 19.0 initially

 

 

[SylenThunder]

happen to have a log?

 

[org_256]

which one? the latest one ?

 

[Liesel Weppen]

Wasn't there a change after 19.0, too, where you should start a new map?

I have the same issue, but by far not as extreme as shown on the screenshot.

However my map is generated with latest nitrogen as of 19.2.

I never examined it in detail. I just assumed that relates to the known "ghost block bug".

 

[org_256]

Here is the latest one log I found in the game data directory

View attachment output_log__2020-11-22__11-50-10.txt

Also one of my friends told me recently he has same issue on new created map after 3-4 loads...
It seems game miscalculates somehow the the current player position...

in his case sometimes it's happens right after save load and sometimes right on the place during looting the POI

 

[Beelzybub]

@org_256Try updating your driver to this one from Nvidia. Also, try directx instead of opengl.

(select from the launcher).

 

[org_256]

Oh, really, I forgot I switched to OpenGL recently... Should be the reason...

Also, yeah, driver... 

But again, friend uses DirectX