Lisias

ANNOUNCE Release 2.4.6.25 is available for downloading, with the following changes: Checker for the need specific TweakScale Companions was added. Your `GameData` is checked for 3rd party add'ons currently supported by a Companion and a Dialog Box is displayed listing the ones you need to install. Some mistakes on the configuration files were fixed. Thanks to @zangonoid for the heads up! The TweakScale Companion Program is reaching the mainstream. Properly. Now TweakScale will evaluate your GameData and will alert you when a Companion is available for something you have installed The AlertBox is still crude, but things will improve Soon™. Disclaimer By last, but not the least... This Release will be published using the following Schedule: GitHub, reaching first manual installers and users of KSP-AVC. Right now. CurseForge. Right Now. SpaceDock (and CKAN users). Soon™. The reasoning is to gradually distribute a potentially Support Fest release in a way that would me allow to provide proper support if anything else goes wrong.

And that's the whole point. What decides if you will issue a single-fix-only release is the damage the bug is doing in the field. Non critical bugs can wait a large release to save some money in the process, but really critical bugs should be fixed on the spot. KSP2 is a game, so no people are going to die due a software glitch (right, Tesla?), but some bugs are seriously affecting the revenue - and this is similar to being killed from the Publisher's point of view. Doesn't really matter if we are talking software, hardware or embedded (a combination of two). The decision on releasing a single-fix-patch or a multiple-fixes-patch is made based on the damage the bug(s) is(are) doing on the field, and anyone ignoring such criteria is going to loose some money in the long run. It's all about the money. It's always about the money.

Yep. And I also reproduced the problem here. Silly typo in the configuration files, really stupid. I'm fixing it and will issue a new release ASAP (having internet issues on my neighborhood, damn...). In the mean time, just click on Cancel to Humm.. cancel the message, ignoring it. Thanks for the report, I don't use Waterfall myself (still on 1.7.3), I completely missed that one...

Holly Crap, this is a new one. Please send me your KSP.log, I need to figure it out ASAP. Thanks

