howie87 Posted January 29, 2017 Share Posted January 29, 2017 Works fine in 3 position switch mode but not when mapped as a two stage trigger. It gets stuck in the first detent mode (T1) when releasing the trigger. Link to comment Share on other sites More sharing options...
razo+r Posted January 29, 2017 Share Posted January 29, 2017 that's why you also have to map the T0 button/detent Link to comment Share on other sites More sharing options...
howie87 Posted January 29, 2017 Author Share Posted January 29, 2017 You can't map the T0 mode with a two position trigger. The T1 state should only be active when the trigger is depressed and then go back to the T0 state when it's released. In other words it should act as a momentary switch, like PAC1 does in the A-10C. Link to comment Share on other sites More sharing options...
scaflight Posted January 29, 2017 Share Posted January 29, 2017 Yeah, this'd be nice to resolve somehow. :) Link to comment Share on other sites More sharing options...
Phobon Posted January 29, 2017 Share Posted January 29, 2017 As a temporary fix, you can add the following line to your "DCS World OpenBeta\Mods\aircraft\AJS37\Input\joystick\default.lua": {down = 3006, up = 3005, cockpit_device_id = devices.NAVIGATIONPANEL, value_down = 1.0, value_up = 1.0, name = "T1 Fix (Hold)", category = "Radar"}, and then map the new command "T1 Fix (Hold)". I've used this for the first detent of my Warthog Trigger and it works fine there. 2 Link to comment Share on other sites More sharing options...
Home Fries Posted January 29, 2017 Share Posted January 29, 2017 Great job, Phobon. I actually used TARGET to assign a DX button on MapKeyR for TG1, but your way works with any 2-stage trigger. This really needs to be officially implemented. -Home Fries My DCS Files and Skins My DCS TARGET Profile for Cougar or Warthog and MFDs F-14B LANTIRN Guide Link to comment Share on other sites More sharing options...
Dahlbeck Posted January 29, 2017 Share Posted January 29, 2017 So how do people do this, all you who've been running the preview, anyone? Link to comment Share on other sites More sharing options...
QuiGon Posted January 29, 2017 Share Posted January 29, 2017 It really misses a "T1 Fix (Three Position Switch)" entry in the configs. I guess it will come with one of the next updates. For now I mapped T1 (the normal one, not the three position switch one) to the first detent, TV to the second detent and T0 to another button that I can press if I initiated a fix with T1, but then want to abort the process. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing! Link to comment Share on other sites More sharing options...
Warthog_Farmer Posted January 30, 2017 Share Posted January 30, 2017 Confirmed here too! I thought it was something I was doing wrong. Link to comment Share on other sites More sharing options...
hughesj2 Posted January 30, 2017 Share Posted January 30, 2017 Thanks for this Phobon, where do I enter it in the file? Do I have to delete any existing lines etc? I've tried a couple of options that both left me unable to edit the mappings in game? Cheers James Link to comment Share on other sites More sharing options...
Phobon Posted January 30, 2017 Share Posted January 30, 2017 (edited) Thanks for this Phobon, where do I enter it in the file? Do I have to delete any existing lines etc? I've tried a couple of options that both left me unable to edit the mappings in game? Cheers James Sorry, I'm not at home right now so I can't show you my working file. But your version should contain a large list of similar looking lines. Just drop it somewhere in there :) If you did that and still have problems, your editor might have messed something up while you were editing it. In that case, I recommend repairing DCS to get the original file back and then try again with Notepad or even better Notepad++ I will post my complete file in a few hours when I'm back at my computer.default.lua Edited January 30, 2017 by Phobon Attached working default.lua 1 Link to comment Share on other sites More sharing options...
hughesj2 Posted January 30, 2017 Share Posted January 30, 2017 Ok thanks Phobon, I'll give it a go using Notepad ++ Link to comment Share on other sites More sharing options...
hughesj2 Posted January 30, 2017 Share Posted January 30, 2017 Yeah it was the fact I hadn't used Notepad ++, worked fine after I dropped it in the Radar section Cheers! James Link to comment Share on other sites More sharing options...
bart Posted February 1, 2017 Share Posted February 1, 2017 (edited) As a temporary fix, you can add the following line to your "DCS World OpenBeta\Mods\aircraft\AJS37\Input\joystick\default.lua": {down = 3006, up = 3005, cockpit_device_id = devices.NAVIGATIONPANEL, value_down = 1.0, value_up = 1.0, name = "T1 Fix (Hold)", category = "Radar"}, and then map the new command "T1 Fix (Hold)". I've used this for the first detent of my Warthog Trigger and it works fine there. This worked great, thank you for sharing it. :thumbup: Cobra, any chance you can implement this with phobon's permission of course (or something similar) as standard code for us Warthog users please? Edited February 4, 2017 by bart System :- i7-12700K 3.6 GHz 12 core, ASUS ROG Strix Z690-A Gaming, 64GB Corsair Vengeance RGB Pro 3200MHz, 24GB Asus ROG Strix Geforce RTX 3090, 1x 500GB Samsung 980 PRO M.2, 1x 2TB Samsung 980 PRO M.2, Corsair 1000W RMx Series Modular 80 Plus Gold PSU, Windows 10. VIRPIL VPC WarBRD Base with HOTAS Warthog Stick and Warthog Throttle, VIRPIL ACE Interceptor Pedals, VIRPIL VPC Rotor TCS Plus Base with a Hawk-60 Grip, HP Reverb G2. Link to comment Share on other sites More sharing options...
doodenkoff Posted February 4, 2017 Share Posted February 4, 2017 Phobon's fix should work for an X52 two-stage trigger, shouldn't it? Win 10 | i7 4770 @ 3.5GHz | 32GB DDR3 | 6 GB GTX1060 Link to comment Share on other sites More sharing options...
scaflight Posted February 4, 2017 Share Posted February 4, 2017 Phobon's fix should work for an X52 two-stage trigger, shouldn't it? Sure does for me ;) Had to put it back in place after this Friday's update. Link to comment Share on other sites More sharing options...
Recommended Posts