Lisias

Ugh. Appears to be something new. The latest TweakScale gets rid of the duplicates, so at least in theory, you are facing something new. The newest commits (se the orthodox branch) are patches only. You can fetch them and test them on your installment and check what happens. That weird problem I described by last just vanished. The glitch happened on my playing installment, and the dud SAS here forgot it next day and updated some Add'Ons, and now I can't reproduce it anymore. At least this hints that by updating to the newest versions of the Add'Ons the problem goes away. but i'm unrest about it, I want to know what happened. I would like to see your KSP.Log to compare with mine. This can help us to narrow down the glitch's source! — — — — — Guys, I found some Kraken Food between TweakScale and Kerbal Animation Suite. https://github.com/net-lisias-ksp/TweakScale/issues/29 At the moment, there's no other workaround but to do not install both Add'Ons at the same time. It's not clear if it's a TweakScale issue, KerbalAnimationSuite one, or if there's something else inducing the borking by side effect. More news on it ASAP.

Please, Dear God. Not on Friday, I have a deploy schedule and it's hard to deploy things while playing KSP!

Now you pulled a good argument from your hat. "Look, you *need* to add some clouds and novelties to the game, as the present Look&Fell are making you look as a kid's toy". I'm not exactly dissatisfied with the current Look&Feel - it allows the game to run on my MacPotato, and since it's currently the only gaming machine I have, I'm counting my blessings. But yet, I already bought the game, and Squad needs to convince new players to buy it in order to keep their revenue flowing. So, as long such GPU intensive thingies can be disabled so I can keep playing for some more time on my MacPotato, yeah, I can agree with you now. And yet, KSP "looks like a child's game". I can see your point now, but look both sides of the coin: a the same time they need new gamers buying the thing, they can't make their current user base angry - or they will face a backslash, and the fallout could cost them more than any new incoming they would get on the stunt. They need to measure the consequences with prudence. This is probably one of that weird situations in which two opposite points of view can be simultaneously right (or simultaneously wrong!). Hard nut to crack, if you ask me.

