安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
@Teeege - Try setting the "ForceCockpit" variable in the config to your main control block, and check if you have any remote control blocks or other flight controllers facing the wrong way.
@Andywht - No, there's no way for the script to know the altitude of Water Mod's sea level, unfortunately. It's always going to be off. I'll consider putting a constant offset into the config.
@dga8705 - I think what Kana did was set the absolute limit on roll and pitch to 0 and left it to only control the yaw. Look for === AUTOPILOT LIMITS === . The reason it might be rolling is to correct any sideslip. If you're moving very slowly, any sideways motion will make it roll hard.
It is Roll when I use modded cockpit & gyro (Consty's pack), and Yaw when using vanilla blocks
running with no argument overrides the gyro without doing anything (much like cruise mode), and it throttles away without changing direction when try to land
It seems thruster override is okay but is unable to control gyro
Property Pitch is not of type Single, correct type is Boolean at Sandbox.ModAPI.Interfaces.TerminalPropertyExtensions.Cast[TValue](ITerminalProperty property)
at Sandbox.ModAPI.Interfaces.TerminalPropertyExtensions.SetValue[T](IMyTerminalBlock block, String propertyId, T value)
at Program.æ(IMyGyro Q, Double Í)
at Program.nj()
at Program.Main(String ŋ, UpdateType Ŋ)
Property Pitch is not of type Single, correct type is Boolean at Sandbox.ModAPI.Interfaces.TerminalPropertyExtensions.Cast[TValue](ITerminalProperty property)
at Sandbox.ModAPI.Interfaces.TerminalPropertyExtensions.SetValue[T](IMyTerminalBlock block, String propertyId, T value)
at Program.æ(IMyGyro Q, Double Í)
at Program.nj()
at Program.Main(String ŋ, UpdateType Ŋ)
an inclination greater than 0° and less than 90° is a prograde orbit.
an inclination greater than 90° and less than 180° is a retrograde orbit.
an inclination of exactly 90° is a polar orbit, in which the spacecraft passes over the north and south poles of the planet; and
an inclination of exactly 180° is a retrograde equatorial orbit."
I would like to have a request for implementing Inclination handling.
"he inclination of orbits of natural or artificial satellites is measured relative to the equatorial plane of the body they orbit if they do so close enough. The equatorial plane is the plane perpendicular to the axis of rotation of the central body.
Inclination Hold. Holds current inclination.
Inclination xx turning to xx inclination. I kindly ask you to implement these functions if you have time and motivation, also, if not too big hussle.
@Khazul and @PanzerScorpionT I'll put your suggestions on the list. Been away for a while but I'll see what I can do.
I do have a possibly dumb question about it however. After looking at the in-script documentation I can't find a way to engage the autopilot for the first time using whatever heading i'm currently facing. The result is that I either manually run a command using my exact heading (eg: 287,2000,60) or I wobble all over manually dialing in the heading, then the altitude and then the speed.
I'm looking for some way to basically use the [hdg] tag from the LCD's but in an argument passed to the programmable block. (eg: [hdg], 2000, 60) My goal is to make takeoff's a single press affair.
Any light you can shed for me would be most appreciated. Thank you, and again fantastic work!
dahm this script be bussin'
Could I suggest an alternative setup?
Tag two blocks on the center line with [Runway Start] and [Runway End]. For eg, I could tag a couple of runway light blocks and use the locations of those directly.
If it's having trouble establishing a glide slope on the landing, you might want to increase the LandingFinalApproachDistance, to give it more time to settle. There is also a change note about the landing speed about 3 weeks ago.
// List of blocks to use for display.
// Block's Custom Data controls what is shown. See below.
string[] Displays =
{
"Fighter Cockpit",
//"LCD Panel"
};
I agree that one should be able to start the script without having to control a cockpit or remote block on the same grid.
I already have single thrust, winged UAV's that can auto take off and do task's at the press of a button. Having them be able to manage their own landing task initiation would be pretty sweet for my automation chain.