You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an area on Kerbin where I have a high-resolution altitude scan, the slope is consistently being reported as around 5.58 to 5.60 times the reported (and reasonable) elevation. The factor varies within that range. Over the ocean, the slope is positive while the elevation is negative, and the factor is about -5.59 rather than 5.59.
It seems pretty clear that this does not correspond to the slopes I see on the scansat overlay map, and is furthermore pretty useless since it gives me no additional information I could not deduce from the elevation.
The text was updated successfully, but these errors were encountered:
I wonder if this is an encoding/decoding issue as the number returned by :SLOPE is way outside anything one would expect. The docs describe it as a percentage (standard highway sign type "grade" I assume) but I'm getting 5 significant digit values with 2 decimals places on Moho, which is clearly neither a grade (percentage) nor a degree value. Additionally, without the direction of the slope the information is a lot less interesting for rover stuff. But all in all, kerboscript can get all this information and more so not sure how big a deal this all is other than for "realism" (no slope calcs until scansat done etc)
In an area on Kerbin where I have a high-resolution altitude scan, the slope is consistently being reported as around 5.58 to 5.60 times the reported (and reasonable) elevation. The factor varies within that range. Over the ocean, the slope is positive while the elevation is negative, and the factor is about -5.59 rather than 5.59.
It seems pretty clear that this does not correspond to the slopes I see on the scansat overlay map, and is furthermore pretty useless since it gives me no additional information I could not deduce from the elevation.
The text was updated successfully, but these errors were encountered: