Rudolf Meier

Sorry for my late reply for the request to add targetting and autocapture to the Berthing Mechanism. But... this is intentionally not included. I thought about it a long time and for me, the BM is not a docking port and just something you use together with a robotic arm (or similar). That's why I think it shouldn't have it.

unfortunatelly not... I tried something with the version you saw on Youtube... but, it's not good enough for what I wanted to achieve (the idea is a dead end which cannot be improved... at least one of the two parts) and that's why I went back to the drawing board and never built a solution that could be distributed... but, I hope to find some time soon to implement the new idea

unfortunatelly not... I tried something with the version you saw on Youtube... but, it's not good enough for what I wanted to achieve (the idea is a dead end which cannot be improved... at least one of the two parts) and that's why I went back to the drawing board and never built a solution that could be distributed... but, I hope to find some time soon to implement the new idea

Just for information: Next has been redesigned a while ago and offers now settings (in the difficulty settingscof the game). The main idea behind it is to fix the game inaccuracies and to make auto-struts obsolete by replacing them with an automatic fix. In case of problems with some ships, tweaking the settings can help. (But for ships a little bit crazier, it could also help to mix it with autostruts... or real struts, which I think are simply necessary for some constructions.)

try and tell me what you think

only in flight... in the VAB/SPH the game uses a different camera and I couldn't find out how it works until now

no problem, I'm glad to see that there's some interest in this mod... I hope this mod gets a bit more popular soon... and by the way, it also uses the "DockingFunctions" which is also a library to do docking completely without stock functions (and thus without all the problems it has)

sure... I did build for example patches for HabTech2 and htRobotics ... maybe that's a starting point (it seems, that they are not yet in the latest release by the way... don't know when there will be a new release) or, if you still have questions, I can also try to create a little documentation (which is planed anyway, but I thought, maybe I'll wait until I have finished all my tests... and then I ran out of time... but I'll do it somewhen in the future... especially now that it seems to be clear, that we won't see a shift towards KSP2)

no, it's not, but it is more a mod for other modders to add it to their parts... that's why I don't have much news to post... I can help building MM patches or stuff like that or modify it in case someone wants more features... but in the end it must become popular with the part makers

I will look into it when I have time and fix it... thanks for the report

currently not, because the limits are no axis but fields... all you can probably do is turn them on and off

I am sorry, but I checked this and here on my computer it shows all the axis (about 25). And this has been added about 5 years ago (or even earlier... I did only go back 5 years).

It should be compatible... I don't know why it doesn't work. I will try to find out what's wrong...

Well... that's true. But: What they should have done and haven't, is something you can see without playing the game. And this is create a solid new foundation. A stable and reliable foundation. But what they did is create some fancy graphics, a poor performing system and they brought back problems of KSP1 (wobbly rockets for example). And that's where my frustration comes from. But I know, that in such projects you often have customers who only see what they can see... and that's what's on the screen. For every new Windows version almost everyone is talking about the start menu, the icons and how good the browser is. But that's not important. The most important thing is how stable it is. How performant it runs and what driver architecture it offers. Sure, only 1 out of 10'000 speaks about it. But that's what matters! ... a shiny new car is not usable if the wheels fall off when you go into a turn of more than 5° ... and here we have just this: The foundation seems not to work (after 5 years or more). And that's something you cannot fix anymore. Try to swap out the foundation of a house after you moved in.

That says all... The software project becomes unsupportable, if version 2 of it is in alpha, at best... after 5 (7?) years of development. No idea why this should be so hard (and I am developing software for over 20 years now... so I know what I am talking about). ... I think one of the main problems today is, that today we have "meetings" and no solutions... we try to be "polite" and not address what is crap... and that both developers and managers don't try to achieve a goal but simply maintain their reputation!

In general you could download all files and reinstall them from Github, or download only the Patches folder... this might work as well. I personally did a full reinstall from the latest state on Github.

I already made them... they're online here: HabTech2/GameData/HabTech2 at master · benjee10/HabTech2 (github.com) But it seems that Benjee didn't release a new update since then. (By the way -> I did also modify the existing ones which were more for the old versions ... and I also added files for other mods that I made like the Connection System and DockingPort Next and those things.)

Looks like the Canadarm2 servo for me. This one should already have the MM patches for IRn. ... if it doesn't work, then my question would be "What is it? How did you get/install it?"

No, that's a bug. But it seems you're the first one to detect it. During development the mod was named "TrunnionPort" and then it changed for the release to "PayloadRetentionSystem-Next". But it seems that I forgot to modify the patches for HabTech2. ... thanks for the report

For the payload bay you don't need patches. Simply put the latches into the bay (use the attach nodes to put the latches into the bay). To see how you can add pins to parts, you can use the patches in HabTech2 as examples. You can then play with the settings in the VAB to find the correct positions.

That is a known problem and will be fixed in the future... at the moment I cannot do it myself, because it is a problem with the model files and I don't have them. But I'm in contact with the creator of them.

Sorry, my explanation wasn't detailed enough, that's true. The autostruts are spanned from a part on one side of the joint to a part on the other side of the joint (or directly to the joint from a part on the "lower" side of the joint). This is what causes the locking of the joint.

that's what I expected sound like overlapping parts... how did you dock and undock? which modules and mods did you use? Let me give you an example when I last saw this problem on one of my missions... when I tried to bring the S6 module into space, I stored it in the payload bay using the payload retention system mod. But after undocking it from the shuttle, the trunnion pins did overlap with the shuttle and I got this problem. The solution was to place the ports higher up in the payload bay so that no overlapping occurred anymore (the S6 is too large to fit correctly into the payload bay). An other problem could be, that your arm is clipping through a part and after changing the way of how it is all connected (dock, undock, redock), suddenly the colliders get treated differently and you have a similar problem.

In every case I know of, the problem were the Autostruts. In case of wrong settings, they don't respect moving joints and make them unusable (also stock robotic joints). A special problem is, when you have joints between legs or wheels and the heaviest part of the ship. In this case you cannot do anything againts the problem (except use a mod... but I don't know which one solves this problem... I only know, that my mods don't handle it... it's a case that's simply too rare... but, maybe I'll do something some time...) Reaction wheels? SAS?

thanks... I never really worked with them, that's why I never remarked this. Almost everything of IR has been modified from original IR to IR Next... except the Foldatrons... until now... I will take this on my list and fix it in the next update.