Jascha

Dang... I just bought this module and was about to start training. Let's just hope that it won't took too long to fix this.

@Sokol1_br Finally, I've figured it out (took only 3 hours)! Here is a video demonstration. Maybe it will be useful for you too: But... unfortunately I'm unable to set these axes in DCS as I wanted. It's just how modifiers for axes work right now. Unlike modifiers for buttons, the unmodified input is still seen: EDIT: After thinking it thorough, actually it's not DCS fault. DCS doesn't know that this is the same physical axis. It sees axis RX, RY, RZ so no wonder using modifier with axis RY/RZ doesn't block axis RX from responding... What a bummer... Still... It could be useful if someone want just to split a physical axis in two separate ones.

Well the software is not very user friendly. I know I'm close, but can't figure this out. This post from il2 forum you mentioned is exactly I'm looking for, but there is no explanation how to do it! I'll try asking on VKB forum, although it's a bit... difficult to get a proper support in English over there, I think.

@Sokol1_br Well, if you had permanently enabled virtual axes (one for left twist and the other for right twist) you could bind them both to "wheel brakes" (axis = both wheel brakes input) and corresponding wheel brakes (axis = left / right brake input) using two different modifiers. And that's my plan with T-Rudder. In DCS this certainly seems doable. I'm not sure for IL-2, as I haven't use it in pretty long time (can you set custom modifiers for axis there?).

That's ARC-210 radio, not ARC-186. Editing UHF Radio preset channels (you must be in PRESET mode):

A-10C Tank Killer - ARC-210 radio "now in progress".

What? But don't you use the twist axis from joystick? If it's an axis, the virtual brake axes should work the same (not like buttons). Thanks. I'll try.

@Sokol1_br First of all, thank you for all your time. I appreciate your help. I'm not sure what I'm missing but that's exactly the opposite how I want it to work! It amazes me that T-Link doesn't have the option to invert this. Now, I don't fly warbirds much so I don't really need separate left and right pedal brakes, but if I would, I'd like it to work like this: when I press the Break Source Button (BSB) axes stay at 0%, and then applying left pedal input results in left brake force being applied from 0% to 100% and applying right pedal input results in right brake force being applied from 0% to 100%. Now it works like this - press BSB = 100% brake force, applying left pedal input results in RIGHT brake force being decreased from 100% to 0% and applying right pedal input results in LEFT brake force being decreased from 100% to 0%. Everything is the other way around. I want to apply left pedal so I can turn left, not release right pedal to turn left. Or actually, to be specific, I want to bind left and right virtual axes so pressing left OR right pedal WITH modifier will result in BOTH brakes going from 0 to 100 (so plane won't turn), as in VKB you cant press two pedals at once. Or at least I'd like to have an option to choose what setting I want. BTW how about Gremlin? Can you set it up like this there? Thanks a lot for the link, I'll check it. Because ideally I want to have the virtual axes constantly on without any software running in the background and than use modifiers in DCS axis assign setup to bind them. Well, it looks promising but assuming rudder axis middle is full left 0, center 50, full right 100, when I apply 50% left pedal (so rudder axis goes from 50 to 25) I want virtual axis left brake to go from 0 to 50 (virtual axis matches the pedal input). Makes sense? So in your example X at ~25% from right should mean axis Y to be at ~50%. That's clear. But it won't matter if the virtual axis are constantly "on", if they are not assigned. Here are step by step screenshots (axis X = rudder, Y = virtual axis for right pedal, Z = virtual axis for left pedal): No input: Only the Brake Source Button pressed: Left pedal ~50% down: Left pedal 100% down: Right pedal ~50% down: Right pedal 100% down: Yeah, but all it changed is in one version pressing the BSB resulted in 100% brakes applied and in the other releasing it resulted in 100% brakes (thus brakes being at 100% all the time). It is, afaik.

So I've tested the T-Link software after all (although I'd like to avoid software running in the background only for this...). No idea what I'm doing wrong but two virtual brake axes work for me like this: just pressing the T-Link Brake source button (no pedal input at all) acts as full brake: Then pressing the left and right pedal decreases the brake input. Also - in T-Link window right brake indicator is left pedal and left brake indicator is right pedal. Below, Brake Source Button in, LEFT pedal at 50%, RIGHT pedal - no input: Now, in DCS I can invert axis and pedals will work correctly (i.e. virtual axis 0 to 100, instead of 100 to 0), but in this case letting go of the Brake source button will leave the brakes at 100% al the time. I wonder if it's possible to leave the two virtual axes permanently enabled from the VKB profile configuration tool. But this software looks like you need a PhD in mathematics to use it.

