Kobymaru

You guys are obviously all wrong. The best fighter plane ever was the MiG-21. Sure, it could not beat the F-22 in BVR or intercept an SR-71, but it's cheap, sturdy, repairable and made for eternity. Sometimes just showing up wins the battle, and with its low maintanenca and flight costs and over 12.000 units produced, the MiG-21 did a lot more showing up than the 195 units of overpriced F-22's Which reminds me, @memes in space why does this poll only have options for American Fighter Jets? There's a plethora of Russian, British, French and Italian Jets too that deserve a mention.

Before posting feature requests or bug reports, please read the FAQ. Download Toolbar Controller and Click Through Blocker and SpaceTux Library are now dependencies of the Trajectories mod. Please install them first. On SpaceDock On GitHub Description The mod displays trajectory predictions, accounting for atmospheric drag and lift. Works with the stock aerodynamic model, and with Ferram Aerospace Research (FAR). With this mod, you can choose precisely the location where you'll crash. The typical precision is about 6km. Plan Aerobraking maneuvers that can, for example, put you on intersection trajectory with another body (see point 1 about what you can do from there) Keep in mind that this software comes without warranty of any kind, and in particular that it may or may not help you survive, reach a specific target, or anything at all. But it usually helps FAQ Works with stock aerodynamics and FAR Reportedly works with deadly reentry real solar system Rescaled Kerbin Outer Planets Mod Compatible with Blizzy's toolbar If you see weird spirals or other crazy lines everywhere, double-check you didn't enable "body-fixed mode" by mistake If the predicted trajectory seems inaccurate, check that you set the correct orientation in the Descent profile (or checked Prograde or Retrograde), and that you keep that orientation all the time It's not possible to predict a trajectory for a future stage. We know this is a highly requested feature, but unless we duplicate big parts of the KSP-internal code, we are limited to simulating the current state of the vessel. Parachutes are not simulated (that's usually not a problem if you open it near the ground) User manual See your predicted trajectory Open the map view This is it ; trajectory display is enabled by default, you have nothing else to do White is the trajectory in space, red is the trajectory in atmosphere, the red cross is your impact point (that takes the body rotation into account to show the impact point on the terrain, this is useful both for bodies with and without atmosphere) Disable the trajectory display Click on the Trajectories icon in the stock KSP toolbar (or Blizzy's toolbar if it's installed) to display the main UI Click "Display trajectory" to toggle it on/off Click "complete" to toggle display of the complete trajectory (including parts where it is superimposed with the stock KSP trajectory) Set a target point (nav ball guidance) Adjust your velocity so that the red cross is located where you want to go Click "Set current impact as target" to enable the green cross Alternatively, there is a button to set the target on the KSC (works on Kerbin only obviously), or you can enter longitude/latitude Go back in flight view, and notice the two new indicators on the nav ball The square indicator shows where you need to point your craft at if you were exactly following the predicted trajectory The circle indicator is a hint about the direction you should go to adjust your actual trajectory to reach the target (this is not necessarily where you need to point, what's important is the direction between the square and the circle, and the distance between them indicates how far you are from the perfect trajectory) Body-fixed mode Use this toggle to switch between the regular mode (similar to stock KSP orbits), or body-fixed mode. In body-fixed mode, the trajectory is displayed relatively to the body frame, following the body rotation. This mode makes sense for atmospheric or low terrain fly-by, and also to adjust a geostationary orbit. However, for most high orbits, it will just look funny. This can help you keep occupied for those 2-year-long planetary transfers, but try not to burn up all the fuel to see how it can make funny curved lines. Manoeuver nodes You can plan aerobraking or re-entry after manoeuvers, just place your nodes as usual and see the predicted trajectory. Keep in mind that you always place nodes on the stock trajectory, that might be very different from the predicted one, so you may have to place nodes at a point that have an effect somewhere else on the predicted trajectory (especially when planning landing on a body without atmosphere with body-fixed mode). Also, atmospheric prediction can happen only for the body you are currently orbiting, so you can't plan a Kerbin re-entry while you're still arround the Mun. Support and Bugs If you have questions and feedback regarding a current release, feel free to post in this thread. Please post bug reports on the GitHub bug tracker. If you don't know how, don't want to learn or are unsure it's a bug, you can ask in this thread. Contributions This mod is a community project! It was originally written by @Youen and is currently maintained by @linuxgurugamer. The following people have already contributed to this project (in approximate order of commits): Youen (Github neuoy) PiezPiedPy Kobymaru (Github fat-lobyte) atomicfury (Github sawyerap) And many others. You want to be part of this list? Contributions are very welcome! Read our Introduction for Contributors, fork the Repository on Github and have a go at the code! When you feel that your changes are mature enough to be included, send us a pull request! It's always best if you work on your "pet problem" - a bug that needs to be fixed or that you personally want to see implemented. Or you could just grab an issue from our Issue Tracker! Change log The changelog started with release v1.6.7. For the changes in versions older than that, please visit the GitHub releases page. License This mod is under GPLv3 license, feel free to look at the source code: https://github.com/linuxgurugamer/KSPTrajectories/

