Lisias

So, I did another run on KSP 1.9.1, but this time using KAX and Open Cockpits - yeah, I'm wetting my feet slowly, Add'On by Add'On. However, this time the glitches are starting to get on my nerves. Problems on Symmetry on editing parts on VAB/SPH are annoying, but survivable (you just set things twice). Glitches on the Map where you need to select a Node in order to KSP "remember" to load all the Manoeuvring Nodes (instead of remembering them as you load the Map Scene) are annoying, but finding and clicking on a Node on entering the Map is not the worst thing that happened to me on this game. But Symmetry glitches on the Control Surfaces on craft spawn are near unbearable - every time I spawn a craft, need to revise all the controls to make sure nothing got the deployment inverted (pretty nasty on flaps). There's also a new glitch (at least for me): something is forcing the "Control from Here" to be set to the wrong part! I had to force the "Control from Here" on the Stage action, otherwise I would had to fix it manually every time too. On the other hand, once these bugs are manually fixed (or "gambiarrados"), the thing is working fine, I had some fun on it: On a nice touch, the gunners can be set to automatically "search for targets", a pretty guns animation! Craft on Kerbal-X.

The last news I had about UK is that they are going to avoid closures and lockdowns - the rationale is that it's impossible to hold the spread of the virus by now, the Winter is near the end (and so the Public Health will be less pressured by the winters diseases) and that it's better to immunise the population by now, when the rest of the World is on a lockdown anyway (and so the economic impact is unavoidable) than have to cope with the same drama next winter when the disease will be back - by there, they expect way less UK citizens to be vulnerable. However, besides UK is still receiving passengers from outside, I think it's unlikely that other countries would be receiving passengers from UK...

Ah, the Prophet-5.... Friend of mine owned one, once...

This one is what I managed to build on the free time today - just some more silliness on KSP 1.9.1 . This time, with the craft on Kerbal-X.

Money talks, "Piece of Paper" walks...

Yep. But, sir, the logs are not for you. The logs are meant for people that will provide support for the Add'Ons. These logs are the reason we can diagnose the problem by just telling the user to send us the logs, instead of going through a tedious and long series of "please try this, please execute these steps, please do that".

