Jump to content

Search the Community

Showing results for tags 'flight controls'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Welcome Aboard
  • Kerbal Space Program 1
    • KSP1 Discussion
    • KSP1 Suggestions & Development Discussion
    • KSP1 Challenges & Mission ideas
    • KSP1 The Spacecraft Exchange
    • KSP1 Mission Reports
    • KSP1 Gameplay and Technical Support
    • KSP1 Mods
    • KSP1 Expansions
  • Kerbal Space Program 2
    • KSP2 Dev Updates
    • KSP2 Discussion
    • KSP2 Suggestions and Development Discussion
    • Challenges & Mission Ideas
    • The KSP2 Spacecraft Exchange
    • Mission Reports
    • KSP2 Prelaunch Archive
  • Kerbal Space Program 2 Gameplay & Technical Support
    • KSP2 Gameplay Questions and Tutorials
    • KSP2 Technical Support (PC, unmodded installs)
    • KSP2 Technical Support (PC, modded installs)
  • Kerbal Space Program 2 Mods
    • KSP2 Mod Discussions
    • KSP2 Mod Releases
    • KSP2 Mod Development
  • Community
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
    • KSP Fan Works
  • International
    • International

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


About me


Location


Interests

Found 4 results

  1. My suggestion in a fly-by wire avionics system, and I'm not referring to SAS. It could be implemented into stock or made into a mod. This way an aircraft with, say, a broken elevator or missing canard, could fly. Heck, if the system were properly implemented, you could fly an aircraft that is facing backward without the control surfaces going the wrong way, or even fly an inherently unstable aircraft! Some background info (especially for those who don't know what an actual fly-by wire system is): From Wikipedia TL;DR: Instead of the aircraft responding to the stick being pulled (or in this case [ S ] being held) by deploying elevators, the aircraft just calculates what control surface movements would actually accomplish this pitch up. Here's a hypothetical situation to demonstrate what I mean: You're flying an F-16, but (oh no!) your right stabilator isn't moving, no matter what you do. Now, whenever you try to pitch up, it also rolls the aircraft left. A fly-by wire system would accommodate this by also using the ailerons to stop the roll before it even happens. Another example: you're flying an Aeris 3A (modified to be supermanueverable), and now after pitching up to vertical, you have stalled, but your attitude is still nose straight up. You try to pitch back, and the canards face leading-edge up and the elevators face trailing-edge up. When flying normally, this would do the right thing. But because you are falling backward, it causes a new pitch down. Similarly, roll is also reversed! To simplify it further, the fly-by wire system makes it so that the aircraft does what it thinks you want, instead of what you asked for. KSP could gain so much from a fly-by wire system. Even if you don't fly aircraft, it'd still be useful. Vertically landing rockets would be so much easier because you wouldn't have to fiddle with a negative authority limiter on control surfaces.s2
  2. Had an idea for a new set of SAS buttons to add to the current set: Flight heading Buttons. Currently you can set your SAS autopilot to prograde, normal, etc., but it would be extremely helpful to be able to align your craft with the compass headings. 90°- (east) 0° - (north) 270° -(west) 180° - (south) While it would have many helpful uses, I currently have the greatest need for it when launching into orbit and want to keep my heading at exactly 90°. The only way to do this currently is to manually keep your marker lined up with the compass. The prograde marker helps, but constantly changes heading while under acceleration.
  3. Do you hate it when your craft is tugging along on SAS and you want to correct the course a bit? You touch pitch controls and it gets all wobbly. There is a simple solution to your problem: SAS should not control the control input, but work via the TRIM settings. You control input would be combined with the TRIM and you would have perfect controls even with SAS activated. Better yet: Allow the TRIM settings to be kept when leaving SAS (maybe with a modifier key or so) and move your craft from SAS to full manual control without even the slightest bump. Why we should do this? Because usually it is done like that. Your input is combined with stabilisation/trim. If it is still unclear what I mean exactly, move down three posts. User OHARA does explain it better!
  4. I Have a Saitek Cyborg Evo Force in an unmodded install of version 1.3.0.1804. I can map all the joystick buttons, the thumb hat, and pitch & roll but not throttle or yaw. These functions work in the control panel but KSP seems to not detect them at all. Happy to provide more info if required. Also does KSP support force feedback? I have read that afbw mod may solve the issue but it seems to be no longer available. Thanks in advance
×
×
  • Create New...