KAX uses FSplanePropellerSpinner, FSswitchEngineThrustTransform and ModuleAlternator. The only novelty is ModuleEnginesFX and EFFECTS nodes (that, frankly, I'm rolling back to FSEngineSounds as they behaves better with it). I have KAX historical releases since 2.0, and this part had born on KAX 2.3.4 (KSP 0.90). Problem is… Nothing had change significantly on the thrusting model. But your hint leaded me to FSswitchEngineThrustTransform: MODULE { name = FSswitchEngineThrustTransform defaultTTName = thrustTransform alternateTTName = alternateThrustTransform useNamedAlternate = 1 So I think I had to search for the problem on Firespitter itself anyway. KSP 1.3 appears to have break this. Problem is… This is already an stablished behaviour for KAX since 1.4.0. I'm unsure about the decision I have to make - to break (new) expected behaviour, or rollback it to the previous one (assuming I can fix Firespitter).

I would gladly send some of them to take a ride with the Musk's Starman if I could.

I will work on it, thanks - it's a nice idea. It may take a little due some other pressing issues (mainly on Real Life), but I will get into it. https://github.com/net-lisias-ksp/KAX/issues/3

I'll change my name to Nostradamus. Client decided to use a feature still not homologated . We never tested that feature, because we need testing data - but testing data is not available (or possible), as a lot of things depends from third parties that don't provide us with testing data. So we had to make a controlled, dry run with live data as homologation. But the client decided he would risk it. (sigh) Aftermath: If I was a surgeon, I would had made a heart transplant on a pilot. With the guy piloting the Kraken damned aircraft. 8 trucks full of merchandising on the parking. Some of my hair got gray today - replacing some of the fallen gray hair. — — — — THEY DID IT AGAIN

Forget about. This thing is so old than it doesn't use it yet. I really need to update this thing sooner or later. Please backup your savegames!

There's an unusual situation in which a (third party) DLL borks on loading that halts MM. The funny messages are still shown in the screen, but the progress bar (and the text where the current action is being displayed) halts permanently. It's a third party DLL borking. You delete or fix that DLL, and things work again. KSP.log pinpoints the problem, it's usually on the last line of the file as everything halts. If you installed Hyperspace you need to close KSP before taking the LOG , as Hyperspace makes writing to the log more "chunky" - it waits for way more data to fill a buffer before writing something to disk, and closing KSP flushes that buffer.

Unzip the thing on your KSP's root. The GameData goes to KSP\GameData , and the Plugindata to KSP\PluginData . The files ends up in the correct place by doing that. Don't forget to install KSPe too - it's a hard dependency. And yeah… I need to update the thing, it's still using my first attempt on packagings. (but this will take some time yet, I'm overwhelmed by now…) Oh, and the thing is NON-MAINSTREAM. Even the naming is non-standard, it should be just "/L" and that's it. (the current maintainer is welcome to merge back anything he likes)

I'm working on a nasty bug since October/2018 on TweakScale. The problem is essentially "solved", but I need time for testing the coupling with remaining Add'Ons (guess what? it's borking on some of them), I need time to implement the new solution to correctly cope with that coupling, and I need time to think on how I will implement that new solution in a way that it will not bork too heavily when something on KSP changes again (I'm not complaining on the changes, I just saying it will be another change sooner or later, and I don't want to do this again). I can say that I spent about 8 hours/week since then (some weeks I spent more time, some others I just didn't touched the thing). And this for a single bug, that it's easily solvable if I would be the only guy in town authoring Add'Ons for KSP. Things escalate exponentially, not linearly. Each new "feature" I add to TweakScale explodes on a lot of potential side effects on everything else. And this is not due any "bad architectural decisions" on KSP (yeah, there're some very bad ideas there, but they are not the problem [they're just nuisances]), it's due the fact this Kraken damned thing mangles with something that everybody and the kitchen's sink needs : mass. A bad decision about how to handle a mass here, and I can induce someone to a bad decision, that then makes something blow up into space in the less desirable and pleasant way possible. TweakScale also mangles the thrust. And area (or volume). So it influence resources consumption (or generators). What do you think it will happen if by some mishap of mine, a fellow Add'On author is induced to generate ZERO electricity on a situation where it was defined by design it will always generate electricity? The first code that would try to determine how much time of electricity it has will get or a Division By Zero, or a INF on the result. Now try to imagine what would happen if I do a mishap on the Area, and allow something goes negative. And so on. Now extrapolate all of this on the whole KSP. Now try to figure out every Kraken blessed Add'On in existence borking due a change you did, and now you have to face all that public backslash. And then hurrying up to patch that hole no matter what so you stop the backslash, and once the backslash ended, you need to handle the fallout. And once the fallout ended, you need to properly fix that thing you did in a hurry, or another backslash will happen soon. I said once, and I say again. KSP is not a "project" like Assassin's Creed or Battlefield. It's a "program", like Windows or the Space Shuttle. Every new interaction has a huge legacy to cope, or you loose your userbase (as the new guys on Microsoft just discovered with Windows 10 ). Microsoft had 25 years to deliver a stable, "final" release of Windows since Chicago (that Windows 95 thingy). They are still on it.

At least me, I'm not "defending" Squad. I'm defending my class. I'm a software developer, exactly like them - and the fact I develop a different kind of Software doesn't changes the fact that we have similar issues. They bork? Yeah. Problem is: me too. Sometimes, because I didn't give enough thinking on the problem. Sometimes, because I had to rush something into production or I would fail a deadline that would cause more damages that the stunt I did. Sometimes because someone else borked, but I was on the frontline and so, I had to handle the fallout. Exactly. KSP is owned by TTI, not by Squad. TTI is a business. Squad work for that business, and then, are accountable for the results they provide to such business. The exact same way I am to my boss and his customers. On the bottom line: the client borks, I handle the fallout. My boss borks, I handle the fallout. I bork, I handle the fallout. Someone promotes bad press about my work, I handle the fallout. But only 3 of them pay my bills. And it happens that neither you or me are part of the decision making party. Right now, I'm having to cope with a new module on the project I'm executing that, frankly, doesn't makes me too happy. It will be messy. We will have to waste resources on shielding that we don't need to do now. We will be exposed to attacks that are plain impossible by now. It will be a hell of pain, but some big player wants that way and we need their money. So... I'm implementing that Kraken Poo. The best I could do is to explain the stakeholders about the incurring costs of the thing, and to convince them to keep alive the current solution so we can still apply it on the retail and keep our costs low for the other clients - let the big guy absorb all the costs his demanding us to take, and if by any means he goes away, we don't need to spread such costs on the remaining clients - we just pull the plug of the damned thing. Welcome to Real Life (tm). I don't expect life is easier for these guys.

Doom 2005 was a hell of a good movie, once you skip the clutter and go right into the good stuff. It only happens that the clutter has 1:23:24 and the movie itself just 5:36.

The freaking autocomplete "typed" have, I meant HAD. (sigh). This changes your line of arguing somehow? If not, yes. There was a need for a new and cheaper rocked, and that's the reason SpaceX managed to get there. Being probably the reason Musk is betting on Mars and Moon. So, yeah. People willing to build that space station will need to pull it out a need from their hat. Tax evasion usually is a very lucrative reason. So I stick with my argument - one of the main uses of such space station will be tax and labour fee evasion.

Musk didn't have [HAD] a client willing to pay for his rockets when he started Space-X. Neither Bezos with his Blue Origins - but this one had some funding by (indirectly) participating on government funded programs some time later. Virgin Galactic already sold some tickets to space, by the way. From all of these, who is commercially operative and recently docked on ISS? Yep. That crazy loud mouth called Musk. Life is more interesting than our imagination sometimes.

The transatlantics hired by India to do data typing overshores to USA hasn't neither - except by breathable air. Food, water, medcare, everything has to come from the continent. Since prices on USA were way higher than on India, given the scale of the enterprise, such provisions probably were sent from India using cheap shippings by ship (couldn't help myself on this ). Once kicking provisions to space is cheap enough by kilogram sent (what not mean that the shipment itself would be cheap - compare the prices of shipping a container with the cost of the ship and the fuel for the trip), my guess is that some kind of stunt like I described would be probably the entry point for a lot of poor countries on space. In 1968, the first IT plant on India (practically Burroughs, using Tata as local dealer) was just one year old. From 1973 to early 80s (less than 10 years), the presence of the Indian IT on the World were insignificant in absolute numbers [but they were there already!!!], but on the 80's the growth was astonishing. Absolutely astonishing, in 1983 or 84 half the IT magazines of that time were talking about India (it was this way that I learnt about the transatlantic stunt, and when in the 90's they published about the IT Services Bureau demise in Europe, I already knew the reason). I bet my mouse Arthur C Clarke knew about Mumbai, and wonder if he did it to prank IBM - that was acting as tech consultant for Kubrick on the movie. Clarke wrote the script/book at the same time Kubrick shoot the picture. Source: https://en.wikipedia.org/wiki/Information_technology_in_India

