ruprecht Posted August 19, 2009 Posted August 19, 2009 (edited) I thought I'd start this thread to let ED know what we as cockpit builders would really like to see in their sims. Please try to keep it on topic and constructive, and please limit it to items specifically for cockpit builders. Other issues with the sim (trees, AI etc) have been done to death elsewhere. We are hoping that ED recognise that though pitbuilders are a minority group when compared to the wider user base, we are their most dedicated and passionate customers. My starting requests: - Discrete keymappings for every switch and knob position. Cockpit builders need one keymapping for Gear Up and one for Gear Down, not a single "toggle gear". Toggles lead directly to switch synchronisation problems. The rotary on the Targeting Mode Control panel is a classic example - only two commands, Rotate Left and Rotate Right - for a five-position switch. It doesn't matter if they're left unmapped by default, at least please give us the option to use discretes if we need to. - Every indicator state (lamps, text displays, lit pushbuttons, warning lights etc) available in Lua Export. - A10C MFDs available for separate display. I assume, given the excellent inclusion of Abris/Shkval export in BS, that these will be included in the initial release. Here's hoping that the Thrustmaster MFDs will include OLED/LCD displays and we'll have ready-made MFDs! - Easy switching of push for power and pull for power on HOTAS. Many of us elect to pull for power with the HOTAS throttle in BS, as this more closely replicates pulling on a collective. However on the A10's release, we will want to push for power again. If we have to go deep into the DCS controller options to do this every time we switch aircraft, it will get painful. Would it be simple to include a keymapping for "invert throttle" so that we can map it to a switch? Edited August 19, 2009 by ruprecht DCS Wishlist: | Navy F-14 | Navy F/A-18 | AH-6 | Navy A-6 | Official Navy A-4 | Carrier Ops | Dynamic Campaign | Marine AH-1 | Streaming DCS sometimes:
Jasper2610 Posted April 30, 2011 Posted April 30, 2011 Discrete keymappings for every switch and knob position. I also would love to see ACTIVATE and DEACTIVATE key stroke options TehgRa (n-TehgRa-tea)
m0jo Posted April 30, 2011 Posted April 30, 2011 - Every indicator state (lamps, text displays, lit pushbuttons, warning lights etc) available in Lua Export. The function EKRAN:get_actual_text_frame() should be implemented for every display inside de Ka-50 and the A-10, including for example the PVI-800 7 segments display and the CDU on the A-10. - Correct FFB on the pedal/yaw axis with a FFB wheel or joystick to support force trimming like the cyclic with a MSFFB2. The yaw FFB is somewhat supported on FC2, the pedals are shaking in overspeed situation but with the Ka-50, the FFB wheel is only used/detected as a normal non-FFB axis.
Recommended Posts