Lisias

Try something like this on your code: namespace MYMOD { public static class ModuleManagerSupport { public static IEnumerable<string> ModuleManagerAddToModList() { List<string> tags = new List<string>(); if (checkFor("KopernicusSolarPanels")) tags.Add("MYMOD-Kopernicus-Classic"); if (checkFor("KopernicusSolarPanel")) tags.Add("MYMOD-Kopernicus-RTB"); return tags.ToArray(); } private static bool checkFor(string typeName) { Type type = Type.GetType(String.format("Kopernicus.Components.{0}, Kopernicus", typeName)); return null != type; } } } Then on a config file: SOMETHING:NEEDS[MYMOD-Kopernicus-Classic] { // Define something using classic kopernicus } SOMETHING:NEEDS[MYMOD-Kopernicus-RTB] { // Define something using RTB's kopernicus } I built this from copy and paste from some personal projects, and I didn't tested it - but anything wrong on the code should be easy to detect and fix on the IDE.

NOW I got it. It's related to the tech-tree, I didn't paid enough attention when you talked about R&D... I reproduced step step your video, and didn't found any change on my (crappy) FPS, about 10.98 . However, I found a huge amount from what follows: [LOG 00:34:14.172] MiniAVC -> System.NullReferenceException: Object reference not set to an instance of an object at MiniAVC.AddonInfo.get_IsKspExcludedVersion () [0x00000] in <d7230d01a6174087a11daadf631edf08>:0 at MiniAVC.IssueGui.DrawNotCompatible () [0x00030] in <d7230d01a6174087a11daadf631edf08>:0 at MiniAVC.IssueGui.Window (System.Int32 id) [0x00006] in <d7230d01a6174087a11daadf631edf08>:0 and MiniAVC were found on PBC's directory. By manually removing all files starting with MiniAVC on my installment, these exceptions vanished - and my FPS became slightly less crappy (11.2..). Install ZeroMiniAVC. I think it may be the trouble maker on your rig, and with a extremely more powerful machine than mine, the tax imposed by the I/O is bigger for you. And since it's embedded on a lot of add'ons, we may have a explanation about this thing happening in weird combinations: KSP-Recall is usually installed, and when some Add'On with MiniAVC is installed, the avalanche of exceptions on your KSP.log causes the drag on FPS. I failed to establish a link with Recall, however - the DebugMode didn't shown any activity from it (unsurprisingly, as Recall was told to do not be loaded on anything but Editor, Flight and TrackingStation). Exactly why on the R&D, and why things get better on unlocking the Arm it's, frankly, beyound me...

A pretty clean installment, only with MM, Recall and Probes Before Crew deterministically reproduces the problem for you? I'm completely out of time for exploratory tests, but if you have a deterministic script/receipt/walkthrough to reproduce the issue, I can find a quarter of an hour to try to confirm it.

As I said, you are not helping.

Culture. Availability. Access to new blood. All of these matters. You are failing to understand that we (not only me, I'm the one talking about openly) are not concerned about previous developers being used to help on the new product. We are concerned about: Previous developers that utterly failed on keeping the previous product healthy are now on the new product A previous product those last versions were utterly bugged A new version of the previous product that was released without the minimum set of tests required to get the most basic and evident of the problems (like the RCS Block V2 on 1.11.1). A new product being delayed for a long time A very harsh economic environment that will endure for years to go A (apparently) shrinking userbase, driven away by the current set of problems (something else? I think I'm missing something) Yeah, I was missing a Company being sacked recently about the same product! Yes, we can. Once the appearances start to look similar, we can argue that the management appears to be the same. If not the same people, apparently the same M.O. And this matters. Yep. Very different. We are managing to keep ours afloat, besides this tsunami. Being slightly paranoid is one component that is being used to accomplish this. Don't expect that I'm the only one doing what I'm doing. Of course I may be wrong - but my logic stands with the information I have at hands. I expect this logic is being used by some people more. Some evidences appears to corroborate my assumptions. You don't like it? Me neither. What we can do about? Point taken. Well, I'm arguing. And mine statements stand too. The confusion appears to be that you think I'm trying to prove you wrong. I don't - because I don't need it, you may be right without proving me wrong, so I don't need to even try to prove you wrong. It's not. It's an incomplete data that, added to some other incomplete data we are gathering around, can lead to a partially correct conclusion, that by itself can lead to a good decision nevertheless. We have a chain of events that suggests something nobody is going to like - shooting the messenger is not going to make it better. Even with me being wrong on some assumptions, I'm not alone on it and repeating ad nauseaum I'm wrong and that I don't know about what I'm talking about will not make things better - because, you see, it's also another hint that something is not going that well. People willing to gain trust listen to the concernings and then addresses them instead of trying to detract the concerned, distrusted contender. You need to break that chain of events in order to get trust again. Do you know how we build trust, right?

And exactly what is being done to signal that anyone investing on KSP would not do the same error (in minor scale, of course)? Success from the Part don't pay bills on the Present. Nope. From the very beginning of this discussion (as well from another ones), I'm repeating ad nauseaum that I think the problem is environmental, ergo related to management - not the developers. What doesn't really matters from the investor point of view. Ok then. I'm absolutely sure that every investor on this World has a Master Degree on Game Development... You build a house. The dude the initially worked on it was not professional house builder, but he did a splendid job on building a house that everybody wanted to have. So the House Building Company hired some professionals on the field in order to be able to accomplish the task. But these new guys are not Architects, they are Engineers (with variable degree of professionalism), and so they stopped to listen to the people that was wanting the house and started doing engineering stuff that sounds solid on a first glance, but pushed away the very same people that WAS wanting a house like that. Now the Company decides to retroject the whole house, trying to bring some sanity to the mess. And they bring that very same engineers that screwed up the last project on it. There's a planned neighbourhood called Kyssia in a city called Manaus in which I lived some decades. The interesting thing about Manaus is that on the XIX Century, it was one of the richest cities of the World due the huge success of the Latex Extractivism, then they gone through decadence some decades, and suddenly on the 60s, by government initiative, a Industrial Pole was created there and suddenly that city got a lot of money again - but with a twist, they need to suddenly bring specialised professionals from the whole country to work on that Pole (my father was one of these). And there were not houses for everybody. So they had to build whole neighborhoods from the ground. But since the guys that have money at that time (and was the ones investing on building houses) had no experience on building houses this way, they brought engineers for doing this job. But they hired no Architect. Well, that houses were a tragedy. They were big houses, people from Sao Paulo and other regions from Brazil would like to live on such houses - if they were built in Sao Paulo or in the other regions, as on Manaus, 4 degress south of the Equador Line, what they had built were stoves, not homes. Oh yes! The W.C. were built in the center of the house, with not direct access to the outside (they put the kitchen between the W.C. and the outside wall), so no proper ventilation on a neighbourhood built on a city where 36oC (about 96F) is the common temperature of the air... at midnight, because on noon we had to endure 45 to 50 sometimes (113 to 122F). Oh, yes!!! The Manaus Sewerage was still the one built by the British on the Amazonian Belle Époque, and only on downtown - so anything else had to rely on private sanitary pits that had to be emptied regularly... Someone already did the math? W.C.s built in the middle of a inadequate built house for the Equatorial climate without proper ventilation and relying on sanitary pits? Good thing you could sleep outside, believe me. And that were very expensive houses built for rent and make money from the specialised professionals that were being "imported" by the new Local Industry. Why I told you this history? Because something is smelling funny on KSP from some time,we want a new "House" and I want to be sure the guys building the new one will not make the same mistakes the guys that built the older one did. However... The current house is on ruins, as the maintainers are giving the finger on it but the smell is still there, and the very same guys that didn't listened to the clients before are now working on the new house. Do the math. The prospects suggest that the best option may be to leave. It's not the game being challenged, sir. I thought this was made clear already. You are misleading, again, the discussion. What is being challenged here is the ability of the current developers on successfully compete profitably on this market. Doom Eternal had TWICE the peak players over KSP, what suggests twice the number of sold copies are still interested on the game. Additionally, the concurrent players are INCREASING on Doom Eternal, while KSP ones is DECREASING -worst, on a time where KSP has published a new Release with new Features - essentially, expending money to lose players. Huge difference, sir. Any statistics, by itself, are meaningless. You need to cross check them to get (imprecise, but still useful) knowledge about what you are looking for.

You didn't reproduced the problem! There's no entry like this on your log: [LOG 23:10:23.374] RobotArmScanner.S1 added to ship - part count: 17 Please try again: Install KSP-Recall DebugMode (what you did) Go to Editor Reproduce the problem: Create or load something simple Attach the RobotArmScanner.S1 on is Quit the editor Send me the KSP.log Cheers!

Do you own a Company? I do. A fraction of a Company, to tell you the true - so I'm used to justify my opinions in order to get consensus on my partners. Taking good decisions based on insufficient data is exactly what every investor do for living. And it's exactly due this that now and then we end up "wasting" some time and/or money on things and tasks that would not directly improve our product (in which we get moderate success): we need to convince our customers (who play the role of "investors" for our company) about the perception of value of our products we need them to have in order to stay afloat. They lose confidence on us, we are toast. They are the ones paying for our party.

Yep. I remember somewhere in the past quoting the price of the Warcraft Trilogy, those full price was about 86BRL (while KSP's full price was 72BRL). Supply and demand concept doesn't apply to infinite supply items, as digital downloads are - the supply is virtually endless, the only cap is the broadband available to deliver the good. You can try to artificially create some scarcity, but immediately you will be fighting piracy where the costs of such endeavour not rarely are greater than any loss it would incur to you. On purely virtual goods (as digital download games), the key word is PERCEPTION OF VALUE. What's the perception of value of KSP1? Frankly, pretty low by now. What's the perception of value of KSP2? Pure speculation, but at least for me, is risking plummeting. (see below for MOAR REASONS) No argument on that. Huge market, huge demand - and a hell of a huge competition. Tough life for a game that "lives and dies in its niche". Facing a shrinking and highly competitive market, what's the strategy to explore new options and how this will affect the expected RoI of the current investors? On a side note, there's yet another handicap for game computers around here: electricity cost. Inflation affects way more that only the hardware and software prices, I expect that power efficient computers would be way more used around here than power hungry ones. So, bear with me. In order to play KSP2, I will need a new rig. I will need to reserve more money for the power bill. I will need to pay for a Windows License (250 to 350 BRL , but you can risk your SAS buying keys fro 90BRL from some shady sources). The expenses just piles up - for a game that I'm loosing confidence of being worthy the very price tag, what to say the lateral expenses. In order to play KSP1, all I need to do is to just keep doing what I'm doing right now, without any additional investment. Me and a lot of Brazilians - and I suspect this will not be something specific to my country. I understand. But my argument is about investors. How any of this would counter-argument me from an investor point of view? Someone still need to pay for the party. And they want their interest back.

Your log is not going through the Flight Scene, I found no line as this one on it: [LOG 16:37:26.372] [HighLogic]: =========================== Scene Change : From LOADING to MAINMENU ===================== Your log stops abruptly way before the Main Menu, exactly here: [LOG 02:04:02.180] [Scatterer][Debug] Added eclipse caster Minmus for Kerbin [LOG 02:04:02.250] [Scatterer][Debug] Atmosphere config found for: Kerbin [LOG 02:04:02.281] [EVE CloudsManager]: Clouds2D is now MACRO So it's of no use for me. So I gave a shot on my minimalistic 1.11.2 Test Bed, but using the Debug Release of KSP-Recall, and tried to reproduce your problem using the CRSY Light Scanning Arm: No misbehaviour detected. Whatever is screwing your FPS, it's something else. One way to induce Refunding into guzzling your CPU is by issuing thousands of OnEditorShipModified events - since Refunding relies on this event to detect when the ship was modified on the editor and refire the original costs calculations. But even on this, it's something else playing havoc on your rig, not KSP-Recall. Reproduce your problem using the DebugMode release, then publish the full KSP.log (from startup until quitting the editor after reproducing the problem). This will pinpoint if someone is inducing Refunding into guzzling your CPU. Then we can try to nail down the real culprit, once we manage to establish a deterministic and univocal way to detect the misbehaviour on the log.

You are misleading the discussion, trying to minimize my argument to mere launch times. Forum rules prevent me from vocalising exactly what you mean. Go back, read again. I'm talking about Money, Opportunity Costs and, implicitly, Return Of Investment.

A seven-day forecast can accurately predict the weather about 80 percent of the time and a five-day forecast can accurately predict the weatherapproximately 90 percent of the time. However, a 10-day—or longer—forecast is only right about half the time. Source. Good comparison. And since we are here: In 2020, world output shrank by 4.3 per cent, over three times more than during the global financial crisis of 2009. The modest recovery of 4.7 per cent, which is expected in 2021, would barely offset the losses sustained in 2020. Source. We can't be able to predict correctly the Weather in 6 months, but we can affirm for sure that Siberia will not have a Summer day on the peak of their Winter. The prospects are not good, not matter from what edge you see the thing. At least on the short term. Perhaps. But I fail to understand how this would comfort CDPR's investors that lost that money, and now have a perfect escape goat to use (or sue) for such losses. I was expecting you to use that card. AGAIN. If the userbase that are entitled to get DLCs for free are still significant enough to prevent profit from the DLCs, even after 10 YEARS, I need to tell you that the problem is not the userbase, but the failure on the Company on inject new blood on the franchise and expand the user base. How do you expect this will affect potential investors' attention? What you already depicted on item 1 : if the current userbase entitled to get free updates are still so significant that this makes selling new DLCs unprofitable even after 10 years, the sells of new copies must had been abysmal... So there're very few attention of the public on it. So the demand must be small. Again, how do you expect this to keep investors happy, once the sequel is being postponed and postponed again? (Had I mentioned that the development team that failed to keep the product healthy in its life is now working on the sequel, what can be a bad sign?) On Steam, current price for KSP in Brasil is 72BRL, what converted is about 13.06USD. The price for the United States is 39.99USD. So you need about 3 sold copies on Brasil to get the revenue from a single one on US. On Argentine, the converted practiced price is 4.65USD. You need 8.6 sells on Argentina to get the revenue from a single on on US. I fail to see how this would please investors, mainly because as you said yourself, "KSP lives and dies in its niche". We posted at the precise same second! Given the current losses on the Steam's charts for concurrent players, I fear that KSP being the biggest competitor for KSP2 would be the good scenario... (posts were merged)

The History is plenty of examples that proves YOU wrong. I may be right or I may not, but your statement is wishful thinking at best. As much as CD Projekt Red were wishing to do it when they launched CyberPunk 2077 some months ago. But yet, last time I read about, the losses were on the 1Billion USD scale. One Billion Dolars lost in less than 6 months. On a personal note, I think they will recover. But you can bet your wallet the investors are cutting some throats around there. 1 Billion USD could had generated a lot of interest anywhere else.

Hard to tell. The Golden Era was on the 1.2.2 and 1.3.1 times. Personally, I think 1.7.3 is the best compromise between a rich and relatively recent modded environment and stability (and relativelly low nasty bug count)

There're also Modular Fuel Tanks (my favorite), Firespitter and B9 Part Switch.

And clearly not on KSP2, an eternal Work In Progress game aimed to be on a more expensive class where bigger players will fight to their teeth to dispute on shrinking market. And I will not even extend into the fact where the people that were unable to prevent a ship to sink [for more then 6 years now] are now working on the boat. And it is exactly because investors (that wish to keep their money, at least) usually don't fall on the sunken cost phallacy that I think we have a big problem here: there are way more profittable or safe investiments out there - is the Opportunity Cost on keeping my money here bigger or smaller than the money I will lose by bailing out?

You are wrong (there was no fundamental flaws on the Max - only a bunch of badly implemented features, badly integrated), the 787 is the one that you should be looking at. But you are right - this is not the place for discussing Boeing, I used it as a (already admitted dramatic) example of how a series of bad decisions can weaken the Company to a point it may not survive a major crisis. Worse, the inflation and taxation will grass around the whole World. Economies are shrinking as a cheap shirt washed on cheap soap - with one exception, but this is not the place to discuss it neither. You cannot expect to sell too much copies of KSP2 on Brazil, where the USD <-> BRL jumped from 3.5 to 5.7 in less than an year. 60 bucks, now, is something about 342BRL, about 25% of the minimum wage around here. And I will not even touch the problem of acquiring hardware - lots of people (including myself) are postponing hardware upgrades for some time - computers for gaming are now costing more than cars here. The shrunk economies around the word and the unavoidable retraction on the consumer market for non-essentials suggests that KSP1 should be the tittle having some attention right now, as it is way easier to get some bucks using it to do many and many small sales of 10 to 15 bucks every year than to try to sell a 60USD, supposedly A class tittle. But KSP1 now is losing players (or at least is what Steam is telling me) from some time now in a way that was not happening in years. Now put yourself on the investors' shoes: where is the best place to put their money now?

It's not about technicalities. It's about environment, culture, internal politics and, most of all, about who is paying for this party and what they is wanting back as interest - and why I should put my money on it. Using a somewhat dramatic comparison from the Aeronautic Industry: you can bet your SAS that every single engineer on Boing is pretty competent as an individual. But, yet, there's the Starline Capsule fiasco (not to mention 737 Max). Once the problems on the Max was solved, it ended up being a pretty good aircraft - but had you checked Boeings stocks price lately? It's slowly recovering, but there's a thingy called Opportunity Cost: why I would invest 1000 bucks to earn 1010 on something while I can invest the same 1000 bucks and get 1020 on something else?

Seems like the rounding errors can go both ways... KSP should do a rounding on its own, but without knowing how and where, I'm reticent to blindly find my way on this. Doing roundings early or later on the process makes a difference. In a way or another, kick me here if you find anything else! Cheers!

Humm... I'm a bit more sleep deprived than I thought. I will re-relase the code as 0.1.0.8, then we will see what's happening on this use case. -- -- -- 0.1.0.8 is published instead. Same code I intended to release on .7, but now it's properly identifying itself. -- -- -- @Krazy1Jeez, I screwed up the 0.1.0.7 packaging! I managed to publish again the previous version!! Holy Krap! Your craft is working on 0.1.0.8 (as it would do on 0.1.0.7 if I had packaged it right!!). Sorry for wasting your time, dude, and thank you very much for the heads up!!!!

Yes, and this is even worse for the franchise.

ANNOUNCE KSP Recall 0.1.0.7 0.1.0.8 is on the Wild, featuring: Finally diagnosed and fixed an issue on refunding Kerbals on Command Seats (or standalones) Reworks the issue #16. This Release will be published using the following Schedule: GitHub, reaching manual installers and users of KSP-AVC first. Right now. CurseForge. Right now. SpaceDock (and CKAN users). Right now. The reasoning is to gradually distribute the Release to easily monitor the deployment and cope with eventual mishaps. Cheers!

Given the way less than ideal results being delivered on KSP 1.11, with the way less than desirable consequences on the intended audience (at least, on Steam - about 40% of the gamers in the World are on Steam, do you know?), had allowed experienced staff to work on projects those deadline is way ahead from a near and very important historical milestone for the franchise was not exactly what it would be considered a wise move. (hell, on my time on Corporations, at this time we would be counting this deadline using weeks instead of months...) So, yes, the manager should be informed about this (my guess is that he is already are). But not exactly the one you think: you know, your boss has a boss... Someone is paying for this party. And I consider the odds of he/them being happy slightly dim by now.

Yep. To simplify things (I hadn't enough time for testing things as I want), I was cheating my funds before launch to have barely the money needed to launch the craft. If the thing costs 7015 , then I zero my account and cheat it into 8000 . So, on recovery, I need to have that 8000 back. Easier to track failures without having to bean counting things! Tomorrow I will reserve some time to proper test FMRS and Pay to Play (just to be on the safe side - this is the point where overconfidence usually bites me on my SAS). Everything going fine, I will release the thing into the Wild Wide Web. -- -- -- POST EDIT -- -- -- FMRS is working fine, automatic recoverings are being carried out without over or under refundings. Pay to Play I'm not sure, I may had screwed up something on it, as I think I'm being under-refunding on recovery.... -- -- -- POST POST EDIT -- -- -- Found a small and practical test case for Pay to Play, and it worked. I will consider 0.1.0.7 a proper release, and it will be distributed as usual from now on.

Today is this magnificent piece of art from Wendy Carlos, TRON.