No. RasterPropMonitor was designed to provide an interactive IVA experience. It can not be used to run "monitors" placed outside the craft, and it can not be used to draw on windows/overlays either. There are no plans to change that. The license for RPM is very open, so if someone wants to use RPM as a basis to make something similar for outside-of-IVA use, they're more than welcome to try.
RasterPropMonitor is intended to be a toolkit for IVA makers. It includes updated IVAs for most Squad pods, as well as a handful of other pods, but most of those IVAs were included to demonstrate some of the RPM features. If your favorite / preferred / currently-being-used IVA does not have an RPM-enhanced version, it's probably because no one has offered to share one that can be included in RPM. The developers of RPM have to prioritize their time, and maintaining and expanding the features of the plugin will almost always take priority over creating new IVAs.
I do not actively support CKAN versioning information. KerbalStuff has an option to automatically update CKAN when I post a new version, but that is the limit of my involvement with CKAN.
I make efforts to keep the RasterPropMonitor.version file accurate (which affects AVC, and maybe CKAN), but due to the way my release cycles work, there is always a chance that version info on GitHub will be changed before a release takes place.
TL;DR: The current version is always identified on the forum, KerbalStuff, and GitHub . Any other sources of versioning are secondary, and not authorative.
Certain buttons are reserved for future expansion, which happens pretty rapidly -- there's nothing assigned to them. It may also be that you're expecting the "up" and "down" buttons to switch pages. They don't actually work this way -- in the example package, every page corresponds to a single button, and cursor buttons only work on cursors and other similarly-behaving entities, which only certain pages actually have.
It's sort of an approximation of how actual MFDs work, though they typically use interfaces even less similar to what you might expect. Since version 0.13, you can switch pages in much more creative ways, but the default package does not make use of them.
- Make sure the installation is correct and everything is where it should be. The plugins will complain if they are not where they should be when possible, but not every time.
- Make sure that there is only one RasterPropMonitor.dll and that it is located at GameData/JSI/RasterPropMonitor/Plugins/RasterPropMonitor.dll -- several earlier third-party capsules distributed old versions incorrectly. They will fail to work in 0.23.
- Make sure that you're using the appropriate versions of every other plugin, in particular SCANsat and MechJeb -- failures of loading the interface DLLs for those can cause RasterPropMonitor to stop working, and there's little I can do about this. Blame Squad and be sure to eradicate MechJebRPM.dll if you do not use MechJeb / delete SCANsatRPM.dll if you do not use SCANsat.
If these steps do not solve your problem, please follow the steps in (this post on the forum)[http://forum.kerbalspaceprogram.com/threads/92229] and post the required information on the (RPM forum)[http://forum.kerbalspaceprogram.com/threads/117471] or open an issue on (GitHub)[https://github.com/Mihara/RasterPropMonitor/issues].
Update Active Texture Management to latest version and remember, for the future, that not all textures can be safely resized -- with any capsule that uses RasterPropMonitor, the problem may recur if you don't manage your Active Texture Management settings intelligently. "Aggressive" settings are called that for a reason.
To my knowledge it isn't -- I started developing it on a machine that is well over five years old and was very conscious of the framerate the whole time. But it might be a problem I have yet to bump into, and if you help me, I can probably fix it.
I want your KSP_Data/output_log.txt and as precise a description of what you were doing as possible.
RasterPropMonitor relies on SCANsat for mapping data. These are the precise satellites it means to have a connection to -- install it and launch some, they're quite a lot of fun. It's one of those things that makes probes more than just a practice launch.
This is a Kethane problem. Update to Kethane 0.8.4 or newer.
They are the traditional symbols for ascending node and descending node respectively. See Wikipedia page which also nicely explains what those node things are. :)
Basically, they're points in which you want to burn to change your orbit inclination optimally.
RasterPropMonitor is more of an IVA makers toolkit than a standalone product, I spend most of my time programming new things for the monitors to show, but barely have the energy left to arrange it for actual presentation. My own implementation is a few generations behind. Check the list of variables and the documentation on page file syntax, it's quite possible what you want is already there, just isn't presented to the user in my own implementation yet. Customize your monitors and share the results -- if you make nice pages, I'll be happy to include them in the distribution.
Not yet. While it is in the plans, there is the considerable question of how to make a menu-based maneuver node editor with an interface that doesn't suck.
You can't. String.Format is a (rather basic by itself) string layout language, but it is not a mathematical expression processor. Tags are a screen layout language, but they are not a mathematical expression processor either.
While there have been calls for implementing one, that's one of the things I'm very wary of doing at all -- it's not particularly hard to do, but it's also all too easy to produce a Turing Tarpit, unwieldy to use and slowing the whole thing down, I've spent much of my life fighting these things and I don't want to create another one. If it's to be a programming language, I can at least make sure it will be a real one and make it suck in modules that will get locally compiled from a domain-specific Boo variant or something to that effect. It will take a while for me to write that, though, but I'm pretty sure eventually I will.
In the meantime, if you want a variable that is derived from existing variables, there's no problem at all just adding one -- give me a list of what you actually want. I'll readily add anything provided it doesn't require writing more than a page of code to do it, and I will seriously consider things that will so require.