t1mb0b

totally pointless, it's a sim not an arcade game

Yeah I know it's a wish list but come on don't be ridiculous, ED have enough to do. When you create a mission involving airfields you add your airfield 'furniture' etc. In the real world a fob or farp needs prior planning - you don't just 'turn up' somewhere, so plan it in your missions and add the fuel bowser or whatever you need to refuel. Lazy.

..except just excluding the folder - what's so difficult?

yup all working, note that i did have to do a DCS repair obviously to fix DCS, and the reset lua code after checking the ob box.

re. the 'OB' check box This is surely a temporary workaround than a fix right? The effect of doing it simply creates a parallel folder DCS.openbeta alongside the DCS folder(if that's what your particular setup conisists of), so DCS effectively just 'carries on as normal' because the export.lua DCS is looking at doesn't change. Before DCS 2.5.6 I never had to have the ob box checked, that's the only material change i have made to continue using the plugin. Just saying and if that's not correct someone who knows for sure please say so. T

..nothing actually to do with MAV F's then, misleading title, should be 'problems mapping slew with <insert hardware>' and probably in the Controller Profiles and Problems section

+1, I also get this

its been a while since i used JTAC but from memory i think i used to check-in simply with; 'Axeman 11(obviously whichever c/s is appropriate) - playtime 15 minutes' Have you tried that?

I beleive it's the export.lua in saved games/scripts you need to worry about

non-steam

I was answering 'emc'. ...and, i was with you until your last line, VA isn't listening when i'm pressing PTT for SRS :)

with todays openbeta.... delete saved games\scripts\export.lua repair DCS re-install SRS if you use it custom path to DCS folder and OB ticked reset LUA in VAICOMPro works for me

At the risk of this becoming more VA related than SRS.....for which I apologize.... my setup for what it's worth, seemed the logical way to me start with SRS - all controls mapped to keyboard, see later ==================================== (1)choose a keyboard key combo for Radio 1/Radio 1 Modifier eg Alt 1 (2)do the same for Radio 2 eg Alt 2 (3)do the same for Radio 3 eg Alt 3 (4)choose a keyboard key combo for PTT/PTT Modifier, eg Alt O VA == add your own command for; SRS PTT(press) button: eg Joystick 1 Button 11, shortcut is invoked when no other buttons are down action: press the keyboard combo you chose in (4) and another for; SRS PTT(release) button: (same button as used for 'press') Joystick 1 Button 11, shortcut is invoked only when all buttons are released action: release the keyboard combo you chose in (4) VAICOMPro ======= 'TX1 press' you should have a mapping for the button(or preferably 4 way switch) eg 'when i press button: Joystick 1 Button 14', shortcut is invoked when no other buttons are down this will already have an entry for 'Execute external plugin...' below this add an action: press the keyboard combo you chose in (1) 'TX1 release' as it's only a ptt for VAICOMPro don't add anything to this, the action of pressing the button switches the radio only Holding will ptt to VA/VAICOMpro only repeat similar for TX2 and TX3 The reason to effectively use VA to 'translate' the keys for SRS was because i ran into problems if for example i use those same joystick buttons combined with a modifier(eg the 'pinkie') to do something completely different, which i do, i found that i was operating the radio when i didnt want to. Hope this helps someone

'left', 'down' and 'right' select the radio. Hold any of those and its the ptt to talk to the SIM/AI/VA, 'up' is the global ptt for SRS. Think about it, draw it on paper, trust me it works a treat

Been using them both for over a year. I use a 4-way switch on stick; 'Up' (hold) is SRS ptt, voice attack isnt listening 'left' selects box 1, left(hold) is TX1 ptt voice attack 'down' selects box 2, down(hold) is TX2 ptt voice attack 'right' selects box 3, right(hold) is TX3 ptt voice attack so i can talk to my human buddies without the SIM/VA intepreting anything.. and i can talk to the SIM box1/2/3 etc without my human buddies hearing. Isn't that what you want?

I'm on DCS ob 2.5.5 with the latest VAICOMPRO patch for 2.5.6 ob and i'm fine zero issues

+1 broken

just clarify, are you talking to assets 'with SRS', or do you mean you can't get anything from the SIM when SRS is installed?

don't shoot the messenger...but ......only with FC3 aircraft *i think*, for high fidelity aircraft you can set the channels in your .miz in the aircraft menu on the comms tab(looks like a wifi symbol) Someone will correct me if i'm wrong.

"don't use autopilot" +1 what's the point of doing something that just isn't done IRL ? You need to fly accurate formation first, then try A/A refuelling

did that as well as unchecking both controllers, re-checking, my VA reports all the normal 'listening resumed/suspended' messages, but additionally usually would show every spoken phrase, eg 'xxx recognized', but there is none of that

completely dead after the plugin upgrade, then the VA upgrade to 1.7.3 in that order. Any ideas how to resolve

re bad first impressions Hi, that made no difference but this config on the F/A-18C Sim Axes did; Thrust Left [JOY_X] Deadzone 0 Saturation X 50 Saturation Y 100 Curvature 0 Slider yes Thrust Right [JOY_Y] Deadzone 50 Saturation X 100 Saturation Y 100 Curvature 0 Slider yes I know not whether that is a workaround or how it should be, but the result is 2 identically operating throttle levers in game

bad first impressions Just bought one of these, I'd kind of expected the throttles themselves to work straight out of the box, but I am not impressed. When I try to add them to left and right thrust axes respectively in DCS World controls, I cannot get them to map in a logical way. The symptoms in game ( F18 ) are when I move the left throttle a tiny amount from 'zero' the throttle lever in game jumps to about 50%, then when advancing the throttle through its entire range, in game the lever travels to the fully forward position. With the right throttle, i have to advance the throttle all the way for it to go (in game) from zero to halfway. If i then just nudge it with very light pressure at the end of its physical travel, in game jumps to fully forward. I accept the fact that I may be being stupid(perhaps for buying a 3rd Logitech product ?) but i seem to be going round in circles(literally) with re-calibrating, inverting the axes, setting it as slider, most if not all combinationsi can think of but at the moment all i have on my desk is £200 worth of useless ornaments

i attempted to PM you, let me know if you got it please