In the 70s and 80s, India had no footprint on IT. None. Zero. Squat. But they had a lot of cheap human labor. So they started to sell low tech IT services for Europe, specially Data Typing. At that time, digital telecommunication was in their infancy, but it already was there using dial-ups and modens from 300 to 2400 and even 9600 (expensive as hell, by the way), and companies were starting to get digital somehow - with tons and tons of documents in need to be typed in order to be processed. India offered the best service at the time, guaranteeing up to 100% error free: they put two or more typists working on the same data (as much as the client wanted to pay for accuracy), compared the results, and typed again anything that mismatched. Europeans mailed the tons os papers to be typed, India transmitted back the data by modem. And then there was no more Data Typing Bureau in Europe, and there were no more available clients for the emerging IT industry on India. So they tried USA - but USA was too far away, air mailing tons of paper would be expensive as hell and shipping by water unfeasible -not to mention transmitting back the data on noisy underseas copper cables. And, of course, moving to USA and paying all the local taxes and labor fees would make the deal unattractive. So they just hired a freaking transatlantic, anchored it overshoes at the international waters and put a lot of Indians typing night and day, with boats bringing the jobs and delivering the tapes with the data to be mailed or transmitted on the continent. And that was the demise of the Americans Typing Bureaus too. I don't know exactly what will be the type of service, but I bet that something like that will be the first economical race to the Space; tax and labour fess evasion.

Publish your KSP.log . The answer is usually there. In the mean time, from where did you downloaded it? The latest version I found is here: https://github.com/Kopernicus/KittopiaTech/releases

For aircraft landings, you don't want to get the distance between your cockpit and the ground exactly below you. That piece of ground is not a threat to you anymore (unless you are in free fall). You are worried about the distance you are from the ground ahead of you, as there is the rock that can kill you. It's useful on the final approach, but by then you know there're not obstacles ahead as no one use to put airstrips behind a hill. The ASL altimeter will be useful for suicide burn landings. I found some didactic material on Radar Tilting here. Look for "paint the ground". GPWS is the thingy that yells TERRAIN on the movies.

Because they are not brave. They are "righteous". Some people, by having had a hard life, ends up believing that the World owns them compensation, and so everybody should comply with their wishes. Some other, by having a very easy and unchallenging life, ends up believing that they are "better", so they deserve "better", and so everybody should comply with their wishes. In a way or another, the aftermath is exactly that: people thinking that hey can do whatever their want in disregard for everybody else, and becoming angry and revengeful to anyone and anything that challenges that.

And this is why we are call our galaxy The Milky way!

The Earth is a Donut. And I'm hungry.

Nowadays, they have the Betas - Squad uses it to allow users to easily "stick" to a specific KSP Version. Open the Properties for the game, look for the Beta tab. I think this is on TweakScale shoulder. Check this bugtrack, I included your issue there to check as time allows. https://github.com/net-lisias-ksp/TweakScale/issues/27

With additional code by Rudolf Meyer merged up, so it's not exactly the Ferram's "stock' code. (on a personal note, it's better) On page 89 (if memory serves me right), there's a recompile made by a fellow Kerbonaut (and the memory DOES NOT serves me on his name) that is the Ferram's code untouched, except by being able to run on any KSP version.

Ow. This is my favorite kind of issues! The ones that doesn't exist, so I don't have anything to fix! Not a problem. It just happened that I'm working on some issues on TweakScale, and by "luck" (I hate you, Murphy!) what you described fit perfectly on the potential colateral effects I'm worrying about. The thing is deeply buried on some site, and then, zipped together a lot of other patches: https://www.dropbox.com/sh/wrjma4jq9gu0frj/AACUNwRheKYoUULqeEhC_0cha?dl=0 Unzip the thing somewhere, and move what you want to your GameData. (and thanks, by the way! I had forgot about this, and it's interesting to have it along to include on the testing! So, this ended up being useful! )