Well that's probably because I uploaded an old version Sorry guys. Download again from the same link: https://github.com/neuoy/KSPTrajectories/releases/download/v1.6.9-rc1/Trajectories.dll If the file size is 95 232 Bytes, then it should be the right file. Also, for testing please state the situation that you tested (which planet, which Periapsis/Apoapsis, AoA, what kind of craft, wings, control surfaces?)

Cool. I mean that does sound interesting, but I'm afraid I won't have time to implement it. If there are more interested people, you could join forces and implement it yourself! I take pull requests if the code quality is OK and it doesn't bog down performance too much. It's discussed on GitHub: https://github.com/neuoy/KSPTrajectories/issues/37 But it's not really related to your feature, and a totally different topic

TBH, right now I can't quite imagine what this has to do with Trajectories, what to do with that data. Is it related to that "landing ellipse" thing that people have been asking about in the past?

Well it doesn't have to be bone stock, I just meant Stock Aero and not FAR

Ok, then I shall do that.

Is it "dangerous" in a way? Here:

Wasn'T there a method to do that "transparently", meaning that all posts are transferred? I recall it had something to with merging threads and/or changing post ownership or something.

Hi, I have a question about transferring thread ownership. How does this actually work (internally)? Is the thread URL preserved? Are the posts preserved? I might have a request soon for a thread transfer ownership, but I'd like to make sure that the thread stays healthy

Thank you

Hey guys, could we get a little bit of stock precision testing with this one? Trajectories.dll

Hi @sarbian, I like your ground marker and path drawing code that you have for the landing predictions. I would like to use it for the Trajectories mod, specifically, I would like to copy-paste the MechJeb2/MechJeb2/GLUtils.cs files. Would that be ok with you?

Turns out writing a good UI is difficult and time consuming. RoverDude's time is better put to use in different parts of MKS. But if you don't like the UI, why don't *you* contribute a new one?

Ok, I'll take a look. Would you mind creating a GitHub issue? Me too buddy, me too. I'm writing a small logger/telemetry that might help with debugging. If you (or anyone else) can read code, some eyes on the DragCube calculation stuff would probably help, because that's where I presume the issue lies: https://github.com/neuoy/KSPTrajectories/blob/master/Plugin/StockAeroUtil.cs#L158 Well, it still kinda works. I don't have concrete definitions of when it does and doesn't but from experience: Eve is a big nope Kerbin and Laythe are OK The higher the aerodynamical force is compared to the mass, the more wrong it is The flatter the trajectory, the more wrong it is Don't rely on it for aerobraking Best to just try out it. It's still accurate for short and steep trajectories.

Gotta say, works pretty darn well for me:

PSA, the Mod seems to work under 1.3.0 even without a recompile. @Boris-Barboris, would you care to upload a version bump? All you have to do is change the AVC version file, bump the mod version and the KSP compatibility version (, optionally recompile) and then release a new version. If you are lazy, I can assist by making a PR.

Unmarked sarcasm on the internet is a risky business that is best described by Poe's Law . There are enough people on the internet in general and on these Forums in particular that feel "entitled" to mod updates and features being implemented. Even upon re-reading your comment, the sarcasm wasn't particularly clear to me. I didn't know that image macro/meme, so i could only take it for face value. So please excuse me, if I mistook your post for something that it was not. Or maybe I'm just bad at sarcasm. Who knows.

New release is up! Version 1.6.8 with fixes to the In-Flight trajectory display, download from GitHub or SpaceDock. Provided that the CKAN fairies have heard prayers and pleas, the update should propagate to CKAN soon™. Full Changelog: The inofficial title for this release is "Jeez you guys."

No problem, you're welcome I'm very hesitant about auto-switching. Cuz with this kind of stuff, some will be unhappy and demand options. And we end up with 5 more options: Show in-flight trajectory? Auto-Switch in-flight trajectory? Maximum Altitude for switch? Minimum Altitude for switch? But maybe I want it to not ignore planes? We can talk about this kind of stuff when we have a better GUI, but now I really don't want to unnecessarily clutter everything up. I'll definitely add the in-flight trajectory toggle since you guys seem to really need it, but otherwise let's be very conservative with the stuff that we cram into the GUI, OK?

@dlrk you are also not the only user of this mod, and I don't serve as your personal programmer. Other people here *have* asked for this, that's why I have even bothered with this.

I'll take a look at it.

Upload savegame and output_log for me please. Ok.

Does it? I recall setting the lowest suppoted version to 1..2.9. Did I forget some config file? Getting pretty crowded in the menu Could you report the issue on GitHub? Yes, the cross being always there is admittedly annoying. Could you also create a GitHub Issue here?

New release is up! Version 1.6.7 with KSP 1.3.0 compatibility, download from GitHub or SpaceDock. Provided that the CKAN fairies have heard prayers and pleas, the update should propagate to CKAN soon™. Full Changelog: Big Thanks to all contributors, especially @PiezPiedPy for their help!