Lisias

No. But it's way worse launching without the needed requirements met. Doing the right thing is not the same as doing things right. Sometimes, you just can't win the battle. All you can do is to choose the less painful/costly way to lose the battle, and live to fight another day. So, yeah. It's a "the right thing" to be delayed if the launch is doomed (see Challenge). Perhaps setting up the launch date was a mistake, but it depends on what really happened - a last minute update on the console firmware would demand a full recertification (see Anthem problems on PS4), and this is completely unforeseeable . Real life talks louder than any reasoning.

Non Disclosure Agreement. Essentially, "you want to work with us? Sign this agreement where you will agree on not talking anything we don't want you to talk about the work, otherwise we will sue your pants off"

Not only that. A security update on the Console's firmware can change the expected behaviour of some internal functions, and things that used to work yesterday doesn't work anymore today. And you are not allowed to talk about due the NDA. Do you are aware of that stunt from Anthem on PS4? From the point of view from someone that wrote embedded firmware for the automobile industry, I see some resemblance to a firmware bug acting over a programmer failure to cope with some small security feature (being that forgetting to hit the feature, or hitting it too much), followed by a fail-safe being trigger happy. This is a Joint Effort Task - you just can't get yourself on such magnificent mess without a lot of help. My guess? Since the problem appears to affect only Consoles with SSD, I think the developer was using the disk access routines to calm-down a watchdog (perhaps something designed by Sony to prevent a game crashing while writing the HD, what would screw up everything?). With SSDs being hugely faster, the routine kicked the watch-dog too fast, and triggered a response from it. Later, a fail-safe prevented the Console to turn on, as the watch-dog told him that someone had crashed while writing to the HD and so its better to abort the boot to do not cause more damages (perhaps in an attempt to preserve the HD contents on disk crashes?). If I'm right (and this is a big IF - it can be thousands of different things), BioWare and E.A. are just not allowed to talk anything about the subject. They are not allowed even to tell us it wasn't their fault, as this would imply it was Sony's fault - and the NDA forbids them to pinpoint Console flaws to the public. Since Squad are usually open about their mistakes, I think it's reasonable to assume these ones can be related to third-parties where NDA applies.

Standard Procedure. When you develop for Consoles, you sigh some very scaring NDAs, severely restricting what you can say to anyone else. Keeping the communications at a minimum is, usually, the safest way to prevent telling people something you are not allowed - what could ending in you paying some very harsh fines. You can break a small game studio with only one.

Give a look on the Advanced Fly By Wire mod. I'm pretty sure you will find it useful to your needs.

No. It needs to be way faster to be classified as Slow. I forgot the anti-alias on, and this on my MacPotato is way expensive - shared memory on GPU and CPU is the main issue here, as when the GPU is anti-aliasing the frame, the CPU cannot access the memory. I usually hack the physics engine to extend a "computer second" to many real life seconds while recording videos, but since this was just a fast test run, I didn't bored. But forgot the anti-alias on. (make no mistake, my machine is terrible - it just happens that it's yet more terrible on the video. )

