<Kopernicus>
[Kopernicus] sswelm commented on pull request #328 d322ab2: Yes it is, it gives the Vector3d, which is 64 instead 32 transform https://git.io/fxH10
<Kopernicus>
[Kopernicus] sswelm commented on pull request #328 d322ab2: Yes it is, it gives the Vector3d, which is 64 bit instead 32 bit transform https://git.io/fxH10
<Kopernicus>
[Kopernicus] sswelm commented on pull request #328 d322ab2: Possibly, but perhaps we should only use scale space scape position when it is actually relevant, by default you don't need it https://git.io/fxH12
<Kopernicus>
[Kopernicus] sswelm commented on pull request #328 d322ab2: Possibly, but perhaps we should only use scale space scape position when it is actually relevant, by default you realy don't need it https://git.io/fxH12
<Kopernicus>
[Kopernicus] sswelm commented on pull request #328 d322ab2: Possibly, but perhaps we should only use scale space scape position when it is actually relevant, by default you realy don't need it. My gut feeling sais that if it is relevant, you are better of calculating it manually by multiplying COMD by the scale. https://git.io/fxH12
<Kopernicus>
[Kopernicus] sswelm commented on pull request #328 d322ab2: Yes it is, it gives the Vector3d position of the vessel, which is 64 bit instead 32 bit transform https://git.io/fxH10
<Kopernicus>
[Kopernicus] sswelm commented on pull request #328 d322ab2: Possibly, but perhaps we should only use scale space position when it is actually relevant, by default you realy don't need it. My gut feeling sais that if it is relevant, you are better of calculating it manually by multiplying COMD by the scale but I'm not sure. Either-way should aim for maximum precision at all times https://git.io/fxH12