Jump to content

Lisias

Members
  • Posts

    7,387
  • Joined

  • Last visited

Everything posted by Lisias

  1. I think there's another option. Instead of changing an already deployed and in production code (the new DockingPort Module), I think a new (custom) module can fix the problem: Every time the craft goes on rails, the module would save the current attachment positions of its Part, and once the craft goes off rails, the module would restore these values. Additional benefit is you being able to patch this module on any needing part, and not only on Docking Ports - any similar glitch on any other part would be fixed with a new MM patch. I will give this a try this WeekEnd on KSP-Recall, let's see if I manage to pull this stunt.
  2. I can't help but to contemplate my own landings on KSP on watching this one: Pretty harsh landing, but everybody survived unscratched (including the craft). https://www.aviationnepal.com/worst-landing-by-boeing-737-300-pk-ygw-at-paro-airportvideo/
  3. News from the Front With the 1.12.2 release this week, I re-run my reports to see what exactly was new on this one so I could update the (Work In Progress) TS patches. The work is being done slightly slower than expected, but with a important milestone reached on Day Job, I hope time will be sensibly less scarce on the following days. Wish me luck! And, of course, I found a pretty stupid mistake on my report generator that ended up screwing up the reports I'm running for almost an year already… Oh, well… Better late than never. On the spoiler below (not mobile friendly, sorry. You will probably need to maximise the Window to properly read the contents) the updated reports for new parts and modules for every KSP Version I ever had put my dirty pawns on - hopefully correct this time. Cheers!
  4. So I found some time to play KSP a bit, and realised it's a lot of time since I played KAX by the last time. So,.. Inspired on a craft I posted on my "Real Life Kerbalisms" thread: (I initially tried to use Stock+TS KSP 1.12.2 to do it, but didn't found my way on the propeller engines yet)
  5. This is EXCELLENT news! Thanks a lot! I mean it!
  6. A plane with wings filled with water. David Rose's RP-4 Another source. — — POST EDIT - — Moar Pics! Source.
  7. TL;DR: I didn't tested and I don't want to answer questions about it, so I declare it a conflict so people do not install it. There's a difference between being incompatible and being unsupported. I don't mind people not wanting to support TweakScale, the whole TweakScale Companion Program aims to seamless support third-party add'ons without hassling TweakScale neither the third-party add'on. But declaring it a conflict shuts the door for any official support, as the end user will need to override CKAN - denying one of the core reasons to use CKAN at first place. That said, this is not a TweakScale problem (neither CKAN, by the way - no need to hassle CKAN guys on this neither) - TweakScale is compatible to KTT in the same way it's compatible to others Tech Tree around here, it is only not supported by it. Unfortunately, due the KTT maintainer's decision to declare TweakScale a hard conflict, there's no incentive for incepting a Companion for KTT where such support could be added. So I don't see a reason for further discussing the matter here. Sorry.
  8. Don't have a clue. All I can say is that someone declared TweakScale as a conflict on KiwiTechTree. This happened 9 months ago, by the way. You will need to reach CKAN guys and ask them about.
  9. thanks! Ouch. Sorry for that. These messages are a pain in the SAS , I know, but sometimes these situations can screw up something. Not always, granted, but since it's pretty unfeasible to try to detect when it's fatal and when it's not, I choose to err on the safe side. I really need the KSP.log and the ModuleManager Patch Log - without these files, I can only do blind guesses. Most of the time these problems happens when more than one add'on patch a part completely disregarding that maybe someone else had patched it first. So it's pretty possible that KRE will not trigger anything on my test bed because it is only half of the problem, and I need the KSP.log to see what's the other half. You can upload the files using Dropbox or GoogleDrive (remember to allow people to download it!). Or if you have a github account , you can leave a comment on this issue dragging and drop a zip file with the logs.
  10. Well, since we are talking about vehicles with weird wheels, how about Rolligon? — — — POST EDIT — — — And CHECK YO STAGING! https://www.reuters.com/lifestyle/science/russias-nauka-space-module-experiences-problem-after-docking-with-iss-ria-2021-07-29/ ( Who never? )
  11. Because you regulate voters, not funders. And the new feudal lords are the Energy producers apparently.
  12. I agree. Please talk with the CKAN guys, I'm not responsible for this. I'm not aware of any problems on these add'ons, by the way - but there should be a reason for that - if you find it, report here and I will see what I can do. (Ping @DasSkelett )
  13. Makes me remember something I did some time ago!
  14. ANNOUNCE KSP Recall 0.2.0.4 is on the Wild, featuring: ChillingOut is not working as expected. Deactivating it. Any problems will need to be tackled out punctually. 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. Being a rollback release, all Distribution Channels were updated at once. Cheers!
  15. So it's ChillingOut without the slightest doubt. I'll rollback it and I'll post a new release ASAP.
  16. And I will not even talk about the push for Electric Cars - these things are not going to use the very same electricity?
  17. Yep. This is what I was aiming to fix with ChillingOut . Ideally, I should find a way to identify what parts need the fix instead of applying the fix on everything as I'm doing now. Any suggestions about how to do it will be hugely appreciated! Probably because I may be stomping KSPIE's toes with ChillingOut. The root problem is simple, something related to Heat is not being correctly initialised sometimes as it was being done until KSP 1.10.1 . If we manage to zero in the culprit, a better fix can be cooked and so we ChillingOut have a better chance of not screwing up something else by accident. — — POST EDIT — — Uh.. Wait….. @rawhide_k, you are telling me that by using the previous version of KSP-Recall, things were not exploding? So the new KSP-Recall version is the one causing the problem??? o.O
  18. Dude, you are appreciated . the next release will have some experimental thingies that need to be manually activated to be tested. My worst problem is not being able to predict how some changes will affect the mainstream - I know how they affect the part, but I have little visibility about how it affects real life users with real life save games. Someone willing to burn free time with a backup of his/het save games will be a huge help!
  19. Unfortunately, an upgrade may be more problematic than expected... https://www.techradar.com/news/intel-warns-of-cpu-stock-shortages-in-near-future Not sure if this is going to affect only Intel or everybody, but in a way or another upgrading CPUs will be a problem. And this will affect the prices for used CPUs too...
  20. Yep. But since most people usually buys a prebuilt PC (or so I was told), this appears to be a big issue. The computer mentioned on the Article (ALIENWARE AURORA RYZEN™ EDITION R10 GAMING DESKTOP) is not that big, 550W. I think my old PS3 is more of a power hog than it. Even my NAS, that supports 6 5.24" spinning disks, needs a 5A PSU... I think this will impact somehow the new generation of Games - and I'm not even talking about some issues on the current ones...
  21. Yeah, I probably messed up on the Workaround for some exploding parts problem that were introduced on KSP 1.11. It's something related to heat no being initialised correctly, exploding everything on launch. Apparently, the thingy is screwing up KSPIE by accident. I opened an issue to investigate it: https://github.com/net-lisias-ksp/KSP-Recall/issues/25 Can you inform an engine that you had tested and confirmed the bug? This will save me the potential bad luck of choosing an engine that doesn't have the problem, what would waste some time (and unfortunately, I'm low on it these days - anything you can give me that would save even a hour of work will be a huge help). In the mean time, edit the file KSP-Recall.cfg on your GameData/999_KSP-Recall to be like this: KSP-Recall { INSTALLED { Attached = false ChillingOut = false Driftless = false Refunding = false Resourceful = false } } @KSP-Recall { @INSTALLED { @Attached:NEEDS[KSPRECALL-ATTACHED] = true // @ChillingOut:NEEDS[KSPRECALL-CHILLINGOUT] = true // Here! Comment out this line! @Driftless:NEEDS[KSPRECALL-DRIFTLESS] = true @Refunding:NEEDS[KSPRECALL-REFUNDING] = true @Resourceful:NEEDS[KSPRECALL-RESOURCEFUL] = true } } And then edit the chillingout.cfg file from GameData/999_KSP-Recall/patches to be like this: @PART[*]:NEEDS[KSPRECALL-CHILLINGOUT-IGNORETHIS] // Note the "-IGNORETHIS" { %MODULE[ChillingOut] { active = True } } This will override the internal code that decides what to install or not.
  22. News from the Front. I finally got my… rectangular pieces of paper together and managed to enumerate everything that TweakScale was missing for KSP. TL;DR : Geez, I have some work to do!!! Theoretically, all the missing support for parts (but Serenity, as this beast will give me a run for my money and will be tackled down separately!) are "implemented" already, the next step is to revise all the Scale Exponents for missing modules. This is currently work in progress, and I may have some (good) surprises for you! For the sake of curiosity, follows a somewhat comprehensive report for all Parts and Modules that were ever present on KSP since the first release I had access on Steam (0.22, unfortunately not available anymore…): (not mobile friendly, sorry. You will probably need to maximise the Window to properly read the contents) This is the most cumbersome task from the scheduled ones for the next release, it will take some good days of hacking to iron out these ones. Please be patient. Cheers!
  23. IMHO, one of the best features from Making History is the Mission Editor. And one of the best Missions built with it is this one - you may want to try it once you get a grasp on the new parts:
  24. I found this one today and for some time I didn't knew where to post it. I think this fits this thread, so here we are. "Dell won't ship energy-hungry PCs to California and five other US states due to power regulations" https://www.theregister.com/2021/07/26/dell_energy_pcs/ Frankly, I didn't saw that coming and I don't like the smell of it - not to mention at least some of the mentioned states are pushing electrical vehicles...
×
×
  • Create New...