when getting far from the hub the textures start to glitch
#[SPZ2-1287] textures glitching when moving far away from hub, floating point issue
wide steppe
proud flame
thorny grove
Ooh, floating point shenanigans?
charred verge
Looks like Minecraft's far lands
tawdry oyster
This is floating point imprecision, we need to have a look at this later
steep cape
wide steppe
you do need to go further but this still appears
rough jacinth
[SPZ2-1287] textures glitching
tawdry oyster
Merged into this: https://discord.com/channels/1000343719314198548/1165359808677949470
kindred garden
maybe another effect of this, shape asteroid previews stop displaying after some distance to the hub
tawdry oyster
To be fair that's ~250 sectors away from the hub 😅
kindred garden
yeah you wouldn't go that far in normal playthrough, I was just scrolling to see if I could find two shape patches touching each other to see if https://discord.com/channels/1000343719314198548/1243872908170891264 would happen as well in this case
rough jacinth
[SPZ2-1287] textures glitching when moving far away from hub, floating point issue
still happening in 0.0.2 as reported
red monolith
I noticed this today and after some testing found that textures start to have some buggy behavior even as few as 30 sectors away from the hub
austere violet
I also notised this, made a video of the bug. This is an extreme example tho, i did notice it increases memory usage, at the end it was about 22 GB of ram (video quality is quite bad so text is hard to read). After i returned home tho it went down to 16 gb, after some time.
I did place some objects far away to test, and this might have ruined my cause its pretty hard to get out there again, dont know if that is something there could be a fix for since this is a pretty extreme example of the bug
Video of the bug:
https://www.youtube.com/watch?v=T8mkspj-SQo
If its relevant heres the log
languid badge
Very noticeable at 15|O, which I'd argue is not that far away from the base.
proud wave
I gotta look for the far lands now
nvm everything started flashing like crazy. I couldn't take it
red monolith
This does happen if you move far out (I think this was either 500 or 1000 sectors out just on the horizontal axis)
nova panther
i don't think you can solve this error. sadly this is built-in-engine limit.
you can try and make it so that the player is the center of the world, and make thee world move and not the played. this would fix it but cannot be done easily i imagine.
red monolith
My best solutions are
- If the code is using single precision floating point values, using doubles instead would massively reduce the issue, though still not remove it entirely.
- A sort of psueo fixed point number could be stored using the
BigIntegertype. This should fix the problem entirely, but would require major code refactoring.
Now, I'm sure the devs are already fully able to come up with these and potentially better solutions as well lol
frosty delta
Is there a seizure warning on this game? If so I can't find it.
candid wedge
Is there a seizure warning on this game? If so I can't find it.
no but you arent ment to go that far to be fair
red monolith
my guy it takes about 80 seconds straight of just moving to get to where the map starts to disappear, so of course there isn't a seizure warning because of a bug that only causes a severe enough issue to even consider warranting a seizure warning if you are TRYING to find it
turbid jasper
went out to 0 | -XC and i just wanna say that the camera also has issues if you zoom in completely
it's like, snapping to a grid of sorts (the floating point numbers probably)
looks like it gets worse the further you go out
also selecting stuff is completely obliterated
over at 0 | -BXK
placing platforms and buildings is very screwed
also graphics looks like this
now at 0 | -CUZ
the giant space grid (completely zoomed out) can flash, or even disappear when i move
turbid jasper
now at 0 | -CUZ
the giant space grid (completely zoomed out) can flash, or even ...
0 | -DDG
(yes i had to place multiple thats how difficult placing is now)
anyways here my journey comes to an end (i dont want to do this anymore)
tawny sequoia
am here because i ran into this at -56 -BQ which honestly didn't feel that far out.
tawny sequoia
actually, signs of degradation start fairly early, clearly visible shaking in the camera while panning, and slightly misshapen shapes at 30 | A
strange glade
lower that lower bound down. Texture glitching visible at -1 | A when zoomed way the hell into a trash cell on Extreme preset
See https://discord.com/channels/1000343719314198548/1280933437540270211
woeful meteor
i believe the trash is a separate issue
strange glade
i believe the trash is a separate issue
https://ptb.discord.com/channels/1000343719314198548/1277431144195031060 being marked as duplicate of this bug report says otherwise
woeful meteor
oh I misremembered, my bad
kindred garden
iirc there was a report about the trash and it was said to be a different issue, but I can't find it now so its case might have changed
kindred garden
ah yeah it was this one