anegostudios / VintageStory-Issues

Vintage Story's public issue tracker for reporting bugs, crashes and the like
46 stars 16 forks source link

Some snow blocks persist/refuse to melt #2321

Open 0nymous opened 1 year ago

0nymous commented 1 year ago

Game Version

v.1.17.9

Platform

Windows

Modded

Vanilla

SP/MP

Singleplayer

Description

Snow blocks have a somewhat regular frequency to simply refuse to melt (be purged on chunk load during high temperatures). The cause of the issue seems irregular - initially I had though it only happens to snow piles that gathered under tree leaves or vine "blocks", but there are exceptions to that as visible in the screenshots.

How to reproduce

  1. Enter any standard-generated world
  2. Simulate the passing of a winter season into spring/summer in a moderate climate
  3. Travel through the world until the issue is visible (search the map for odd white pixels)

Screenshots

Screenshots were taken during summer, with in-game temperature around 25°C.

2022-12-13_01-42-45 2022-12-13_01-43-07 2022-12-13_01-43-50 2022-12-13_02-06-42 2022-12-13_02-25-59 ![Uploading 2022-12-13_01-02-53.png…]()

Logs

Log

noelle-lavenza commented 1 year ago

Snow blocks are not purged on chunk load. Instead, when a single snow block receives an update that it should melt, all adjacent blocks melt as well. In flat areas this can look like clearing all the snow in a chunk.

The snow in the screenshots will melt eventually, it just takes a while by virtue of it choosing a random block in the chunk to tick every, well, tick.

0nymous commented 1 year ago

The snow in the screenshots will melt eventually, it just takes a while by virtue of it choosing a random block in the chunk to tick every, well, tick.

That doesn't change the fact that we are left with extremely awkward single blocks of snow in a 30°C weather during summer. Even if it's not a technical bug, it's still highly immersion-breaking.

Craluminum2413 commented 1 year ago

Closing due to inactivity

noelle-lavenza commented 1 year ago

This issue still exists, why was it closed? It's inactive because devs haven't responded to it—which is understandable, because it's difficult to fix—not because of a lack of information.

Craluminum2413 commented 1 year ago

Okay