Thank you for your take on this. I tried tweaking the axis settings but I couldn't come up with anything close to what I initially hoped for (no rudder input = 0% brakes, full right pedal = 100% brakes). When I tick the slider box in axis tuning I don't see a difference (rudder with no pedal input = 50% brakes). For now I'd like to avoid using 3rd party software and see if this can be set in DCS only. With use of DCS in-game options - I don't think so, but maybe some lua editing could fix this (I have to ask around as probably not everyone monitors VKB controls forum). It's interesting to notice, that when you let go of the modifier (slew push on Wartog throttle in my case) the brake input will remain in position according to pedal position when the modifier was released. So, modifier + max left pedal input would mean 0% brakes, release the modifier and no brakes position is "saved". Then when I apply brakes I use modifier + right pedal which operates brakes in range 50%-100% brake input. Then I just have to "reset" brake position with left pedal before releasing the modifier. Cumbersome, but maybe I could get used to it...

Thank you for taking your time to check this and to post a proper bug report. Regarding the VHF FM radio - this problem can possibly be related only to ATC. I had no problems communicating with JTAC on 30.000 MHz via VHF FM in SP campaign. I do recall that I couldn't reach ATC on lower frequencies (FM) though (once, not recently). I can't say for sure if this was A-10C or different module (F/A-18C possibly). But I didn't dwell on it, as there are other ATC frequencies to choose and I mainly use UHF radio to contact ATC anyway.

Easy communication are disabled (I have no frequencies in comms menus). I've noticed it playing the Georgian Hammer campaign. Tested in SP only. You can check it yourself easy. Just launch A-10C instant action, tune in UHF to ATC and use the two methods I described above.

Well it does. That was the point of this whole topic. If you use "\" comms menu (in DCS described as Interphone) you can "talk to all 3 radios". If you set the rotary dial to INT (or actually any position but VHF), the communications menu that is enabled by MIC forward lets you "talk to all 3 radios".

Thank you for clarifying this. So if I understand you correctly this means that communication menus and rotary dial in DCS A-10C don't work in 100% realistic way. However, we can always use them in a correct way. Communicate via VHF FM radio only with MIC aft menu (regardless of rotary dial setting). Communicate via UHF radio only with MIC down menu (regardless of rotary dial setting). Communicate via VHF AM radio only with MIC forward menu (with rotary dial set to VHF). (i.e. other means to communicate via these 3 radios are not realistic) And to communicate with ground crew (intercom) - as you mentioned. Is this correct? Oh, that explains why I was hearing TACAN Morse code suddenly without changing the TACAN volume knob.

Ok, now I feel like we are getting somewhere. This seems realistic. So what we currently have is a.. simplification where I can use one communications menu - the one initiated by "\", described incorrectly as "Interphone" that acts as mic for all 3 radios, which is not realistic. Is this correct? You mean in DCS or RL? Because that's how it works DCS right now. Well, kind of. FM and HF and INT (and blank) rotary dial positions let me talk on all radios from the same communications menu (initiated with MIC forward). MIC switch down and aft will get me ground crew as well. I understand that this should be correct provided that HM switch is on. Right?

