Weegie

Not on the aerobatics server anyway, it's a possible problem for sure. In the aerobatics they all have discrete frequencies and in the Hornet or Harrier you see the frequncy changing on the UFC. I haven't refuelled in a while, as I've been playing with the warbirds and earlly jets though Another possibility is coalitions but again aerobatics has all the aircraft on the one side if I remember correctly, need to go in and try it again

Many Thanks @hornblower793 @sthompson AND THE WINNER IS @sthompson Like the utter dullard I am, Batumi was a Blue base and I was in the Red aircraft, that had me foxed as I've not come across that particular problem for a long time Soon as I changed the base coalition Bingo Batumi called me right back

@hornblower793 Thanks I'll check but pretty sure both reciever and transmitter were set to the same frequency, think it was wave number 170 with frequency 4.25 I'll double check for sure @sthompson Good catch never even thought of that perhaps that might be part of problem and my ineptitude very much appreciated I'll be back!!!!

I've no idea if this is prevalent in other modules (for now) but I've been flying the MiG-15 and although yet to try all of the Caucasus airfields I can get some to register fine, but others not Kobuleti, Anapa, Kolkhi and Krasnodar all pick up fine, but I cannot get Batumi or Krasnodar Pashovsky to be recognized at all. The VA window is telling me the commands are recognized, but I don't get the confirmation Beep and nothing happens. Tuning in manually to Batumi doesn't seem to work either. Sometimes it's hit and miss as I did get Select to regonize Batumi once but I still could not establish comms with the tower. Anybody know if this is a bug or is it specific to my setup? If so any recommendations?

Just checked now I have Batumi responding in the VA info window but no audio, it must be Vaicom that's flaky I'll post up in the Input/Output to see if I can get any joy there

Need to check for sure @Art-J I used the dial on the LHS near the throttle and I believe it dials in both transmitter and reciever but when I run the module again I'll double check. It's odd and yes 170 dialled in with Vaicom telling me the frequency selected was 4.25 MHz yet no reply, I'll try it without Vaicom to see if I can get a response It may well be Vaicom, I tried the "Select" command where Vaicom dials up the frequency for you and nothing happens with Batumi but the others I tried had the dial jump to the correct wave number. Then I dialled in the frequency manually and tried, same thing no reply. Thanks for checking for me appreciated, I'll report back if I can find anything

I'm just getting started in the MiG 15 have not been near it in ages Anyway using Vaicom so not sure if it's a Vaicom problem or the module I can talk to Kobuleti and Senaki but whenver I dial up Batumi on 170/4.25MHz, nothing!!!! Just wondering if it's a bug or if I'm the only one having this problem, yet to the other airbases Either way really fun module, I'd forgotten how good it is

Let us know how you get on Sorry to hear that's happened, I feel your pain I hate when something like this happens I did have problems with a Mamba a loooong time back and VKB were very responsive Fingers' crossed for you

I'm not having any problem with the top center hat. I substituted the analog ministick for the four way hat with push and it's working fine Both firmware versions I know of are at v2_02_5 and you selet the firmware for either twist or non twist What is the exact problem you are having? Is it failing to register a button? That could be software related you can use the VKB_Dev_Config program to tailor the buttons to what you need VKB has a nice video tutorial on how to https://youtu.be/nEJk0yytoXw I've attached the firmware files, I'm running a non twist stick so using that version, I also calibrated the stick and base after uploading the firmware to be sure all was Ok Perhaps you could try them _BlackBox_MK2_GF_MCG_Ultimate_Twist_v2_02_5.vkb _BlackBox_MK2_GF_MCG_Ultimate_v2_02_5.vkb

I'll try to have a look later @XecutriX You are quite correct on the swapping of keyboards I've now got a label on the right of the Taskbar where I can change keyboard type on the fly. I usually only change from the native keyboard to the US American specifically for commands that use R_ALT (ALTGR) and then change back to native for any other commands I'm making keystrokes for. I haven't ran in to your problem but I don't use the Keystroke Hot Key that often, so I'll try to see if I can make 2 commands in a profile, one incorporating R_ALT and another for the "Numpad /" key to see how it behaves

