troyfawkes

Nothing to contribute here but you guys are the coolest nerds ever and you're making it so hard to wait for RO et al to stabilize for 1.2

Since lots of people are here, all you steam people should 100% wait for update to finish downloading, right click on the game, go to properties->local files, and click "Verify Integrity of Game Cache...." Lots of weird update bugs happen due to weird steam issues.

100% this is just PC. The next console patch is not going to be 1.2 either since the consoles have huge approval processes and the development work has to go through a third party developer.

It makes sense, the game has been released for a while now. Maintaining a piece of software isn't nearly as exciting as creating a new one. That having been said, lots of folks love coming in and perfecting things (Nathan et al), or creating amazing new things to throw on top of a functional framework (think modders, or all the modders who are now working for Squad). Not surprised in the least over here.

Oh man, this made me want to capture an asteroid so bad... I'd love a 4 million ton asteroid in orbit. Apparently a 100m radius object made out of iron would weigh about 3.3 million tons, so they're not crazy off in weight at least, and that's assuming there's nothing heavier than iron in that rock (though it's also assuming there's nothing lighter).

Ah ok, I'll submit those on a case-by-case basis. The issue I was having with a couple scripts before I ripped out half my hair was a null result, but "has:node" etc. might resolve those. Hopefully those are new and I didn't just fail at going through the documentation :/

I'd love some way to prevent errors where I know they might crop up outside of my control, isNull or isValid etc. style checks would be a godsend. It just bothers me on a spiritual level to see a script crash due to something I could easily write a check for, but can't, and no way to refactor (alternately, "why do I have to refactor? This is inherent in every programming language..."). Then you just run the script again and hope that one possible issue doesn't occur and crash the script, or give up entirely on solving the problem.

If you're on windows (not sure how it works on other platforms): Create a shortcut Right click -> properties In the Shortcut tab in the Target box, make sure the path is wrapped in quotations and add -popupwindow afterwards. Should look like this. Hit apply and launch using the shortcut. Actually I think Steam lets you add launch flags too.

Have you tried setting the -popupwindow flag? That works flawlessly for me

Probably should be a sticky, but LOTS of people have a couple of problems that are easily resolved and have nothing to do with existing bugs in the game. If you have issues and are a steam user, check at least these two things: Are you still opted into betas? Steam -> Library -> KSP -> Properties -> Betas. Opt out (None). If your client starts a download, bingo, you're golden. Subtly broken install? Steam -> Library -> KSP -> Properties -> Local Files -> Verify Integrity of Game Cache. Completely fixed my crashes. My 2 cents.

(deleted)

Not sure if this is working as expected, but if you recover a simulated craft (why? I don't know, reflex I guess), the simulation doesn't end...

You may have some luck with this guy: http://www.articleformatter.com/ Strips out special characters without having to rewrite. Might help?

Re: Crashing bugs, this was the culprit for me: http://bugs.kerbalspaceprogram.com/issues/8241 I'm not sure if 1.1.1 fixed it, but it's at least a lot less noticeable for me.

@Camacha AFAIK nothing major has changed around reference frames. You can check what's upcoming here and in the issues tab: https://github.com/KSP-KOS/KOS/milestones If you've wrapped your head around it and have a good idea on how to implement it, I bet the devs would love to hear from you I personally hate the reference frame system too but I kind of just... gave up on it

Actually stationkeeping is the term for "Maybe require RCS ports on the satellite, and consume very small amounts of monoprop for adjustments." Stationkeeping is a big part of the Orbital Decay mod, and is intended to solve the problem you're having using the solution you've proposed

Question for the airplane lovers out there; are you guys using the keyboard for everything, joystick, or the mouse-steering mod that came out? Or what have you tried and your thoughts? I'm usually pretty good with a joystick, but flying/landing KSP planes has always been a bit of a hassle for me.

I appreciate all the decisions Squad has made around releases. Would love to see a quick patch for wheels, but right now the only issues I have for them are that they fishtail a bit too much and you can't clip them at all without causing shenanigans. You should have seen the amount of issues in the pre-release that they fixed. And beyond ANY other improvement Squad has ever made, the performance boost blows everything out of the water. Besides, I have to wait for mods to update and go through some bug-fixing before I really get into a campaign anyway <3 Squad!

@Dombi @Ohm Machre I've been having lots of mod-related crashes in 1.1, no stock crashes surprisingly. In Prerelease, deleting Physics.cfg fixed the first problems I was having. For Steam 1.1 release, "verifying integrity of game cache" fixed the second. I'm currently having crashing issues that are definitely tied to KW Rocketry Redux (in VAB), might be an interaction with Editor Extensions Redux (redux all the things!). If it's not those things, it might be worth playing another game for a couple more weeks (I might try to push it to a month!) and come back when everything is shiny and updated I wouldn't be surprised if New Horizons updates in pieces such that it won't be in a stable state for quite a while, but that's up to Kill Ashley's caffeine addiction and artistic lunacy

Might be a useful cross-over for the CTD from the VAB issue:

Just found this in the KW thread, looks like a very similar problem to what we're having: Will try stock + EER + KW and see if I can get CTDs when I get home. Probably not a coincidence though.

Yeah this exactly, no errors, not even a crash log. The other thing is it doesn't occur on stock only + EER, but the moment I re-add EER to my modded install I consistently CTD in VAB/SPH. It might be an interaction with another mod, so when I get home I'll throw up my mod list and try some combinations (don't have time to check them all unfortunately).

Anyone else have a CTD from Editor Extensions? I'm trying to figure out what exactly is causing it so I can give a useful report, but basically it's a CTD in the VAB/SPH when interacting with a part (generally picking up or deleting). I'll try pure stock w/ just Editor Extensions and check it like that, but it may also be a mod interaction..

Gah, I thought I was done with landing scripts. Now i need to try this :/

Awesome work KA!