acr_8133

v0.2 is out! Changelog: - New GUI! - Removed abort button. - Made nametag setup automatic. - Couple of bug fixes and optimizations. - That's it.

PARAM.ks should contain the lines needed to change it

Yes The parameters are made to work for 2.5x scale. You can try changing them for it to work on stock scale.

SpaceX Launch Software v0.2 An autopilot for your SpaceX rockets! Automate launches and landings with this collection of scripts. The goal of this project is to simplify and automate launching and landing rockets, more specifically, rockets from the mod Tundra Exploration. I already did an attempt for this kind of autopilot before but setting it up properly has been kind of a hurdle. With this, you can just simply setup action groups, add the boot files, then customize your mission with the GUI included! No need to open other programs to edit the parameters and such. Check out the README file for further information. The GUI has been made with user accessibility in mind, I would love to hear feedback from you so join us on our Discord server for updates, bug reports, and suggestions! Videos for showcase are to be uploaded in the future Disclaimer: The contents of this kOS scripts are in no way taken from actual SpaceX rockets' flight software. Features: - A GUI to customize your mission on the pad - Automated rendezvous and docking for Dragon spacecrafts - Interplanetary missions with help from RSVP - Multithreading for faster and broader RSVP maneuver search - Launch to target's plane without rendezvous - Automated warp functions that won't invite Kraken (hopefully..) - Automated booster landings - FMRS mod compatibility - Change your LZ coordinates on the pad - Load your last mission's flight parameters - Persistent Rotation mod compatibility - A button for flight abort (added for Kerbal safety concerns) removed - and much more to be added! Planned: - Compatibility for Starship - Automated landing on other bodies - More optimal launches with help from the community - Ability to integrate user's own script after launch process - Autopilots for other rockets! Links: - Github: https://github.com/acr8133/kOS-Scripts - Discord: https://discord.gg/h2eqFShxhX - YouTube: https://www.youtube.com/channel/UCk_DBA5HwP1-caYMyhU4a5A

Is there a way to make smaller tanks on the start of the game without adjusting the maximum size of the tank I can make? it seems like the minimum size is also capped on career mode

Are there recommended mods so that I won't start the game with a Stayputnik probe core? It makes the sounding rockets look weird with the ball as a nose. Edit: I don't want to remove the Stayputnik from the starting node, I'm just wondering if there are alternatives I can install.

hi, im having a bug where the flameout sparks on the engines shoot out perpendicular to the engines and not straight out of the engine bell. i'll provide more info if this isnt a known bug yet. im using restock configs.

thanks!

anyone have an idea how can I change the size of the SOI of a body?

I'm on a modded save, and there are quite a lot of part mods. The only relevant mods I guess are the latest release of Kopernicus from the stable branch, Didymos mod (for the DART mission), and a 2.5x Rescale. I also edited the configs(below) for Didymos in \Rescale 2.5x\PlanetSpecificConfigs.cfg\ so it won't be rescaled. @Kopernicus:BEFORE[SigDim2]:NEEDS[SigDim] { @Body:HAS[#name[Didymos]] { @SigmaDimensions { @Resize = 1 @landscape = 1 @scanAltitude = 1 } } } Background to what I have now: I am currently trying this method you sent. Because I still see the first one unreliable for giving out dates. On a random date. The orbiting probe sends a launch date, and on the pad, the mothership reads the sent date and warps half of a day before it. The mothership then launches and tries to go to an orbit very close to the probe (difference is <100m Ap and Pe, <0.1 deg inclination). After entering a stable orbit, RSVP will be run from the mothership to find a good maneuver. The options are (search_interval = 1), (search_duration = ship:orbit:period), (create_maneuver_nodes = first), (final_orbit_type = none). Everything else is left on default. The maneuver created by RSVP for the mothership is very far from what Mechjeb outputs. 5km/s dV for RSVP and 2km/s dV for Mechjeb. I know the date sent is a good window because Mechjeb's porkchop plotter show good values. What I also find is that RSVP's maneuver node is much more inclined than Mechjeb's, and the Mechjeb node intercepts Didymos near its AN/DN.

Hi its me again, I'm having some problems with the node creation. I'm using Mechjeb's porkchop plotter as reference for the most efficient transfer. For the current situation, Mechjeb plots a 2km/s dV node, while RSVP plots a 5km/s dV one. Here's a link for an idea of what the orbits look like: https://imgur.com/a/i00qrTG The RSVP node has higher inclination than the Mechjeb node. Mechjeb also has its intercept close to the ascending node. I tried making the search interval 10 second for a greater chance of finding the most efficient node. The search duration also is not very far (ship:orbit:period * 2, still higher than the Mechjeb plot). Just hit me up in case you need more info.

I tried the second solution and it is able to find a time for launch. When finally in orbit, I made the search duration 2x the ship's orbital period and the launch cost went from 3500m/s to 5500m/s when finally creating the maneuver node. If I didn't limit the search duration, the waiting time increases again by multiple years. Any suggestions? edit: I had a node created just 50 days away, only happened once though after many attempts edit2: I'm just dumb and mixed up the times, it now works much better. However, while in orbit, it has a weird tendency to put the maneuver node behind the ship (including the time). Options code is below: local options is lexicon( "create_maneuver_nodes", "first", "verbose", true, "final_orbit_type", "none" ,"search_duration", (ship:orbit:period * 2) ,"search_interval", (min(ship:body:orbit:period, target:orbit:period) / 16) ,"earliest_departure", time:seconds + (60 * 5) ). I added the earliest departure to maybe fix it but it still put the node behind.

im playing with life support mods and Im trying to make the launch late as possible so I can bring less consumables

Is it possible to use RSVP to determine the T-0 of rockets waiting on the pad? I don't want my ships to wait 2 years in a parking orbit around Kerbin before I can proceed in the interplanetary transfer.

thanks everyone!