mrenigma03

I think it's a KSP/Unity issue. I've had that problem with just Mechjeb before. Try clicking on the game window, then dragging the protractor window. Also make sure your game is finished loading before trying to move the window.

Protractor update! Changes in 2.3.3 - converted to partmodule - model source files no longer part of package, available upon request - substantial code cleanup - fixed draw code to work on SOI intercepts - added symbol around close approach distance to indicate target is selected for map line - changed save to use more robust system I suggest removing all protractor files from Parts, PluginData, and Plugins before installing due to the switch to partmodule and new save system. This will work with previous ships.

I've considered adding a "closest approach" that tracks other vessels and debris orbiting the same body as you. Is there anything else useful to display for vessels?

Extract the .zip. Open the folder called "protractor vx.x.x" (the x changes with each version). You'll see three folders: Parts, PluginData, Plugins. Copy those into your KSP install directory. Click yes to merge/overwrite.

Get as close to 0 with phase angle first, then as close to 0 with psi. You're really unlikely to get both to 0 simultaneously. The goal is to get as close as possible. You have a decent margin of error depending on which planet you're going to.

Thanks, glad you like it! I'm not a software developer by trade, so this plugin is my learning project. All these features are the result of "hmm..I wonder if I can do 'x'" and then learning how. That's also why it gets updated almost daily.

Changes in 2.3.2 - tweaked visibility of closest approach line - added total dV counter - added functionality to track dV using something similar to a stopwatch - added save functionality for toggle buttons

Adding this.

Changes in 2.3.1 - overhauled closest approach to fix errors caused by how the game handles SOI switches - approach line looks a lot nicer - has similar appearance to orbit lines on the map Onion920, can you get on IRC so maybe we can fix this? Make sure you're using the latest mod version too.

Thanks! I'm actually fine tuning the closest approach. Right now it has some odd behaviors from time to time, and can be a touch inaccurate. I hope to have an update done by the end of the weekend, along with a brand new line look.

Check the plugin folder, do you see protractor.dll (and no planphaseang.dll)? I'll be on #KSPOfficial (Esper) for a little while longer if you want to drop in.

New update! Changes in 2.3.0 - moon -> planet transfer - show/hide moons or planets as a group - click on name of a body to hide all other bodies, click again to restore - window automatically resizes to reflect number of bodies in list - if orbiting a moon, Ren. θ to planets shown after accounting for transfer orbit to host planet - distances now calculated to surface, not to core of target - collapsed ren θ and θ into one column - burn when this is 0 - collapsed current Ψ and eject Ψ into one column - burn when this is 0 - updated manual to reflect changes - closest approach line resets at SOI change Click the "?" mark on the window.

Haven't yet. That's why I'm working on it

While your pluginmakes it relatively easy to fine-tune the orbit to get a patched conic 'hit' on the target planet (at considerable fuel expense), I have noticed that more often than not I do NOT get a SOI change on my first try when I follow the angles from your plugin but I DO get a hit on the first try when I follow the angles from AdamKSP. What is the reason for this discrepancy? We each have a different method of calculating the angles. Different assumptions are made to simplify the quirks posed by inclination and eccentricity. I'm working on a version that takes eccentricity into account, and once I get that done the discrepancy will be irrelevant.

Crap. version 2.2.3 introduced a bug in the closest distance. DELETE planphaseang.dll FROM YOUR PLUGIN FOLDER IF USING VERSION 2.2.3 OR EARLIER Changes in 2.2.4 - added window position saving - fixed bug with closest distance when SOI switch detected

Changes in 2.2.3 - minor text alignment adjustment - line for closest approach properly scales with zoom - line for closest approach no longer slides back and forth within a tenth of ship orbit

Yes, closest approach takes inclination and eccentricity into account. It's main purpose is as a way to fix the inadequacies of the angle functions caused by the angles ignoring eccentricity and inclination.

Ah, I did misunderstand, sorry. 1) You want to level out your approach so that you enter Duna's SOI at its equator with a 0 degree inclination. This is something you can do two weeks ahead of time (once you have an intercept course). 2) Use the "closest" column. It tells you how close your current orbit takes you to your target. Do a quick RCS thrust in each direction (right, left, forward, backward, up, down) and see which ones decrease that distance. Then burn in that direction. You can also click on the number and draw a line showing the closest approach, then try to make the green line shrink. Right now, the green line only works with another planet if you are orbiting the sun, but a future update will fix that.

1) Land on Duna near its equator, then take off heading east (just like you would from Kerbin). 2) As far away from Duna as possible, start fine tuning your approach. The earlier you correct, the less fuel you have to use. Start tuning from Kerbin, then do more adjustments 10 days before you enter Duna SOI. This should leave very little work for you to do once you're in Duna's SOI. Eventually you want to aim to have a periapsis around Duna of between 9 km. and 10 km. Use parachutes. If you do it right, you won't have to spend a drop of fuel from your lander. If you're trying to get to Ike, use a periapsis of above 12 km. That will aerobrake you but not so much that you don't leave Duna's atmosphere. Mechjeb landing module predicts your apoapsis after an aerobrake, so use that as a guide.

Pretty sure any plugin version post 2.0.0 works on any ship built since 2.0.0 (1.x.x weren't even released on these forums). I leave a lot of ships in certain orbits to test the mod, so I'd notice if it broke backwards compatibility. If that happens, I'll let you know. Unless it's a major feature update (or caused by Squad updating something), I wouldn't introduce anything that breaks old ships.

No, the tool is designed as instrumentation. It has to use simplified versions of the orbits to do the math. The result is that it gets you 95% of the way just by following the numbers. That last 5% requires an understanding of space flight so you can make the necessary corrections. There are a lot of really good guides littered about the forums, and you can always join the #KSPOfficial channel and ask for help.

- fixed crash related to 0 thrust/mass ratio and adjust psi

Yep! I'll let you know if anything ever breaks backward compatibility.

New update! Changes in 2.2.2 - improved scaling of the closest approach line so as to be visible on the map when zoomed out - tweaked ejection burn adjustment values to work with low thrust/mass ships - adjust ejection now works for transfers between moons - closest approach now styled to reflect distance - bold for close, bold and italics for intercept - significantly improved GUI - code optimization

The line drawing is definitely still in an experimental phase. That being said, if you zoom out too far it disappears. You are looking on the map, right? And it draws a closest approach later in your orbit, so the line may not be anywhere near your vessel. Try it from a parking orbit around Kerbin by clicking on where it shows the Mun's closest approach in the "closest" column.