drPhibes

The method described by soundwave197 works for me. Make sure you have the latest update installed, and if that doesn't thelp, try running a repair (repair dcs world on the start menu) and/or reinstall the Av-8B module.

Here's a step by step guide that works: 1. Go to Options -> Gameplay and activate Easy Communication 2. Mission editor: add a Harrier. As an example, I have set takeoff from ramp, with no other settings changed. 3. Add a KC-130. I changed the altitude and speed, but no other changes were made (the TACAN setup in the advanced waypoint options is added automatically when adding the KC-130 in the ME). 4. After starting the engine, turn the COMMs volume knobs clockwise 5. Take off, open your communications menu, and press F6 [Tanker Texaco etc...] 6. Press F1 [intent to refuel] -> "Request rejoin" 7. The tanker replies with "proceed to pre-contact" 8. Get close to the tanker and press F1 [Ready to pre-contact]. If you are close enough, the tanker replies with "cleared contact", and reels out the hose. 9. Get your probe out and refuel!

Same here (if my screens should meet Razbam's selection criteria).

Excellent work (as always)! Thanks a lot!

The whole "open beta vs. release" issue doesn't really matter unless you need to use both versions (e.g. if you fly MP on servers that stick to one or the other type of release). When a release version goes live, the open beta receives the same updates as the release, and they are at that point identical and 100% compatible MP-wise. And you can switch between openbeta and release at any time using the dcs_updater utility if you should wish to do so. Or TL;DR: delete 1.5.

Just one question: why? The mav seeker is automatically slewed to the target you have marked with the TPOD when uncaging. Going via DMT/LST is completely pointless. If you have a TPOD, use it. If you don't have one, use the DMT.

Perhaps they're actually working on the module instead of hanging around on forums all day? Some patience is required when byuing early access modules.

If you have saparate install directories for 1.5 and 2.5, then yes, you can delete 1.5.

Turn up the volume for comm1 & 2 (knobs left and right of the UFC keypad), and use easy comms for communicating with the tanker.

The KC-130 has TACAN now. It was added a few patches ago. The settings are located in the advanced waypoint section:

Previously, when the release branch has been updated, the open beta and release branches have been synchronized (i.e. both updated to the same version), so there's no difference between them at that point. The open beta gets updates faster than the release, but these updated may prevent you from connecting to MP servers using the release version, and they may also introduce new bugs. If you don't care about that, and you are willing to risk potential bugs introduced in the beta updates, go for the beta. If not, you can switch your current install between the open beta and release branches using the dcs_updater utility (guide: https://forums.eagle.ru/showthread.php?t=114030). (Edit: when the release version goes live, of course.)

That's not a texture issue. For some reason the cockpit .edm (3d model) isn't showing up. Try repairing DCS.

That list is over 5 years old. This is the most up to date info from Razbam: https://forums.eagle.ru/showpost.php?p=3060848&postcount=1

Here's a temporary fix (if you play SP or MP on servers without IC enabled): https://forums.eagle.ru/showthread.php?t=201353

Nice video! Did anyone else notice that the wheel gauge of the trains and the track gauge doesn't match? Perhaps the track texture is based on standard gauge (1435mm/4ft 8.5"), while the VL-10 and ChME3 locomotives are russian gauge (1520mm)? I guess I'll have to set the year in the mission editor to 1945 and check if the DRG class 86 matches the rail gauge (setting the year to some time in the "steam era" actually replaces the modern(-ish) comblock rolling stock with steam locomotives, if you have the WW2 asset pack).

The flashing stops after changing the code (when airborne). The fault does not reappear after subsequent rearm and refuel cycles; it only happens the first time the TPOD is added.

Have you tried googling "qfe to qnh conversion"? The first hit (stackexchange) explains it pretty well. As long as you are able to find the airfield elevation and have a calculator (for dividing by 30 or 900), the conversion is pretty straight forward.

Not a good idea unless you check with ED and get permission. Asking for donations for DCS-related work is a violation of the EULA, and it could get you kicked off the forums if you're unlucky. Nobody wants that to happen.

You can toggle between the wide and narrow field of view using sensor select left in HTS mode (double click sensor select down to switch from TPD to HTS). Unfortunately, the regular zoom is not controllable from the HOTAS unless you map the relevant MPCD buttons to buttons on your stick (and this will ofcourse mean that these butons have a different function in other MPCD modes)

If you start a mission with the pod and GBUs loaded you can use the pre-set 1111 code, but if you add the pod and bombs through the rearm&refuel dialog, you need to change the code to something (otherwise 1111 will just keep flashing, like when you are on the ground).

I have had some trouble with the auto hover lately (it was impossible to engage it with the assigned keyboard and joystick inputs, even though the ground speed was close to zero, and the vertical velocity and bank angle was within spec), but re-doing all my SA342 control assignments fixed it.

Same here. I Spent most of the day yesterday lasing and dropping GBU-12s, so it definitely works. Try running a repair using the dcs_updater application.

Not all of them. The ЧМЭ3s are diesel powered.

I never really considered buying CA, but this video (and general fooling around at treetop level in 2.5) convinced me. And I finally got to spend some of my bonus points, so it cost me just 6$ :)

Green is a color. Joking aside, the displays are capable of displaying other colors, but green is used in the AV-8 for NVG compatibility.