Quite recently a paper on dust devils on Mars was published: https://arxiv.org/abs/1708.00484
Three quotes that could be of special interest to you (Brian Jackson et al. 2017):
"Instead, we can adapt their formulation for our estimated typical, actual diameter of 13 m (Figure 9), which gives an occurrence rate ten times higher, 1 event per sol per km2. [...] This estimate includes detection biases and a population average should be used instead of typical values, but these results are roughly consistent with terrestrial field studies that estimate 40% of dust devils lift visible amounts of dust (Lorenz and Jackson, 2015)."
"Figure 8 (b) shows the resulting Γobs distribution. Consistent with estimates of the distributions of dust devil widths (e.g. Reiss and Lorenz, 2016), wider devils are less common than narrow devils, and Figure 8 (b) shows a power-law model for the differential distribution with index -1.6 provides a reasonable fit.
The distribution also declines for dust devils narrower than [...]18 m, seemingly at odds with the results of Reiss and Lorenz (2016), which conducted a visual survey of dust devil tracks and reported a population dominated by devils with a diameters < 10 m. However, the apparent decline on the narrow-end of the distribution is likely the result of selection bias in Ellehoj et al. (2010). Given the typical wind velocity of 5 m/s measured at the Phoenix site, a devil with a width ∼ 10 m would produce a signal with only a ∼2-s duration."
"For example, the devils with the deepest pressure profiles seem to occur preferentially around mid-day local time both on Mars Ellehoj et al. (2010) and the Earth Jackson and Lorenz (2015)."
Which means that for the 25 sq mile map (about time you Americans finally switched to metres now that even Myanmar and Liberia are converting) there should be around 64*0.4=25.6 visible dust devils per sol, skewed towards midday. They should be generally small at around 10m diameter or less, although a rare one might reach a width of around 100m. They should move at a speed of some 5 m/s on average.
I seem to be getting considerably less oxygen in 0.59 / 0.59.1 than in the previous versions, so much so that I'm slowly running out of oxygen even though the reoxygenator is running constantly, while in previous versions I have always been bulding up a healthy excess over time, and I'm doing things in the exact same manner / pattern than before so my oxygen usage should be about the same.
I have a suspicion that oxygen production may be stopping completely while the player is not "near" the habitat; maybe outside of terrain load/unload range? Can't think of any other reason why I'm getting much less oxygen than before as when I'm in/around the Hab, it seems to be producing about 6L / hour, and if it continued to do that while I'm away on a 35-40 hours long exploration trip, I should be seeing quite a lot in reserve once I'm back, but it's actually not even enough to refill the canisters I used up while away.
When moving between habitats, the status display panel may show the system states of the previously exited Hab under certain circumstances, until the player interacts with the status consoles at which point the display gets updated to the correct states.
There appears to be some inconsistency in this: when I moved from a powered up Hab to an unpowered one, the display was correct (all red). When I moved back to the powered Hab, the panel of that Hab still showed all red even though everytjing was in fact running, until I used the status console there.
When the Hab reserve power is full and the suit gets trickle charged, it sometimes may show a charge level slightly above 100% on the manage suit screen; I usually see 100.4% or 100.7% in such cases. This excess charge can be transferred back and forth between the suit and the hab without getting lost.
This condition may have something to do with having rested for long enough to have the suit fully charged by the trickle during the rest period; I didn't explicitly test for this.
The power level / charge rate of all hab systems, regardless of how many solar panels are installed, drop to 0% in a storm affected area, while the portable solar panel still charges at the expected very low rate as it did in the previous version.
The patch notes mention a change to power production while in a storm, but not that the 15% charge cap has been reverted and the storm completely shuts down power generation again.
I was examining the new habitat status panel and it displayed the text "Left click too..." so i clicked. Turned out it was the door which was still open. The door closed as you would expect. Not a big deal.
I am not color blind but I can't imagine someone who is can tell the difference between a healthy system and one that is failing. In addition to color you could use flashing text or have additional iconography to indicate there is a problem. Color alone is not going to be sufficient.
I had gone to sleep and at some point the power had drained. When i woke up and checked the status the reserve power was showing a negative number. How can you use more electricity than what is available. The system was charging so the number was going back to zero. Finally, if you charge your suit when the number is negative it will remove power from your suit setting the habitat to zero.
I noticed the new habitat health status display on the wall next to the inner door. The Habitat Power was showing as off (when i checked the terminal) and yet the status showed "green". I guess this is just a reflection of the "electrical charging" status? It seemed odd to show green when all the lights were off.
Either the reoxygenator doesn't drain any water at all while producing oxygen, or the water reclaimer still produces water while turned off. Not sure which is the actual cause, but while the water reclaimer was turned off for over 30 hours while the reoxygenator was running during the same period, the amunt of reserve water never decreased (it was capped so I couldn't see if there was any positive change, but there was no negative change for sure).
Customer support service by UserEcho