ManTrelk

Congrats to the team at Squad! There was frankly a lot of doubt about this release in the community, but you pulled it off without a hitch. Spectacular!

Not at all. But the concerns have been voiced. This topic has been debated endlessly since the announcement. What I'm saying is I think it's time to accept the inevitable and get behind it as much as possible, to make the release of this epic game as positive as it can be.

I think most of us would prefer another beta release before 1.0. Hell, I'd be happy for squad to simply puh the experimental branch to stable and let us do a few weeks testing of the new systems before release, if it were possible. That said, I think it's pretty clear they're dead set to go ahead as planned and make the next release 1.0. Given that reality, I think it's time we stopped criticising the move and got behind Squad. We should celebrate the move out of early access. This is a fantastic game and development has been a wild ride. Let's give Squad the support they've earned and help make this event as happy and successful as possible.

Reverting to launch or VAB from an active ship often causes the game to do this: ksp.log Modlist Appreciate any help I can get... This bug has made my game unplayable and I have a feeling it's corrupted my save.

Okay. Well, I won't waste your time with that. I might post in the mod support forum later. I'm guessing the problem involved kOS in some way though, because it's only started appearing since I've installed the mod. Any advice on the "Tried to push infinity to stack" error? It doesn't seem to affect anything, it's just annoying.

Hmm, okay. Thanks for the advice. I don't think that's the issue though, because I put ROUND in there to try and fix it. The error was occurring before ROUND was in the code. Will this update add support for user defined functions? Because I cannot WAIT for that. Now that I've done a bit more testing. I'm not sure that the line I pointed to was actually the problem - it's hard to say. The error only occurs *most* of the time I run this script, so I'm not sure if it's just coincidence that it disappears when I remove that line. There's also the fact that when the error *doesn't* appear, reverting my ship seems to break KSP. I get a screen with no ship visible, only the skybox, and no velocity. And I can't revert. I'm 90% sure it's related to kOS. Maybe it's a problem elsewhere in my script which is only manifesting itself when it gets to that trigger? I could post my whole script if someone wants to spend their time and hunt for the bug (It's my first script though, so I'd rather not embarrass myself ).

Small question, why does result in the error "Tried to push infinity to the stack?" The problem line is SET stagetime TO ROUND(TIME:SECONDS).

:| Oh? I wasn't expecting that answer. That does sound like my problem though. Why isn't this a bigger deal? I'd have thought pretty much everyone would be using that command. It happens with any design I make. A Mk1 command pod as root, kOS core, a 1m tank and an LV-909. Or one of my heavy lifters. Any craft that locks steering as it accelerates off the launchpad (or just above the launchpad, or on the launchpad) has this problem.

Since I didn't get a clear answer last time: if I use a command to to change compass heading like LOCK STEERING TO HEADING(90,pitch) should my vessel tilt off axis when changing its compass heading to 90? Or should it roll smoothly along its longitudinal axis? Right now in my game giving any basic direction commands using LOCK causes the vehicle to pretty much lose control a few meters above the launchpad, making kOS unusable. Is it a bug on my end, or with kOS?

Thanks for the reply. I don't really mind changing the roll if the ship does it smoothly without deviating off its roll axis. Just to clarify, is that an artefact of UnityEngine or were you referring to the 360 degree roll I experience? That first bit of code you posted keeps the roll steady, but locks the ship to UP. Is there a way to get one without the other? Also, is gt0 an undefined variable in the until loop?

I'm so confused... New to kOS here. The command LOCK STEERING TO R(0,0,0) should keep the ship pointing in whatever direction it's currently facing, right? No rotation about its axis or anything as a result of that command? The command LOCK STEERING TO HEADING (SHIP:FACING:ROLL,90) should also result in no change to roll, right? Why does it make my ship do a 360 degree roll? How can I avoid this and lock steering without changing my ship's roll?? More to the point though, is something wrong with how kOS handles changes to a ship's roll value? My vessels seem to shift on other axes when I give it a command to change its roll (which is why I'm trying get it to maintain its current roll...).

HA! Like I'm falling for that one!

SVlad, I had the same problem. If you have a save from before the upgrade completed, staying in KSC view while it completes will upgrade the building properly.

I'm having the same problem as Evi - LOCK STEERING causes the craft to oscillate around the target orientation. I don't have mechjeb installed, though.

Kerbal Crush Saga? Really??

Yeah, some of them were at level two. I noticed it because Jeb suddenly didn't have access to the more advanced SAS options. deleting the .dll undid the problem. Big fan of KCT by the way it really completes the career mode IMO and construction time should be a stock feature.

So, I added the Field Experience .dll to my GameData folder, and it's reset all of my currently active Kerbals' skill level to 1 (not 0). That's not supposed to happen, right? I'm on Linux x64.

Okay, thanks. I'm glad I don't need to go bughunting.

So I guess some are left in there because they unlock further nodes? I have pretty much all of your mods, big fan will that lead to some empty nodes, like (off the top of my head) Improved Nuclear Propulsion?

Are there supposed to be empty nodes in my career tech tree? Sorry if this has been answered before, I looked but can't find any reference to it.

Is this the right place to put this? It's my first thread here. Anyway, I done screwed up. My game crashed while my favourite pilot was soaring over the Mun's surface in EVA mode, and when I reloaded the game, by the time i could get back to flight mode he was missing from the tracking station. I loaded up the lander thinking it hadn't saved for a while, and naturally the first thing I did after that was press f5 (stupid). Obviously the game had saved over Bobvin's death and I'd just erased my last backup. So my question is this: Is there a way to resurrect my poor pilot with his skills intact, and preferably to put him back in the lander that's now sitting cold and dead on the mun? I'm no stranger to save file editing, so if it can be done, please let me know. I'm the kind of person who will throw out my entire save file over this kind of screwup, so any help would be appreciated.

I had exactly the same problem. I even got ike contracts before mun. I solved it by completing all my accepted contracts (this is important) and then going into the debug menu and finding the 'clear all contracts' button. This refreshes the explore contracts that are offered, as well as refreshing all the others. I kept doing this until the mun explore mission appeared.

Is this likely to cause issues if I want to upgrade to the official update later on?

Can't wait for this release so I can finally jump into 0.25!

1) I think we owe him an apology for the community's crazy, frothing-at-the-mouth reaction. That is what's caused this whole issue. People coming here to rabidly defend their favorite developer. Why would we apologise to him for his actions? Makes no sense whatsoever. 2) You're blaming Cerebrate for stupid_chris deciding to spit the dummy? I'm sorry, in my world, adults are responsible for their own actions. 3) I don't know exactly what the circumstances behind Cerebrate's fork were, but in the software development community, it's agreed upon that a) you have no right to be upset if someone uses your code within the bounds set by your license, and you can't update your license and expect it to be retroactive. What stupid_chris did was taken as a spit in the face by many, and I imagine that includes Cerebrate. There's no justification for arbitrarily restricting how people use your code, and if it has an open license the of course people are going to compile their own versions to remove said spit-in-the-face. As a software developer you have to get used to the fact that 90% of bug reports will be bogus. That's just how it works, and these guys should be happy they're lucky enough to have a community which will take the time to help them with development. Implementing arbitrary restrictions is not the way to combat this issue. All it achieved in this case was to alienate a significant portion of fans of this mod.