Weegie

I'm average on a good day, but I can AAR all the other modules, perhaps not first go but probably more often that not, I do find the Viper a challenge. The Jeff though is giving me a real headache I think the problem lies with pitch sensitivity, I so much as look at the stick and it's off all over the sky. I then release to let the PIO fllatten out but the slightest touch on the stick again and boom off on the roller coaster, it's like a day at Allton Park (big funfare) I can't understand it, if it was that hard there would surely be a lot of tutorials out there, but there's not. The few I found seem to keep the refuelling pod center on the HUD and the drogue goes in, as most other modules. I try that and get a face full of basket, followed by the pogo and the tutorials don't seem to reflect that. Has the flight model has been tweaked since the probe was added at any point. What on earth am I doing wrong bacause I sure as hell cannot figure it out. Think I've managed a connect to full in a single shot twice out of hundreds of attempts

Much appreciated for the compare@Minsky Your kneeboard sheets are fantastic BIG THANK YOU for them too

Terrific Result, I agree I hate it when I have an issue like that

Thanks @Apache600 I first noticed when a new kneeboard page from @Minsky appeared and specifically mentioned this. https://www.digitalcombatsimulator.com/en/files/3312200/ I hope they put the frequencies back to the old settings No explanation or detail makes it really frustrating

It's not a problem it's just the way DCS is configured The "Axis" category is entirely separate from "All" confusing as that may sound it does make sense "Axis" covers what it says where you are able to map the Axes you have available from your hardware "All" covers digital inputs, be they Keypresses or Dx buttons. The reason you see the same command repeated is DCS is trying to cover more than one base to accomodate those of us who have multiple axes available and those who may not so they can use a digital input instead operated from a Joystick hat or directly via the keyboard. So if you have rudder pedals and are using the axes from them, then there isn't any need to use the keyboard command. You can just ignore it or you can delete it if you like, as long as you don't map it to a Dx button or use that keyboard combo then it shouldn't interfere with the axis commands. As far as Zoom is concerned, AFAIK there are digital inputs for Zoom, in fact I think there are 3 a fast slow and normal for each making 6 in total. The usual default for digital zoom in slow (which is what I use bound to hat on the stick) is the Num* key. If you press Num* key the "All" will jump to that position and you should see it, it is listed under Zoom and is at the bottom of the list Hope that helps a little

I commend the team for the fixes and additions to the TACAN and ATC My question is have they altered some of the exisitng ATC frequencies? I've yet to fully check it out and I hope I'm wrong If they have been altered this is going to screw up all the Frequency tables and maps for PG the community has produced in the past. I have no clue what it will do to Vaicom but suspect that will have some wrong frequencies assigned until the next update as well

Unfortunately I can't use VKB US coz I'm in the UK I'm already in touch with VKB Europe over this Had no intentions of purchasing a new stickright now but that looks amazing, just hope I can snag one when it gets released

Not sure and wait for @mutz to answer, but I think he's referring to the orignal Export.lua, this may contain lines from other programs, example TacView to name one. I'd recommend renaming your old Export.lua to something like Export.old so as it's not overwritten. Then when you point Vaicom to the correct path it will make a new Export.lua. Open them both then add the extra lines in the Export.old to the new Export.lua so as nothing is lost.

I haven't used Bailey's F-14 profile so could well be talking outta my ass here, but some thing's to keep in mind. I am ASS-umming you have Vaicom as the primary Profile with Bailey's F-14 profile appended, I've found that to get stuff to work well, it's best not to append too many profiles, ideally only one. As Vaicom is the primary if you use a phrase in Bailey's profile that's also in Vaicom, Vaicom will "grab" it and not pass it through to Bailey's profile. Check the VA window to see what's happening with a command that's giving you trouble. You can also check in the Vaicom editor to see if the words are in the Key Phrases. With Bailey's profile you could change the "When I Say" to another phrase to get it recognized, or simply delete that phrase out of the profile. Another option is to run Bailey's profile as primary and Vaicom as appended, it's not recommended but it shouldn't break anything and you can just swap it back if it doesn't work. Can you give some examples of the problems as it's kinda hard to troubleshoot the problems without any specifics?

