Sprool

Great, thanks - found it - I was looking in the main config folder :/

On the early slopes of the learning curve here so thanks for your patience. I have a teensy 2 board and a load of pushbutton switches working ok in game but have 4 rotary encoders (with push-button switch facility) to control cockpit stuff like lights, radio volume, etc. I can get windows game controllers to recognise the Teensy board and the rotaries but they are unusable as theres so much 'chatter' when they are turned they cannot be mapped within dcs. On some of the example programs in Teensy/Arduino they work fine and are precise but I cant get them working well enough to use in game. Maybe I'm lacking the right code or the wiring is not right? Any advice/help gratefully received.

My default.lua for the Hornet does not have any mention of iCommandEnginesStart (or stop) - can I confirm location of the original default lua file to edit?

No thats very useful to help adopt the right terminology when asking techy questions ;)

I read late last night the encoders accuracy is much better if the 2 sensor pins A & B (to detect clockwise or counterclockwise rotation) are wired into the controller board pins that have interrupt capability - on the teensy 2.0 thats pins 5 to 8. If there's not enough pins available (ior too many rotaries) then you can get 2nd best performance by wiring one of the rotary pins to an INT pin, the other to a standard analog pin. If youre just doing the knob for lighting level or radio volume then they dont need to be super-accurate. Having just started playing with R/E's on a teensy 2 board i have same issue with too much chatter & interference when buttons are picked up in the windows game controller. Maybe I need some better specific code

You sir are a star - thats exactly what I want to achieve, a standard 2-pole on/off switch (not a momentary switch) for the quick start.

@LeCuvier I'll want to add it for the F-18, Yak, Huey, BF109, P-47, F-5e, then a different combo for the Flaming Cliffs 3 planes that dont have the same autostart

Is it possible to assign the (cheat) quickstart keypresses (using LWin+Home) to an on/off toggle switch? I cant find ref to in in the controls/keyboard lua?

My control config files are kept in user>saved games>dcs.openbeta>config>input, not the main DCS directory, does that mean they will remain safe and untouched when the next version emerges? Other settings in there (skins, aircraft mods, helios, srs, etc.) seem to remain intact.

I think I found the info I was needing: https://forums.eagle.ru/showthread.php?t=89226, Dcs needs some lua code editing. Virtually all joystick buttons are momentary, they dont stay switched on, DCS needs to be told some switches are going to stay open, so you can use standard 2-pole on/off switches.

I'm going to have a go at putting together a switch/button box using the Teensy 2.0 interface to USB into DCS. Thinking of one potential problem which is all joystick buttons are momentary push or toggle switches. How about if I add a few straight & simple on/off switches, how can I tell DCS its not a momentary switch? Esp for turning on power, starting engines, that sort of thing?

its a safety feature to stop it burning out

A-10 is a complex one to skin, lots of separate texture files that need to be matched together seamlessly, lots of hours work, good luck with your request. Note: A-10A and A-10C has same exterior model so skins are same for both.

dud normally means fuses not set

doesnt the zoom function change FOV? (Mouse wheel)

Interesting info, I set up new snap views + default front facing with tweaked FOV yesterday for 10 aircraft, using the quickstart instant action missions to get quick access to the planes, then was totally confused as to why when i flew other missions, the settings were lost. Ive also reset views in my own missions but they dont stay saved next time I jump in. Frustrating.

Yep been round in circles through those threads and tried a couple of modified luas but still I cant produce anything resembling a nice semi-gloss bare metal look.

I keep trying to shield the on-screen DDI from the daylight with my hand over the monitor. Not very effective and the kids think Ive gone soft in the head :)

Huey Time Trial racing around Calais

if you go the freepie rout i can send you the script i use for the korg nanokontroller to see how it works

With the aid of 2 small free programs I used a Korg nanokontrol midi controller as an inexpensive way of getting an additional 8 sliders, 8 rotary axes and 35 buttons all to map, using vjoy and freepie. Works fine and probably 1/10th the cost of a dedicated flightsim unit. Took a couple of hours to work out how to get the program talking to the joystick emulator. https://forums.eagle.ru/showthread.php?t=259519&highlight=midi https://forums.eagle.ru/showthread.php?t=221268&highlight=midi Even without midicontroller, vjoy is worth downloading and using (its free) as it can enable multiple rotary axes to work off single controller, which DCS setup doesnt permit under normal circumstances, eg: I use to control all the lighting knobs in the F-18 or Huey simultaneously by mapping to a single spare rotary axis on my hotas.

Happens quite often for me. Sometimes I do a ctrl+alt+del to end process then boot up dcs in admin mode. Sometimes it works ;)

in saved games/dc.sopenbeta/config folder is options.lua. Here you can reset graphics & displays, monitors, etc. Good to save a backup copy when its back to normal.

appreciate the link but its a pain replacing a texture parameter when you cant then pass the multiplayer integrity check :( This is stated in the read-me.

I'm after a nice bare metal Huey skin, not high chrome, just reasonable gloss like the ones you can get for the F-86. I'm ok editing dds and luas, and have the unofficial RoughMet patch installed, (got a lovely semi-shiny bare metal skin on an F-5 now) also an edited json file, taken from one of the texture threads on the Huey, but I cannot seem to get a reasonable bare metal skin effect. Any ideas or pointers please?