And it is. ABS is software controlled. Been there, seen that - I was working on an autoradio with CAN integration, and so I had to cope with electric steering, ABS, ECU, you name it. You see, you was replying to someone openly stating they had work on a huge project involving hardware and software. And then you ask him about a single project that had issued a single fix patch. You was the one forcing your hand on the subject. But, since you now is defining better the scope of your argument… In 2021 Mercedes had recalled millions of cars due a software bug on a device responsible to locate the vehicle to emergencial services. It was a software only bug. No hardware involved on this one. (and yes, now I'm being picky ). I think you should refrain yourself from doing this kind of judment about people you don't know. The World is bigger than you.

Volvo just made a Recall for 106k vehicles due a bug in the brakes. if the problem is big enough, you not only do a single-bug release, you even pay for the installation of the replacement on the customer's product. World is way bigger than you think. And some dudes around here live there. ;)

Me too. But let me tell you, the whole project was partitioned in a lot of individual components integrated with very well defined interfaces. No development team was bigger than 5 to 10 guys, being it hardware or software. Under that monstrous development process Siemens had paid someone to create for them (IBM? I forgot) at that time - when I blew a fuse doing a stupid thing, they made me fill a form and I spent the whole morning on the warehouse to get the replacement. This was the level of control they had over the whole process. You won't believe how small details caused huge, really huge problems on the pipeline completely defeating the Process - like when someone forgot to connect the mass ground on the cable that connected the JIG into the iPod, and we burn a couple until I got liquided off, disassembled the cable and noticed the mishap. No matter how mature is your development process, it will fail now and then due the Imponderable. Sooner or later someone will forget or twist a wire, the testing process will miss it and you will get the whole team hold back for a month because you blew up all the development toys due the crap. That said, you are not wrong. It only happens that you are not the only one right on this discussion.

No. Wait a few months, otherwise you are going to get a lot of grief - the thing is really not flyworthy yet. It will be one day, I think. So it may worth buying it now to save 10 bucks instead of buying it when the thing finally goes gold - but I would not spend time trying to play with it now or in the near future - it's a bet. I risk one, at this time. Things may change at anytime, however. Check things again on every Early Access new release.

ANNOUNCE Withdrawn Release 2.4.6.24 is available for downloading, with the following changes: Checker for the need specific TweakScale Companions was added. Your `GameData` is checked for 3rd party add'ons currently supported by a Companion and a Dialog Box is displayed listing the ones you need to install. The TweakScale Companion Program is reaching the mainstream. Properly. Now TweakScale will evaluate your GameData and will alert you when a Companion is available for something you have installed The AlexBox is still crude, but things will improve Soon™. Disclaimer By last, but not the least... This Release will be published using the following Schedule: GitHub, reaching first manual installers and users of KSP-AVC. Right now. CurseForge. Right Now. SpaceDock (and CKAN users). Soon™. The reasoning is to gradually distribute a potentially Support Fest release in a way that would me allow to provide proper support if anything else goes wrong. In time, it's just me or Forum is royally screwed up today?

Humm.. let's see. These are the threads were you can find help for each one of the mentioned add'ons (or CKAN): The Cryo Tanks is here: https://github.com/post-kerbin-mining-corporation/CryoTanks/releases But drop a message to Nertea nevertheless - I don't think that downgrading Cryo Tanks will give you any (new) problems, but don't hurt to talk to Nertea about.

This new log have essentially the same exceptions from the last one I checked. No news, everything appears to be the same. There's no other option but to talk to FAR maintainers - I don't know this thing, I don't have the slightest idea about how to fix it. About the CryoGenic Engines, I checked the dependencies. It needs Cryo Tanks 1.6.3 - but the latest release is the 1.6.5. I'm guessing you need to downgrade it to 1.6.3 to fix your issue? It's a wild guess, it's safer to talk to Nertea about it. You may want to reach CKAN guys too and see if they didn't forgot to set something on the NetKAN file. CKAN is giving me some headaches since some time already, by the way.

Not exactly. I need a description of the problem, and at least the full KSP.log (not only a fraction of it). Check the OP (the first post of the thread, on page 1) inside the spoiler under the tittle "Support:" to see where to find KSP.log . Use dropbox or similar service to publish it, paste the link here with the description of the problem.

1GB log? Gee… Well, zipping it will shrink it a lot, and I use automated tools on my side so the size of the thing is not a big problem. I'm unsure about what you are describing - please confirm: 1) You installed a new release of the Cryogenic Engines (from Nertea) 2) Things screwed up royally It's probably some missing dependency. Do you remember what was the previous release you was using? By looking in the older release dependencies, and checking the new release, I should be able to detect the problem.

Speaking frankly, I fail to understand why so few of us do it. Keeping the legacy parts alive is the best (if not only) way to bring people from older KSP versions - most of the time people just give up from KSP if the only way to update it is to lose their savegames. The industry is littered with examples of excellent new versions of something that failed to keep backwards compatibility and so were simply ignored by the consumers. New people wants to reuse things from the old guys, and old guys want to keep using their toys. I can't see why KSP would be spared from such phenomena!

On the Kerbal Way - 1927!

Nope. You probably just found the source of problems, hidden behind some other problem - it happens, KSP is a very complicate piece of Software! I found this: [LOG 20:32:43.250] B9TankSettings: registered tank type RR_ATMC [WRN 20:32:43.400] DontDestroyOnLoad only works for root GameObjects or components on root GameObjects. [EXC 20:32:43.450] [ModuleManager] Exception while calling B9PartSwitch.B9TankSettings.ModuleManagerPostLoad(): System.Reflection.TargetInvocationException: Exception has been throw n by the target of an invocation. ---> System.Exception: Fatal exception while loading tank type RR_XPL ---> System.Exception: Exception while loading field resources on type B9Part Switch.TankType ---> System.Exception: Exception while loading field resourceDefinition on type B9PartSwitch.TankResource ---> B9PartSwitch.Fishbones.Parsers.PartResourceDefinitionV alueParser+PartResourceNotFoundException: No resource definition named 'Explodium' could be found What tells me that you need to install something in order to get that "Explodium" being used by some parts. I also found this: [ERR 20:32:53.586] Kernel 'CountPixelsMain' not found [EXC 20:32:53.595] ArgumentException: Kernel 'CountPixelsMain' not found. FerramAerospaceResearch.Resources.Kernel..ctor (UnityEngine.ComputeShader shader, System.String name) (at <12ef3e87e4dd4d9896231922a21a371a>:0) FerramAerospaceResearch.Resources.FARComputeShaderCache+ComputeShaderAssetRequest.AssetLoaded () (at <12ef3e87e4dd4d9896231922a21a371a>:0) FerramAerospaceResearch.Resources.Loading.AssetRequest`1[T].OnLoad (T resource) (at <12ef3e87e4dd4d9896231922a21a371a>:0) FerramAerospaceResearch.Resources.Loading.AssetBundleAssetLoader`1+<Load>d__4[T].MoveNext () (at <12ef3e87e4dd4d9896231922a21a371a>:0) UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <ef038509c5b948af8d6049dcab97ad3f>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) [ERR 20:32:53.596] Kernel 'CountPixelsMain' not found Don't have the slightest idea about what's `CountPixelsMain`, you will need to reach the FAR maintainers in order to get help on this one. Burst is also spitting up Exceptions a lot: [ERR 20:32:53.802] [KSPBurst]: Are you missing mono installation? https://www.mono-project.com/download/stable/#download-mac [ERR 20:32:53.812] [KSPBurst]: Burst compiler terminated with an exception [EXC 20:32:53.816] Win32Exception: ApplicationName='/Users/rhycecomley/Library/Application Support/Steam/steamapps/common/Kerbal Space Program/PluginData/[email protected]. <....> Can't help on this one neither, but you can reach the Maintainers for further help too. From this point, there's another huge load of B9PS exceptions, that may be splash damage from the first one (or at least is what the log message is telling me), followed by this one: [LOG 20:35:53.441] PartLoader: Compiling Part 'KeridianDynamics/Parts/KD-LaunchSite/KD-LaunchSite' [ERR 20:35:53.454] Cannot parse Enum value. Field defaultActionGroup, value Lights on object of type ModuleAnimateGeneric: System.ArgumentException: Requested value 'Lights' was not found. at System.Enum+EnumResult.SetFailure (System.Enum+ParseFailureKind failure, System.String failureMessageID, System.Object failureMessageFormatArgument) [0x00023] in <9577ac7a62ef4 3179789031239ba8798>:0 at System.Enum.TryParseEnum (System.Type enumType, System.String value, System.Boolean ignoreCase, System.Enum+EnumResult& parseResult) [0x0017a] in <9577ac7a62ef43179789031239ba8 798>:0 at System.Enum.Parse (System.Type enumType, System.String value, System.Boolean ignoreCase) [0x00010] in <9577ac7a62ef43179789031239ba8798>:0 at System.Enum.Parse (System.Type enumType, System.String value) [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 at BaseField.ReadPvt (System.Reflection.FieldInfo field, System.String value, System.Object host) [0x00b07] in <46478292153440df94e04a2a2ddd1062>:0 telling me that KeridianDynamics is not going to work for you. You need to reach the maintainers for this one too. From this point, your KSP.log is being littered by problems on USITools: [EXC 20:35:53.471] NullReferenceException: Object reference not set to an instance of an object USITools.USI_SwappableBay.Update () (at <3dac2b1a9b2d4a589ca5156d8c89686f>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) And this is yet another one you will need to reach help from USI's Mainteiners - I don't have the slighest idea about what this means! Yeah, found it: [LOG 23:10:01.235] PartLoader: Compiling Part 'NovaPunch/Freyja/Freyja/FreyjaTrunk/NP_Freyja_Trunk/NP_Freyja_Trunk' [WRN 23:10:01.246] PartLoader Warning: Variable LF not found in Part [WRN 23:10:01.246] PartLoader Warning: Variable OX not found in Part [WRN 23:10:01.246] PartLoader Warning: Variable totalCap not found in Part [WRN 23:10:01.246] PartLoader Warning: Variable massOffset not found in Part [WRN 23:10:01.246] PartLoader Warning: Variable costOffset not found in Part [WRN 23:10:01.256] DontDestroyOnLoad only works for root GameObjects or components on root GameObjects. [ERR 23:10:01.257] Module ModuleB9PartSwitch threw during OnLoad: System.Exception: Fatal exception while loading fields on module ModuleB9PartSwitch on part ---> System.Exception: Exception while loading field subtypes on type B9PartSwitch.ModuleB9PartSwitch ---> System.Exception: Exception while loading fields on subtype PartSubtype LNH3 ---> System.Exception: Exception while loading field tankType on type B9PartSwitch.PartSubtype ---> System.Collections.Generic.KeyNotFoundException: No tank type named 'RR_CryoA' exists at B9PartSwitch.B9TankSettings.GetTankType (System.String name) [0x00030] in <a3c2951fc74e4639820ef37d2d29f386>:0 at B9PartSwitch.TankTypeValueParser.Parse (System.String value) [0x0000b] in <a3c2951fc74e4639820ef37d2d29f386>:0 at B9PartSwitch.Fishbones.NodeDataMappers.ValueScalarMapper.Load (System.Object& fieldValue, ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00022] in <a3c2951fc74e4639820ef37d2d29f386>:0 at B9PartSwitch.Fishbones.NodeDataField.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00043] in <a3c2951fc74e4639820ef37d2d29f386>:0 at B9PartSwitch.Fishbones.NodeDataList.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00025] in <a3c2951fc74e4639820ef37d2d29f386>:0 It's NovaPunch this time. Something is missing (or plain broken) for it, you need to find whatever provides `RR_CryoA` into the game and install it. I think that it's Rational Resources and I have found this post about a fix for it. You will need to reach Rational Resources maintainers for further information, I'm at lost on this one too! On the OP, there's a Spoiler below the title "Support:" . You will find instructions about how to find the KSP.log and Player.log there. Then you just need to upload them into dropbox or similar service and post a link here.

