-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Burn in time warp with RO ion engines (new feature suggestions) #2347
Comments
I would love to add this but Eggrobin sais it cannot be done for a more detailed answer see: |
The problem is that there is no way to accelerate a vessel during timewarp with Principa installed. |
Well,the solution may be insert your powered flight plan integration method into prediction.That's to say,well cruise control setting could be setting use a node(then node may appear to have resource-binded infos to prevent over-dv-burns),then a flight-plan-type powered extremely long node will be auto created and insert into prediction line and then during timewarp resource check(especially for ion engine electricity draining which does not ) will be binded with ever integration step.Then if prediction end time doesn't reach end of line and resource deduction plugin goes normal,it goes on and then follow into next loop. |
Well now I'm using 1000x physics warp as a bare solution.I'm still wondering why your flight planner can manipulate orbit but the flight calculation cannot.(Maybe a static model is simpler?) |
You can integrate the rocket equation and update position and velocity and decrement propellant in time warp. That is the easy part. What is the control for the direction the vessel is pointing and what guidance law are you using, and what is the UX/UI for the user to input properties of that guidance law? Pointing in a single direction is going to be garbage. Following an impulsive KSP maneuver node is going to be hot garbage. Starting and stopping the time warp in order to halfway get some precision with the burn is going to be very difficult for human users. There do exist low thrust guidance laws, like the Lawden Spiral, but you not only need to program that kind of guidance law, but you need a trajectory optimizer so that it calculates a maneuver to its conclusion that results in arriving at least very near the destination. That is the actual hard part here. Because if someone builds the capability to have low thrust burns without solving that problem, you're going to suddenly realize how bad that feature is to use. I expect if I go looking at the various abandoned persistent thrust mods throughout the years that the common theme I'm going to find is that the authors solved the basic problem of persistent thrust, but then without a trajectory optimizer and guidance law on top of that it turned into an unusable mess. |
perhaps you didn't notice but KSPIE peristant thrust does support active navigation locking meaing it will adjust its directly exacly as you would do follow a navigation burn in real time. |
I think is it able to restrict usage to make things clearer; if this is just moving the plan integrator to flight, then restricting usage will simplify other works to get it implemented (in official RO wiki on GitHub, it was said that Orbit Manipulator that old mod could have implemented this, which featured same as Principia) |
Now starting to find usables and difficulties |
egg — 16:36 2021.12.29 UTC, at KSP-RO discord |
current status: a temporary solution is reached, by Charon_S. and me, with a fairly OK accuracy with acceptable time efficiency. |
As in reality,ion engines has a very poor thrust (0.092N Vac in 1.6.1 RO as of NSTAR) ,so burn will last for hundreds of days which is really annoying but quite realistion(Dawn burnt for 270 days as 1 burn).As principia make high physics warp in BetterTimeWarp extreme laggy(and the burn will still last for a computer's whole day if use 100x physics warp maximum)so it must be executed in on-rail high time warp.I know principia has a good prediction under thrust so I hope to change this into a executor (spaceship will follow the prediction with thrust,and it's relatively easy since Principia use forces during timewarp on gravity) on and drain required resources (for example xenon(or Argon) gas and electricityfor RO NSTAR ion engine ,but tweakable depending on engine) from resources,and timewarp will be forced to stop if one resource is drained and time warp will stop and warning text will be shown.(pls prevent game crashing!)
Why I have to submit this issue is because KSPI and DSEV`s plugin work only for stock patched conics orbit system (completely disabled by Principia) and they force orbit parameters to change during time warp.(KSPI is completely uselsss,while DSEV drain resources but does not bring any velocity change)But as a RO user I hate to use stock ion engine which violated energy conservation by 1k times.
Hoping to see improvement next moon and tell us how to use this API in cfg files,and thus it will be applied to RO ion Engines,and fusion torches with Mm/s level burn in KSPI&DSEV,and Photon sails in KSPI.
(@sswelm and @Angel-125 for KSPI&DSEV support)
Anyway,again hoping to see improvement next moon.
The text was updated successfully, but these errors were encountered: