yum

Thanks! I did not know that, I don't use MM for anything else. Sounds like an excuse for me to go mucking about in the source, maybe see if it can be triggered when the database is reloaded.

The pictures at the end of the album in the first post explain how to do this. But I'll take a shot at quick instructions. First, you need the texture files, and to be able to open them in photoshop (or at least get a new file started with matching dimensions). I use the MBM converter for unity for this (it's on the forum somewhere). Once you've got them open, it is easy. Make a new layer, fill it in with black (may want to set layer opacity here so you can see what you're working on.) In the red channel, select the area you want to have the base coat and fill it in. Repeat for the other two channels, making two new coats. Set layers green/blue to additive. Save as png and remove file extension (mypart_Paint) Put into KerbPaint folder with the other _Paint files. Add to cfg file (KerbPaint.cfg or new cfg file). (You'll have to experiment with types of shaders/deep replace and the other options here to get it to work nicely for you). Side note: @Texel - When I reload all database from the debug menu, KerbPaint no longer functions (no colors, 'P' does nothing) - until I quit KSP and reopen it. Anyone else have this problem?

With the new update, you can no longer have single unmatched brackets in a print statement. Heh took me a little bit to figure out what was wrong, while deleting the periods from my curly brackets. It throws the bracket matching error. To recreate the bug, simply print "(". However, print "( )". works just fine. As an aside, I watched the update video, and I haven't yet tested this myself, but if I am understanding this right, alt:radar will return the same value as altitude now, instead of -1. Does it work to a higher altitude than it did before? More importantly, alt:radar will return sea level when over water now. I understand that this type of simplification will be beneficial to some users (they don't have to handle errors), but I'd just like to mention that it does limit what we are capable of doing - personally I'd rather have more raw data available and have to account for errors. In any case, I'm loving kOS, thanks for all the hard work.

@deadshot462 "\Kerbal Space Program\GameData\kOS" "\Kerbal Space Program\Plugins\PluginData\Archive"

Try the runway maybe? Nice, self modifying code, I hadn't thought of that! EDIT: Does that launchpad obliterator mod still exist?

@check Yeah that would work for most programs, but my program calculates ground elevation and is dependent on both altitude - (alt:radar - shipHeight) where shipHeight is just alt:radar when the ship is on the ground. For now I'll just pretend it's a real LIDAR without a large range, and keep my altitude low when scanning.

@check It doesn't seem to be consistent however. Sometimes I make it to 9000m before it freaks out (just flying around KSC). But you're right, definitely doesn't work over deep water. Is there a reason why it fails? If we had more range, and could get elevation for arbitrary lat-long values, we'd have a working mapsat and could find ideal landing zones (low slope). ( hi from toronto! )

Seems to be working for me here. //logger clearscreen. print "Attempting log" at (0,15). set toLog to "X,Y,Z". set difference to 0.001. set lastLat to latitude + difference + difference. set lastLong to longitude + difference + difference. set shipHeight to 1.27. //input your ships height (alt:radar while on ground) until 0 { set curAlt to altitude - (alt:radar - shipHeight). //should have named this ground elevation! if alt:radar = -1 { set curAlt to 0. }. //for when alt:radar bugs out...not sure why set curLat to latitude. set curLong to longitude. print altitude + " - (" + alt:radar + " - " + shipHeight + ") " at (15,3). print "ELEVATION = " + curAlt + " m " at (0,4). print "LAT = " + curLat + " degrees " at (0,6). print "LONG = " + curLong + " degrees " at (0,7). if abs(lastLat - curLat) > difference or abs(lastLong - curLong) > difference { set toLog to curLat + "," + curLong + "," + curAlt. print "Logging Active " at (0,15). print "toLog = " + toLog + " " at (0,9). log toLog to logfile. print "Last log print: " + missiontime + " " at (0,20). set lastLat to curLat. set lastLong to curLong. }. wait 0.5. }. Just log variable to filename. If we had arrays and could read from the log...things could get more interesting. Side note - alt:radar returns -1 seemingly randomly, anyone know why?