3! (But my entry will be probably overruled, as I twisted the rules. Sorry, but I'm not exactly sorry - it was way more fun this way. Give it a try anyway, please, just to see how I did!) This is a two stage dragster, as (kind of) allowed here. Instructions: Activate SAS Full Throttle Make sure you have breaks disabled Stage! When fuel is empty, Stage again! Use the cockpit Wheel to keep the nose up and the cockpit head up on… "touchdown". Success!!! Acceptance criteria (sort of ): Stock (check) No drones, a Kerbal must drive. (check) All races will be driven by Jeb, he will be our "Stig", so make sure you give him instructions if you have any. (check) Two stages craft allowed (well…. ) Additionally: The Kerbal survived, The craft's last stage survived. Unscratched The craft 'parked' on the runway. Craft: https://kerbalx.com/Lisias/Triops-Dragster-Challenge-Mark-0 Test Run:

A = People are Mad B = When Release is delayed C = When Release is bugged A = B v C But since Releases are always bugged or delayed, B v C == True. So A = True Ergo: People are Mad. There's no point on arguing about Logic Tautologies.

It's something as asking who's is better, Jerry Lewis or Carl Sagan. Lowne is way more fun on the videos (who don't like craziness?), Manley is usually way more interesting on tech and science background (at least, when he was not enjoying some beverages while broadcasting - when then Lowne have some serious competition! ). If I had to choose only one of them, I would end up in a really, really, really bad mood.

Dude, last time I estimated a deadline for TweakScale, I borked so beautifully that my ears got burning for 3 months. The Welding tool is usable for 1.3 parts for sure (IIRC there was just one VARIANTPARTMODULE part on 1.4, and I missed it completely), and I don't know how this will behave on 1.6.1, as since December, all my sparing time for KSP is for TweakScale (and for good reasons). The good notice about this is that what I learnt form this stunt is directly useable on the Welding tool, so yeah, things will work for sure. Someday. On the short term, I remember someone using 1.5 for weldings and then moving things to 1.6 (or using 1.4 and moving to 1.5? I don't recall). As long you don't use any parts with new modules, everything will be ok. And by using a older KSP for welding, that parts will be eligible to be used on newer KSPs (as long they didn't changed the used textures, but you can always manually copy them back - or even create a MM patch to hot fix them, what I think would be a better solution!). If it can be of any comfort, I'm really using all my spare time on it - I am not really playing for weeks. Real Life is a Sun on a Beach sometimes.

I could not said it better, sir. I wish I could "react" to your post twice.

But you are still alowed to use the software's new versions by not accepting the EULA? Around here, such clausule are "null and void", I.e., I can accept the new EULA because that clausule is dead letter. So I still have the right to use the new software (version). In some other (very rare, usually due illegalities) situations, the whole contract is dead letter - in such (hypothetical) case, my right to use the software would be nullified as well. So I could be prosecuted for piracy by using the software associated to such contract. Since my advice to inform yourself before taking something for granted. And this is not about TTI, but to any contract you take with a foreigner. Humm... Check if TTI has a office in your country. This changes everything.

The ones they didn't had time to test until the new Release time. The problem is not the bug being found - this is proof that they are doing their job right. The release date apparently was set on a perhaps too optimistic mindset. But, frankly, for a sofware being deployed electronically and without the need of a supply chain that would be allocated to the logistics (and so would be earning money by doing nothing), this is not really a problem. It's frustrating, but that's all the real problem they will have to cope: frustrated users. Angry customers are way worse.

Good. Now research about how your Country handles the New York Convention. Yes. I'm being picky, but Law is pickier. I once saw an European sueing (and winning) an American for a stupidly the latter committed on the Internet against the former over a clausule on the former's Country Law. So the inverse is also possible. Keep this in mind: the inverse is also possible: you can be sued by something you did to an American on the Internet that the American laws say you can't. This is the essence of the New York Convention. Be sure your Country's laws about the New York Convention enforces your local law on foreign affairs. And then, just then, you can rest assured about your statement. Remember: Americans are not subjected to your Country Laws, and you were not forced to take affairs with an American Company, you choose to it. Also, do a quick research about how your Country handles Microsoft (as much of these stunts were tried first by them) and check for any precedence. You can bet your SAS I did on mine, and it's not so good as I wish. All I could manage is to know that it's not so good for "them" too.

Not, it's not. I want to share a small history to you guys, fresh on, right from the trenches. Client needed a feature urgently. A feature that wasn't working correctly because it wasn't implemented, besides them giving us the "green flag" and accepted the delivery (the whole product was rushed into production, and we borked on that feature - we just had forgotten about, we gave them a release in 25% of the time we are used to do normally!). Ok. Both parties borked on this one,. But guess what? They really needed that feature, as they already put that in production and they had a whole parking lot of trucks waiting for the permission that the feature was expected to get. Well, we tried to argue that making a hot deploy like that with fresh code was dangerous, etc, etc, etc. But they told us that they were loosing money, and it was best for them to avoid another day of losses. Great. We worked in a rush, and managed to get that feature working fine to the end of the day. The deploy was done 45 minutes before the deadline when the trucks would had to sleep another night on the parking lot. Success! Or near it. Next day I was waked by a phone call. Do you know that feature we rushed into production? It was working fine. But it was the only thing working fine - all the rest were kaput. Just like that. It was a small, idiotic, mistake on a critical code that I had to change in order to shove the new feature on the system - but since we were in a rush to meet an almost impossible deadline, we didn't had the time to run any tests but the one for the feature needed. But they only lose a morning, and the piled tasks could be executed on lunch time. But yet… That caused some unneeded trouble for a lot of people. The bottom line? Pressure only works when the problem is laziness. You can't push more pressure on a already pressured system without blowing things.

