ESzczesniak

A bit delayed reply, but thank you all for the feed back! Is there anyone who has used the T-50CM2 without an extension who feels the stick travel is too limited? I'm likely to be using this for at least a while without an extension, possibly forever. The only drawback I can see at all for the T-50CM2 is the reduced travel if used without extension. If this isn't much of an issue, then maybe there's no down side at all. By the time I'm spending this kind of money, I'd rather take time to save up the extra 100 euros for the better base. So while money doesn't grow on trees, I don't see the cost as a drawback.

@LeCuvier Thank you on both counts! I thought those are the lines I had created, but such is coding I guess...a missed comma or period or something small could have done me in!

I have the Winwing throttle, startup, takeoff, and combat panels. The throttle and startup panel are fairly new acquisitions. All works well except the fuel dump and pitot heat switches in DCS is read as a toggle. The switch needs to be cycled off to on to turn on, then cycled fully off back to on again to turn off...which also leads to the physical position being out of sync with DCS. I thought I knew how to fix this, as the takeoff panel has similar issues with the launch bar and bypass switch. I was able to easily edit the default.lua to have retract and extend as separate commands rather than retract/extend as a toggle. However, I am having issues with the fuel dump and pitot heat. The lines I believe are relevant from default.lua are: {down = fuel_commands.DumpSw, up = fuel_commands.DumpSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Fuel Dump Switch - ON/OFF'), category = {_('Left Console'), _('Fuel Control Panel')}}, and {down = elec_commands.PitotHeater, up = elec_commands.PitotHeater, cockpit_device_id = devices.ELEC_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Pitot Heater Switch - ON/AUTO'), category = {_('Right Console'), _('ECS Panel')}}, I edited these creating two different lines each. I changed the name in on to on/on and the name in the other to off/auto. I assigned values of -1.0 and 1.0 (it seems these may have to be trial and error, but I started here). The result was that even the original toggle command for each disappeared from the DCS controller assignments menu. I undid these edits and stopped at this point, coming here for advice. I appreciate any assistnace! P.S. Is there a better way to paste these command lines? I've seen other posts where they in a gray box without automatic "word wrap" to a new line.

I'm thinking about moving to a Virpil Base from the TM Warthog. I just upgraded to a Winwing Super Taurus + Startup Panel/Takeoff/Combat Panels and have a set of Crosswing MFG pedals with damper. So it seems like the stick is the outlier. I fly the Hornet almost exclusively, so would be planning to use my TM Warthog Hornet stick on a Virpil base. I'm trying to figure out the WarBRD vs T-50CM2 base. It seems the difference heavily boils down to use of extensions or not. I know the T-50CM2 comes with more cam and spring options, as well as about 5 degrees less travel (16 or 17 vs 22). I use a standard Monstertech table mount for my stick, so the excessive height with desktop use is a bit of a moot point. Does anyone have advice if I should plan for an extension in the future? The WarBRD base seems the most drop in for my current setup. And if this is all I'll ever use, no need to overspend. However, I don't know how much value an extension may or may not add and keeping this option open would be good. The only downside beyond cost I could see for the T-50CM2 is the decreased travel if I never move to an extension. So to put it mildly, I'm torn and would appreciate any feedback.

I am hoping that someone here with more knowledge than I could help me reconcile these two scripts. I have the Winwing Combat and Takeoff panels, as well as a StreamDeckXL. Each of these relies on a script to display the output. This means the lights on the Winwing combat panel, and gauge output displayed on Streamdeck--primarily UFC data fields for me. The following is my Export.lua contents: -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') If I repair the lua in the Simapp, then add the DCS exports ABOVE the wwtexport, I got things to work for one flight. But then somewhere through running DCS or more likely the SimApp, I ended with an LUA that looks like this: local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') Now, at this point even if I delete the extra wwtexport added, the winwing panel lights don't work. The Streamdeck has always worked as long as the DCS-Export script is anywhere. But the only way I can consistent get the Winwing panel lights to work is repairing the LUA and adding nothing back. Any suggestions to what I can do to get these two to play along nicely? My serious DCS simming is in VR, but I'd still like to have the lights if at all possible. A lot of my "academic" trial and error (i.e. learning new systems) I do in 2D where it's easier to read all the gauges.

Glideslopes are always intercepted from below. All patterns, ILS, etc approaches setup from level flight and then begin a descent towards the runway. Case I carrier patterns and the basic airport visual pattern start this somewhere on downwind or base, while instrument procedures tend to be more straight in. There is no normal procedure where you are descending to the glideslope, then reduce your descent rate to establish...which would happen if you're intercepting from above. Intercepting the glideslope is a different story than maintaining the glideslope once established. Once established, what you're saying comes in to play. Taking power off when low would lead you to go lower. You would never intercept the glideslope in this configuration.

Not exactly. Glideslopes are always to be intercepted from below. Intercepting from above leaves you the risk of descending through and below the glideslope, while behind the power curve…the very situation you’re trying to avoid. The intent of the rules, and virtually all flying advice, is never be low and slow on approach.

