zentarul

Hi guys, I'm on hiatus until the "Making History" expension comes out. Thanks @linuxgurugamer for taking up the maintenance until I come back.

Yes, this has been a known issue for some time now. I'm going to try fixing it again. Now that I have some professional experience as a Unity developer, I feel more confident I can fix it.

The current version works as is in 1.3. However, I will make a new build this Friday to update the version to 1.3 officially, especially for ckan users.

Fixed in v1.0.1

I have to agree all the way. After checking the combinations of flag values for the ControlTypes, what makes the most sene is indeed to check that all parts of the control group you are insterested in are locked and that the only group which makes sense for generic text fields is ControlTypes.KeyboardInput.

I'm gonna try to get this fixed ASAP! @Diazo if you are online now, give me a ping so we can coordonate. I saw your github post and will try to change the flag to something else.

Yeah, that version is still working. Sorry for the lazy updates, I'll try to put in some more time to do the changes I have talked about previously.

Fixed!

This is rather strange, I tested it around Kerbin and didn't have any problem with that. Could you provide a screenshot of when you can't click on the menu?

It is configurable in a text file in the mod's sub-folders. I'll add a config GUI for v1.1 Yeah, I was lazy, I just kept my own maths, didn't try to interface with the new "aim camera". The result is virtually the same, except that I have a smooth transition.

Now updated for ksp 1.2

New upgraded version is now available for KSP 1.2. I have made a bunch of improvements and implemented what @hvacengi suggested!

Holla Folks! I am back from inactivity. Lets just say that 1.2 experimentals have woken me up. I saw that they have now implemented a stock "aim camera" tool, but I still find that my implementation is better. The noobs at squad didn't even include a smooth camera transition! XD (kidding, I love you guys) But yeah, I will keep maintaining this mod for 1.2 despite the redundant functionality. So look forward to an update soon.

I'm not really impressed, my Camera Focus Changer does a better job with a smooth camera transition and a single key press. Please Squad, I give you permission to use my code in your game! I just want this feature to be at its best!

It could be done, but like Deimos said, I think the WASD Camera mod gives you even more control in the confines of the VAB. Stay tuned though, I might just add it as a hidden feature that can be enabled in the config file.

Now with Speed and Angle to Prograde support as well as working on the orbit of the active target. Some options are disabled by default and need to be enabled in the config file. For the next version I will try to add a simple GUI window in to edit the configs.

Unfortunately, this solution doesn't seem to work with kOS. What kind of text field do you find yourself using? Maybe I can test it with a different mod.

Thanks for the information @Neutrinovore, I'll try to follow those discussions. Since I am a user of kOS, this is a bug that also affects me personnaly, so I'd very much like to have it fixed. Feel free to poke me if you hear that a fix/work-around has been found. Cheers! Thanks for the bug report, I'll try to have a look at it. Maybe if I detect that the camera is now in IVA mode I should reset the camera settings. That's also something I'd like to fix. I'll it a shot this week.

Now updated for KSP 1.1

now updated for KSP 1.1

Thanks a lot xEvilReepers! Here's the result: ABookCase Orbital Reference System

Done!

ABookCase Orbital Reference System v0.4.0.0 This is a request from ABookCase who wanted a simple mod that displays altitude of an orbit at a point by hovering the mouse over it. So I did that and also added time information and more. There is a config file in PluginData folder that can be modified to tweak was is displayed on screen. The mouse is not shown in the screenshots, but I'm sure you can imagine it. http://imgur.com/a/K6wiA Download: Get v0.4.1.0 from GitHub! Also available through SpaceDock and CKAN! Licensed under MIT I'd like to thank xEvilReeperx for his solution.

I am trying to display contextual information about an orbit just by hovering the mouse above it. Obviously, clicking on an orbit allows you to place a maneuver node at that position, so there must be a way to translate mouse position into orbit + obit UT. The question is how? The OrbitRenderer seems to have some info about that. It has a GetMouseOverNode function and a mouseOver member, but it is not clear what they mean. Does anyone have any insight on this? Thanks, Zentarul