seikdel

I... I just don't... understand gyroscopes... at all. This is a little much for my brain o.O

Standalone? Yes. Change profiles for every aircraft? Nope, this just gives you "buttons" for middle positions and off positions, so you don't have to change profiles beyond setting them up in DCS like normal. Not in conflict w/A-10C? Nope, works perfectly with it. Just don't assign anything new to the virtual controller and the Hog won't care what it's doing.

PPJoy creates a virtual controller. GlovePIE pushes buttons on that virtual controller. Short version: You can start your F-15C engines by putting the throttles from off to idle. You can use your boat switch to switch between BVR and Bore, with center being navigation. You can use any 2- or 3-way switch as an actual 2- or 3-way switch.

Not to toot my own horn (noise laws and all), but I just created a thread explaining how to get functional 2- and 3-way switches in FC3. This includes using the TM Warthog throttle idle setting to start and stop engines. If you're interested, I can shoot you my Su-27/33/MiG-29 profile that I've set up to do that. You'll need to do the GlovePIE/PPJoy thing, though.

I've started a couple of different threads on this recently. Although they haven't received much attention, I can't believe I'm the only one who wants a functional 3-way flaps switch in the FC3 A/C. After a couple hours of blood, sweat, and tears, I figured it out! The problem 2-way switches are only "on" when they're flipped up 3-way switches are only "on" when they're not in their center position FC3 (and some functions in other modules) can't respond to "off" events This means that, if you have a 2-way switch set to control your landing gear, you have to flip it off and then on again to toggle the gear The solution Use PPJoy to install a virtual joystick, then use GlovePIE to map these "off" positions on the real controller to "on" positions on the virtual controller Voila! DCS can now react to both "on" and "off" events! P.S. T.A.R.G.E.T. is a total joke Steps: Install PPJoy Create a virtual controller (mine has 0 axes, 0 HATs, and 16 buttons, because that's all I need it for) Install GlovePIE Create a script that maps key releases on the real controller to key presses on the virtual controller I have a TM Warthog. The throttle block is controller #3, after a TM Cougar and the Hog Stick. To find out which number your preferred controller is, open up the "Game Controllers" dialog in windows (easiest way: start menu -> devices and printers -> right-click on whichever controller is displayed in there and select "Game controller settings"). The first controller in the list is #1, the second is #2, etc. This is what my GlovePIE script looks like for my TM Warthog Throttle (remember, it's controller #3 on my computer): [size="2"]if(joy3.button9 = false and joy3.button10 = false) then PPJoy1.Digital0 = true else PPJoy1.Digital0 = false [i]//Boat Switch[/i] if(joy3.button16 = false) then PPJoy1.Digital1 = true else PPJoy1.Digital1 = false [i]//ENG L Fuel switch[/i] if(joy3.button17 = false) then PPJoy1.Digital2 = true else PPJoy1.Digital2 = false [i]//ENG R Fuel switch[/i] if(joy3.button20 = false) then PPJoy1.Digital3 = true else PPJoy1.Digital3 = false [i]//APU Switch[/i] if(joy3.button22 = false and joy3.button23 = false) then PPJoy1.Digital4 = true else PPJoy1.digital4 = false [i]//Flaps[/i] if(joy3.button27 = false and joy3.button28 = false) then PPJoy1.Digital5 = true else PPJoy1.Digital5 = false [i]//Autopilot Switch[/i] if(joy3.button24 = false) then PPJoy1.Digital6 = true else PPJoy1.Digital6 = false [i]//EAC Switch[/i] if(joy3.button25 = false) then PPJoy1.Digital7 = true else PPJoy1.Digital7 = false [i]//RDR ALTM Switch[/i] if(joy3.button29 = false) then PPJoy1.Digital8 = true else PPJoy1.Digital8 = false [i]//Right Throttle[/i] if(joy3.button30 = false) then PPJoy1.Digital9 = true else PPJoy1.Digital9 = false [i]//Left Throttle[/i] keyboard.ScrollLock = joy3.Button4 [i]//Mic Switch, mapped to ScrollLock, which is my TS3 PTT Key[/i] keyboard.ScrollLock = joy3.Button5 [i]//Mic Switch, mapped to ScrollLock, which is my TS3 PTT Key[/i] keyboard.ScrollLock = joy3.Button6 [i]//Mic Switch, mapped to ScrollLock, which is my TS3 PTT Key[/i][/size] Leave this running while DCS is up and you'll get the following results: Boat switch center = Virtual button 1 ENG L OVERRIDE = Virtual button #2 ENG R OVERRIDE = Virtual button #3 APU Switch off = Virtual button #4 Flaps switch MV (center) = Virtual button #5 Autopilot switch ALT/HDG (center) = Virtual button #6 EAC OFF = Virtual button #7 RDR ALTM DIS = Virtual button #8 Right throttle idle (from the off position) = Virtual button #9 Left throttle idle (from the off position) = Virtual button #10 Mic switch forward, backward or down = ScrollLock Now you can map these in DCS! For example, in the Su-25, I have the following mapped: Flaps switch UP (button 22 on the real controller) = Flaps up Flaps switch MV (button 5 on the virtual controller) = Flaps Up/Down Flaps switch DN (button 23 on the real controller) = Flaps Landing Position APU START (e.g. APU switch up, which is button 20 on the real controller) = Landing Gear Up APU OFF (APU switch down, which is button 4 on the virtual controller) = Landing Gear Down So now my 3-way flaps switch works perfectly in the Su-25, and the APU switch works as a gear lever (up and down actually correspond to the gear handle being up or down, instead of just toggling it). Other controls in the game (e.g. Cut of Burst Select) don't have an "up" or "down" setting in the game - they can only be toggled. You can still map both the real switch and the virtual one, which allows you to use the switch as a true toggle switch. You can also map engine starts to the virtual buttons 8 and 9 (for right and left, respectively), and engine stops to the real buttons 29 and 30 (also for right and left, respectively). That's it! A half hour of setup yields functional 2- and 3-way switches in the FC3 A/C! You can also script some keyboard macros pretty easily. The scripting language is a piece of cake to learn. And best of all? No T.A.R.G.E.T.! This means you keep both controllers as discrete entities (instead of the stupid "Thrustmaster Combined" virtual controller). GlovePIE also boots up faster than T.A.R.G.E.T., and since it's not unplugging and replugging all manner of virtual shenanigans, you don't have to reboot DCS to switch from FC3 to DCS modules! I honestly haven't found a downside yet. I hope this works for some folks. Please shoot me any questions you have. P.S. If you have "Synchronize controls on mission start" selected, be aware that any toggle-only switches (e.g. close canopy, cut of burst select, RWR silence, etc.) will be toggled at mission start (because if the real button is off, the virtual button is on, and vice versa, so there will always be a button on). The easy fix is to toggle your controls the opposite of how you want them (e.g. if you want ENG L NORM to equal "open canopy" and ENG L OVERRIDE to equal "close canopy", before you unpause the mission or jump into the pit, set the switch to OVERRIDE). Alternatively, you can open up the arming window (which freezes all controls except mouse) and adjust your switches to match whatever you want. Alternatively alternatively, you can just hit each of the keyboard commands once to toggle the controls. You'll figure it out. Trust me; it's easy.

