{"action":"created","issue":{"url":"https://api.github.com/repos/MuMech/MechJeb2/issues/867","repository_url":"https://api.github.com/repos/MuMech/MechJeb2","labels_url":"https://api.github.com/repos/MuMech/MechJeb2/issues/867/labels{/name}","comments_url":"https://api.github.com/repos/MuMech/MechJeb2/issues/867/comments","events_url":"https://api.github.com/repos/MuMech/MechJeb2/issues/867/events","html_url":"https://github.com/MuMech/MechJeb2/issues/867","id":213553240,"number":867,"title":"MJ (2.6.0 master) + RealismOverhaul, RealFuels: Engines w/Ullage requirements do not calculate node burn length, countdown correctly","user":{"login":"DRVeyl","id":25906300,"avatar_url":"https://avatars2.githubusercontent.com/u/25906300?v=3","gravatar_id":"","url":"https://api.github.com/users/DRVeyl","html_url":"https://github.com/DRVeyl","followers_url":"https://api.github.com/users/DRVeyl/followers","following_url":"https://api.github.com/users/DRVeyl/following{/other_user}","gists_url":"https://api.github.com/users/DRVeyl/gists{/gist_id}","starred_url":"https://api.github.com/users/DRVeyl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DRVeyl/subscriptions","organizations_url":"https://api.github.com/users/DRVeyl/orgs","repos_url":"https://api.github.com/users/DRVeyl/repos","events_url":"https://api.github.com/users/DRVeyl/events{/privacy}","received_events_url":"https://api.github.com/users/DRVeyl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2017-03-11T19:32:28Z","updated_at":"2017-06-02T04:06:38Z","closed_at":null,"body":"Running MJ 2.6.0 (master, from CKAN), RealismOverhaul latest release and its many required additional mods.  Specifically with RealFuels and its support for engines requiring ullage.\r\n\r\nIf the engine requires ullage and the propellant state is not \"Very Stable\" then MJ will calculate an infinte burn time required, and thus an infinite burn countdown.  This results in MJ automatically beginning to execute the next node as soon as it the autopilot is engaged, instead of determining the \"correct\" burn time and burn countdown if the engine were able to perform and waiting/warping accordingly.\r\n\r\nIf the fuel state is \"Very Stable\" or the engine does not require ullage, there is no issue.\r\nIf the engine requiring ullage is in any future stage and has not been activated, there is no issue.\r\nIf the engine requiring ullage is in a future stage but has been de-activated, there is no issue.\r\n\r\nThis can be re-created by launching a craft to orbit in RO.  Activate a stage with an engine requiring ullage (such as the AJ-10 line).  Turn off autopilot and create a maneuver node in the future.  MJ \"Maneuver Node Info\" panel displays for \"Node Burn Length\" and \"Node Burn Countdown\" will read correct when the engine's fuel state is \"Very Stable\" and will read \"Inf\" when the fuel state is anything else.  Link to screenshots: http://imgur.com/a/vTzAh    User can switch between the two conditions indefinitely by iteratively ullaging and then allowing the fuel to unsettle.\r\n\r\nRepeatable workaround: Disable the engine, create a new future stage, and move the engine to that future stage.  This causes MJ to correctly calculate the burn duration and countdowns and behave as expected.\r\n\r\nI don't know if this is better addressed in a RealFuels or MJ issue.  I'm not sure if this is something in RO/RF (ModuleEnginesRF.cs?) causing the engine to have 0 thrust/ISP, if RO/RF is doing this only for engines in the current stage, or if MJ's calculation for future stages is different from its current-stage calculation.  Did not see this in KSP 1.1.3, have always seen this behavior as of 1.2.2."},"comment":{"url":"https://api.github.com/repos/MuMech/MechJeb2/issues/comments/305684017","html_url":"https://github.com/MuMech/MechJeb2/issues/867#issuecomment-305684017","issue_url":"https://api.github.com/repos/MuMech/MechJeb2/issues/867","id":305684017,"user":{"login":"lamont-granquist","id":454857,"avatar_url":"https://avatars3.githubusercontent.com/u/454857?v=3","gravatar_id":"","url":"https://api.github.com/users/lamont-granquist","html_url":"https://github.com/lamont-granquist","followers_url":"https://api.github.com/users/lamont-granquist/followers","following_url":"https://api.github.com/users/lamont-granquist/following{/other_user}","gists_url":"https://api.github.com/users/lamont-granquist/gists{/gist_id}","starred_url":"https://api.github.com/users/lamont-granquist/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lamont-granquist/subscriptions","organizations_url":"https://api.github.com/users/lamont-granquist/orgs","repos_url":"https://api.github.com/users/lamont-granquist/repos","events_url":"https://api.github.com/users/lamont-granquist/events{/privacy}","received_events_url":"https://api.github.com/users/lamont-granquist/received_events","type":"User","site_admin":false},"created_at":"2017-06-02T04:06:38Z","updated_at":"2017-06-02T04:06:38Z","body":"is anyone still seeing this after #882 / 2.6.0.0-694?"}}
{"actor":{"display_login":"lamont-granquist"}}