Nereid

Thanks. It seems it is still broken. But for some airports it works, so I thought it was already fixed.

Well, maybe this is terrain related (Syria map in this case), maybe I'm doing something wrong or maybe this is a bug. I'm taxiing to the correct runway and hold before the holding position line. Then I'm asking for takeoff and I do not get any response from ATC. . If I'm ON the RWY and asking for permission, it works. At some point on the RWY ATC often tells me instantly without asking them they cannot give me takeoff clearance or they give me a direct clearance for takeoff. This happens on some maps and some airfields/airports but not for all. On some it works like a charm. Stopping on the holding position line, asking for takeoff and go. This time it happens on the Syria map, Beirut Rafic Hariri airport, RWY 17. Radio is correctly set, I got permissions to startup and taxi.

I know about the trials. I'm using them for myself and bought the Mosquito because of this. But please keep in mind that some just use steam and they will not even think about registering for a trial on the ED website - if they even would know of it. I'm using steam myself for all other games - but not for DCS. Steam is a great plattform to aquire customers. This friend I was talking about, told me after his trials (on steam) about it and that he failed in every aspect. And as I said: I don't think the module itself or any bug was the reason for his giving up, but he wasn't interrested enough to spend more time on it. If he had told me about his plans, I would have suggested a trial license myself.

Thanks. I have a friend that told me he had trouble with the TF-51D as he was testing DCS for his first time a few weeks ago. That's why I was checking the TF-51D myself. I don't think he will ever come back or he would have purchased any module if there were no such bugs. But trying DCS a frustrating experience for new players even for the good stuff. You really do not want bad stuff to scare them off in addition...

That's not the point. People new to DCS world (and the TF-51D is intended to target those) rarely edit .lua files. So the bug is not fixed and that is the point.

Any button. I tried it on a switch on my throttle.Push for close and pull for open and it does nothing. The axis for the canopy crank it not really usable either (and no, there was no axis assigned while I was trying a button). For the P-51D it works, but not for the TF-51D.

And the TF-51D is their demo for full DCS modules. At least the most obvious bugs should be fixed as soon as possible. A desync with an axis is not that important (even if it bothers me, but beginners rarely use axes for flaps), but non-functional keybindings and desync of instruments/levers/switches with keys pressed should not happen.

The same problem (desynchronization of the flap handle) exists when using an axis for flaps...

Is this bug still not fixed? I'm trying the TF-51D and opening/closing the canopy with joystick buttons won't work.

That would explain why it doesn't happen all the time. But it seems that just a single airfield is affected by this (Lympne as far as I remember).

This is a bit far away for WWII aircraft, isn't it? It seems they changed it. I didn't used this for quite a while near the runway. in modern aircrafts it is more or less not necessary but in WWII planes navigating is kind of a struggle. On WWII maps it's a bit of a problem, because the airfields are hard to see sometimes. It seems the best way would be to call an "inbound", calculate the flight time and look in the direction of the RWY. But on 10 miles you won't see some airfields. Hunton is about 9 miles away from Headcorn, so the initial point if 10 miles away is somewhat south. Is the bug that one airfield identifies itself as "Kresnodar" already known?

Ok, I'm a bit puzzled and maybe I'm doing something wrong. But as far as I remember if one contacts ATC and requests for azimuth, ATC gives the course to the airfield. On The Channel map (I did not test other maps so far), I'm in a Mosquito over Hunton SWS from Maidstone and I'm contacting Headcorn ATC requesting for azimuth. On the map my course to the airfield is about 120 but ATC responds with 201!? ??? BTW: Some of the airfields identifies itself as "Kresnodar" (not everytime), but this seems to be a bug.

Yes, I found this myself a few minutes ago. Unfortunately most if not all cold start tutorials skip this part (even Matts cold start) and in some the switches stay in postion what they not seem to do in the current build.

If I do a cold start in the AH-64D and use the radios there is a lot of white noise there and I can barely hear the ATC (it is very quiet). The squelch buttons on the right panels seems not to work at all. This is not the case in a hot start mission. Any ideas? Got it: you have to push ALL squelch switches to get rid of the noise not just that one for VHF.

For me it seems weird that the CP/G can't control the aircraft even if the pilot wishes this. So I would like to see an option/command to tell George as the CP/G to take control. And maybe it's just me, but often my controls (trim and collective) won't match if I take over again which cause a lot of trouble.

I have the same problem. It just happens near the ground. The whole sim freezes for up to 1 or 2 seconds, sometimes only fractions of a second. But it happens EVERYTIME on start of every mission. Lowering the textures doesn't help. Neither did installing the latest NVIDIA driver. Specs: i7 7700K RTX 2070 super (8GB) RAM: 32 GB DCS is installed on SSD EDIT: Lowering other settings seems to help a bit. And it seems it is somewhat map related, but I'm still investigating.

I can't compare it to the old CM, but as a CH user I thought the CH quality was good (well their sticks and throttles last forever), but the Virpil quality is outstanding.

Map the encoders to a virtual axis and use the axis instead.

I have only noticed this one. But to find your lua was not a big deal anyway. ;)

If you are interested, you can try my soltion for this: VLEDCONTROL https://forum.virpil.com/index.php?/topic/3903-vledcontrol-for-dcs-control-the-leds-of-your-virpil-devices/ download: https://github.com/Nereid42/VLEDCONTROL/blob/main/Releases/VLEDCONTROL-1.0-1305.zip But don't blame me for the code. It was written in a hurry (just a few days).

And now I'm looking for the lights of the autopilot channels. I found the buttons but not the lights. EDIT: found it: 278, 279 "1st SAS Light Brighness"

Thanks. I will take a look. EDIT: This was indeed very helpful. BTW: Some links in your first comment are broken.

Any idea how to export the landing gear UP/DOWN indicator lights in the pilot seat?

To bad. I noticed this long ago with the Huey and I was hoping it would be fixed. A track with the F/A-18 was OK a few months ago. But maybe I was just lucky.

I have just watched a track of a flight with the Mi-24P and the recording was about 1 nm of the real flight after 10 minutes. Are tracks still completely broken? Or are they just not working in the beta or with the Hind?