Because a Console release costs money. Some serious money, as I had read about (your mileage may vary, but I don't believe "Indie game" is applicable to KSP anymore since TTI has bought it). If its unavoidable to have people complaining on you, at least do it in the less expensive way. ;-)

A picture is worth a thousand words.

Just to be sure. I'd tried the same thing too, but I was on sandbox and just realized it after wasting a lot of time. What I did managed to do on career (after I finally realized I could do it only in Carrer - manuals? Who read manuals?) is to copy & paste the experience from another Kerbal into the one I want to mangle. Essentially, once a Kerbal gets a experience, I create one,.rename it to reflect the experience and paste it there. So I have a reference when I need another one with that experience. I found trying to Forge a experience from scratch too tricky.

It's a sandbox game?

Citation needed, please. Civil Law also have loop-holes.

ReStock will not be needed, as it doesn't add new parts. RsStock+ on the other hand, has them - but something gone wrong when I tried it (not sure what, it can be even unrelated to TweakScale), so it's on the Queue waiting to be worked out. But since you are the first to ask it, you can follow the works here. To tell you the true, I'm waiting 1.7 to add the new parts and test the existent ones, so I kind of dragged my feet on TweakScale this week. Everything will be tested again, just to be sure I made that fail-safes right this time.

Thanks! I will test them too, as time allows! (atypically busy week, thanks God not all of my weeks is like this ) https://github.com/net-lisias-ksp/TweakScale/issues/32

I agree. We ruled the DLLs out. Things changed again in a interesting way, apparently: 37573 MB paging file [15752 MB free]. 134217728 MB user address space [134198600 MB free]. Read from location ef3e2008 caused an access violation. The crash is happening again from that "upper memory", where C/C++ data lives and where, probably, CIL code is (as it's data for the C/C++ virtual machine program - sorry being repetitive, but there're more people reading this). However, I found this on your logs too: <RI> Initializing input. XInput1_3.dll not found. Trying XInput9_1_0.dll instead... <RI> Input initialized. <RI> Initialized touch support. -- CUT -- CUT -- CUT -- CUT -- CUT -- CUT -- CUT -- CUT -- CUT -- CUT -- CUT -- C:\WINDOWS\SYSTEM32\xinput9_1_0.dll:xinput9_1_0.dll (00007FFF66430000), size: 28672 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\xinput9_1_0.dll', fileVersion: 10.0.17134.1 Stubborn code, this thingy. It appears to be committed to crash KSP no matter what. An hypothetical next step is obvious, restart the stunt fest on xinput9_1_0.dll .But, frankly? In the next few days 1.7 is will be on the wild, and I bet you are getting pretty "liquided" with all this thing. I have some, but all bad ones. Sooner or later I will shove a new GPU card on my Windows rig, and let me tell you - I will see the bottom of this. What makes me a "waterfall" of angriness on the subject is that this damned problem doesn't happens on MacOS (and I have no knowledge of the problem on Linux neither). This stunt is happening on Windows, thats just the flagship version of any game - and, as we could see from my previous post, this is not plaguing only KSP (and, who would have thought, Unity appears to be innocent on this one? That would be a new!). My pleasure. Let us know if things works fine on 1.7. Best of luck!

I could not had done better. And, yes… It's a real patent! The guy even strapped a solid booster! I LOVE IT! https://patents.google.com/patent/US6817579 (tweet to the image author: https://twitter.com/Zephyr164/status/1104719928081276929)