As others have already said it depends what you want to do, if you're looking to just map, keys then probably no (although it can enhance flexibility.............a lot). If you really want to get the most out of what the HOTAS is capable of then its a must. TARGET can also do Trims, curves and change axes limits on the fly. It can turn axes to button presses, and have buttons replicate axes albeit in a limited way. I use it in conjunction with Voice Attack and love the flexibilty it offers. That said it needs some time invested with it to understand the programming, but even starting with the GUI is useful then moving to the Editor later. To realize its true potential you really need to have a rudimetary understanding of the programming language. The TM Script guide is IMHO the best place to start with that. I would hate to be without it now and wish there was a commercial standalone software equivalent that I could use with other devices. Voice attack is the nearest I've found for buttons and switches, but can't help much with axes.

Different problem that's why I quoted eagleace specifically. I gather you've tried putting in a command into the Vaicom VA profile for the ATC tab and that didn't work, if not surely it's worth a shot? I've got all the Interactive tabs working via the "Execute an External Plugin Fuction" using the commands detailed in the manual. I use VSPX and as of now not all the calls work via Vaicom on its own, without the additional commands being added into the Vaicom profile . Other than that I'm outta ideas @hornblower793 or Hollywood himself are the best bets to help you. I'd also go direct to the Vaicom website and raise the query, although Hollywood visits here from time to time, I've always found shooting a query on the Vaicom website gets a faster response than posting up here.

