Tunefix

Thank you! :-)

Alpha 7 is out! The big one now is maneuver node editing and information display, plus the AGC/DSKY is functional again. Also a couple of new graphs. Changelist: * FDAI YAW RATE needle now moves in the correct direction. * DSKY/AGC is operational again. Documentation T.B.D. * New graph: (SCR 57) Gs/Inertial velocity. For Re-Entry monitoring. * New graph: (SCR 58) Apoapse/Periapse/Altitude vs. time. (This is a big version of the left graph on SCR 1) * Can set target angles for FDAI on NOUN 23 with VERB 20. * New panel: (SCR 110) Maneuver Node Editing * New screen: (SCR 13) Future Orbits. Maneuver nodes and sphere of influence changes * New screen: (SCR 14) Maneuver Nodes. Data on nodes. * Change screen: (SCR 4) Orbit view. Now I know the orbits around other spheres of influences in the orbit view (SCR 4) are off. Also, I have discovered the inertial angles don't make sense to me, so I will look into those.

Cool! I see that kRPC (Which my program uses to communicate to KSP) has build-in support for Remote Tech.

@SSTL_Pete I live in Norway. I really like your idea of a schedule. Should not be that hard to do. (But I have no idea how to make it look 60's. :-) Guess it could just look like a normal computer program.) Do you have the name of a preferred "Limit Communication"-mod? I have never used one of those, so need to check it out.

This looks more retro than Telemachus. I try to get the Apollo 60's feel. I am actively developing this, so any and all suggestions, are massively welcome. :-) It is at an early stage, but got the basics down.

If you have a suggestion for a CRT-screen, I have added my template sheets to the git. They makes is easy(er) to layout text and values. Font-size 3 is the middle-of-the-road choice, and I have used that for everything, except the conusables-list (screen 3) https://github.com/Tunefix/KSP_MOCR/raw/master/CRT-template.pdf

Alpha 6 is out! The biggest change is the look of the telemetry-screens. They are now more in a CRT-style, and with a 4:3 aspect ratio. I also found while doing research a specification for the charactron that generated these screens during Apollo, so i have made font-sizes of the CRT-screens as close to this spec as possible, in terms of number of chars pr. line, and number of lines. Changelist: * Pilot-screen (#100) diabled. (So many things were wrong there, and it did bad things) * New screen for FDAI (#101) * Added error needles and roll rates to the FDAI * New screen for DSKY (#102) (Not wery functional, but the look of it) * Started rewrite of AGC, and added button on main form for starting/stopping it. The AGC should only be running on one instance of KSP_MOCR, preferably the same that will use the DSKY. The state of the AGC is then transmitted to other instances via PySSSMQ. * New screen: Temperature (#7). Shows the hottest parts, parts with ablator resource, and radiators. * New screen: Consumables (#3). Show parts that contains either liquid fuel, oxydizer or monopropellant. * New screen: Electrical system (#6). Show parts that either uses, generates or stores electricity. * Redone screen: Booster (#2). The booster screen is completly redone. * Redone screen: Orbit View (#4). Removed the old FIDO-screen (whitch did'nt work), and replaced with simple orbit-view. (Inclination not included) And now, many pictures to show off the new screens.

Thank you! And, I will make that hybrid solution if I understood you correctly. My previous attempt was to complicated, and tried to do it manually; as in calculating the inertial angles of the burn, then the pilot would use a PAD-load to enter the burn-data into his DSKY, and the burn at RPY 0,0,0, in the new burn-reference. I still like that idea, but just keeping it simple for now and working with KSPs maneuver nodes is better for getting something that works™. Also, a better orbital-view is on the docket. Just making some new telemetry screens. First up is an electrical screen displaying power generators(panels, cells, enginges), power storage, current drain/surplus ...

Alpha 5 is out. Biggest changes are new look of some panels/screens. Also I have added an Event Indicator panel for FIDO, and one Event Indicator panel (out of 4) for EECOM. The layout of these panels are as they were during Apollo 15. They have no functionality in KSP_MOCR, but are more a display of possibilities.

This sends/receives data from KSP via the kRPC-plugin.

I am working on a Mission Control - software that communicates with kRPC. And is has a Map-view. As of now you can't make and edit maneuver nodes with it, but that is in the plans. See this thread for more info and images:

Alpha 4 now available. Changes: * Added H/Hdot-graph (screen 55) * Added some controls to map-view (sceen 8), show/hide tail, set tail length, fade tail A badly managed launch. (But orbit acheived 117km by 75km) The red line is a rough ballpark guideline. The target apoapse can be set in screen 1 (Ascent), and the max HDOT then adjusted if necessary.

Yeah, I got stuck in a kind of rut. Turns out; Rocket Science is HARD. And orbital mechanics; EVEN HARDER! Who would have thunk! So I am now dealing with more low-level issues, like graphs. Will brush up some of the map-stuff next, like a button to turn the "tail" on/off, turn fading of the tail on/off, and setting tail length. Suggestions are also highly appreciated.

Alpha 3 is now out. Changes: * Partial rewrite of graph-system, to get more flexibile graphs. * Added a few new graphs. * Added very approximate guides to some graphs, for launch trajectory. (screens 51, 53, 54)

Finally, things are moving again. Alpha 2 is released! Check original post for more info.

Have not tried, just used it with vanilla so far. Status Update: Not much have happend in a long time, because, you know, life, summer, and everything. When fall comes, and the nights again get dark, I should get more time to move this forwards.

@MeCripp, Yes it does look like Telemachus. That was how i started this project, me wanting something more 1960's Apollo-style stuff. And more numbers, in addition to the graphs. And then I found that kRPC was better suited to my use. And I tought i could share it also! :-) Oh, and with our own PySSMQ-server for inter-ksp_mocr-clients-data-exchange, you can have this (For those GO/NO-GO rounds):

I am making a MOCR-type standalone program, that connects to KSP using kRPC. If you have ideas for this, I would love to hear them.

Map view with ground track history:

Current screen for FIDO calculations: This is not using the games maneuver node-system. Istead it calculates the orbit resultant from burn parameters. It can also iterate through an orbit in steps of either 5 seconds of 1 second. First use the [Iterate 5] to get close, and then the [Iterate 1] (witch takes a looong time to run) to get closer. The result can then be relayed to the pilot, who can then set up his FDAI to show the correct burn attitude. Then after the burn, you can see the new orbit-data from the game in the left column. Then it's time to calculate a mid-course correction! A bit old-school, but thats half the fun. It uses point-burns, so the person manning the Booster-position will have to calculate how long the burn needs to be to achieve the total deltaV, and when to start the burn. (Nominally FIDO TIG - (burntime / 2)) And the burn-angles are in a inertial reference frame.

Alpha 1, can be tested now: https://github.com/Tunefix/KSP_MOCR/releases/tag/A1 It comes with a new and improved FDAI:

Cool, Development have continued on gitHub. No releases are made yet, but anyone can build it with VS2015 or newer. (.NET 4.6) https://github.com/Tunefix/KSP_MOCR

A standalone program that connects to a kRPC-server, and displays spacecraft/flight/orbital data. There are several screen with different types of information on them, i.e. Engine data or Resources data. There are also several screens that displays graphs of data, i.e. Altitude vs. Inertial speed, G-force and Dynamic pressure, Roll-Pitch-Yaw graphs, and more. A resize-able map view shows the current position of the spacecraft with ground-track history. Releases: https://github.com/Tunefix/KSP_MOCR/releases/ Documentation: (The little that exists) https://github.com/Tunefix/KSP_MOCR/blob/master/README.md All the best, Tunefix.