@Lostaviator if you go back to the previous page on this thread, I made a small profile which you can either append to the Vaicom profile or import the commands into the Vaicom profile to open the tabs and the kneeboard if it's of any use

Just in case anybody else encounters what happened to me and panics So plugged in the new grip and checked in VKB_Dev_Config..................nothing the grip wasn't being recognized, the Gunfighter base was, this was a new problem I had never encountered. No buttons recognized, nor the analogue lever and none of the LEDs on the grip were lit. After going through all the usual hardware checks, plugs, seating on the base and the extension etc: I started to Google and apparently this has happened with earlier MCG grips prior to the Ultimate. Onto VKB North America a big shout out to @AeroGator at this point for making it so easy to grab all the latest software manuals and firmware, not to mention his awesome How To's on You Tube. Superb stuff and thank you, as VKB instructions tend to be on the (Ahem!!) succinct side. After downloading the firmware package which gives all the latest firmware currrently available and unzipping, I located _BlackBox_GF_MCG_Ultimate_v2_02_5, there is a different version for those with the twist function. Flashed it and now all working.................Whew!!!

I have VSPX on too and agree with @MAXsenna but I'm not sure if the kneeboard commands are all recognized using VSPX. In general the kneeboard commands and tabs can be a bit flaky, there have been a lot of posts on various tabs and calling the kneeboard command not being recognized. I am ASS-umming you have the Interactive Kneeboard. A workaround I use is to call the Plug in Directly from the Vaicom Profile by placing in some extra commands and for opening/closing the kneeboard just using the DCS menu keyboard command Dunno if this thread might help or not

Had this happen several times on the Aerobatics server, it runs easycomms though. You'd select a particular tanker and get another, tune the radio to the tanker you want to talk to and the frequency would change on the radio and you'd be talking once again to the same old tanker you do not want to contact. For me its been buggy in MP for some time but I can't find out why, it's not generic in all servers, and it also works for me in SP. Even the servers that do this don't do it everytime, I just gave up on trying to find a reason I thought using the call Tanker, or nearest tanker selected the refueller you were closest too, time to dig out the manual again I guess

I'll experiment some more with mine and report, I suspect it'll be as @Monkwolf states. I'm not too fussed on absolute centering, my rudders with a damper are the same, they center approx but not bang on and I'm well used to that I much prefer having the smooth and lighter feel with the downside of an inexact center, rather than having to haul against stronger springs which induces unwanted input (with my ham fisted approaches anyway). This is the downside of getting new hardware (not that I'm complaining you understand) there are so many available options that it can take a long time to even approach your preferred settings. The Grip is awesome now I need to program the LEDs and buttons to match what I had in the Mamba Thank you all so much for the assistance, "I'll be back"

Many Thanks to both @dburne & @Monkwolf I started with a #50 & #30 but after reading Monkwollf's post and a quick trial of the feel I've now got a #40 & #20 and dialled up the clutches to about halfway from where they were from the factory to tight (around 7 turns), so I reckon about 3/4 too. Feel is terrific, stick is light but the friction from the clutches give a lovely buttery, linear heft to the movment. It feels fantastic and like you Monkwolf I reckon I'm going to experiment with lighter springs, down to a #10 or perhaps just leave in the #40, for starters and later play more with the clutches. My Mamba is fantastic and I didn't think it could get much better, now I know different, this setup is another step change I didn't imagine possible

Of course I'll need to just experiment, but I thought I'd get some advice on what other members are using for the Cams, Spring weight and clutch settings for the above for Gunfighter MK III base I perfer a light center and ideally a smooth heavier feel to the stick movement. Thinking of trying a couple of 40 springs initially then seeing how I get on with that, currently have the Avia light center cams in (I think) For now I'll leave in the light cam and not mess with the clutches I read that the Space cams have virtually on center detent at all and wondered has anybody experimented with them yet?

I don't think I'm understanding your probllem @701 In my ExportsModules I have a file F-16C_50.lua, now I cannot remember if I got that off the forum or it's an ED file (I think it's an ED file though) I haven't attempted what you're trying to achieve but I have a very quick and dirty profile for the Viper using Cytler's tool for the StreamDeck and last I checked it was all working fine

