M mike-c Member Joined Jun 30, 2015 Messages 82 Reaction score 0 Points 6 Oct 3, 2016 #1 Is there an update of .cfg-files syntax/semantics to the new orbiter-API(2016) at least for touchdown-point definition? ( Config\Vessels\*.cfg) Doc\OrbiterConfig.pdf seems to be outdated. Last edited: Oct 3, 2016
Is there an update of .cfg-files syntax/semantics to the new orbiter-API(2016) at least for touchdown-point definition? ( Config\Vessels\*.cfg) Doc\OrbiterConfig.pdf seems to be outdated.
gattispilot Addon Developer Addon Developer Joined Oct 17, 2007 Messages 10,552 Reaction score 4,375 Points 203 Location Dallas, TX Oct 3, 2016 #2 Not sure what you are asking. I think most .cfg have a module with the touch down points in them
M mike-c Member Joined Jun 30, 2015 Messages 82 Reaction score 0 Points 6 Oct 3, 2016 #3 gattispilot said: Not sure what you are asking. I think most .cfg have a module with the touch down points in them Click to expand... I'm asking this: Code: ; === Configuration file for vessel class Generic CVEL stage (Atlas V Core) === Module = Velcro Meshname = Velcro/EELV/AtlasVCore ... Touchdownpoints = 0 4.4 -16.778 3.81 -2.2 -16.778 -3.81 -2.2 -16.778 useful if the Addon-Dev doen't want to hardcode but to build in some flexibility. Read them out with: from OrbiterAPI: Code: void VESSEL::GetTouchdownPoints ( VECTOR3 & pt1, VECTOR3 & pt2, VECTOR3 & pt3 ) const But how to code 2016 compat?
gattispilot said: Not sure what you are asking. I think most .cfg have a module with the touch down points in them Click to expand... I'm asking this: Code: ; === Configuration file for vessel class Generic CVEL stage (Atlas V Core) === Module = Velcro Meshname = Velcro/EELV/AtlasVCore ... Touchdownpoints = 0 4.4 -16.778 3.81 -2.2 -16.778 -3.81 -2.2 -16.778 useful if the Addon-Dev doen't want to hardcode but to build in some flexibility. Read them out with: from OrbiterAPI: Code: void VESSEL::GetTouchdownPoints ( VECTOR3 & pt1, VECTOR3 & pt2, VECTOR3 & pt3 ) const But how to code 2016 compat?