skypickle

yes, i was trying to avoid a rotary encoder but it looks like that's what i'll need to do.

I am running the latest openbeta of DCS. I have a TotalControls button box. I also built my own button box with two controllers in it. One controller (named Arduino Leonardo)runs 6 dials on the left side of the box and the other controller (named Serial-Keyboard-Joystick) runs the 6 dials on the right side of the box. (I needed two controllers because windows limits the number of recognizable axes per usb device to 7) These are my bindings for the HUEY axes: You can see the left dials run the lights and the right dials run the radio volumes. But the intercom volumes are not assignable for either of my new controllers. However the Total controls box allows thesde volume axes to be defined. To better understand what is going on, I decided to make a virgin install of DCS and also have a separate saved games entry for it by modifying the dcs_variant.txt file. My regular DCS game has a dcs_variant.txt whose first and only line is 'openbeta'. The new virgin DCS instal has a dcs_variant.txt file whose first and only line is 'pure'. This way I can keep all settings separate. After running the new virgin DCS open beta install I have a new folder in my saved games folder titled 'DCS.pure'. I still have my usual 'DCS.openbeta' folder. This is what the bindings for the Huey axes looks like for the 'DCS pure version': Many fewer axes. Notice, no intercom volumes. I must have done something to my regular DCS install . So I checked the default.lua files for the regular DCS install and the new 'pure' one. They are on different drives C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Uh-1H\Input\UH-1H\joystick\default.lua D:\DCS World OpenBetaPURE\Mods\aircraft\Uh-1H\Input\UH-1H\joystick\default.lua I did a 'diff' and they are identical. Here is the relevant section from the axes definitions axisCommands = { -- joystick axes {combos = defaultDeviceAssignmentFor("roll") , action = iCommandPlaneRoll , name = _('Flight Control Cyclic Roll') }, {combos = defaultDeviceAssignmentFor("pitch") , action = iCommandPlanePitch , name = _('Flight Control Cyclic Pitch')}, {combos = defaultDeviceAssignmentFor("rudder") , action = iCommandPlaneRudder, name = _('Flight Control Rudder') }, {combos = defaultDeviceAssignmentFor("thrust") , action = iCommandPlaneCollective, name = _('Flight Control Collective')}, {action = device_commands.Button_26, cockpit_device_id = devices.ENGINE_INTERFACE, name = _('Throttle')}, -- systems {action = device_commands.Button_28, cockpit_device_id = devices.NAVLIGHT_SYSTEM, name = _('Overhead Console Light Knob'), category = _("Ins Overhead panel")}, {action = device_commands.Button_29, cockpit_device_id = devices.NAVLIGHT_SYSTEM, name = _('Pedestal Light Knob'), category = _("Ins Overhead panel")}, {action = device_commands.Button_30, cockpit_device_id = devices.NAVLIGHT_SYSTEM, name = _('Secondary Instrument Light Knob'), category = _("Ins Overhead panel")}, {action = device_commands.Button_31, cockpit_device_id = devices.NAVLIGHT_SYSTEM, name = _('Engine Instrument Light Knob'), category = _("Ins Overhead panel")}, {action = device_commands.Button_32, cockpit_device_id = devices.NAVLIGHT_SYSTEM, name = _('Copilot Instrument Light Knob'), category = _("Ins Overhead panel")}, {action = device_commands.Button_33, cockpit_device_id = devices.NAVLIGHT_SYSTEM, name = _('Pilot Instrument Light Knob'), category = _("Ins Overhead panel")}, {action = device_commands.Button_12, cockpit_device_id = devices.ADF_ARN_83, name = _('ADF Gain Knob'), category = _("ADF Set Control panel")}, {action = device_commands.Button_15, cockpit_device_id = devices.VHF_ARC_131, name = _('VHF FM Radio Volume Knob'), category = _("VHF FM Radio Control panel")}, {action = device_commands.Button_14, cockpit_device_id = devices.INTERCOM, name = _('C1611 Intercom Volume Knob'), category = _("Intercom Control Panel")}, {action = device_commands.Button_17, cockpit_device_id = devices.UHF_ARC_51, name = _('UHF Radio Volume Knob'), category = _("UHF Radio Control panel")}, {action = device_commands.Button_5, cockpit_device_id = devices.MARKER_BEACON, name = _('Marker Beacon Volume Knob'), category = _("Systems")}, -- TrackIR axes {action = iCommandViewVerticalAbs, name = _('Absolute Camera Vertical View')}, {action = iCommandViewHorizontalAbs, name = _('Absolute Camera Horizontal View')}, {action = iCommandViewHorTransAbs, name = _('Absolute Horizontal Shift Camera View')}, {action = iCommandViewVertTransAbs, name = _('Absolute Vertical Shift Camera View')}, {action = iCommandViewLongitudeTransAbs, name = _('Absolute Longitude Shift Camera View')}, {action = iCommandViewRollAbs, name = _('Absolute Roll Shift Camera View')}, {action = iCommandViewZoomAbs, name = _('Zoom View')}, }, --Cargo view {down = device_commands.Button_1, cockpit_device_id = devices.EXTERNAL_CARGO_VIEW, value_down = 1, name = _('Cargo View'), category = _('View')}, } so then I compared the files for the arduino C:\Users\Stefan\Saved Games\DCS.openbeta\Config\Input\UH-1H\joystick\Arduino Leonardo {160073F0-CC93-11ec-8006-444553540000}.diff.lua C:\Users\Stefan\Saved Games\DCS.pure\Config\Input\UH-1H\joystick\Arduino Leonardo {160073F0-CC93-11ec-8006-444553540000}.diff.lua No difference here either. so then I decided to investigate a file I added some time ago to my regular install: C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Uh-1H\Input\UH-1H\joystick\Total Controls MFBB.lua This file does not exist in the 'pure DCS install'. I added it because I was trying to adapt the total controls box to my A10C In this file I put a LOT of AXES definitions axisCommands = { {action = 3009, cockpit_device_id = 4 , name = _('CMSP - Adjust Display Brightness'), category = _('CMSP')}, {action = 3006, cockpit_device_id = 5 , name = _('CMSC - Adjust Display Brightness'), category = _('CMSC')}, {action = 3007, cockpit_device_id = 5 , name = _('CMSC - Volume Knob'), category = _('CMSC')}, {action = 3006, cockpit_device_id = 37 , name = _('Throttle Friction Control'), category = _('Engine System')}, {action = 3003, cockpit_device_id = 41, name = _('Environmental - Canopy Defog'), category = _('Environmental')}, {action = 3009, cockpit_device_id = 41, name = _('Environmental - Flow Level Control'), category = _('Environmental')}, {action = 3013, cockpit_device_id = 41, name = _('Environmental - Temp Level Control'), category = _('Environmental')}, --{action = 3001, cockpit_device_id = 35, name = _('Altimeter - Set Pressure'), category = _('Altimeter')}, {action = 3009, cockpit_device_id = 49, name = _('Lighting Panel - Formation Lights'), category = _('Lighting Panel')}, {action = 3001, cockpit_device_id = 49, name = _('Lighting Panel - Engine Inst Lights'), category = _('Lighting Panel')}, {action = 3002, cockpit_device_id = 49, name = _('Lighting Panel - Flight Inst Lights'), category = _('Lighting Panel')}, {action = 3003, cockpit_device_id = 49, name = _('Lighting Panel - Aux Inst Lights'), category = _('Lighting Panel')}, {action = 3005, cockpit_device_id = 49, name = _('Lighting Panel - Flood Lights'), category = _('Lighting Panel')}, {action = 3006, cockpit_device_id = 49, name = _('Lighting Panel - Console Lights'), category = _('Lighting Panel')}, {action = 3015, cockpit_device_id = 49, name = _('Lighting Panel - Refuel Status Indexer Lights'), category = _('Lighting Panel')}, {action = 3016, cockpit_device_id = 49, name = _('Lighting Panel - Weapon Station Lights. No function'), category = _('Lighting Panel')}, {action = 3018, cockpit_device_id = 49, name = _('Lighting Panel - Refueling Lighting Dial'), category = _('Lighting Panel')}, --{action = 3001, cockpit_device_id = 45, name = _('HSI - Heading Set Knob'), category = _('HSI')}, --{action = 3002, cockpit_device_id = 45, name = _('HSI - Course Set Knob'), category = _('HSI')}, {action = 3001, cockpit_device_id = 47, name = _('ADI - Pitch Trim Knob'), category = _('ADI')}, {action = 3003, cockpit_device_id = 48, name = _('SAI - Standby ADI Knob rotary'), category = _('SAI')}, {action = 3005, cockpit_device_id = 74, name = _('TACAN - Audio Volume'), category = _('TACAN')}, {action = 3001, cockpit_device_id = 52, name = _('Stall - Volume'), category = _('Stall')}, {action = 3002, cockpit_device_id = 52, name = _('Stall - Peak Volume'), category = _('Stall')}, {action = 3011, cockpit_device_id = 54, name = _('UHF Radio - Volume'), category = _('UHF Radio')}, {action = 3005, cockpit_device_id = 55, name = _('VHF/AM Radio - Volume'), category = _('VHF AM Radio')}, {action = 3005, cockpit_device_id = 56, name = _('VHF/FM Radio - Volume'), category = _('VHF FM Radio')}, {action = 3002, cockpit_device_id = 58, name = _('Intercom - INT Volume'), category = _('Intercom')}, {action = 3004, cockpit_device_id = 58, name = _('Intercom - FM Volume'), category = _('Intercom')}, {action = 3006, cockpit_device_id = 58, name = _('Intercom - VHF Volume'), category = _('Intercom')}, {action = 3008, cockpit_device_id = 58, name = _('Intercom - UHF Volume'), category = _('Intercom')}, {action = 3010, cockpit_device_id = 58, name = _('Intercom - AIM Volume'), category = _('Intercom')}, {action = 3012, cockpit_device_id = 58, name = _('Intercom - IFF Volume'), category = _('Intercom')}, {action = 3014, cockpit_device_id = 58, name = _('Intercom - ILS Volume'), category = _('Intercom')}, {action = 3016, cockpit_device_id = 58, name = _('Intercom - TCN Volume'), category = _('Intercom')}, {action = 3018, cockpit_device_id = 58, name = _('Intercom - Master Volume'), category = _('Intercom')}, {action = 3005, cockpit_device_id = 44, name = _('HARS - Latitude Dial'), category = _('HARS')}, {action = 3007, cockpit_device_id = 44, name = _('HARS - Push-to-sync rotary'), category = _('HARS')}, {action = 3001, cockpit_device_id = 29, name = _('RWR Adjust Display Brightness'), category = _('RWR')}, {action = 3013, cockpit_device_id = 38, name = _('SAS - Yaw Trim'), category = _('SAS')}, }, As you can see, I just copied a file from the A10C directory- there are a lot of controls listed which do not actually exist in the Huey. I had made this file because I wanted to use the Total controls box in the Huey so I thought I needed it back then but it turned I didnt. I just forgot to delete that file. This clears up why I have so many more axes in my regular install. The Total Controls lua file which I had created was adding a bunch of bindable axes. However, these extra bindable controls were irrelevant. I removed the TotalControls.lua files from the game install directory and now the axes list in the Huey looks like the one in the 'pure install' Since I just want to be able to bind the VHF Am and Nav Comm volumes (VHF COMM and NAV comm at the top left of the pedestal) I need to find out what those ids are and add them to the default.lua file. I wrote all this up in case anyone else tries to fiddle with the game install files. It turns out you dont have to and all that needs to be done is adjust the default.lua file to add those controls to be bindable if they are not bindable by default.