Problem is... It's our best tool for diagnosing problems. Messages on the screen are useless, as they don't have enough information (there's no enough screen!) - we usually issue messages on screen to alert about nasty conditions, but pushing on the screen all the messages needed to diagnose the problem is unfeasible. Once a problem happens, diagnosing it is not a mere look on the Exception message - it only tell us what happened, not why , and without the why, there's no possible fix without guessing (what, usually, ends up on finger pointing). So, some logging is needed - otherwise you will not get proper support when things goes badly on this Add'On or even others inducing this one to bork by collateral effect. You may think logs is bad - but it's way worse without them. That said, some logging messages are only meaningful on development (we call these "debugging messages" - and I agree that these ones should be suppressed on releases.

Thrust should be something as logarithmic, but this type of scaling are not available (yet) on TweakScale. That said, I totally encourage specialised sets of customised TweakScale patches for a challenge. You don't want engines being scaled? Get rid of these patches. You wanna different scales for weight, thrust and ISP (fuel consumption), talk to me and let's see what we can do. The same for everything else.

Dawn Patrol (who played it?) on KSP 1.9.1 Somewhat glitchy, but I hope fixable. .

Except that the guy explicitly allowed TweakScale, so it's not a pure stock challenge. So the argument itself is bogus. On your original post, you complained about how unrealistically TweakScale scales parts. Well, I can say for sure: it depends. The scaling is doing using linear, quadratic or cubic exponents depending on how you configure the receipts. From my experiments, engines are tricky to scale because in the real life the trust don't scale on a linear curve as the current configs is set, but instead tends to scale on a logarithm or exponential curve - what's theoretically possible if someone rewrites the patches (the scale is not limited to 2 or 3, you can use rational numbers as 0.123 or 2.444 too!). It only happens that nobody did it to this day. So I agree that scaled jet engines can be shady on a contest. However, it can be very handy for propelled engines used on Firespitter and KAX. Control surfaces and wings behave very well on scaling by the way, this allow you to do some very nice looking crafts. Way more realistic than clipping lots of parts in order to get something near what you indented to do - clipping two wings parts to look as one 50% bigger (150% of the original size) will give you twice the drag and twice the lift, while a scaled part to 150% will give exactly what you intend. And the wheels on the Beta too (to be released soon™), with the sturdiness and strength correctly scaled with the sizing. (and.. by the way.... How realistic is a "space simulator" with green guys poofing around on a planet with a soup as atmosphere and one third the size of the Earth but with the same gravity? Had I missed something? )

Well, this guy took it to the next level!

Just an ordinary song for an Ordinary Man.

Oh, my apologies for that! Exactly. And by being a business, they need revenue. Somehow. I'm on this business too, but not on games (something way less entertaining but equally complicated). And let me tell you, I do some of the stunts these guys are doing, I close business for good - it's not the bugs the problem, but how you cope with them. Every time we bork on the development, people will waste time. No one likes wasting time (worse if you on the paying side of this equation), but most of the time, people are willing to take the hit as long they are helping to get a better solution tomorrow. As soon as people realizes that they are having their time wasted because you choose to save yours instead of trying to make their lives better, they will react - and the aggressiveness of the reaction will be exponentially proportional to the efforts they made in the past to withhold your past borks. Users are your customers, not your subjects - and even subjects had deposed their sovereigns in the past when they got enough. Same here. These freaking little green guys helped me to cope with some really nasty situations. The degree of freedom this game (and the Add'Ons) give us allow people to replicate, in a simulacro, real life challenges and this is therapeutic - it helps on going through that Five Stages of Grief. However... Add up what we just said to what I had said on the previous paragraph, and do the math. Whatever is being done right now on KSP, is not being done with users in mind. Whatever are the objectives aimed by the current development practices, they don't aim the user satisfaction. However, make no mistake, they aim to satisfy someone - we just are not going to like it.

Nope. Just install Recall and the latest TweakScale and you are set.

You will need to check with the All Tweaks Maintainer to be sure. IIRC All Tweak overrides the Default TweakScale patches, but I don't remember what it does when a patch is not supported yet by TweakScale, nor when it became supported later...

One need to be invited to be a guest. Sometimes I think I crashed into this party!

Jan Hammer!

ANNOUNCE TweakScale Companion Program has been kickstarted!

TweakScale Companion is a series of "Add'On's Add'Ons", adding TweakScale /L support for third parties, but decoupling the target Add'On's life cycle from TweakScale's , easing maintenance and distribution efforts. The ÜbetPaket is a mega package including all Companions currently published for the lazy installers. This package is updated sparingly, the Companion's repositories (listed below) will always be updated with the latest versions - and are still the canonical way to have everything up to date. In a Hurry: Current Release: 2024.10.09.0 for KSP >= 1.3 Downloads on GitHub (and KSP-AVC users).. on CurseForge.. on SpaceDock. Announce for the current release. Announce for 2022.05.22 Initial Release. Announce for 2023.03.04 Announce for 2023.03.28 Announce for 2023.03.28.4 Announce for 2023.10.21.0 Announce for 2023.10.21.2 Announce for 2024.02.20.0 Announce for 2024.07.13.0 Currently, the following Companions are available: Current Companions Gold Status TweakScale Companion for AirCrafts Airplane Plus Neist Airline Parts Stock eXTension - SXT TweakScale Companion for Firespitter For (surpringly :P) Firespiter and Firespiter Extended TweakScale Companion Frameworks Test Flight Cryo Tanks Space Dust System Heat Waterfall TweakScale Companion for KIAS KIS KAS (unreleased) TweakScale Companion PKMC Far Future Technologies Near Future Technologies Near Future Aeronautics Near Future Construction Near Future Electric Near Future Exploration Near Future Launch Vehicles Near Future Propulsion Near Future Solar Near Future Space Craft Stock alike Space Station Expansion (Redux and Legacy) TweakScale Companion for ReStockPlus For ReStock[+] Alphas, Betas and Release Candidates TweakScale Companion for OPT Alpha For OPT Classic Legacy Continued TweakScale Companion LivingStyle Beta CxAerospace Station Parts PorkJet's HabPack HabTech (1) HabTech 2 Station Parts Expansion (Classic) Station Parts Expansion Redux Tokamak Industries TweakScale Companion Multipass Beta MechJeb 2 Tarsier Space Technologies TweakScale Companion SpannerMonkey Beta Large Ship Parts pack SM Marine TweakScale Companion for Rockets Beta Arc Aerospace RealEngines And more to come! Licensing Terms Notes * ALPHA means Companions terribly new and unstable, with features that can be added, changed or removed on every release. Don't use on "production" (i.e.,serious gaming). * BETA means Companions nearly feature complete, but not 100% reliable yet. Bugs are expected and will be fixed on demand, but no current features will be changed or removed otherwise. While being possible to use these on "production", you may find bugs on the gaming and the fix of some of them may render your savegame problematic. * Release Candidate (RC) means the last stage before going gold. Only bug fixes are applied (if any), nothing will change otherwise. These releases are supported the same way Stable ones, they just are not widely published yet. * You can follow what I'm doing (or planning to do) on the github issue tracker.

Nope. I didn't managed time to research BG scaling. There's a couple patches for blades on the Beta release, but they worked fine on 1.7, and on 1.8 they misbehave - didn't managed to grab an opportunity to retake this task yet

It's the difference between closing an Issue and implementing a feature: Issue #xxxxx : "implement a cheat allowing the user to arbitrarily reposition a landed craft on the PQS map". Feature : implement a cheat allowing the user to safely move the craft to anyplace on the current planet without exploding the damned thing, by checking for obstacles and objects and preventing spawning the craft inside any existing collider. The Developer did his job properly, the issue was closed. The QA team did their job properly, the issue was implemented as specified. The Product Owner (or whatever they call the guy calling the shots there), on the other hand, failed while writing the requirements and specifing the task.

So it's better to hurry up, or you risk attending his funeral and seeing a Unpaid Day Off deducted from your payment...

Copyrights. Private Division directly manages all the KSP1 Intellectual Properties, from textures to source code. Being directly under Private Division grants them direct access to all KSP1 resources, perhaps to the very source code repository without hassle (as having to secure legally rights to access them). It's more a tactical move than a strategical one. Things will happen faster now, I bet.