Lisias

ANNOUNCE Release 2.4.8.5 is available for downloading, with the following changes: Fixes a long standing mishandling on the Life Cycle of the SingletonBehaviour’s extended classes. Closes Issues: #336 Finally Diagnosed a Memory Leak on EditorHelper Everything in life is ephemeral, including 2nd places! It's unfortunate that TweakScale™ popularity, apparently, is vanishing but so is the Wheel of Life - I always knew this day would come. With these stats, it's unavoidable TS will plummet on the ranks pretty fast. I don't have an explanation for so many add'ons, TweakScale™ between them, plummeting on SpaceDock but, still, I knew this would come one day. But we are not dead yet. Scale safe!!! (and keep launching) TweakScale™ has, currently: 1,217,389 downloads on CurseForge 1,176,948 downloads on SpaceDock And at least half of them are under my tenure. Known Issues There's a long standing issue on TweakScale™ about scaling ModuleEnginesFX's plumes - some engines' plumes is just not scaled, while others scaled pretty badly. It's something that never worked right on TweakScale™, and it will only be really fixed on TweakScale™ 2.5 (when this thing goes gold) The best workaround (and also the reason I'm dragging my feet on this) is to use SmokeScreen or Waterfall. For SmokeScreen, you need: SmokeScreen itself. Real Plumes (to enable SmokeScreen on Stock parts) Additional Part Sets and Add'Ons may need specialised support not included on Real Plumes. For Waterfall, you need: Waterfall itself. StockWaterfallEffects (to enable SmokeScreen on Stock parts) Additional Part Sets and Add'Ons may need specialised support not included on StockWaterfallEffects. See Issue #27 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. Right Now. Being a bug fix release, I hushed the thing into everything at once.

Nome/Nickname: Lisias Idade: 50+ Nacionalidade: Brasil Estado/Cidade: Sao Paulo Capital Tempo de jogo: Desde 1.4.0 Mods: Melhor deixar pra lá.

The information I have is that there's at least one dev to keep the lights on - I don't think there's an AI agent able to do thinks like this on Steam. Yet. They even managed to publish an update to KSP1... Now... If there's something really happening, or that dude is just doing something to pretend things are happening...

Yes. It demands some highly privileged access to the Forum's server itself, however.

I don't think this is related. Would be a shortage on the server itself, all the add'ons would had been handicapped the same, as I had shown on my previous post: However, digging around, I found that not all the add'ons are being affected! See: There's something else happening, and I'm failing to detect a pattern. On a (pretty naive) eyeballing fest, I think that approximately 3 in 4 add'ons are being handicapped right now since last September 9th. @VITAS, are you aware of this?

I wondering if I should worry for my thumbs. Should I change my name to Gandhi?

"I'm not your employee."

Can you, pretty please, lock the following thread? I think it l had ran its course and it's now just being derailed. Thank you.

It has to start somewhere, no? And since I'm known to gladly help users no matter how they install things, it's hardly a suprise they mention it to me instead of doing it to someone that would reply "use CKAN" or "uh 100% no" and finish the conversation? Every time, every single time someone tells anything remotely not eulogistic about CKAN we have a flame fest. It's a surprised that some people choose to avoid dealing with CKAN as it would be the plague? Did you realised the length of the pain that it was endured on this thread just to have a single problem involving CKAN solved due the entitlement of some people that think they own my free time and I have an obligation to them? And when someone else read such a series of unfortunate events and realise that if I would just kept my mouth shut, none of this pain would had happen, what is the message they are getting? Don't have a clue yet. I used my scarse free time during this day dealing with CKAN - a mistake I'm not going to make again, you can be absolutely sure about. Once I manage to get a good night of restorarative sleep (I have DayJob(C) and RealLife(tm) issues to cope with - things are hairy around here), I will fire up my Windows box and give it a peek. Except by some CKAN zealots, I found more good references about NexusMods then bad out there. Granted, a few of these bad ones are a bit hairy and demand some research. But.. this thread is not about NexusMods neither Vortex. I think We should discuss this somewhere else instead of keep derailing this thread as it's being happenning. I just want to lock this damned thread and never touch this subject again.

I'm not your employee. It's not my job to convince users to reach you instead of me. @Snark, could you please lock this thread? I think it already ran its course. Thank you.

