Search the Community
Showing results for tags 'external tool'.
Found 3 results
Constellation Builder v0.3 - Web version File version - requires GeoGebra software, download link below DIRECTIONS: Adjust slider for range of omnidirectional antenna to be used on the satellites, in 100's of kilometers. 4Mm range? Set it to 40. As of v0.3 all distance sliders display in kilometers. The grid scale is still 1 unit = 100km. Anjust slider for number of satellites in the constellation. Select connection requirements. (Do they need to connect to KSC and/or each other?) IMPORTANT: IF YOU DO NOT SELECT EITHER CHECKBOX IT WILL PUT THE CONSTELLATION IN AN ORBIT UNDER THE SURFACE OF KERBIN. This is hardcoded and keeps GeoGebra from choking on it until I implement some more features. As of v0.3 this is no longer true. An additional slider has been added to choose the orbital altitude in km, with upper and lower limits of the orange rings. Area of uninterrupted coverage will be displayed as a wireframe torus built from magenta circles and dark purple rings. Recommended constellation orbit displayed as a dark red ring. This will be removed at some point. Minimum and maximum bounds for the given parameters are displayed as orange rings. ADDITIONAL NOTES: Kerbin has a sort of halo - that's where the atmosphere is. Points representing the Mun and Minmus, along with to-scale spheres for both bodies, correct orbits, and rings representing the SOI of both bodies are present. Minmus' orbit uses y+ as the reference direction and the x-y plane as the reference plane. Zoom out far enough and you'll notice a pair of rings. The blue ring represents Kerbin's SOI. The red ring represents the max range at which KSC can connect to a satellite without relays. For the purposes of this tool, KSC is located exactly on the equator at sea level at (6,0,0) Cartesian coordinates. If you download the file, be very careful not to accidentally change something and break it. All game data from the official wiki. http://wiki.kerbalspaceprogram.com/wiki/Main_Page All RemoteTech data from https://remotetechnologiesgroup.github.io/RemoteTech/. HOW IT WORKS: KNOWN ISSUES: Selecting neither connection requirement results in a nonsensical orbit. Minimum orbit does not respect intersat connection requirement checkbox. My torus sucks. Missing "impossible orbit" checks. (inside the atmosphere, in an area swept by the Mun's or Minmus' SOI, etc.) Latitude of polar shadow is given as degrees north (it's both poles) and simply uses "?" if the coverage zone does not actually intersect Kerbin. Polar shadow calculations don't care if the constellation is actually in range of Kerbin's surface. TO-DO: Fix the known issues. Allow adjustment of the placement of the constellation within the upper and lower bounds. Right now, it places the constellation 100km inside the upper bound. Make the antenna range input in either kilometers or megameters. Draw the polar shadows of Kerbin. Right now, all it has is the latitude N or S above which there is no ground coverage. Add an option to show the calculation objects. Upload the version of this that matches the description of how it works. Add pictures. GEOGEBRA SOFTWARE LINKS: GeoGebra main page - Download GeoGebra - GeoGebra License - About GeoGebra GeoGebra user manual (more like a wiki) LICENSE (because forum rules): I did not make GeoGebra. I also did not invent math. All data related to the game and the mod came from the KSP Wiki and the RemoteTech website. What part of this I do hold the rights to is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Have fun!
I... like many of you, probably, have been dreaming of having all the features mechjeb provides... but without sacrificing all of my screen real estate to it. Eventually I want to build a dedicated cockpit... and that's going to require instruments and buttons, of course. So I've started hacking at a way to get all of that data out of the KSP window, and I'm getting rather close. To start with.. this is just a little project that is standing on the shoulders of GIANTS. Two giants in particular make this work and are required for it to function: Mechjeb does all the mechjebing.... and kRPC does all of the communication between KSP and my client and provides the python library it's built on. I'm just hanging tinsel and bows on the trees that Djungelorm and Sarbian grew from seeds. The interface looks like this at the moment: I've just about finished the kRPC extension to grab the data I need and push in the commands to the active vessel's mechjeb and it's working great,and a quick test of the orbital parameters only worked great and I've tried pulling data ridiculously fast to see if I could impact game performance and so far haven't managed to! So, in the next day or two I'll have the buttons and text boxes all connected and working. The graphical elements (the orbital visualizer, and I really would like to do a better graphical piece for the landing and docking visual guidance instead of the kludgy collection of scrollbars and sliders I've got at the moment) will take somewhat longer as I'm learning as I go and I haven't BEGUN to learn graphics in python... but I'm imagining it shouldn't be TOO awful... Seeing as how we're really talking about drawing a couple of ellipses and lines, and moving a few sprites around the screen? Famous last words right? If anyone wants to help with the graphical parts, I'd welcome it, but I'll get to it myself eventually! Future plans... other than making it all work - I'd like to add another page that has a big grid and a filter selector to give you part level control of your vessel. Hypothetically you could bring up every science experiment on board and give you an interface to run, reset and review them, or pull up all fuel tanks and let you manage resource transfers, or bring up your engines and let you disable, enable, and thrust limit them, or decouplers and docking ports, or parachutes... the ability to configure parts from what becomes your external IVA screen seems interesting to me. Anyway. I haven't realized EVERY button in Mechjeb... just the most frequently used ones. I'd LOVE it if people would pour over the screenshots and say "I didn't see a way to do this... and I wanna." So I don't miss something obvious and useful! For example, as I sat here typing this, I realized the 'node executor' section of every page needs 'next node time' and 'next node deltaV' fields. I'd much rather get the fine toothed comb comments NOW than when it's all put together and working and someone says "Yeah, but why didn't you..." and drops one of those 'should have been obvious but now requires redoing a week's work' bits of wisdom on me! Art