Sprool

Did you sandpaper the LEDs? I found it helped a lot to make it more omni-drectional, just to rough oup the LED surface to a light cloudy matt, then some decent curves which took ages to get 'just right'

this is really great work, you got skillz !

dcs update / repair resets all default luas to...err...default. ive had to redo all my master switches. Question is, can these files be put into saved games/dcsopenbeta and still work ok, to avoid being overwritten again in the future?

My bad-the info to edit is not dcs lua but in E:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Ka-50\Input\ka-50\joystick\default.lua file. (Obv. example for KA-50 module) The Teensy board (and Micro Pro) are tiny, 35 x 18mm so should give you no issues with limited space. The coding works using a button matrix, so if you want 32 switches you dont need 32 separate wires and one ground, you arrange the switches in rows and columns like a keyboard is wired, 6 columns and 5 rows gives you 30 buttons and you only need a wire for each row and each column; 6 + 5 = 11. The youtube build video explains it really well.

doesnt F8 give you the target view? May need to have aircraft locked up first?

Yes its a really slow descent, easier just to push collective down. I assume it will only work while in a stationary hover then, no forward or sideways velocity?

Ah ok thanks, so when you release the switch it stays at the current altitude? And does it only work when in a stationary autohover?

No struggle - what a twisted poll!

Well said, I'm with you on that. More than enough to fix with existing content.

Looking for some info/tuorials or explanations about the descend mode switch on the collective, how to implement, what it does (I'm assuming a controlled descent for landing) and how to use it. Currently pressing D just springs the switch back up to centre position again.

just google capt zeen helios f-18

Theres a free flight option in quickstart for nearly every aircraft.

is this any use? http://www.captzeen.com/helios/F18.asp

Thanks - I thought it was enough just to comment out the countries choice in the lua description, which I do manually for the liveries I want to use, only its not working for the ka-50, - but isnt that only what this mod does anyway?

I have 4 rotary encoders now working really nicely, in a matrix wiring button board, using code adapted from a race sim button box build. It all works fine in DCS - 32 buttons, 4 rotaries, but I had to edit the code to work with my Teensy 2.0 board. I'll share the code used if its any use to you, its the only code I managed to give good stable rotary encoder results with.

Bought the KA-50 a couple of days ago, I found thees loads of livery folders (around 30) in my DCS Bazar folder but only options for 6 or 7 to use in game. I tried copying some of the folders over to my saved games/liveries/ka-50 folder but they still dont appear for me to use as a rearm/refuel option - it works for other aircraft but not the KA-50. How can I access them to allow client use in-game?

pic

Ive just completed a button box based on this - and adapted the code for use with a £16 Teensy board. Works great - 12 push-buttons, 5 on-off-on momentary switches, 4 rotary encoders all on a matrix wiring system - good for improving your soldering skills

Rotary encoders need a lot more coding to get them working sweetly. They are best used (IMO) as controllers for functions allowing increase/decrease level (instrument lighting, volume level) rather than axes. Pots are easier to use and better suited to axes. DCS allows either/both for many functions. I have wired up 5 on-off-on momentary switches in my buttonbox array, so for any control allowing an up or down increment they work fine, eg: FLIR in Hornet, Dispensor switch, flaps, the middle off button will remain passive with momentary switches which DCS prefers as they are more like standard joystick switches.

Heres some code from a guy making a button box for racing sim, with 4 rotaries, you can see theres quite a lot of coding needd to get them to work ok I finally finished editing this to work off a Teensy 2.0 this evening, I have a 4 x 6 button matrix and 4 rotary encoders all working now. Using one of the buttons as a modifier allows me to give dual functions to each rotary encoder (mostly for lighting levels & radio vols). The code irons out jitter, bounce and latency so they work really smoothly with Windows Joystick COntroller. Only thing I didnt end up using is the push-button switch functionality of the rotaries. rotaries.txt

Yep, C:/users/yourname/saved games/dcs.openbeta, I dive in there so often I have a shortcut to it on my desktop ;)

yep thats a very poorly description.lua file! can you post a screenshot of the 4 main texture files you used - F18C_1_diff, F18C_2_diff, and the 2 corresponding RoughMet textures?

Can you get windows joystick controller to recognise the rotary encoders cleanly without chatter or interference?

Great simple and effective idea!

In your saved games folder there will be a file called options.lua in the config folder. Copy that over to use in dcs.openbeta and it should mimic the display settings you had before.