Tee Hee @colubridae naw I'm not English but the missus is & from Cheshire originally ;o) As far as the lockdown, think it's much the same for everybody, just a different face telling you what you can't do (good excuse to learn some more about my modules) Anyway back to the snap views thang, BigNewy's video on how to do a repair (Don't know if you can embed YouTube vids on the new forum engine) https://www.youtube.com/watch?v=x5DImUpk0WU Another approach is to download and use skatezilla's tool and have a GUI to do all this sorta stuff https://forums.eagle.ru/topic/134493-the-dcs-updater-gui-utility/?tab=comments#comment-134499 Try either any probs shout up let us now how you get on, I'm still trying to get my snap views to work with the AV-8B for some reason it doesn't seem to save mine. Small tip once you've made views you're happy with, before making more it's a good idea to backup the SnapViews.lua file in the Saved Games\DCS*\Config\View\ directory. Just in case something overwrites it (this is what is happening to me with the AV-8B and I lost all my other snap views)

Must admit I haven't noticed that but not been in the Tomcat a lot recently. I use VA to go to various pages on the kneeboard and noticed that whenever the Interactive kneeboard had any updated info to display it jumped to the relevant tab and found it really annoying To stop that Uncheck the Auto Browse box in the EX tab of the Vaicom pop up window, it's on the right below the slider that alters the Interactive kneeboard opacity Hopefuly the same thing will work for you

Apologies I misread your post ATC also working fine using kneeboard.tab.atc command in the Plug in Context box that's within the Execute an External Plugin Function command in VA I did have some trouble getting VA to recognise ATC, so used the following in the "When I Say" box [ATC;EhTeeSee;Traffic;Tower] Data VA will then select the ATC tab when I say "ATC Data" or "EhTeeSee Data" or "Traffic Data" or "Tower Data"

I'm running TrackIR 5.4 and it's working fine for me, if you're experiencing that sort of behaviour with TrackIR disabled it sounds like it's a DCS issue. I can't really help as your problem sounds like it's beyond my (very limited) technical knowledge. The normal Keybind is R_CTRL 0 which Toggles the Snap View On/Off. I'll check later to see if it can be changed in the keyboard controls and if it can, does it work properly. Some keyboard commands can behave strangely, it's rare but it does happen. I see you're in Cheshire so Ass-umming UK Extended keyboard, same as me up in Jockland. Just one more thing have you tried running a repair just in case something has been corrupted @Rudel_chw flying the Viggen Good Man I love that bird

I'll certainly give that a try many thanks @Lange_666 EDIT: Just put in the code but changed it a little mainly to change the axis scale rather than the curve, but both would work fine I guess, just what I wanted to do. So I changed the SetSCurve(&Joystick, JOYX, 0, 0, 0, 4, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 4, 0) to SetSCurve(&Joystick, JOYX, 0, 0, 0, 0, -2); SetSCurve(&Joystick, JOYY, 0, 0, 0, 0, -4) That gave me Virtual axes of 25% Y (12.5% either side of the 50% center) 50% X (25% either side of the 50% center) For 100% physical stick movement. It works a treat!!! Still gotta experiment what's going to work best, but that's great thank you so much

K Thanks @Dauntless I'll try some more to see if I can issolate WTF is going on with my setup. It's not so much of an issue now as I've backed up the SnapViews.lua, so at least it doesn't leave me having to redo all the other Snap Views, when the file is overwritten

BUMP!! 47 Views & nothing, not even a Yes or No??

I was wanting to get a button or switch to change axis scales on the fly, handy for when wobbbling everywhere during AAR. Within the SetSCurve command the last digit input can alter the scale so I was trying to write a command then use an EXEC to run it so as I could change the axis scale but so far no joy, TARGET compiles fine but just ignores the command. Any TARGET wizards out there able to enlighten me? For example when I press a button or activate a switch the virtual axis/axes would be limited to 25 or 50% range. The physical joystick 100% range would limit the input into the game of 25 or 50% of the axes range?

AAR tab working fine for me using the kneeboard.tab.tanker command in the Plug in Context box that's within the Execute an External Plugin Function command in VA

Ok just tried that and no luck I'm afraid, I cancelled the Listen command using a VA toggle but the Plug In immediately countermands the Toggle and sets VA to listen immediately afterwards. So no joy, sorry. There may be a way to achieve this using a combination of exposed vairiables and perhaps using Single on the PTT Rotary, but it isn't immediately apparent to me. If I was really set on doing this, then I'd go to the Vaicom website and drop a request direct to them. My dealings with Hollywood and the team there have been nothing but positive. If you don't have any luck post up again and I'll see if I can up with something, however if Hollywood can't help I very much doubt I can

Hi @Biga42 I had a look at your post already and didn't comment as right now I don't know a way to do that I believe that Vaicom recommends that you do not have a global PTT as you have on the first picture. The buttons in VA are actually PTTs not radio select buttons according to the Vaicom manual, in reality they do both. The Vaicom PTTs execute the Plug In and the Plug In also starts/stops VA listening. You could null the command which starts VA listening by issuing a mute command directly after that but I don't know how long the radio remains selected in Vaicom. Let me experiment with it in a module to try it, but I'm not holding out much hope. I'll get back to let you know how I get on It seems a strange request as it just uses another PTT on your HOTAS is there a particular reason to want to use that configuration?

I'm asking because I can save Snap Views in all the other modules I've made custom snap views for so far. When I try to configure Snap Views for the AV-8B they work until I exit the module, when I re-enter the module the Snap Views have gone back to Default I also appear to lose all the Snap Views for the other modules when I save Snap Views for the AV-8B It could well be me but I just can't seem to get them to work for this module so I'd thought I'd ask if anybody else is either having trouble with them or if others have been able to sucessfully save Snap Views for the AV-8B? Thanks

I've been having some difficulty with this as well Eventually I think I've got them sorted, for now, but I'm still having problems with the AV-8B which seems to just go back to it's original bindings and if I'm understanding it also loses all the other custom settings for all the other modules. I may have this wrong as I'm still experimenting. What I did is follow @Rudel_chw 's advice thank you for posting. TrackIR Paused or off before starting to configure the views and also adding in a TrackIR pause prior to activating the snap views once they are saved When I'm configuring the views I'm using the keyboard commands and when I finish a config I exit out the game then go and save the SnapView.lua file in the Config\Views directory I'm using VA to do execute the Sanp Views, although my method is slightly different to Sunstag's. If it helps @colubridae I could make a short vid showing how I did it, but as I say it's early days and I'm still messing with it

@Judy1301 Can't help with the Comms problem but I run VSPX and added the Execute External Plug In commands as detailed in the manual to call the Kneeboard Tabs up and they work great for me When I'm next in DCS I'll look at what the PTT page is saying for Easy Comms, but I cannot recall havinng any problems.