Brun

Would be good to have multiple presets, and the ability to select from those before starting a mission without going into the options.

It was my understanding that these effects were of a long term nature rather than an immediate one. There's currently no practical way to model such things in DCS.

Save that in a file with the extension .obj and it will work fine.

As per today's newsletter: "DCS: Supercarrier will be available for pre-order on January 17th with a 30% discount and will deliver as an Open Beta by the end of Q1 2020. Owners of DCS: F/A-18C will receive a discount when purchasing DCS: Supercarrier"

No plans to, sorry.

Neither am I :)

Hit alt+return after dcs launches to make it full-screen and you shouldn't lose focus.

Appreciate that this sort of thing is difficult to implement with the limits of our hardware, but if the throttle levers are all the way back I'd prefer the engine to go to ground idle as soon as there's WoW, assuming that's what governs it IRL.

Amazing to see what people are doing with the displays. Never even imagined this when I started it last year.

I don't think its a bindings issue. Rather than using the IDLE/OFF binding, mine is set up via target script editor to fire - for example - RALT+HOME when the left lever is moved from OFF and RALT+END when it's moved to OFF. This is working perfectly, it seems to be the sim that is not responding. I'll try using IDLE/OFF instead and see if that helps, but the fact that several people are suddenly having the same issue suggests something's changed DCS-side.

This I started with a BBI-64, but had a spare BU0836A knocking around so I decided to try that for the pots. Means my UFC needs two USB ports, but I've used the spare inputs on the BBI-64 for landing gear/hook levers and am in the process of adding a master arm panel. The pots I used were these and despite the cheapness and crap photos, they're great.

They look very similar to the ones I used so should be ok. The ones you link so say they're 'non-indexed' which I guess means they don't click as you turn them, which makes sense for this applcation. The ones for the COMM knobs need to have a push-button function. To be honest I found the encoders awkward to use. Seemed you have to turn them quite slowly for each click to register, and there's a large disparity in 'turn-rate' between the physical and virtual knobs. I ended up ditching mine for pots and am very happy with the result.

Description on the website is wrong.

Bear in mind that if using encoders, a BBI-32 doesn't have enough inputs for the whole UFC. By my count it needs 40.

Reaching for the master arm switches before remembering you need the mouse gets annoying after a while... In a break with tradition, it's on shapeways already - Master Arm Panel and the OBJ can be downloaded here. Switches: Master Arm, A/A + A/G (x2) and Fire Ext. I kept the mounting fittings generic, not entirely sure how I'm doing that yet. The inserts are M4, but I don't have a link to the ones I ordered and can't guarantee how well others will fit.

Something like this happened to me a few days ago. It was a cold-start mission and the engines both started fine, but after landing neither would shut down. Never thought to try the keyboard before ending the mission. Will check bindings, but I certainly haven't changed anything recently.

Funny you should ask this now, I recently decided I couldn't put up with the crappy switches anymore and - rather than risk pot luck - went with the ridiculously expensive option as discovered by @Vikhrs... https://www.mouser.co.uk/ProductDetail/nkk-switches/kb15skw01-a/?qs=EIJ16CYJdOv2DMeOYQw7Ig==&countrycode=US&currencycode=USD Worse was to follow cos it turns out they don't react well to heat and I actually killed two of them with my cack-handed soldering. Unfortunately (or not, for yuour wallet) it looks like they're out of stock at the moment, and also marked as EoL. Maybe NKK can tell you if there's a replacement? In other news, I have another Shapeways thing on the way. Should hopefully arive Tuesday...

In which case I was mistaken :) And that HUD tape thing does ring a bell.

Hornet is just a single-stage trigger, unless I'm mistaken. I would guess the second detent is used because it's the same button for firing a weapon as previous aircraft such as the Warthog. It also requires a more positive action than the first stage, which may prevent accidental release. I've mapped the trigger to the first stage, simply because it feels weird to pull 'through' one switch before activating the trigger.

I second this.

Also known as the speedbrake switch.

Presumably it's because the Hornet's gear itself is very draggy. Additional air resistance is unnecessary. As far as I'm aware you can still extend the airbrake with the gear down, but it requires holding the switch in the aft position.

Weird that there's a default binding for speed brake Retract/Off but not one for Extend. I added the following (changing the down value to '-1.0') and am happy to report it works as expected... { down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = -1.0, value_up = 0.0, name = _('Speed Brake Switch - EXTEND/OFF'), category = {_('Special For Joystick'), _('Throttle Grip'), _('HOTAS')}},

I'm trying to do this for the Anti Skid and Hook Bypass switches (using the Fuel Norm/Override switches on the Warthog throttle). Anti Skid works fine, but Hook Bypass simply toggles between Field and Carrier each time I turn the switch ON. Any ideas what's wrong here? { down = gear_commands.AntiSkidSw, up = gear_commands.AntiSkidSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Anti Skid Switch - ON/OFF'), category = {_('Specific switch abstraction')}}, { down = cptlights_commands.HookBypass, up = cptlights_commands.HookBypass, cockpit_device_id = devices.CPT_LIGTHS, value_down = 1.0, value_up = 0.0, name = _('Hook Bypass Switch - FIELD/CARRIER'), category = {_('Specific switch abstraction')}}, Also, what does orange indicate in the input editor? It's actually the Anti Skid binding which is orange but that's the one which works ok.

Was doing traps last night. No issues using missions that were created many months ago.