From: Jon B. <jon...@co...> - 2016-01-22 03:34:47
|
The initialization of ECEF position had not been working perfectly since November 2014. I found the problem this evening and made an update. The SetPositionGeodetic() function had been getting called with 0.0 being passed in for longitude and altitude. That caused the wrong planet radius to be used for calculations and the resulting ECEF frame position was incorrect - it wasn't a large error . just a few miles . but we don't want that. J I ran a test and it appears to work correctly, now, for the version 2 config file format. I think this change should be transparent to everyone else, but you might want to run a test script or two. Jon |