Lisias Posted September 22 Author Share Posted September 22 (edited) ANNOUNCE Release 2.4.8.6 is available for downloading, with the following changes: Due recently realised changes on the way CKAN handles alternate downloads, some safeties were implemented to alert the user if by some reason it was installed a non CKAN approved package on a CKAN managed installment. Closes Issues: #339 Prevent non CKAN safe binaries from being used on CKAN managed installations. We are not dead yet. Scale safe!!! (and keep launching) 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... Spoiler No Module Manager, EULA or Forum Publishing Guidelines were harmed during the development of TweakScale™. But a priest may had... 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. Edited September 22 by Lisias All your Distributions Channels are belong to us. Quote Link to comment Share on other sites More sharing options...
JonnyOThan Posted September 22 Share Posted September 22 I’m pretty confused about the intentions here. We’ve sorted out the issues of CKAN pulling from GitHub right? And CKAN will not index pre-release packages from GitHub anyway. If you communicate your intentions to the CKAN team maybe we can come to a better solution? Quote Link to comment Share on other sites More sharing options...
Lisias Posted September 22 Author Share Posted September 22 (edited) 1 hour ago, JonnyOThan said: I’m pretty confused about the intentions here. We’ve sorted out the issues of CKAN pulling from GitHub right? And CKAN will not index pre-release packages from GitHub anyway. If you communicate your intentions to the CKAN team maybe we can come to a better solution? The intention is to warn the user that CKAN managed installments should had TweakScale installed by CKAN, and that only the packages I had specifically tested on CKAN should be used. This is meant to prevent non CKAN approved TS packages to be unattendedly installed on CKAN managed installments, avoiding stomping in your toes - one of the main concerns is on the TweakScale.WatchDog component that aims to prevent mishaps going unnoticed on manual installations, but that have some features turned redundant when the rig is managed by CKAN where such mishaps would not happen. Note that I have a CurseForge specific package too, where another set of rules is used. You will notice on the commit that I created the boilerplate to do the same for CurseForge. As long as I find a way to detect a Curse Installer managed rig, I will do the same there. The rationale is that things perfectly valid on CurseForge are inconvenient (or plain undesired) under CKAN (and probably vice versa). And manual installations need checks that should not be made on both of them - double guessing CKAN while using CKAN is a bad idea. I will quote what will be logged on KSP.log if the user do a manual install (from github or, Kraken knows why, CurseForge) on a CKAN managed rig for reference: Log.force("**YOUR ATTENTION PLEASE!** This TweakScale packaging is not meant to be used under CKAN. It's usually a bad idea to do manual installings when using CKAN, futurelly this may break things for you! Please CKAN to install TweakScale on CKAN managed rigs."); And, other that having redundant checks activated, this will be the only change the user installing manually a non CKAN approved package on a CKAN managed rig will see. Edited September 22 by Lisias less is more. Quote Link to comment Share on other sites More sharing options...
Lisias Posted October 11 Author Share Posted October 11 (edited) NOTAM Waterfall 0.10.0.0, recently published, removed a type from the Assembly that I as relying to identify it and, so, this release broke TweakScale. Big thanks to @BSS_Snag for reporting it! I reworked the TweskScale Compantion for Frameworks, the subcomponent responsible for dealing with Waterfal, and published a new released last Wednsday - on GitHub, CurseForge and SpaceDock. Unfortunately, CKAN until this moment failed to index the new release, and this is the reason fir some TweakScale users getting some problems when Waterfall is installed. Until there, I have to ask to all CKAN users to manually update the Companion to the newest (currently Release 2024.10.09.0 ), or at very least the Frameworks to 0.4.0.5. I'm working with the CKAN team to have this sorted out. My apologies. === == = POST EDIT = == === Problem located and fixed. Creating releases in a rush at lunch time is, usually, not the wisest of the ideas. Note to my future self: http://status.ksp-ckan.space/ Edited November 1 by Lisias POST EDIT Quote Link to comment Share on other sites More sharing options...
Lisias Posted November 18 Author Share Posted November 18 (edited) ANNOUNCE Release 2.4.8.8 is available for downloading, with the following changes: Fixes (AGAIN) a regression on handling attachment nodes, thanks Kraken affecting only KSP 1.4.3 (and almost surely 1.4.0 to 1.4.2, but I didn't bored to check). Special attention and caring were taken to do not change anything on support for any other KSP. Finally fixes an embarrassing bug that where doubles were being squashed to floats. I do not expect any change the default scalings, but people using some dramatic customisations on really big and really small exponents should see some improvements. Removes some (TS unrelated) sanity checks when a CKAN managed installment is detected TweakScale is, from now on, blindly trusting CKAN on keeping the running environment sane, only yelling when it's directly affected. Updates KSPe.Light.TweakScale to 2.5.4.5 Reworks Issues: #307 Attachment Points are not being scaled (or being reset) after changing the Variant. I'm playing KSP 1.4.3 just for the lulz, but - as usual - I found something "interesting"... I detected that Issue 307 somehow caused a regression. But only on 1.4.3 (not complaining, but... What the heck?). This release fixes that. Spoiler Problem: two months ago I did some regressions tests, including on 1.4.3, due another change, and this problem wasn't happening. And I had evidences about. And since I did regression tests on all TweakScale historic releases, I detected that the last "working" release was 2.4.7.3 - so a change on 2.4.7.4, in theory, caused the problem. Except that the problem didn't existed at all until recently, otherwise I would had detected the problem - at last in may, on TS 2.4.8.0 (that were working on 1.4.3 at that time, and now it's not), but more probably recently because, heck, 1.4.3 is the fastest KSP on a rig of mine I use constantly, and I DO PLAY THIS THING sometimes while waiting for something on day job. And there's absolutely no change on anything remotely related to scaling or loading or saving craft files on Editor, I inspected every change since 2.4.8.0. Thrice (the 3rd was right now). Oh, well.... I'm counting my blessings. It only affected 1.4.3 (I did regression tests up to 1.7.3, and a quick smoke test on 1.12.5). But yet, I can't explain this misbehaviour. Or I can? Additionally, when TS is installed from a CKAN downloaded package, and it detects CKAN, it does not checks the KSP runtime environment anymore. From now on, TS will blindly trust CKAN about the sanity of the installation, complaining if and only if something that it's definitively going to hurt TweakScale is detected. This behaviour is easily tweakable, just edit GameData/TweakScale/TweakScale.cfg to activate or deactivate the "readiness" of the installment - the rest of the package is, literally, the same for manual installers, CurseForge and SpaceDock packagings. And we are not dead yet. Scale safe!!! (and keep launching) 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... Spoiler No Module Manager, EULA or Forum Publishing Guidelines were harmed during the development of TweakScale™. But a priest may had... This Release will be published using the following Schedule: GitHub, reaching first manual installers and users of KSP-AVC. Right now. CurseForge. Eventually. SpaceDock. Sometime after CurseForge. Unless someone besides me still plays on KSP 1.4.3, no one really needs this release. So I will take my time on pushing this to the upstream so I can evaluate some runtime checkings being withdrawn when installed under CKAN. Edited November 18 by Lisias I forgot the change log... (sigh). Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.