Oh! That's... new and different from the established tutorials. I thought the "MBR" was Cyrillic for "MER", i.e. multiple ejector rack. I guess giving us control over the actual interval is an improvement, though. Can't believe I didn't think to try this myself. This is new functionality, right? I'm not just crazy?

Honestly, I'm not positive. I think they should be swapped, but it'd be really nice if someone with real-life experience with the ADF system could offer some insight. The argument the guy made in the thread I linked makes sense to me, but he could be wrong, and I'm fairly clueless. Thanks for the INU update fix! That one's bugged me for even longer =)

The MERs on the Su-25 seem to be borked. I load up my 32 FAB-100s, take off with visions of Arc Light dancing in my head, set my ripple quantity to all and my interval to the KMGU-MBR setting, pull the trigger and... I'm suddenly met with the disappointing sound of all my little gifts of joy dropping simultaneously. Hell of a cluster bomb, but not very effective for the aforementioned delusions of being a strategic bomber. Anyone else?

Try C:\Users\(your user directory)\Saved Games\DCS\Config\Input\ka-50\joystick Rename it to whatever the existing .lua file in that directory is.

I'm pulling my hair out, folks. Back in the day, when we had the TM Cougar, we used Foxy. Foxy can create a profile, compile it and load it to the stick. It then stays in the stick. The stick stays plugged into the computer. I can compile a different profile at any time and the stick still stays plugged into the computer. Enter T.A.R.G.E.T. Target seems to only be able to "run" a config, which means it keeps running in the background. Furthermore, it seems to only be able to "virtually disconnect" the actual stick and connect its "Thrustmaster Combined" virtual stick, which means I lose DX buttons and have to rely on key presses instead. Since DCS doesn't like plugging anything in while its running, if I have different profiles for different aircraft, I have to quit to desktop every time I want to change birds. This holds true for A/C I don't even use target for, like the A-10C and Ka-50. Please help, folks. Tell me there's some hidden undocumented feature that lets me just compile a config for a single controller and load it to the controller. Tell me I'm missing the "don't use thrustmaster combined" option. Please tell me something about this I've missed. I can't believe we've gone backwards so that the newer stick can't do some of the most useful functions of the old Cougar. Any help at all? Please help me out here =( Edit: I should clarify that I haven't found any functionality for this in joytokey, but if I'm missing it, please tell me. Also, has anyone found any other programs akin to joytokey that will let me do this? Edit 2: After some more fevered searching, I found GlovePIE, which is complicated but very useful. It allows you to map button releases as key presses. I'd still love to know if target can do more than it apperas, but GlovePIE is a suitable workaround for now.

