Ziw

I've spent some time writing up some UI helper classes while waiting for pre-release, and once you get the hang of it it is actually not that hard, but to simplify your main code you need to create at least 1 more abstraction layer for UI, like your own Window, Button, Text and other primitives. Once I get home from work I can try to arrange a github repo with all that I've come up thus far so everybody can help build a proper UI library for modders.

Is adding them via module manager config possible?

There is a link to the latest beta in the first post of his thread and it works perfectly fine in 1.0.5 There are some nice wheels, even very big ones as well somewhere in his pack.

There is a problem with symmetry in legacy Hinges. Please try this part pack from Zoduis - [WIP] MSI's Infernal Robotics - Model Rework (v02 Pre-Release Beta) His pack does not have Gantries, but it has some very nice and sturdy parts.

This is strange, so you're saying that some parts set to be inverted in editor are not inverted when you launch? Maybe post two pictures of your craft with IR window open from SPH/VAB and on the launchpad/runway so I can better understand what is happening? P.S. And welcome to the forums!

These are harmless. If you dont use these parts, you can even delete them.

Not yet, but it might be a good idea for IR. I've added it to my possible new features list.

it theory yes, implementation might be lacking, so I would appreciate your help in testing it out. I have some ideas as where to look at in the code already, all I need is some time to tinker with it, which I am lacking at the moment.

Just don't use ATM or set it to exclude IR parts. IR parts use texture sharing, so they use minimal RAM.

emm, the Lock Servo option should work exactly as you described, you can even put it on the action group.

You can scale up the parts manually by creating a copy and editing the part.cfg (you need to edit the scale factor)

Please try using Zodius reworked parts (linked multiple times here), they are reported to be a bit less wonky. Also you may want to scale up some parts, because original ones are not designed to hold such weights.

Hi, long time no see Here are the changes I made: https://github.com/MagicSmokeIndustries/InfernalRobotics/pull/74/files#diff-e2ca92d8a9e6bebed32c75d95e97a475L133 I moved the edge case check after the newVel is calculated and performed the check against it versus raw maxDeltaVel, which was too high in @allmhuran's case As for option to disable the acceleration completely - I'll see whether it is possible to untie interpolation easily.

Great. If you come up with a better algo feel free post here or as a github issue.

Try this build (re-uploaded the new dll) https://github.com/MagicSmokeIndustries/InfernalRobotics/releases/tag/0.21.5-pre

he uses mavDeltaVel (derived from max acceleration) instead of current velocity, I think that is where the problem lies

You see from the line I linked that @pellinor left a very generous margin for edge case - I can lower it and give you a custom dll to test out

There is also a problem of a Physics tick https://github.com/MagicSmokeIndustries/InfernalRobotics/blob/develop/InfernalRobotics/InfernalRobotics/Command/Interpolator.cs#L133 As you see here there is plenty of clamping but i believe the problem is with this 10% overhead, which gets noticeable at you level of acceleration

Interpolator that accounts for acceleration has an edge case when servo approaches target position. Its not my code, but I'll take a look. For now you can try lower acceleration.

Good news, with the help from other kOS devs I've found the fix. It will be in the next kOS update.

There were so many changes to kOS since my PR was submitted... I confirm that I have reproduced the bug and it's not IR bug, because IR UI still moves the part properly. Looking into integration code.

All this indicates a problem with servo object pointing incorrectly somewhere inside kOS integration I feel like 0.21.4 dll will work the same, so I need to look deep into code. Will revert as soon as I find out anything.

Yes, that is my concern. What puzzles me most is the absence of kOS errors if its the case. That is why I want the log, maybe there is something there.

You said reverting to launch did not help? what if you scrap it and launch once again? Please do 2 things for me: test with 0.21.4 release dll just to rule out the simplest possibility (though 99% it won't help) and give me the log file (KSP.log should be sufficient)

@Tirehtoori R.I.P, @ZodiusInfuser and everyone else willing. Please check out this new build with the bugs you reported fixed. https://github.com/MagicSmokeIndustries/IR-Sequencer/releases/tag/1.0-beta1.2