One method, though it may be considered a cheat by the purists, but IMHO is no more of a cheat than curves or other methods. For sticks where the software is capable of implemetning it or using free joystick software like joystick gremlin (I think) is to map a button that reduces the sensitivity of the pitch axis (and anything else you want). It can be programmed in TARGET, using the Editor, or VKB_Dev_Config where the range of the virtual throw can be reduced but the physical throw remains the same, this decreases the sensitivity meaning you can move the physical stick more in relation to elevator movement. Using that method means it's a lot easier to fly during normal flight but can give full throw for dogfighting etc: at the touch of a button. Virpil software probably has something too but as I don't have any Virpil devices I don't know

Since using @grafspee recommendations of running the engine at 1100-1200 rpm from cold, I've not encountered any problems and before it was quitting on me all the time What I do is throttle up to to 1100 give or take and then straight out and taxi using the brakes, don't touch the throttle. If a medium to long taxi is required with the radiator shut, default on start I believe, by the time I reach the runway I'm pretty much good to go with minimum temp I also try to stay clear of the RPM range idle to 1000rpm where the aircraft shakes, I don't know if that is also modelled to break the engine, but better safe than sorry Pre warmed option would be good for MP, as you are at the mercy of the server on the aircraft state, of course you might find that if it's introduced then the server might disable it. I've never checked but when starting from taxi I'd have thought it was already warm, but that's just a guess

There isn't an option as such, when Voice Attack is started the Vaicom version is automatically checked to determine if the version running is the latest. When a new version is available it will ask if you want to update to that version via a pop up If I'm not connected to the internet and start Voice Attack I get a version check error box, along the lines of unable to contact server, after a few minutes. I'd also check the Voice Attack version too, I don't think it was the last update, but there have been issues in the past where Vaicom can't update to the latest version because Voice Attack wasn't running the latest version My version of Vaicom is reporting the version on the Vaicom pop up as 2.5.24.0 One other thing you can do to check version numbers is to go the Help Tab in the Vaicom pop up and click on the DIAG button, this will give you a version list of Vaicom, Voice Attack etc: and tell you if the latest version is installed

That's odd, there's also the auto update, I haven't had to complete a fresh install in a while. I'd have expected that if you downloaded V24 but ended with 23, then Vaicom should also have Autoupdated I assume you're running Voice Attack as an Admistrator Have you checked that you are also running the latest version of Voice Attack, mine is V1.8.7 You can see that under the Options (wrench symbol), General Tab, System Info Box, Voice Attack Information option If that's all up to date I'd raise a ticket on the Vaicom website asking about the discrepency, you're more likely to get a quicker response there.

If you look at the picture you posted of the Vaicom pop up menu, you can see on the bottom in small text the version number, it's shown on all the pages. According to the Vaicom site 2.5.24.0 is the latest version

Can't comment on the "Other Sim" Like the others here, I find the Spitfire a joy to fly stable and predictable (well perhaps taxi-ing can be a bit fraught, initially, even then, now if I taxi slowly I very rarely even use the brake) I find it much easier than the Axis warbirds to fly Post up with your complaints, lots of offers of help and that includes me. I can't give you tips on combat but taking off landing taxi-ing and free flight I might be of some assistance, be a shame to give up on such a nice module

I don't have the SpitfireLFMkIXCW_easy but do have SpitfireLFMkIXCW @imacken, I "think" what happens is if you alter the settings then DCS will make an appropriate folder to store the info. So I'm thinking you perhaps went into the CW "easy" and made changes there. I think what I did, it's been a while, was copy the folders and files in the SpitfireLFMkIX folder into the SpitfireLFMkIXCW folder Alternatively if you've already made a bunch of commands in the SpitfireLFMkIX_easy by mistake just delete the _easy on the end of the SpitfireLFMkIXCW and I'm pretty sure they will show on the settings for the sim version of the settings