The inability to use the flaps switch on the TM Warthog in the Su-25(T) has been driving me nuts. I've recently learned how to hack 3-way switch functionality into the Ka-50 .lua files, but then it occurred to me: Why aren't we allowed to map a button release event as a control? After all, that's how the A-10C handles it. Releasing button 29 starts the left engine start cycle. Pressing button 29 shuts down the left engine. Releasing button 22 OR 23 puts flaps in the maneuver position. Releasing 16 and 17 puts the left and right engines, respectively, into fuel override mode. Releasing 9 OR 10 puts the boat switch in the center position. My point is this: While we can hack some of this functionality into the Ka-50 (still no luck with the route and descent switches) and the P-51D (although I haven't figured out how to assign a specific flap setting to a button yet), we can't do it in FC3. Adding the ability to map button releases as events would require a substantial remapping of the current default control sets, but it would pave the way for much more flexible controls in the future, and DCS really seems to be future-focused at this point. Thoughts? Hard mode: Let us map buttons as modifiers! inb4 use target. Target gives us flexibility in programming, but unlike the much older Foxy program (for the TM Cougar), you a) have to have target running in the background whenever you want to fly (vs loading a script to the device, where it stays active until the device is unplugged) and b) have to accept the fact that you lose axes by combining the different controllers into one bizarre "combined" thing. Edit: Here's a workaround that I discovered, in case anyone else is bothered by this.

Are we still wishing here? I, for one, would love to have a setting for the flaps switch that mimics the A-10C's functionality. For example, in the Su-25(T), have UP correlate to retracted, MV correlate to maneuver, and DN correlate to landing. I hope this would be a relatively easy addition, and it'd be a welcome improvement.

Time to revive this thread again. Have we figured out where to put ark.lua in .miz files recently? It seems to have changed. The closest I've gotten to an answer is bad_crc's post, but I still can't get the darned thing working. Anyone else have any luck? Edit: Nevermind, it's still the same path as before. I was using the wrong ARK.lua file and trying to figure out why my personal airfields weren't appearing. Stupid PEBKAC error.

Hey Devrim, thanks as always for the continued work on this mod. It's still my favorite cockpit mod by far =) While researching an ABRIS function, I came across this little gem. Based on what that guy says, the TLG and TLF (telegraph and telephone) modes are swapped: the up position is telegraph mode (filters out the base signal) and the down position is telephone mode. I can't seem to find much information on these two broadcast modes via google. Perhaps a real-life pilot/NDB expert can shed some light on this. Anyway, if that guy is correct, it'd be a simple fix, right?

Please tell me how to edit my lua files so that the flaps switch will does the following: UP - Flaps all the way up MV - Flaps 1 DN - Flaps full

From what I read in this post from this thread on how to fix toggle switches, the route switch can't easily be configured to work this way because it's not clickable in the cockpit. The simplest solution is to use the TARGET software, but it's sadly far from ideal. I've just resigned myself to having to toggle the route switch. If you're looking to fix up your HOTAS controls in the Shark, that thread is a worthwhile read. Edit: try the following: In your saves\DCS\config\input\joystick folder, open up the lua file for your device. Look for something akin to this: {combos = {{key = "JOY_BTN7"}, }, down = iCommandPlane_RouteMode, name = "Engage/Disengage Route Mode", category = "Ins Collective Stick"}, And add: {combos = {{key = "JOY_BTN7"}, }, down = iCommandPlane_RouteMode, [b]up = iCommandPlane_RouteMode, [/b]name = "Engage/Disengage Route Mode", category = "Ins Collective Stick"}, This'll make the switch (in this case, the speed brake forward switch on the warthog throttle) toggle route mode both when it's switched on and when it's switched off. See if that helps =)

Could I please get a source on this? I really want to read up more on the Shark's targeting capabilities. This thread has already been super helpful =)

LAlt + c?

On the one hand, thanks much to ED for coming out with smaller patches much more often! The knowledge that some of the more egregious issues will be fixed without having to wait for a gigantic patch really keeps me motivated to keep playing! On the other hand, will you devs please fix some of the significant bugs in the Ka-50? Especially the ones that have been around forever...

You could try editing your joystick lua file in user\saved games\dcs\config\input\Ka-50 and doubling up the trigger to both. I don't know if it'll work or not, but it's worth a shot.

I tried this a couple months back with some buddies and we had no luck. It's a shame, because it'd be an amazing feature! Talk about expanding the Shark's role as AFAC! Imagine a flight of Su-25s loaded with Kh-25MLs engaging targets while the AFAC sits out of ground target's range and repeatedly designates. How great would that be?

Is it a pre-defined failure in the mission?

Hey all. Thanks for this incredibly helpful thread! Question about macros: I've created one, but even though I start at time = 0, there's roughly a quarter-second delay between hitting the control and having the macro execute. Any known reason for this?

Yay for the Ka-50...?

I've noticed it as well and would love it if it were fixed!