BudgetHedgehog

Rhetorical question, I think I know the answer. It appears fine on parts, but on the big flag in the VAB, it's stretched. Yes, it's not something as simple as 'my flag isn't circular', I assure you it is. I'm guessing the answer is that the aspect ratio of the big flag isn't the same as actual normal flags. Yeah, not a major issue, but it just looks so.. unprofessional, I guess. KSP 0.25 x86, completely stock except for this flag.

I'm more curious as to why it's linked to Tantares Space Tech.

My side of things - before dds and latest ATM, I was running at around 2.2Gb (this is with OpenGL and the aggressive ATM). After a bit of DDSing and updating ATM, I'm running at about 1.8Gb max. Not to mention load time has decreased severely - it's probably worth converting to DDS just for that, tbh. Like, I'm talking from about 10 minutes to less than, let me check real quick.. less than 5. It's certainly worth giving it a go.

As mentioned:

There's still the rest of the entire day to go, I wouldn't write it off just yet.

Huh, I do these exact AGs too. Everything else changes almost all the time, but those two are standard across the board for me.

I don't think anyone's mentioned it, but holding the Mod key down while attaching will disallow surface attachment and only attach things via the attach nodes. That will stop the 'things sticking halfway through the bay' problem. As for their usefulness, they're really only designed for probes or small service compartments. Send an ion probe to Moho from it, or stick in batteries, RTGs, life support, SAS and a few science thingies, whack it on a spaceplane and send it to take to Laythe. It's pretty useful for FAR players where putting something at the front or on the side/top of a plane would be less than ideal (like a part you're going to test, or science sensors etc.

Purely guessing here, but I think it's awarded on both. The internal progress tracking keeps itself up to date with whatever you do, so I'm guessing KXP either hooks into that or uses something similar. Also, again, guessing, but I'd imagine you get KXP every time a kerbal does something, no matter if it's been KXP'd before. Otherwise, you'd eventually end up with literally no way to train your new kerbals up as everywhere had already been visited before.

VABs gotta limit something, yo. I'm no coder, but I think part limit was easier to code than physical size limit and is a very rough workaround for it - excluding tiny science stuff, antennas and RCS blocks etc (I did say it was rough), the main parts you'll be adding are fuel tanks, engines, SRBs.. big bulky stuff, basically. 40 fuel tanks, 5 engines, a command pod and a couple SRBs are going to take up a lot of space anyway.. why code a phsyical size limit when you can code a part limit and get the same result? Granted, this doesn't take into account the tiny radial stuff I mentioned and the fact part clipping is allowed now, but yeah, it's rough. Honestly and seriously though, if anyone can show Squad a way to code physical size limits into the editors, I'm sure (or rather, I hope) they'd listen. Myself, I can live with part count limits (I apply handwavium + the first paragraph), but I can live with size limits as well and they seem to be more popular... EDIT: Personally, I think people are getting a bit Chicken Little about this whole thing.. It's been mentioned that the first upgrades for the buildings are so cheap, you already have enough money to buy them when you start a new career, the fact that you'll likely hit the weight limit before the part count limit to begin with, and the fact that you can make an orbit capable rocket with level 1 tech with less than 50 parts anyway. That will get you enough money to upgrade the VAB and it won't be a problem any more.

You're already limited by weight thanks to the launchpad/runway. Starting tier one can take, I think it's about 10 tons. You physically cannot launch anything heavier than the limit.

They're available to view at any time in game, but only if activated via the debug menu.

It was mentioned last week that contracts to visit certain biomes will be included in 0.90. I don't know if they're just like 'go plant a flag on Gillys Midlands' or 'transmit or recover scientific data from Dunas Poles', but yeah... I guess it'll be up to you to find the actual biomes though and that's where SCANsat/the debug menu comes in handy.

I like that idea - I was thinking of doing that before settling on this way, but your idea makes more sense. Gimme a minute, I'll get it sorted out.

OP has been updated with a review of the Squadcast just finished. Additionally, it is also below. Previous summaries are spoilered in the OP for your convenience. Summary for 2014-12-13 - Watch it here (Twitch) -Pretty slow one, Max is just finishing off his mission to Ike. I won't bore you with those details, that's not why you watch Squadcast However, the big news was the first showing of the features video Previous takes of the video ended up at like 22 minutes long which is great, but pretty boring. In other words, they're best left to the media team. The official features video was played to great reception - however, a couple UI elements have changed in the actual update compared to the video, just FYI. Most of the features I covered in last weeks write up. I don't want to write a review of features video as you can watch it for yourself. -Biome maps are available to view ingame, but only available in the debug menu. They're open to feedback on this though - if a large majority of players want that as an unlockable feature, it's doable. -Update is coming, and I quote, "soon ;^)" -Squad is doing their best to make saves compatible, but understandably they don't want to promise anything. AFATK though, no incompatibilities exist with old saves when upgrading. That said, the game has changed a lot so to get the full benefit from it, you should start over. -IVAs will be coming in beta, not in this update - they're great to have, but are a lot of work to make. A lot more work than making a whole new awesome part, for instance. But they're coming, don't worry. But for now, no new Mk3 IVA (I personally suggest using B9s HL IVA until then). -Cool stuff with some merch happening soon as well, will be very good and unique to every KSP players. More info later. Yeah, that's basically it.. as I said, pretty slow one, not much new, you should probably just watch the features video. All important info is there anyway. See you guys next week! See you guys next week!

Oh my, those look brilliant!

Hah, great timing! I'd just finished a trip out the the VLA in a new plane for testing, was thinking about posting a pic (then my control surfaces fell off and the last quicksave was days ago..). Thanks for the update!

Why? Toolbar already has a built in update checker.

OP has been updated with a link to the last Squadcast if you want to watch it for yourself. Thanks to Rowsdower for pointing me in the right direction, I'll try and get one up sooner next time around. Also in the OP is updated info for biomes and KXP. Kinda bummed I missed out on this first time round!

Well, in order to say whether you're installing them wrong, I'd need to know what you're already doing. Inside a mods zip file, there is usually a Gamedata folder. Drag the contents of that to your KSP Gamedata folder so you end up with 3 folders - Squad, NASAmission and the mod. First guess is that you're either running out of memory (those mods do eat a fair amount of RAM) or on OSX (replacing contents of Gamedata instead of merging).

Some SPP intakes and wings on there as well as KAX landing gear.

You can do this from the Tracking Station. Click the 'i' on the right when you have a craft selected.

There's LostInSpace which enables rescue contracts from places other than LKO. I've had to rescue guys from Minmus and Duna before. I say it enables it, because apparently, the code is already in the stock game, it just wasn't made available.

Google drive? If you want an answer to your problem, you're going to have to post it somewhere. What you could do to limit the size of the log is to enter the editor, go to windowed mode, alt tab to the existing output log, delete everything, alt tab back to the game and then cause the problem. The log should start writing from that moment on without 50 (?!) pages of loading and everything. Or you could try on a stock install with just MkIV and it's dependecies to try and replicate the bug. If you can, post the log (it will be short enough). If you can't, start adding in mods until you cause the bug (use the binary method: add in half of your current mods. If problem occurs, the cause is one of those mods. If bug doesn't occur, the problem is in the other half. Once you have the half that causes the bug, remove half of those and try to replicate. If problem occurs, the cause is one of those mods etc etc. You shouldn't need to restart KSP more than about 5 or 6 times, depending on the amount of mods you have now)

Emphasis mine. Bi propellant stock RCS works fine if it's just in one direction, like the Vernors. I don't know if ModuleRCSFX fixes this, would certainly be a great addition to it if it doesn't.

Try installing it properly. If you're sure it already is, could you post a screenshot of your Gamedata folder please?