hornblower793

https://forums.eagle.ru/showthread.php?t=272323 will give you the discussion about Radio Tune for Sector scan it is worth reading the latest version of the manual page 43 on and check that the commands are all listed and add them if not - these are different from the normal command words when used - you need to say them as a phrase rather than leaving pauses between words

There is a whole separate thread on TACAN tune and similar commands - will try and point you to it later when I am on my machine. In terms of the commands, some are command phrases and don't appear in the dropdown list but only in the VA list of commands for the profile. Again, will point you in the right direction later if noone has beaten me to it Sent from my SM-T835 using Tapatalk

You can just train the commands you want so you only need to do those you skipped:thumbup: For the Select command, try adding it to the Microsoft speech dictionary and recording it. To do this, right click on the Microsoft microphone when in speech training and select Open the Speech Dictionary and then add the word

I am but only have this issue / messaging becoming unresponsive after takeoff on a few of the modules. What I have found is that it only happens when Easy Comms is off and once I have used one of the modules with an issue it then appears to affect other modules until I restart DCS (no need to restart VA). For the FW190 my issues start the moment the wheels leave the ground - I have provided @Hollywood_315 with the details and also what I see in the VAICOM PTT window. I am working through the other modules where I have issues to see if the symptoms are the same as this. Running latest versions of VA, VAICOM and DCS OB standalone Sent from my SM-T835 using Tapatalk

Looking good Sent from my SM-T835 using Tapatalk

Hollywood is taking a look at this case to see if he can figure out what is happening. I think it may help with the other airframes as well

I have just been playing around some more and this doesn't seem to occur if Easy Communication is On and the radio works consistently throughout the training flight. I then turned Easy Comms off without changing any other settings and repeated the test. The two screenshots below show the VAICOM overlay on the runway and shortly after takeoff with the PTT button pressed. The first clearly shows the radio tuned to the recipient while in the second this information is not present (and it does not show the radio in use either)

I have seen this and have sent Hollywood a question about it. The radio works fine on the ground but stops as sonn as the wheels leave the ground Sent from my SM-T835 using Tapatalk

The new design looks fantastic and I am already really enjoying the first trial set so can only imagine what these will be like to use. The rough surface on the has allowed a superb level of grip in socks so wouldn't want them smooth anyway Sent from my SM-T835 using Tapatalk

Can't wait to try, although I have no real complaints about the ones I have now

I play 1440p on a curved 34" and it looks fantastic

These will be the re-engineered bars for adjusting the spring strength Sent from my SM-T835 using Tapatalk

Yes you can refer to your original post - click on the post number, then copy the url and paste it into your new message. Sent from my SM-T835 using Tapatalk

I also fly VR and have mapped the keyboard PTT key combo to the push of the Warthog thumb button. When you have problems have you used a SELECT command at all? Does options > take x work if it is the first thing you do when you have entered the mission? Sent from my SM-T835 using Tapatalk

I am also happy to try these:thumbup:

Please could you give more details such as airframe, what you are trying to do, version of DCS etc., whether easy comms is on or off etc. Sent from my SM-T835 using Tapatalk

Does the command work for standard menu items (e.g.contacting ATC) and does it work if it is the first command you use once you have spawned (and tuned the radio to the correct frequency)? If it doesn't, does it then work once you have pressed the keyboard PTT key? Do you run Easy comms on or off? Which version of DCS do you fly? Which VAICOM extension packs do you run? Sorry for the questions, but trying to pin down a simple set of steps to replicate the problem (or maybe find that everyone's is different). Sent from my SM-T835 using Tapatalk

I have just taken my Huey for a spin and can confirm that these pedals gave me a great feel in rotary wing as well

Will make sure I give them a good hammering over the next few days for you and then take them off and take photos so you can see how they are standing up. I will also try more with footwear on as I know I push harder with a solid sole under my feet. Testing yesterday was largely focussed on braking to taxi my taildraggers without locked tail wheels. Will try some more aerobatics / aggressive airborne maneouvres to stress them as rudder pedals as well Sent from my SM-T835 using Tapatalk