I downloaded this mission for the Huey https://www.digitalcombatsimulator.com/en/files/search/?q=hover&s=Search I added an apache but the script does not seem to work. Even the units are not properly placed. For example, there is a HUEY whose mission is labeled 'hover-practice-normal'. I put an apache right next to it. Both are set to skill Client. When I get in the huey, the streip is line with a course and red flags. When I get in the Apache-there is nothing-no course, no people and no voice narration either. There are no waypoint actions attached to the huey. There is a single trigger labeled ONCE (briefing-hover, NO EVENT) with 4 pictures that are supposed to be shown-I assume these are the instructions that appear when in the Huey. But they never show up for the Apache. And there are no triggerzones over the hover course so how does it know when to pop up these pictures. And how does it know to narrate with voice? In this mission, https://www.digitalcombatsimulator.com/en/files/3312548/ the huey is given the skill-Player. When I add an apache, it cannot be player, rather the skill is Client. And when I try to put it next to the huey I get an error dialog that says to put it on smooth land. So I added a helipad and it let me put the apache on the ground. But now when I follow the leader, I am not scored.Despite the fact that a similar performance when I flew the huey was 240.

I built a box with a bunch of potentiometers and an arduino clone. It works great for controlling various dials in the aircraft which allow it-for example the volume controls in the Huey. However, I dont know how I can assign some of thesede dials to control the lights. Although the rows are present in the cintrols settings dialog, i cannot assign anything to them. And their cells have a slightly darker gray tint to them than the cells that are assignable.

