Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
@Destormer I considered a script that matched,maintained at given position/orientation, it wouldn't be that hard to adapt my framework to do such a thing, I just have no time for it. Try my Full Control script, it might be closer to what you desire.
my guess is it's the angular dampening response overreacting,
could be factor of gyrostoppability, hopefully that's all it is. Otherwise might need tuned in AngularDampen function but it seems I may not have a tuning variable exposed for it there.
could be lag due to updateperiod, can try increase up to 60
could be steeringsensitivity related
I don't think the alignangularresponse* PID are hooked up to this part
lowering the tick rate (defaults to 30 iirc, can go lower, like 15x/second) might help, on a server.
I've used this on several servers, personally, and it was always fairly reliable, or about as reliable as Keen VRAGE networking is in general, which isn't great, but GA seemed to handle it well enough. I don't recall any truly bizarre problems like that. Ships in general can get physics "frozen" strangely online, requiring some extra oomph on the gyros to wiggle loose of a frozen state, especially if connectors are involved.
Use a terminal Group. If you play with other ships using the script, use a different Group name for each vessel; if they all use "Aligner" default, they'll hit this same problem.
Yeah just bind a hotbar slot for Run PB with "pitchofs=90" (or is it -90?) and one for "pitchofs=0' to switch between mining and travel modes. That's what that's for!
this script can adjust the pitch tilt angle almost arbitrarily using "pitchoffsetdegrees=X", or you can use a remote control instead if your ship is strangely designed somehow.
public static void ShowFor(IMyShipController ctrl)
see where it says if (false && ....
change that to true
pick a surface number (if 1 doesn't work)
foreach (var s in Screens) Chart.ShowFor(s);
foreach (var l in Lights) Chart.ShowFor(l);
Chart.ShowFor(Scanner.Me);
Chart.ShowFor(Vessel.Controller); // disabled, no easy way to configure yet
}
Thats what I got. Im using the control seat with 5 screens. It works on my older ship with the old code but not the new one.
I might have disabled the support in Chart.ShowFor also... check there
That's funny, as soon as I disable it, folks want to re-enable it. I must spend some time on thinking up some way to configure it.
no longer claiming a Cockpit screen (you're welcome) .. can be re-enabled in code.
Probably will play a bit on this upcoming update, can work on it then.
tuning GyroStoppability might help. If it's smallgrid you can maybe increase the RPM limit. There are many settings to fiddle with.
Lazy, yes. Very. You don't even know.
if (chart != null && ctrlb != null && ctrlb.SurfaceCount >= 2) chart.Show(ctrlb.GetSurface(1));