What's completely irrelevant to the outcome we were discussing, the (so I call them) borderline use cases. They are pilling up, but you are not being informed - perhaps because every time someone reaches you to tell something similar, the net result is something like this thread? (or, perhaps, feedbacks like this one?) I'm not the one with a beef with CKAN - just saying. And exactly how this is going to help the user to solve their problem? As I said before: Stop covering your arses and start fixing the problems. Life can be as simple as that sometimes. I'm not your employee. And given the outcome we got here, it's surprising I'm not inclined to use my scarce free time to reach the users for information, when you can do it yourself? This whole drama started here. Feel free to go there and ask them yourself - you don't need me for that. Again, why not asking the users directly? After all, they were the ones reporting the problem, no? I just had the unfortunate and regretable decision to support their oppinion on this Forum. A mistake I'm not inclined to commit again. Because they don't want to use CKAN, and it's not my job to convince them otherwise. Giving the outcome of this thread, and the personal consequences I got, I totally sympathize with them. My job is to fix their problem, and not every time the problem is fixable with CKAN - it's exactly the other way around, most of the time I get involved because something bad happened after using CKAN. I diagnose the problem, fix the problem and advise the user how would be the best way to prevent if from happening again. And that's all I do. I will not deal with this subject again. And I will pinpoint this thread to anyone asking me why.

[snip] So you don't know? If you don't know, how in hell do you make claims about 99.999% of effectiveness? Yes. Because they don't like how it break things sometimes. And one of the reasons are the terribly inaccurate way to set retro-compatibility as explained here: [snip]

And, yet, nobody ever mentioned Vortex to you. That's the whole point. If the user's installment gets screwed after using CKAN and it wasn't before, the net result is a screwed up installment no matter who's in fault. On the other hand, if the user installs something by hand, screws it up and CKAN detects and fixes it... Can you see the huge difference it would do? This is not a Court of Law. We are not being sued. Nobody will be declared guilty and do time due it: it's merely the matter of getting the job done or not. If there's bad metadata on CKAN's database, it's up to CKAN to deal with it, not the user. It's the whole reason users are using CKAN at first place, to do not have to handle these problems, even the borderline ones. Of course, CKAN can choose to give the one finger salute to users that find themselves on some borderline use cases - but, by then, it's reasonable to blame the user for trying to solve the problem without CKAN? Because I support my users, not CKAN, Nexus or whatever. When an user reaches me with a problem in which anything I do is involved, I help them no matter how they installed the damned thing. Virtually all the support requests I get nowadays** is related due something else botched on the user's machine, causing collateral effects that affects something I published. ** Exception made on the following days I publish a new release, when now and then I bork something and let it pass trough into the release.

Guys, @VITAS I think there's something weird happening on SpaceDock. Since Sep 9th, the downloads for the majority of the add'ons I checked plummeted from 6 to even 16 times less than the day before! This is a too much dramatic drop, something wrong must be happening - or perhaps was happening before? Not every add'on is being affected, I paid attention mainly to the most downloaded ones, but I found some newer ones also getting screwed - I'm still investigating. In a way or another, I think you guys need to do a public statement about what's happening - this is risking affecting the confidence on the site. === == = POST EDIT = == === Finally finished munching some numbers. SpaceDock had a peak of downloads at 2024-0908 in the early hours (4k downloads). On the early hours of the next day, the site's download reached the rock bottom (ONE download). Things apparently were coming back to normal on 2024-0910 peaking nearly 3K at 19:00, but then plummeted again and didn't recovered until this moment. Whatever is happening, is affecting the whole site. Are you guys under a DoS attack? === == = POST POST EDIT = == === SpaceDock downloads from the last 90 days. Note the rock bottom values on September 9th and 11th.

But not all of them. CKAN is still causing (or being accused to) cause troubles on the wild. This Forum is not the main resource for support anymore, people (by some reason) are finding their way outside. And now people are asking for help, outside this Forum, on KSP installations managed by Vortex too. Please reread what I had wrote here and in the origin thread under this new light: I came here to warn CKAN that something is happening - hardly something related to someone that have a feud (or beef) to someone. I surely have my disagreements, but absolutely none of them reflects on the user - I will always support the user the best I can - I'm suggesting CKAN does the same, definitively something that I'm not seeing on this specific use case that triggered this FlameFest we are now stuck inside. Planet Packs are a very relevant niche on this Scene. I suggest to better serve these guys - or someone else will.

You know, I think they are right on the money on this one. This damned thingy had the same problems on the 2nd Orbintal Test. I mean... They sit on their hands on the problem since then? Lockheed's Orion was launched to the Moon and came back at 2022, right? Someone at Boeing surely had received the memo... They surely know how to make you open your heart to them...

