[0.24] Gimbal Auto Trim 1.1 (Sept 2)

[dak180]

Any progress on this?

[bigdad84]

Awesome! Just came across this for the first time. Definitely going to keep an eye out for an update!

[sarbian]

I, err ... fixed it 3 weeks ago and kinda forgot to post it. 1.1 is now available. Sorry

Edit : meanwhile I forgot what was the math problem I was trying to fix. The commit show I changed some of the math, so it may work now.

A quick test worked but it may fail for some some ships config. Post those

Sarbian, the sleepwalking coder.

Edited September 2, 2014 by sarbian

[Taverius]

Tried it on B9, works great, except for having to use the stock gimbal module, which is too awful to bear, because the LERP makes response speed unusable.

B9 R5.2 will be back on KM_Gimbal, hopefully you can get it to work with dtobi's too.

[funk]

Very nice! It's a musthave mod. But I hesitate because I´m running DavonTS... though i think it doesn't controls gimbals i'm not sure if both effects each other. Is it iterative like DTS, or does it the math with linear programming?

[Starwaster]

Tried it on B9, works great, except for having to use the stock gimbal module, which is too awful to bear, because the LERP makes response speed unusable.

B9 R5.2 will be back on KM_Gimbal, hopefully you can get it to work with dtobi's too.

You can tweak that in the stock gimbal modules. It's not really documented or talked about anywhere. I don't recall the field names nor can I check on this particular computer (brand new machine; still installing things. Haven't got to developmental tools yet)

[Taverius]

You can tweak that in the stock gimbal modules. It's not really documented or talked about anywhere. I don't recall the field names nor can I check on this particular computer (brand new machine; still installing things. Haven't got to developmental tools yet)

Thank you, but I'm aware of it.

The specific values are not an issue here - I can set gimbalResponseSpeed high enough that it stops being an issue and causing course correction overshoots and other shenaningans, but at the point its also indistinguishable from disabled.

With a sane gimbal module that implements a linear response speed rather than a lerp, a much slower effective response speed causes such issues.

So, B9 R5.2 will be back on KM_Gimbal for everything we ship.

[The Pink Ranger]

I wonder if there's a way to control the craft from an engine and have the navball line up with the direction of thrust.

[Starwaster]

I wonder if there's a way to control the craft from an engine and have the navball line up with the direction of thrust.

Why would you want that when your flight path isn't necessarily lining up with your thrust vector?

[FennexFox]

I think I missed something, because this doesn`t work at all to me...

Is there any compatible issue, especially with TweakScale?

I put 2 .625m size LB909 for my OMS, out of CoM, and hit "enable autotrim", nothing happened.

[sarbian]

No that I know of. Is that the only other mod you have ?

[goldenpeach]

It may sound stupid but.... How do we use this mod?

I can't find how to activate the auto-trim gimbal

[sarbian]

Did you use the ModuleManager example patch from the first post to replace your gimbals ? (you need MM of course)

[goldenpeach]

oops...

EDIT:Can mechjeb take in account the fact that the center of thrust isn't "inline" with the rocket?

Edited September 14, 2014 by goldenpeach

[FennexFox]

No that I know of. Is that the only other mod you have ?

No, I have actually 65 mods...I downloaded your plugin, put that in gamedata folder, and made a cfg file. Isn't it right way to apply this mod?

[FennexFox]

oops...

EDIT:Can mechjeb take in account the fact that the center of thrust isn't "inline" with the rocket?

There's an extra plugin for mechjeb to that, which was made by sarbian too.

Edit: oops I confused, that was plugin for km gimbal, not for this. Anyway I think that's possible, because who made mechjeb made this.

Edited September 15, 2014 by FennexFox

[sarbian]

EDIT:Can mechjeb take in account the fact that the center of thrust isn't "inline" with the rocket?

Not at the moment. It require quite a lot of change in MJ to align with an arbitrary direction. It may comes since there was other needs (VTOLS), but not yet.

[FennexFox]

Please, give me a suggestion. I still got no effect from this mod.

As I have "Toggle Autotrim" button, SO I don`t think it`s an installation error.

I can toggle that, but nothing happen. CoT unaligned with CoM.

[sarbian]

maybe you could post a log ? I can't diagnose a bug from thin air.

See that post to see which log is useful : http://forum.kerbalspaceprogram.com/threads/92229

[FennexFox]

maybe you could post a log ? I can't diagnose a bug from thin air.

See that post to see which log is useful : http://forum.kerbalspaceprogram.com/threads/92229

Thanks, I came back with the log and unedited video.

Log here, and Video here. Video shows not working auto trim.

I wish I provide proper information. If not, please ask me to.

[sarbian]

I had a look Saturday but I could not see anything wrong. You have a lot of error related to KerbQuake so you should try without it, and you should remove the old version of Module Manager you have.

Could you put the ship file somewhere, so I can try it ?

[FennexFox]

Here is my craft. I deleted KerbQuake, Updated Module Manager, and some other suspicious mods, but it still not works.

Edit: Sorry, I didn`t list mods I used to make the craft. It uses SpacePlane+, Infernal Robotics, Aviation Lights, TweakScale. I made this to use with FAR and AJE.

Action Groups...well, 0 toggles Rapiers, 9 toggles OMEs(LV-Ns), 8 switches Rapiers and toggle intakes. Other numbers are less important.

Edited September 28, 2014 by FennexFox

[bobprime]

I can confirm that this works in 0.25. I just tried it now and it works fine. I am using an updated version of module manager. To get the modules on.

[CatastrophicFailure]

I'm getting alot of spam in the log that I think traces back to this, which otherwise seems to be working just fine. It's also causing the engines its activated on to overheat & explode (DRE) when there's no reason they should. I noticed when it's doing this, there's no info in the right-click about correction & angle, etc. Here's one of the many errors:

ArgumentOutOfRangeException: Argument is out of range.

Parameter name: index
  at System.Collections.Generic.List`1[UnityEngine.Vector3].get_Item (Int32 index) [0x00000] in <filename unknown>:0 


  at GimbalAutoTrim.ModuleGimbalAutoTrim.updateThrust () [0x00000] in <filename unknown>:0 


  at GimbalAutoTrim.ModuleGimbalAutoTrim.OnFixedUpdate () [0x00000] in <filename unknown>:0 


  at Part.ModulesOnFixedUpdate () [0x00000] in <filename unknown>:0 


  at Part.FixedUpdate () [0x00000] in <filename unknown>:0 

Entire log is about 19 meg so I'm not posting it right now. I'll try and get a shorter one when I get home tonight. Up till now this plugin and that engine were working just fine.

ETA: On second thought, here it is, with my condolences:

https://www.dropbox.com/s/gpbt86d35obo611/output_log.txt?dl=0

Edited October 13, 2014 by CatastrophicFailure
linkey

[Ruedii]

Thanks for the great plugin. I hope you get it working with other gimble plugins, as I love Tweakable Gimble, but I'd rather have this.

Finally, I don't have to line my engines perfectly center, and my plane will still work! Finally, I can make more conventional jet designs!

BTW, could you make an even better version that adds drag compensation? (You'd have to use a different module version for FAR/NEAR than stock for this, but it's doable.) For now SAS should work for most conventional designs on this.