amorymeltzer

This seems pretty cool!

I would imagine they're quite busy at the moment. US holiday mere days after a major update - servers are probably getting pounded! I'm not even playing the game until 1.1 and I've already downloaded around 20 mods from the site; imagine what everyone else here is doing...

With a mindset like that, you could run for office!

Excellent!

You're correct that it doesn't need to be in that folder. Your setup is totally fine, it was a lazy regex that didn't account for some windows formatting in your persistent.sfs. I uploaded a quick bug fix - https://github.com/Amorymeltzer/ksp/archive/v0.97.3.zip - which should work!

Hey oab2, sorry it's not running right! It should work just fine on 1.0.4 so can you upload your files so I can take a look at what might be happening? At the very least I'd like to check your persistent.sfs and ScienceDefs.cfg, but it wouldn't hurt to have the others as well. Thanks so much.

If you want to use git, you could simply automate this - a rudimentary bash script could take care of all the the adding and committing. Personally, I just backup persistent.sfs after I quit, placed into dropbox with the time and date. Simple script, run it when I'm done, no thinking. Here's the source, also copied below: #!/usr/bin/env bash # ksp_backup_files.sh by Amory Meltzer # Simply copy pilot files to a save directory dateandtime=$(date +%Y.%m.%d_%H%M%S) folderpath='/Users/Amory/Dropbox/KSPstuff/pilot_backups/'$dateandtime ksppath='/Applications/KSP_osx' userlist=$(ls -1 $ksppath'/saves' | grep -v scenarios | grep -v training) mkdir "$folderpath" for i in $userlist do cp "$ksppath/saves/$i/persistent.sfs" "$folderpath/$i.persistent.sfs" done ls -lFGh "$folderpath/"

Minor tweak - have the SCAN agency only offer scanning contracts. Rescuing Kerbals seems outside their stated purview...

👠(too short)

Danke!

Awesome update! Psyched about the contracts integration, I know you've were super helpful enabling them in the first place. What will happen to those of us using his contract pack already, will it all switch over nicely, or should we grab some new contracts for already-scanned planets?

Thanks for the work! And making this happen!

Everyone has summed it up pretty well here. I use both because I like MJ for some and KER for others --> porquenolosdos.jpg

Gonna be honest, the one time that happened I didn't even think about that. Pod + Flea + Crash = No longer on roster. Reputation is for suckers.

You should use the Tree Toppler mod. I get the same effect in the F12 menu, which is kind of disappointing. Maybe you should change the subject category, but I'm on a Mac so it's probably system-neutral.

THAT would explain the "HighlightingSystem : Edge Highlighting requires AA to work!" warnings I get throughout KSP.log - thanks!

I always used the old one as an idea-generator when I was feeling uncreative, and usually played around with them a bit. Hell, half the time I didn't use the name, but used ones inspired by it.

You want Tree Toppler. It does EXACTLY that. AND MORE! Debug menu never worked for me either. ETA: Give rep thattaway ↓

0.2 looks pretty sweet!

Oh hell yeah baby

Can someone shed a little more light on this? From some searching it seems Unity does allow for 64bit on Mac but for KSP it's a POS, even worse than windows. And that won't change with 5 or 5.1 or 5.2? Is that right?

It's the Field Research contract pack, by the same author, and yes, you are mistaken. On Kerbin, there are plenty lakes in grasslands which count as "splashed in grasslands". You can, in fact, get a "splashed down" and a "landed" in every major Kerbin biome (ie NOT the KSC ones). If you read the contract text that everyone ignores, you'll notice that it even alerts you to the fact that this is rare science, and gives you a few waypoint locations where they can be found. It's the most genius part of the contract pack, I think.

I think this is the way to go. Make some interesting and variable scatters, so that not every grasslands or highlands looks the same. They can be functionally the same but as long as they look different here 'n there, they'll be fun to get to. They can even be hardcoded (I would imagine) so that they don't change up on you (it would be weird to have trees and ice floes move around).

Well, I like GH, but I'll reply here so it's easier for others to chime in. tl;dr - I vote change the wording. I actually think this contract needs a slight rework. The point is to force the user to somehow "check out" the planet/moon beforehand, whether by SCANsat or the stock ISRU-scanner by: - Probe - Orbit - Scan So, why the need to re-orbit Kerbin? That didn't make sense to me, especially since, in theory, the antenna would relay all the information. I think it makes perfect sense to just need a probe doing some scanning, so I think the wording can just be changed and it's alright for it to be a pre-existing scanner. One thing you could include (more work, though, for you and the users) is to require that the probe has actually transmitted some sort of scanning data. I'm no ContractConfigurator whiz, but is it possible to check to see if the probe sent back scanning data? If so, that could be a good middle ground. So, I can use my SCANsat probe already around Minmus, but I have to actually send back data to Kerbin. You'd have to allow it to just auto-process if scanning data is maxed-out, though, since ISRU is all or nothing; if someone isn't running SCANsat, and has already ISRU-scanned Minmus, they need a way to be able to trigger it. So, maybe this isn't such a good fix. I suppose the logical work-around is to offer some scanning contract if there is something they haven't scanned, but if they've maxed out ISRU or SCANsat, screw it just let 'em build the base there without the first basescan contract. Is that possible? I just made your life harder, sorry!

Word. Raised PR. Also, much less importantly, sometimes the photog is a "she" but the contract uses "he." Raised issue #2.