Doesn't that copy the entire thing? The button/switch type, the command/keyboard shortcuts, and the icons? I'm specifically trying to figure out how to switch the button type, i.e. from keyboard shortcut to DCS Interface Switch, etc. I hadn't tried that yet, but I was wondering if that might work.

This is more a general Stream Deck question, but can anyone tell me how to reuse an icon from another profile/button? I know how to select custom images, but as I'm piecing parts of various profiles together to make what I want, I find sometimes I like the icon from one profile, but not the coding/action. And the icon seems to be written in to the profile, I'm not finding a separate place Stream Deck puts icons when you import a new profile. Most commonly, I've found icons I like but they utilize keyboard shortcuts. So I want to use a DCS Interface button command, but with the icon from the keyboard shortcut profile.

Thank you, I'll take a look!

This seems to be related to the sync HOTAS option. Removing this effectively fixed this issue. In a quick free flight the aircraft starts slowly banking to the right, but is easily corrected with trim. Turning this option back on reinstates this issue. Overall, I prefer the C&D to C&D missions, so this won't be much of an issue. But Any work around other than disabling the sync HOTAS commands?

I was wondering if anyone has advice for the A-10C radios? I'm trying to make very comprehensive A-10C and F/A-18C profiles. The one's I've found have utilized keyboard shortcuts, which have room for problems. So I'm wanting to make my own profiles with DCS Interface. I want to both eliminate (or nearly eliminate) keyboard commands AND have feedback (i.e. current NMSP selection is green to indicate it's active). I've made the UFC, AHCP, and CDU and have these working well. These are a bit simpler and mostly momentary buttons with no feedback. In particular for the radios, does anyone have experience having the current frequency/channel displayed on a Stream Deck button? While I haven't programmed it, it seems using rotary/buttons to switch the frequency, modes, etc, will be relatively straight forward. Thanks for any help!

Thank you for the replies. I will try the FFB and synchronize controls suggestions. If not successful, I'll report back with a track. I hadn't forgotten to mention that. I had already checked and removed the duplicates that existed.

I've been flying the Hornet a lot for the last 18-24 months. I've been starting to have an interest in coming back to the A-10C, but am having problems with the module now. At the mission start, the aircraft starts to roll and yaw to the left. At first, this was irrecoverable. I uninstalled and then reinstalled the modules and following this I can recover the spin, but I'm unable to maintain straight and level flight without constant control input. Trim alone is not enough. I have MFG Crosswing pedals and a TM Warthog HOTAS. The RAlt+Enter controls input shows input at neutral. The controllers all appear to be functioning fine in the windows game control menu. I do not have this issue in the Hornet. This issue occurs with the A-10C and A-10C 2. Any thoughts for further troubleshooting?

Kind, me! And I'm happy to be paid in beer! I can likely build whatever it is (I have most wood shop stuff other than a jointer planer), but am very non-committal to design. In big picture, I've been thinking between a bookcase style storage for everything, a bin on the floor, or wall mount. And then in details I've been back and forth if it was better to hold/mount by the table clamp, or the base at the bottom. So I was hoping to learn from other's experience before committing time and materials.

I have a set of 5 Mostertech table mounts that rotate based on my setup. Two are HOTAS for DCS, 1 for a CDU for civilian sims, and 2 x airbus stick/throttle. I also have a yoke/throttle, so at times all 5 may be unused. Does anyone have any good storage solutions? I see Monstertech has wall mount racks, but I'm not sure I want to spend $35 x 5 plus shipping to the USA. Anyone have any other good solutions? Hardware store brackets? Bins or racks?

Thank you for the replies. Reading further in the thread referenced by markturner1960, I realized editing the commands in default.lua can create separate "up" and "down" commands instead of toggles. I had not read this nuance previously. Once I realized this, the edits were fairly quick and then I just remapped the controls through the DCS controller menus. Unfortunately this is going to get reset frequently in DCS updates. I will keep a backup of the file, but this may change with time. It would seem like DCS could be well served by an "advanced controller setup" or "home cockpit controls" option in the menus that automatically generates on and off state controls rather than toggles alone. It would keep it cleaner for the more casual player (I assume that's why things are setup as they are), but allow an easy option without editing files themselves.

I am very new to editing the LUA files for controllers. I've been reading on the forums, understanding that they can be editing to use on on/off switch to control a toggle in game. I just got the two WINWING control panels and everything works very well except the hook bypass and launch bar. The two issues are: 1. The launch bar mostly works. For some reason the launch bar is starting "extended". If the switch is left in the extended position physically, then all is well. But the bar then has to be retracted in C&D. I don't know what happened in this process, as prior to connecting these panels the launch bar always started "retracted". I an also click the virtual cockpit switch to "sync" if the physical hardware starts out of phase. This switch is a two position switch, but the command only has a toggle extend/retract. Anyone have any ideas why the launch bar default to extended now? Or how to change this. 2. The hook bypass switch is "on" at the field setting. The command is a toggle, so ideally it would toggle on release as well to keep the state in sync. And in a really ideal world, there would be separate commands for switch state so we could ensure controls were in sync. These are the relevant sections of the WINWING***.diff.lua file: ["d3008pnilu3008cd5vd1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN8", }, [2] = { ["key"] = "JOY_BTN7", }, }, ["name"] = "Launch Bar Control Switch - EXTEND/RETRACT", }, ["d3009pnilu3009cd9vd1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN20", }, }, ["name"] = "HOOK BYPASS Switch - FIELD/CARRIER", From my reading, the bypass section needs something added with a -1, but I'm a little unsure where to add this. For the launch bar, I have less of an idea. Thanks for any help!

