ainamogel

First of all, let me add my thanks to Navy for updating this super mod. Definitely on my "must have" list. Having said that, for future reference I'll just note that the "NavHud" mod provides similar functionality and much more in a (to me) slightly less appealing way. Finally, to address Casvah's second question: "RPM" is short for RasterPropMonitor, a perfectly wonderful mod that makes IVAs (the view from inside your command pod) much more fun and immersive. This mod is integrated with RPM so that you can dock efficiently from inside the command pod: lots of fun! "MFD" is short for "MultiFunction Display", which is the cockpit display inside of RPM on which the DPAI information is displayed when using RPM. Unfortunately, RPM is now deprecated and is being replaced by a new mod which (for now) does not have DPAI integration as far as I know. Really finally, the first video on the first page of this thread gives you a good idea about how to use this mod: 1) select "control from here" for the docking port on your craft 2) select "set as target" for the docking port that you want to dock to 3) turn on SAS and RCS 4) hit keys on your keyboard until you find out which ones move the different cross hairs which direction... (wasd centers the orange crosshair (angle), ijkl centers the yellow (velocity) and green (position)) 5) center everything using those keys 6) accelerate toward your target with the h key, decelerate with n 7) dock slowly! Good luck! Ainamogel

I know what surprise _I_ am hoping for this weekend. My fingers are crossed, Navy! Thanks again for a "must-have" mod! Ainamogel

I don't know from planets or moons, but my favorite soda is purple Doctor Pepper and my favorite ice cream is green mint. Just sayin'. Deeelishus! Ainamogel

Hi there, Do you have any more information to share on this subject? I know it's been a while since your post that I have quoted, but if you'd be willing to share some sample code that renders the mapview camera I'd really appreciate it. I am specifically trying to render the mapview in my own screenTexture, but so far am just getting a black screen. Thanks muchly, Ainamogel

OK, I understand. It was the following two code snippets (from FlyingCamera.cs) that misled me: private readonly string[] knownCameraNames = { "GalaxyCamera", "Camera ScaledSpace", "Camera VE Underlay", // Environmental Visual Enhancements plugin camera "Camera VE Overlay", // Environmental Visual Enhancements plugin camera "Camera 01", "Camera 00", "FXCamera" }; and: if (cameraObject != null) { // ScaledSpace camera and it's derived cameras from Visual Enhancements mod are special - they don't move. if (i >= 3) { cameraObject.transform.position = cameraTransform.transform.position; } cameraObject.transform.rotation = rotation; cameraObject.fieldOfView = FOV; cameraObject.Render(); } Thanks for the feedback, Ainamogel

Hello all, RPM appears to contain code (in JSIFlyingCamera.cs) that is meant to allow it to display the map view camera's output. Does anyone here know how to get that working? Just putting the name of the map view camera into the config file in place of, say, the docking camera, did not work. Any help you all could offer would be greatly appreciated. Thanks, Ainamogel

Sad to say, the RPM code doesn't appear to work for the map camera. It nominally includes the map camera as a case, but doesn't render anything when that case is called. I guess there is something special about the PlanetariumCamera class that stops it from rendering the way a regular camera does, but I have no idea what yet. I am open to any suggestions, and will also ask for help on espernet and reddit, I guess. Thanks for any pointers you can offer, Ainamogel

Well, I haven't figured this out yet, but it looks like RasterPropMonitor contains code that basically does the job. Ainamogel

Hi all, Is there some good sample code for controlling and rendering the view from the map view camera? I would highly appreciate it if you could point me to some. Thanks, Ainamogel

Interesting! It is hard to say, but it could be true. Ainamogel - - - Updated - - - Not in this case. A really minimal craft: clampotron jr, chutes, command pod, fuel tank, spark engine. Ainamogel

1) Build whatever you want. Make the total mass a few tons or less. Put some fairings around it. 2) stick it on an Orange tank. 3) stick it on a half orange tank. 4) stick it on a Mainsail 5) drive it up to orbit. Voila, SSTO the easy way. Ha ha. (Perhaps Mainsails are a bit overpowered for the new atmosphere?) Sorry for the diversion from your actual, legitimate question. Ainamogel

I have KJR installed. I will try _disabling_ it. (Remember this is a very very light craft... might drift faster than a multi-ton station, naively.) I am not sure about the acceleration. I had the impression it was a constant angular velocity. Thanks, Ainamogel

Oh ho... I will look in the craft file to see how many C-o-T Jr.s are on there. Only one is visible, of course, on the nose of the command pod. The only electricity on it is the 50 stored in the command pod; nothing is using it at the time I am trying to dock, since everything is turned off. No solar panels. Thanks, Ainamogel

Blush... Note to self: read the thread next time. Ainamogel

Thanks for the help so far, all. The target craft has no probe core or Kerbalnaut on board, so I have no easy way to adjust the controls, such as turning SAS on or off or resetting the trim. I don't have FAR installed. I don't have a joystick installed. Is there an easy way to tell if part clipping is happening? I did not intentionally clip any parts or enable part clipping, but I don't know for a fact that it isn't happening. Finally, I already use DPAI (love it!) and have never felt the need for RCS aid; I just plonk the RCS thrusters down symmetrically around the CG and things work acceptably. I'm not having trouble controlling the active ship; it's the (nominally completely uncontrolled but nonetheless spinning) target ship that is causing the problems. Thanks very much; maybe this additional info will help debug the problem. I am afraid that capi3101 is correct, though, and it is just a random game bug. Thanks, Ainamogel