I examined the way the local temperature of the Fumarole Biome changes throughout the year for edit wiki.
Excluding random fluctuations within the range of [-16, +16], which is the return value of the function CalculateSeasonTemperature() in fumarolelocaltemperature.lua and obtained the following graph. The horizontal axis represents the number of days, start with autumn to the end with summer, and the vertical axis is temperature.
It is easy to notice that there is a clear problem here: in winter, the temperature here will first rise and then fall back.
For comparison, here is the global seasonal temperature in game. Its correct: the temperature will first fall and then rise back in winter.
The reason for this situation is that in the file fumarolelocaltemperature.lua, the value of WINTER_CROSSOVER_TEMPERATURE (This represents the temperatures at the beginning and end of winter) is lower than MIN_TEMPERATURE (This represents the temperatures at middle of winter, and its should be lowest temperatures in the year).
Quote--------------------------------------------------------------------------
--[[ Temperature constants ]]
--------------------------------------------------------------------------local TEMPERATURE_NOISE_SCALE = .05
local TEMPERATURE_NOISE_MAG = 16
-- 70
local MIN_TEMPERATURE = 80
local MAX_TEMPERATURE = 125
local WINTER_CROSSOVER_TEMPERATURE = 75
local SUMMER_CROSSOVER_TEMPERATURE = 90
Quotelocal function CalculateSeasonTemperature(season, progress)
return (season == "winter" and math.sin(PI * progress) * (MIN_TEMPERATURE - WINTER_CROSSOVER_TEMPERATURE) + WINTER_CROSSOVER_TEMPERATURE)
or (season == "spring" and Lerp(WINTER_CROSSOVER_TEMPERATURE, SUMMER_CROSSOVER_TEMPERATURE, progress))
or (season == "summer" and math.sin(PI * progress) * (MAX_TEMPERATURE - SUMMER_CROSSOVER_TEMPERATURE) + SUMMER_CROSSOVER_TEMPERATURE)
or Lerp(SUMMER_CROSSOVER_TEMPERATURE, WINTER_CROSSOVER_TEMPERATURE, progress)
end
Check local temperature of the Fumarole Biome changes throughout the year
-
2
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now