[snip] Please read the original posts. Please also remember that you don't represent the totality of the current users of CKAN, and that at least some of them presented reserves about some of perceived CKAN's weaknesses that I took the unfortunate decision to bring to the table. There's a reason I'm getting support requests from people using Vortex on KSP.

I think that @ColdJ had nailed it at the first shot. Aproximately at 10 or 11AM Zulu, we had a hiatus on the occurrences. However, about 5 or 6 hours later we got back the http 429 , suggesting that the pressure increased as whatever it is being done is done. I want to stress that I'm keeping the same pace during the whole period (about 20 to 25 hits per minute, given or taken, topping at near 40 very occasionally). So it's my opinion that whoever is hammering the site, is increasing their hammer's cadence as they realizes the site is getting more responsive (while I keep the pace at best, down it to 0 at worst). I have, at this moment, the following working theories: Forum's original IP is not protected by a firewall from accesses from IPs outside the Cloudflare's range, and the hammer knows and use this IP directly; Forum's original IP is protected, but someone punched a hole on the firewall to allow a 3rd party to directly access the server; Whoever is hammering the site, is probably being whitelisted by Cloudflare and are hammering Forum unchecked using Cloudflare's infra structure. In all, absolutely all by attempts to find what would be the maximum hit rate I could get by (ab)using parallelism, Cloudflare kicked by balls after less than 5 minutes near 60 hits per minute in average. PER MINUTE. I can reach 2 or 3 hits per second for less than a minute before Cloudflare axing me out for an hour (and, yeah, you can find the axe dropping on me on the charts), and this is the reason I ended up with the 3 working theories above. The only way to check these working theories is by analyzing the Forum's NGINX logs - the http 502 messages spilt the beans (disclosing even the NGNX version used - and, yeah, I'm kinda liquided about it too, because it happens the same on DayJob©). Pinging @Vanamonde@Deddly and @Gargamel (and now @Anth) as suggested by @ColdJ above.

Jesus Christ! It's real!!! This forum probably became a riot during the Staliner drama, no?

Moved to

[Moderator note: This thread was split from the main CKAN thread here.] Moving from another thread. Ping @Grenartia I dispute that number, but whatever - you are clearly using rhetorics here. Users will do the path of less friction. If CKAN imposes too much friction, users will do manual installs - or will try anything else, as Vortex - that, interesting enough, are starting to be mentioned when people reaches me for support. I strongly suggest to ask the users why they are preferring manual installings instead of setting up CKAN to assume all 1.8.1 addons to be compatible to 1.12.5. Curseforge may had forsaken KSP, but there're others willing to fill the niche - as I said, I had noticed an increased interest on using Vortex while doing support.

I confirm both impressions. Things are escalating terribly again since the first hours of Sep 9th.

And, so, how exactly telling @Iapetus7342 to install manually the Planet Packs and letting CKAN handling the other dependencies is not the best solution for this problem? And exactly how this madness is less mad than users bluntly telling CKAN to allow installing incompatible add'ons as a workaround to allow installing a single (empirically confirmed) compatible add'on? What doesn't means that CKAN is not behaving wrongly on borderline situations, and then manual installing of these specific use cases would be the best compromise. We have a problem here: CKAN is preventing people to install add'ons that are perfectly usable on the target KSP, and the users are (rightfully) trying to find a workaround for it. By telling these users that manual installing is not an acceptable solution, exactly how do you think the users will handle the problem?

With the due respect, I think that the Technical Director (formerly "Senior Manager of Engineering") is the one with these roles in the Team: I do not know how Furio and Nate relate themselves on the PD's Corporate Hierarchy, but the information I have now suggests that whoever was Furio's boss, they is the one deserving having their cheeks being bashed by you. If we establish that Nate was his boss, then you will be right for sure. Other than that, I'm inclined to agree with you on the rest of your argument.

Nops, @Iapetus7342 has a point. CKAN's metadata is lacking on Planet Packs. Kerbol Origins, for example, is flagged to work only to KSP 1.8.1 on SpaceDock, and this information is replicated on CKAN. But it was confirmed that it works fine on KSP 1.12.5: So the user have to tell CKAN to consider KSP 1.8.1 to be compatible to KSP 1.12.5 to have it installed. But not everything that works on 1.8.1 will work on 1.12.5, subjecting the user to the risk of install incompatible or troubled add'ons that are known not to work on 1.12.5 at all - sometimes unattended due the Recommendations and Suggestions. So, yeah. @Iapetus7342 is right. It's best to install the Planet Packs by hand, letting CKAN handling the other dependencies without using the somewhat unaccurate KSP compatibility flags.