There should be no issue - mine is the other way round with Windows on the NVMe and DCS on the sata SSD and it works fine. Considering getting a second NVMe for DCS Sent from my SM-T835 using Tapatalk

Does the motherboard have a second M2 slot? Sent from my SM-T835 using Tapatalk

Have now spent a reasonable amount of time taxiing, flying and landing WW2 warbirds and I feel like I have a great degree of control with the pedals and there is no feeling of flex that I can detect. I have settled on aligning them one hole back from the most vertical (which hurts my ankles). The holes in the pedals (I am trying the F-18 ones) feel fine with socks only (I don't fly barefoot but cannot see it would make that much difference) and braking has a nice feel to it.

I have now done some more testing and think I have narrowed the issue down (certainly in my case) to something related to air starts. I used one of the built in free flight missions as a base and in turn tried the FW190-D9, KA-50 and P-47. For each one I first set up a very simple flight plan of takeoff from runway and then fly to a waypoint. When I flew these all modules were instantly recognised by VAICOM and the radio behaved as expected. For each in turn I then changed the 'takeoff' point to a fly over point in the mission editor without moving it and left all other settings unchanged. On flying starting the mission, the FW190 was not recognised by VAICOM until I pressed the keyboard key for PTT and then the radios worked until I issued a select command - after this nothing worked (including selecting from the menus) until I used the keyboard PTT key again. Would be useful if someone else could also try this testing with one of the modules they have an issue with and see if the behaviour is the same. In this, I also noticed that the comms menu appears at random when a command is issued and I had to use Take 12 to clear it. This has only happened since the Jester backup wheel was introduced

I don't think it is that @Hollywood_315 doesn't acknowledge the problem but if it cannot be replicated on the test rig (we are not talking a big company with loads of test rigs) then it can be very hard to track down ( I know because I spent many years coding / leading development teams). It would possibly be helpful if everyone could run the same scenario, albeit with different airframes, to see whether the misbehaviour is consistent. I ran all mine throught the DCS Instant action freeflight missions (see previous post in this thread) but interestingly could not get the same behaviour in simple missions I created with just a single airframe. I will experiment further later and see if I can find anything Sent from my SM-T835 using Tapatalk

Received my pedals today - I don't have an issue with the spring force on the weakest of the standard holes in the MFG set so have not yet installed your system (I ran them on the second strongest with the MFG footplates). I initially tried with the same spring force and then adjusted it down My pedals are S/N 6461. In terms of vertical adjustment I currently have them 1 setting more vertical than Lang_666 and am running them on the upper set of holes in the plates (so they are closer to the ground). I tend to lift my heels slightly when using the rudder, but I think that is just a question of adjusting my muscle memory (I used to run with flatter pedals when they were whole foot). I am also sat at a desk but fortunately have a gaming chair that allows me to get low enough to avoid bashing my knees on the desk. It might also be worth seeing if the mounting holes can be moved horizontally towards the centre of the plate a bit (probably only 0.25 to 1cm), or adjust the top hole to allow a bit of angle adjustment - with the holes as they are at the moment it places my feed slightly wider apart than the standard MFG pedals and I used to have those angled out slightly. I would possibly like the pedal plates to sit slightly lower to the floor (i.e. have the holes a fraction closer to the toe), but haven't had the opportunity to play with them enough to be sure. I am sure some of it is they just feel different to what I have become very used to. Initial try was with my normal house footwear on. Am about to run a test wearing just socks with a WW2 bird to see how they feel and will feed back more after that. Having said all the above, these feel sturdy and I certainly didn't feel like I had less control over the plane while taxiing, taking off or landing. Good job:thumbup: EDIT: Have just tried the P-47 and had a nightmare on landing, but that was 100% due to my poor airmanship - the pedals felt great:D