cold start , 15 degrees C, Caucasus map. Left engine started fine. Right engine seemed to start- moved R throttle to idle as per usual when Ng>20% However rightr engine stopped spooling at 50% and then spun down. Shut off all systems. Waited 15 min. Same problem. Tried manual override keeping starter held till Ng 50%, went to idle, engine didnt spool. What did I do to this bird?

George never shoots rockets no matter how hard I try

How do ‘big’ flight simpits manage to integrate so many analog flight controls? Windows only supports 8 axes per HID device. Other flight sims (xplane) supports plugins with a well documented SDK to create them. am I destined to use another arduino for every 8 analog dials/sliders/levers I want to add?

Where does DCS store the list of servers I have favorited?

confused. What would improve? As it is, streamdeck with the DCS-exportscripts functionality allows the stream deck to send and receive the states of control buttons and dials from the aircraft in dcs to be reflected on the streamdeck hardware. Helios as I understand it, is just a way to duplicate the gauges and screens in the aircraft on secondary lcd panels on your desk (or simpit)

I have had similar issues with simshaker and other mods. The solution that worked for me was to change the order or the relevant lines in the exports. Lua file

mine always defaults to LAT/LONG. How to change it to MGRS?

thank you

but even Hueys empty need aft cyclic to hover. The center of gravity is under the mast so no aft cyclic should be needed. The wiki (https://en.wikipedia.org/wiki/Bell_UH-1_Iroquois) says: 'The UH-1H also features a synchronized elevator on the tail boom, which is linked to the cyclic control and allows a wider center of gravity range. ' how does the elevator affect the cg? do they mean center of lift?

what doesa external cargo safety do?

I also am pondering using helios. Currently I just run a monitor config that includes my main display and a smaller one. By setting variables like MFCD in the monitor config, I can get DDIs, MFCDs, MPDs etc on my second screen. But I take a FPS hit (obviously because DCS is rendering more pixels). What kind of a FPS hit does Helios cause? I know I should just do it for myself but I thought I'd ask since anything I've ever thought of has already been done.

Thank you for you generous help. Did you use prebuilt shift registers or build your own? I’m not so good at soldering. Did you design your own pcb?

duh. how could I miss that. Is the aft pull needed because the center of gravity is forward of the center of lift?

I can understand why you need left boot - to counter the torque of the main rotor But why do you need to put the cyclic to the left of center and a little back if the weight is balanced (center of gravity=center of lift)?

Thank you for writing this. I gather this allows each SEPARATE DCS folder (the folder with the game) to use a different saved games folder. Is it possible to start the SAME DCS but direct it to use a DIFFERENT saved games folder?

@SkateZilla u said 'The Path setting is so the App knows where to look for config profiles, Each build's SG should match the setting DCS is using.' What is supposed to happen if the DCS build I'm using is on the C drive and the saved games folder path is on the F drive? I am not detecting a difference. Thank you and sorry for being dense. just curious. As per VeeSpike, could Skatezilla write a dcs_variant.txt file containing the info in Skatezilla's 'saved games Folder Path' and put that into the directory specified in Skatezilla's '.DCS Folder path'. This would allow DCS to use a saved games folder in a non standard location. I found the documentation here: Creating Multiple Installs w/ Separate Settings Folders from One Source Install, using dcs_variant.txt Step 1, Open Notepad, Type a name for your main DCS Install, (ie MAIN) etc. save as dcs_variant.txt, Place the TXT File in your /DCS World/ Main folder. Step 2, Run DCS, Allow it to load to the main screen then choose exit, Step 3, Verify DCS_Variant is working correctly, Goto /<User Name>/ Saved Games Folder, and there should now be a new DCS folder, (ie DCS.MAIN), This folder will hold all the settings for your main install. Step 4, Copy and Paste your Main /DCS World/ Application folder, rename folder as you wish (ie /DCS World Open Beta/) Step 5, Open the dcs_variant.txt file in your copied DCS World folder, and change the name from MAIN to a different descriptive work (ie BETA), Save and close. Step 6, Run DCS from the Copied folder to the main menu, then exit. Step 7, Verify you have a new folder in the /Saved Games/ Folder for your copy (ie DCS.BETA) Repeat for as many builds you need. No matter which directory I specify in the Saved games folder field of skatezilla, I cannot detect a diffference

thank you for your reply. If I interpreted it correctly 'The Path setting is so the App knows where to look for config profiles, Each build's SG should match the setting DCS is using. You cannot use the App to tell DCS to look into a different folder, that's done through DCS or DCS Variable File.' means I can load a specific install of DCS and use the contents of the 'Config' folder of the saved games location specified in the Skatezilla field to the right of the field where the DCS install is specified. The remainder of the files in that location are ignored and DCS looks in its default saved games folder location? How can I 'tell DCS to look into a different folder' for the saved games->DCS.openbeta folder ?

Well, this is the way skatezilla is configured. I have three builds Lets focus on builds 2 and 3. build 2 is the default saved games folder in the default location with DCS in the default location. build 3 is a pure dcs installation on a different drive with a bare saved games folder without mods. I can select each build like so: or The default saved games nissions folder looks like this: The bare saved games missions folder looks like this: No matter which I launch, I have lots of missions available, as if the default saved games folder is being used. How do we debug this? ED has a habit of breaking things and and not telling us.

@Karon thank you for your contribution which in and of itself is already beyond my full understanding. But how do you make the arduino talk to a pc over usb? Also, why do you need a 3x3 matrix ? I can understand this for example // Rotary Encoder Inputs // https://lastminuteengineers.com/rotary-encoder-arduino-tutorial/ #define CLK 2 #define DT 3 #define SW 4 int counter = 0; int currentStateCLK; int lastStateCLK; String currentDir =""; unsigned long lastButtonPress = 0; void setup() { // Set encoder pins as inputs pinMode(CLK,INPUT); pinMode(DT,INPUT); pinMode(SW, INPUT_PULLUP); // Setup Serial Monitor Serial.begin(9600); // Read the initial state of CLK lastStateCLK = digitalRead(CLK); } void loop() { // Read the current state of CLK currentStateCLK = digitalRead(CLK); // If last and current state of CLK are different, then pulse occurred // React to only 1 state change to avoid double count if (currentStateCLK != lastStateCLK && currentStateCLK == 1){ // If the DT state is different than the CLK state then // the encoder is rotating CCW so decrement if (digitalRead(DT) != currentStateCLK) { counter --; currentDir ="CCW"; } else { // Encoder is rotating CW so increment counter ++; currentDir ="CW"; } Serial.print("Direction: "); Serial.print(currentDir); Serial.print(" | Counter: "); Serial.println(counter); } // Remember last CLK state lastStateCLK = currentStateCLK; // Read the button state int btnState = digitalRead(SW); //If we detect LOW signal, button is pressed if (btnState == LOW) { //if 50ms have passed since last LOW pulse, it means that the //button has been pressed, released and pressed again if (millis() - lastButtonPress > 50) { Serial.println("Button pressed!"); } // Remember last button press event lastButtonPress = millis(); } // Put in a slight delay to help debounce the reading delay(1); } but windows does not see it as a game controller/

thank you for your reply but i am a little dense and cannot parse it. what does this mean? 'Saved games for each build is set in the saved games section' are these not the fields to the right of each build field? and is 'that's for the App Settings and Log..' referring to the skatezilla app? Why would anyone want a special folder for your app settings?

I have two installations of DCS and this wonderful utility launches each properly. One is 'pure' and the other has changes in various lua files. However, I have also specified different saved games folder in the app settings for each. One DCS folder in the proper saved games location has many missions in its missions folder. The other DCS 'saved games' folder in the alternate location has an empty missions folder. When I launch the 'pure' client which is associated with the DCS 'saved games' folder in the alternate location ( with the empty missions folder), the game starts up with all of the missions from the proper folder with all the missions.Both presets have green squares in the status column. Then there is a button labeled 'Specify Custom User Profile folder'. Isnt that what the entries in the 'Saved Games Folder PAth' are? custom locations? When I specify a 'Custom User Profile folder', which slot/build does it refer to?