I understand that Interphone is not a radio. I never said it is. I said that in DCS I can broadcast to to all 3 radio frequencies (that I'm tuned in to) via Interphone communications menu. Does Interphone in A-10C has separate mic switch? How do you use it in RL?

Yes, I'm aware of that. Just to be clear - I posted pictures of menus to show their radio description (or lack of) on the top. Description "VHF AM" / "CB UHF" / "VHF FM" over communications menu - means that I will broadcast only via the indicated radio. Description "Interphone" (or no description at all) means that I will broadcast on any radio (on frequencies that are currently set on them). I'm not sure if this is how it always was or has this changed recently. I'm using the latest Open Beta.

[DISCLAIMER: I have tested this in A-10C legacy but as far as I know it affects A-10 Tank Killer Upgrade as well.] Here is something that bothers me. A-10C (legacy) has 3 radios (VHF 1 AM, UHF, VHF 2 FM). I understand, that if I disable easy communications I have to set up correct frequency and use correct radio (mic switch) to communicate. According to the official ED manual these are: The communications menus will look as follows (example): MIC switch forward: MIC switch down: MIC switch aft: But in DCS there is also a keybind for communications menu (default “ \ “) which I occasionally use out of habit. Then the communications menu will look like this: What is interesting to me, with this keybind i.e. "Interphone" menu I'm able to speak to ANY frequency that is currently set on ANY of these three radios. Meaning - I can use it to speak using VHF 1 AM, UHF, VHF 2 FM (or ground crew). So here is the first question - is this realistic? Another (related) question is - is the rotary selector dial working as it should? According to the official manual (rather vague): (btw I don't understand "and monitor" in this description) From my tests this dial affects MIC switch forward. If I set it to INT and use MIC switch forward I'll get "Interphone menu" (same as “ \ “). If I set it to VHF and use MIC switch forward – I'll get “VHF AM” (default setting). If I set it to “FM” or “HF” (UHF?) or the last position (no description): in all these three cases MIC switch forward will enable communications menu like this (no radio indication at the top): This menu also gives possibility to speak to ANY frequency that is currently set on ANY of these three radios. Meaning – any setting of the rotary selector dial different from “VHF” will cause MIC switch forward to enable communication menu valid for all 3 radios (and ground crew). So the question is - is this correct? What’s also interesting, I can speak to the ground crew using any of the radio menus (any mic switch) with canopy closed (which doesn’t seem right). Now, this is only my gut feeling, but I think that: I should be able to talk on UHF frequency only using MIC switch down (and Mic switch forward with rotary dial in HF position?). I should be able to talk on VHF FM frequency only using MIC switch aft (and Mic switch forward with rotary dial in FM position?). I should be able to talk on VHF AM frequency only using MIC switch forward with rotary dial in VHF position. I should be able to talk to ground crew with canopy closed only using MIC forward with rotary dial in INT position. I should be able to talk to ground crew with open canopy using any communication menu. Any thoughts?

I tried setting up toe brakes for VKB Rudder Pedals with the use of modifies in DCS axis controls. For A-10C axis commands I used HOTAS Warthog slew push button as my modifier for the pedals axis X. Initially I wanted to have functionality where using the modifier and pressing the right VKB pedal will act as pressing of the wheel brake (left and right) in-game. It works but... not as intended. It turns out that after setting it up like this A-10C in-game acts as wheel brakes are being applied all the time (without me using VKB pedals at all) and when I use the combo modifier + right pedal it actually gradually releases the wheel brake in-game. I inverted the axis in axis tune options but all it changed was that this functionality has been assigned to the left VKB pedal. Any idea how to correct this?

I use USB hub with ON/OFF switches for each port. Very convenient. I've bought this one just last week:

When flying in formation smoke trails are not visible for wingmen in case of Su-25 and Su-25T. They can be seen when they are trying to join up and when they leave formation (attack target, RTB, etc.). Su-25 - 3 and 4 still joining formation: Su-25 when flying in formation. Trails disappear: Same with Su-25T. 3 and 4 still joining: Su-25T in formation: In case of MiG-29A this problem doesn't exist:

Just out of curiosity, how does CMS switch work for someone that has legacy A-10C only without the Tank Killer Update? Has this change affected only A-10C for A-10C II owners?

I've finally purchased the app and I love it. It really enhances the experience. Worth every penny! The installation and setup was quick and painless btw. So far I've tested it with A-10C an UH-1H and I have some (humble) suggestions & wishes. Please excuse my ignorance as I'm not a developer and I don't really know what's doable and what's not. Here's my list, sorted by priority (from my POV of course): 1. MORE FLEXIBLE PANEL ACCESS IN APP - I'd love to have possibility to choose order of the panels and also option to exclude specific panels from use. So let's say for A-10C I want only UFC and CDU so I can just quickly switch between the two. Other than that it would be handy to have (optional) panel quick access buttons (top or bottom) so it's possible to quickly select a specific panel. 2. MFDs - it would be great if MFD button descriptions are also displayed in the app. So for example, in case of TGP obviously there would not be an actual TGP feed but OSB labels as on the actual TGP screen would be visible in the app as well. Also, in case of A-10C, it would be great to completely emulate DSMS, the same as CDU. 3. MAP - option to choose topographical maps of the terrain as used in DCS 4. COMMS - dedicated communications panel where all F1-F12 commands are displayed the same as in DCS. 5. MAP ZOOM - option to set the default map zoom. 6. MAP ICON - heli icon on map when flying helicopters.

As I understand from the previous discussion, it has been confirmed that this is a bug. It has been reported and will be fixed (someday).