drPhibes

https://forums.eagle.ru/showpost.php?p=3408896&postcount=12

Try reducing the Y-axis saturation for the slew axis. And you could try adding a slight deadzone.

It doesn't. As long as you don't have the flashing 1111s , you can use other codes. I don't know which code range they have simulated in the av8, but I have tested 1111, 1234 and 1688, and they all work fine.

No. Source: https://forums.eagle.ru/showpost.php?p=2869238&postcount=28

Make sure that you are in TGP mode, and not HTS (enabled/disable by double clicking sensor select down). Then click the NWS/undesignate button.

It works with the TPOD, but not with the DMT (yet). Version 2.5.0.14304.321

The seeker points at the correct area, but the HUD indication is incorrect at the moment.

Avionics hardware is usually quite primitive, with limited memory and processing power, which some times has impractical consequences like this.

http://www.boeing.com/defense/support/qf-16/index.page 1. Multi million dollar jet 2. Piloted by a human being (remotely)

He hasn't deleted it from all threads yet: Perhaps this is like on the gun forums, where 90% of the members claim to be ex-navy seals...

There are several snow camo skins in the user files.

Just define the pattern manually using waypoints.

No. The upcoming module has a new 3d model, so the old template is incompatible with the new one.

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.