Jump to content

Lisias

Members
  • Posts

    6,487
  • Joined

  • Last visited

Status Updates posted by Lisias

  1. I wish to kindly ask you to avoid polluting TweakScale's thread with unrelated matters.

    I have email, I have private messages here, and I don't remember a single request of yours that I didn't gave the deserved attention before.

    Thank you.

    — — POST EDIT — — 

    Never mind. You last interaction about something I work on makes clear we have no possible common interests about any matter.

    The best outcome for both of us is to ignore each other - but I would prefer not hearing of you making less than truthful declarations about my work.

    Have a nice day.

  2. Opa! Tudo bom?

    Parei aqui pra dar feedback sobre o Universal Storage.

    Eu comecei o trabalho ainda naquele fim de semana, mas tropecei nos PartModules custom dele, que têm uma sintaxe diferente para alguns valores no prefab, e vou ter que escrever Scalers customizados.

    E isso é muito mais fácil de fazer no TweakScale 2.5, que teve um baita revamp no framework de suporte de código. Então ao invés de fazer de qualquer jeito no 2.4.6.xx (que vai sair uma meleca, como aconteceu com o Waterfall), eu tô implementando isso logo no TweakScale 2.5 e vou botar no ar no mesmo tempo quando lançar o TS 2.5

    Se você quiser dar uma olhada no que tá feito:

    https://github.com/net-lisias-ksp/TweakScaleCompanion_US

  3. Hi!

    I have some news for you on Recall's thread:

    Not the news you would like, I still don't know whats happening - I could only confirm this is not a problem being caused by Recall neither TweakScale.

    I'm trying to figure out what to do next.

    1. Show previous comments  2 more
    2. Lisias

      Lisias

      Hi!

      I concluded the report:

      There's something fishy on the IT part config. Since I don't know the KSPIE PartModules, I can't say what, but hey… Now we know where and how.

      You will need help from the IT guys, and probably from the KSPIE's maintainer too in order to identify exactly why only IT parts are borking.

       

    3. GoAHead

      GoAHead

      thx @Lisias. i will let them know. i'm afraid there will be no support. .. but lets try

    4. Lisias

      Lisias

      Just to finish the report, as I had diagnosed things later and my last message here left implied that KSPIE and/or IT were at fault somehow:

      • It's a KSP's limitation : the IPartCostModifier uses float , and so are prone to loss of precision with really expensive (or cheap) parts.
      • KSPIE had no role in the problem, other than triggering it.
        • IT, ditto. It only happens that these parts are expensive enough to get screwed by the float squashing problem.
      • A new PartModule were added on KSP-Recall to handle the situation.
      • All the other problems detected were just noise, they didn't affected the outcome.
  4. I think you may do a good use of this concept!! :)

    6c2063c42b1edeb1164a9225eadaeb0c.jpg

  5. Hi!

    You recently asked on the 1.12.3 release announcement about a real fix for the parts drifting:

    On 1/12/2022 at 11:52 PM, Staticalliam7 said:

    Ah, makes sense. Is there a mod that corrects this, or is it too deep within the game's code to mess with (without losing your mind)

    I think you will be interested on my findings on KSP-Recall:

    A "fix" is still far away, but at least I found my way on the problem.

    Cheers!

    1. Staticalliam7

      Staticalliam7

      Oh cool! Very interesting. I hope you find a solution!

    2. Lisias

      Lisias

      Me too! :P

      KSP is terribly messed up nowadays - I almost always need to find a fix for something that ended up broken because of another fix (there're lots of code written relying on the bug!)

      Cheers!

  6. Hi!!

    I'm Lisias, not Sarbian!  :D :D 

    I forked MM for my personal use - one of reasons is that now and then Sarbian's server (the current maintainer of Module Manager) is down as it's today, and people needs Module Manager.

    As the time passed, I made a lot of changes to meet my own use cases, what makes my binaries not suitable for the end user (as you). So, really, stick with the canonical ones. ;) That link I published have the safe ones.

    Sarbian, the current maintainer, also has a GitHub for Module Manager: https://github.com/sarbian/ModuleManager/releases

    I would had pinpointed you there, if Sarbian had made ModuleManager's canonical binaries available for download on his github - but he didn't. ¯\_(ツ)_/¯

    So… 

  7. About this post...

    2 minutes ago, FreeThinker said:

    Make sure when reinstalling KSPIE, you remove Interstellar_Redist.dll from all Plugin folders (both WarpPlugin and PhtotonSailor) and it should only be present in the GameData folder

    I also corrected the CKAN file for this change.

    It was my understanding that KSP 1.12 changes on the DLL loading mechanism had solved this issue...

    This is essentially what MM WatchDog prevents about MM, so what do you think to extend it a bit and check for multiple Interstellar_Redist.dll too and issue a warning if more than one is found? Ideally it should warn about its absence when it should be there too, but this is a bit more tricky (but not that much).

    As it appears, this problem is going to stay...

    1. Show previous comments  1 more
    2. Lisias

      Lisias

      Okie dokie!

    3. Lisias

      Lisias

      When a problem is found, a page can be opened after quitting KSP. 

      Since I'm coding a WatchDog for Scale_Redist too, I will send "my" suffering users into TweakScale Forum Thread, as this is usually the fastest way to the user to get help. But this also means that the user will be freshly burnt by the problem, and not rarely a bit angry on you.

      Do you want that "yours" suffering users to be directed into Interstellar Forum Thread? Do you prefer them to be directed to some other page? Or just quit KSP and after the Fatality Box and call it a day?

    4. Lisias

      Lisias

      for now, I'm sending them into your Support Thread:
       

      But I will wait your feedback before even building the thing.

  8. Found the problem on your MM patch!

    TL;DR: shove a :FINAL on the patch and it will work.

    Don't have an answer for this yet, it's working hours. I will try to explain that at night!
     

     

    1. Show previous comments  1 more
    2. Lisias

      Lisias

      errata: answer == explain!  :D

      (too much work, I pulled an all-nighter yesterday! :P )

    3. Lisias

      Lisias

      Humm... The bug is still there.

      I recompiled MM with LOGSPAM, and noticed that with or wihout :FINAL, the patch enters in a infinite loop!

      The difference is that, somehow, the :FINAL is not locking the thread.

      I think that by not using :FINAL, the patch runs on the LEGACY phase, and whatever calls the LEGACY phase locks waiting for its finish, but don't lock FINAL.

    4. Lisias

      Lisias

      I may have a good theory about what caused this problem for you.

      I will keep you informed if I find something new.

  9. About your problem described here, I suggest to republish your log on this thread below instead. 

    The maintainer is right about not being a problem on MechJeb, but I think its diagnosis is wrong and not helpful on locating the problems and get them fixed.

    We need to get people willing to help on a lot of testing to get this figured out, it's too much work to be done by a single dude.

    Let's crack this nut. :)

  10. Hi.

    This is a heads up about your issue. Please don't forget to send me your KSP.log and ModuleManager.ConfigCache AFTER updating to TweakScale 2.4.3.8 (or 2.4.3.7, they are essentially the same except that .8 will warn you if you try to run on KSP 1.8).

    This is important. If you look into the TweakScale thread, you will find  a lot of complains that ended up being thrid parties patches borking up. Some few of these patches will render your savegame useless once these one triggers the static explosions.

    I don't know if the rogue patching on your installment - i.e., the third parties patches that are bugged - will render your savegame into a fatal mess. What I know if this can happen, and only a visual inspection of the KSP.log and ConfigCache will give me the answer.

    You may want to check this link:

    https://github.com/net-lisias-ksp/TweakScale/tree/master/Extras/TweakScale/BreakingParts

    Most (if not all, I don't recall right now) of these Add'Ons are already fixed on the latest releases, but since you are using a older TweakScale release (otherwise this would not had happened), you may also have older versions of Add'Ons.

    Link to the latest post about your issue on TweakScale's thread:

     

  11. Uh… I swear we were on the Lounge, didn't realized we were on the CKAN thread. :P

    well, about this post:

    Spoiler

     

    Do you remember when this happened? It's more for the sake of curiosity, as I saw a lot of problems on Github at one time, and I curious on the matter.

  12. Hi. I got into an issue from a M3X and SME about TweakScale recently, and while (borking the :P ) diagnosing, I realized that the releases for M3X and SME are not pushed into the github!

    https://github.com/SuicidalInsanity/Stockalike-Mining-Extension
    https://github.com/SuicidalInsanity/Mk3Expansion

    There're releases for this year, but they are tagging a commit from 2018.

    The Mk2Expansion has a release for the same day of the current latest for that ones (2019/Apr), and the commits are correctly updated

    https://github.com/SuicidalInsanity/Mk2Expansion

    So I think you forgot to push the changes to the origin.

    Cheers,

    L.

    p.s.: I'll withdrawn my patches for these Add'Ons on TweakScale. Yours are (considerably) better than the ones on the distribution!

  13. Hi! Just answered your question, we posted at the same time at that time! :)
     

     

    1. Calvin_Maclure

      Calvin_Maclure

      Ha! What timing! Great minds my friend, great minds.

  14. Hi. This is a heads up about your issue on TS..

    You need to reach the maintainers of ContractPacks/AnomalySurveyor and Mk2Expansion to check that two erros preventing the creation of the MM ConfigCache. Without the ConfigCache, I'm on the dark and unable to start looking for the problems on TS.

    Fixing these two errors will also make your KSP load faster, as it will be able to use the cache. :)

    (click on the link on the top line for details).

    Cheers!

    L.

  15. Moved out of the thread to prevent derailing it :) 

    21 minutes ago, Yeet_TheDinosaur said:

    Sure thing mate.:wink:

    Wait....... Did I see you before?

    Had your KSP crashed lately? :P :D 

    1. Yeet_TheDinosaur

      Yeet_TheDinosaur

      Uh..... No. But I'm pretty sure you replied on my post.

    2. Lisias

      Lisias

      Got curious. I think it was on the Breaking Ground hype thread!

    3. Yeet_TheDinosaur

      Yeet_TheDinosaur

      Yep. I posted something about whether the ew DLC was worth the money, and youreplied.

      Thanks for tip back then ^. ^

  16. If you are interested, that fork I mentioned is

    http://GitHub.com/net-lisias-ksp/Kerbal-Joint-Reinforcement

    Read the install.md as you need to install a dependency in order to make it work.

    The Next is on

    Http://GitHub.com/meirumeiru

    I don't remember the exact URL, but this one will present you with list. It's one on the options. This one has no dependencies.

    Try both and report any discrepancies to Rudolph. This will help him to help you.

     

    edit: ugh… I managed to mistype the name of my own fork. #facepalm - I was typing from mobile

  17. 11 hours ago, Deddly said:

    The way to stop being quoted in a conversation is to stop participating in it. If you post something here on a public forum, people can and will reply. 

    Another way to prevent  being annoyed on threads in which you lose interest is to add people that insists mentioning you on threads you don't care into the ignore list using the "mention" option  - and you can always delete them from the ignore list once the heat is over.

    It's not about anger or grief - it's just to prevent receiving notifications on the mobile when you are busy trying to focus on a conversation that interests you, and this can be really annoying.

    Since I can't add you on such lists as you are a Moderator (and yeah, I understand the reasons this is the way it is), can I ask you to handle such misunderstandings in private messages in the future?

    Thank you.

    1. Deddly

      Deddly

      Adding to the ignore list also works, that's true. But you know this isn't a private conversation, right? Anyone who clicks on my profile can read and participate. That's fine for me but I'm not sure that's what you wanted. 

  18. Hi! Thanks for your help!

    1. Lisias

      Lisias

      Oh, yeah… If any reasons, your KSP locks up, there's a chance that you should kill it using the TaskManager.

      This is more a Unity/Mono bug than anything else, but whatever. The net result is indeed killing the KSP process by brute force. :/

  19. Hi! Found a typo in one of the WarpPlugin config files, and fixed on this pull request:

    https://github.com/sswelm/KSP-Interstellar-Extended/pull/261

    L.

  20. Thanks, dude. You did a hell of a work. :) 

  21. Hi. I'm the dumb-SAS that had the terribly stupid idea of deleting the CurseForge project for StageRecovery.

    I'm terribly sorry for even considering that stupidity, the CurseForge has 4 years of Project History, from the KSP 0.24.2 era! Would be sad to loose that.

    I would like to kindly ask you to lock down the project instead, and edit the front page to state that new versions will be available on SpaceDock only. I think this is a better way.

    I meant well, I was thinking on people relying on CurseForge only and that would be unattended of the change, but didn't though enough about the consequences.

    Sorry for the mess, I should had known better.

    1. magico13

      magico13

      Not a big deal, but I didn't get the message until after I had already done it. Looks like I can still access the projects so I'll try to download all the files off there just in case they get permanently removed at some point but someone still needs access.

    2. Lisias

      Lisias

      I have all the release notes consolidated on a text file, if you need it.

  22. Hi.

    Your problem is related to RemoteTech . I'm 99% sure of it.

    The MFI is just a "telephonist", it just redirects calls. Anything that goes wrong after the redirection, is due a problem on the end point. But since MFI is the one that made the redirection, it got itself involved on the stack dump.

    As a side note, I kindly ask :) to reach me here or by mail when something I wrote gots involved in the mess. It will save both of us some… Headaches. :) 

    1. Show previous comments  10 more
    2. Lisias

      Lisias

      Hummm….  I'm seeing the code that throwed the Exception, and it only runs when TweakScale finds a module called "ModuleFuelTanks" on the part.

      I'm inclined to believe that TweakScale is innocent this time. My understanding about KSP is that it throws away orphaned data - so if the vessel was loaded and that part has a ModuleFuelTanks module on it, it must have a DLL that provides such module.

      For my future reference: line 452:
      https://github.com/net-lisias-kspu/TweakScale/blob/master/Source/Scale/Scale.cs

       

    3. Gordon Dry

      Gordon Dry

      There is no single instance of ModuleFuelTanks inside my MM cache of the last session.

      I also checked all files *.cfg for ModuleFuelTanks if there is a bad config or patch that just adds it. None.

       

      And fun fact:

      After months of NRE thrown for bluedog.Saturn.VFB.MissionModule as mentioned above - it was fixed just today with such a simple change:
      https://github.com/CobaltWolf/Bluedog-Design-Bureau/commit/e35b4a13e57905146b96b66d1f3c8b3b1f246804
      :o

    4. Lisias

      Lisias

      Most of the worst problems have a simple fix! :)

×
×
  • Create New...