I second that!

Between all parts involved on the launch. You see, the Launch wasn't exactly a success. Worst, the state of the game is blatantly under the minimal requirements to achieve a minimally acceptable result. The whole structure failed on delivering the needed results, what suggests that something is missing on the equation. We usually get better results on this situation by having a trustable outsider, without his skin on the problem (but surely interested in the best outcome possible), mediating the unavoidable conflicts that most of the time, ends up blowing up in the face of the weakest stakeholders without such mediation. The Aerospace Industry is full of examples about how to deal with such failures. I suggest to ask what NASA would do on a situation like this, and do something similar - these ones are pros on handling huge mistakes, they did they share in the past, and they successfully managed to get out of the problem bigger and stronger.

Right now, one week after the KSP2 Launch, the concurrent KSP players are almost twice of the KSP2 ones - while the total reviews on Steam shows about 49% of positive feedback (KSP has 94% for comparison). Whatever they are going to do, I suggest to bring an external mediator to handle the unavoidable conflicts and preserve all parts involved from unnecessary wear and tear. The Dev Team, as the name of this thread is already suggesting (in good faith, I'm absolutely sure), are the one going to be on the receiving end without an impartial, 3rd party mediation. The genius is out of the bottle, there's no way to put him back - now someone will be called to scramble to salvage the situation at any costs - and we had already seen this movie before, so we know how it ends.

I have some evidences that switching from the PWD may not be the best of the ideas. Users on Steam Deck appears to be being screwed by this change, I'm investigating the matter. https://github.com/net-lisias-ksp/KSPe/issues/48

It looks like something had screwed up the nodes in the prefab... Are you using some mods and, so Module Manager? Inspecting the ModuleManager.ConfigCache can tell us if there's someone patching nonsense into the parts, or if this is something happening at runtime while playing. The GameDatabase is not readonly, I had toyed with it making changes on the editor - never published anything doing this stunt by obvious reasons...

There're more people playing KSP than KSP2 in Steam right now. https://steamcharts.com/cmp/954850,220200

My friend, you have a really, really messed up Config Cache! By the Krakens! UrlConfig { parentUrl = Belafonte/Parts/Zelicopter.cfg PART { name = CJZelicopter <....> MODULE { name = ModuleAlternator RESOURCE { name = ElectricCharge rate = 3 } } { name = ModuleAnimateGeneric animationName = Commander_lights layer = 9 startEventGUIName = Work Lights ON endEventGUIName = Work Lights OFF actionGUIName = Toggle Work Lights defaultActionGroup = Light } { name = ModuleDockingNode referenceAttachNode = dock nodeType = size1 aquireForce = 20.5 aquireRange = 15 captureRange = 10 stagingEnabled = False ejectionForce = 10 } You see? For this part, the "MODULE" node name is missing. And I still looking on the first 10% of that file... This is going to be a challenge… I will edit this post in half a hour, once I manage to finish running the my lint tool. — — POST EDIT — — Dude, things are horribly messed up on your Config Cache! UrlConfig { parentUrl = CrewLight/Localization/es-es.cfg Localización { es-es { #autoLOC_CL_0001 = Luz de tripulación #autoLOC_CL_0002 = Alumbrado automático de la cápsula <...> } { es-es { #autoLOC_CL_0001 = Luz de tripulación #autoLOC_CL_0002 = Alumbrado automático de la cápsula #autoLOC_CL_0003 = Los Kerbals encienden la luz de su cabina/cápsula cuando embarcan/desembarcan #autoLOC_CL_0004 = Detector de luz <...> } You have nodes being duplicated inside themselves. — — REPORT — — Oukey, I have confirmation that the (old and deprecated) SpaceY is the one triggering the problems in your rig. However, these "TweakScaleRogueDuplicate" problem is something that is already diagnose and worked around for ages, and it shouldn't be a problem nowadays. There's something else on your rig stepping in the screwing up things in a way that prevents TweakScale from doing it's business correctly. It works to mention that I found lots of weirdities on your ConfigCache, and I don't think that these ones are related to bad patching - they are completely different from any occurrence I had with MM in the past years. It's even weirder that on the same group of parts, some have the problem and others not. @wreckreation, please reach SpaceY maintainer and ask about what can be done for you about that patches - perhaps installing a new Add'On together the newest SpaceY will help on the mather? At the same time, the other problems I located are screwing some of the parts in your game (and this is completely unrelated to SpaceY). Please consider doing the tests I sent you in PVT. Cheers!

I recommend some PMI instead. I just didn't believed that the devs, honestly, would think that the current state of the game would be viable for User consumption even on Early Access, so, yeah, this didn't crossed my mind. If you are right, people involved on this launch had shown some serious poor decision making skills. Well, so perhaps PD should hire Iron Maiden or Metallica for managing the development so? In a way or another, being an Art or a Science, Managing is about Accountability and Responsibility. Absolutely none of your arguments is changing that. This launch gone south terribly, and I doubt the costs of the firefighting will overcome any benefit (monetary or not) this stunt will render. I'm seeing a Death March coming over the dev team, with all the nasty consequences not only to the developers but to the final product itself. History repeats itself. But now on an AAA budget. That said, your opinion on the subject is clear and you are not going to change it. Same for me, so we need to agree on disagree on the matter. None of us have our bacon on the game anyway.