Thank you! I had read enough there were issues, but didn't quite grasp the details apparently. From my prior reading, it had sounded like it was about which DDI it was on. A lot of things are working better now understanding it has to do with SOI, not the specific DDI.

I'm aware of the bug that required the FLIR to be switched from the left MFD (and then back if desired). Accounting for that, I have no troubles on my first target. I select the appropriate waypoint, WPDESG, and the FLIR slews. However, I am having troubles moving to a second target area. I double press the NWS/Undesignate button, slave to snowplow or VVSLAV and then repeat the WPDESG process. However it seems after this second round, I am always staring at blank terrain and somewhere random. Any hints or thoughts? And while I'm asking, did the last couple rounds of updates fix the need to swap MFD's on the FLIR? I haven't seen any change logs show up regarding the updates.

This mission outwardly seems like a simple missions, but I'm having troubles. I should not there is some spoiler here, so stop reading if you're worried. 1. After taking out the truck filled with IED, I get a formal 9-line for a compound in the city. I open SEQ2 and set WP11 to it's coordinates (N 30 30 04 E 47 48 04, elevation 10). Then WPDESG and my ATFLIR shows me an empty spot of desert about 15 NM south of the city. There's no decimal seconds given with the 9-line, so I was wondering about that. But I can't really figure out what I'm doing wrong. Wingman nails the target, so technically taken care of. 2. After the second show of force during Bowser's exfil, I don't find any truck leaving the city. I've given in and watched a YouTube recording to make sure I'm looking in the right place, and still don't see it. Is there a particular trigger for this? Also, is the save function after AAR really working? I've flown the mission twice and filled the tank fine both times. But am not wishing I could skip the AAR to not repeat the same early monotonous stuff early in the mission. Thanks for any help or thoughts. I know "attach a track" is coming, but I didn't think to save one after the mission. If I do it again, I will.

I'm looking at revamping my home cockpit setup. I am currently using a VolairSim chair. I have not been very happy with the ergonomics. My two largest complaints are that most rudder pedals only fit in a very flat and close position and the chair is rather low to the ground. The pedals are also very hard to change out, so I rarely move to my racing setup. I use primarily 3 setups for my simming: 1. Fighter/Tactical (DCS World): TM Warthog chair level center stick and left hand throttle, MFG crosswind pedals, possibly adding a couple WINWING panels in the future 2. Commercial (P3D/MSFS): Center desk level yoke/MCP, left hand CDU, right hand throttle (TM Airbus vs Honeycomb Bravo depending on the aircraft), MFG crosswind pedals 3. F1 Racing: Center desk level wheel, pedal plate Display is on a 55" wall mounted 4K TV or VR headset. I am thinking about switching to a desk/chair combo. The pedal sets could sit easily on the floor and the yoke or wheel mount to the table. What I'm looking for to complete the setup is a chair with at least left and right side mounts for the throttles and stick. Everything I'm finding is along the lines of the VolairSim Chair, or like these Next Level Racing Chairs (https://nextlevelracing.com/products/gtultimate-v2-flight-simulator/). They all seem to have the pedal and yoke mount built in. Does anyone know know of any chairs with the HOTAS mounts. Or any HOTAS mounts that can easily be added to chairs? I've also seen some desk mount versions of HOTAS mounts, but they all seem flimsy. Thank you for any advice and input!

Jonass1, thank you for the idea/example file. I don't run almost any external programs (occasionally VoiceAttack). So I reconfigured this to simply switch settings before running the main DCS executable. This switches options.luas and Joystick *.diff.lua files with 3 basic configurations of VR, 2D in 4k, and 2D at 1920x1080. When I fly in 2D, I use a 4k TV, but when I'm troubleshooting I prefer to use my desktop monitor. This is all working beautifully. If it's not too much trouble, could I ask where you found the official Windows name for your sound devices for the nircmd tool? I like your idea of ensuring the sound is set to either speakers or the VR headset. However, when I take what's in my sound settings page of Windows (Speakers (High Definition Audio Device) or Headphones (Realtek USB2.0 Audio)), this portion of the cmd doesn't seem to do anything. No errors are returned, so I think it's finding the programs appropriately. But no changes are made.

Thank you! I think this is the path I want to go. I just need to learn a little bit about the command/code lines so I can edit and/or create. Thank you for sharing!

I also need to look in to this option as well.