lmp

I'm not sure this is how it's supposed to work or not, but if you have a flight plan, using direct-to doesn't create a leg from your current position to the direct-to destination, but rather from your originating waypoint to the destination.

After a few attempts in the Su-33 (with similar results to OPs) I'm not that worried about doing it in the Hornet. I've done a lot of landings in DCS, the runway being smaller and moving doesn't make it that much harder. What I'm struggling with a lot more is aerial refuelling. Haven't done a lot of those. So far I'm finding the Su-33 with its special autopilot mode pretty forgiving, compared to the Mirage... I wonder how terrible I'll be doing in the Hornet.

You use the Dogfight/Resume Search switch, which is located on the stick under the thumb. The control action is called Dogfight/Resume Search Switch - CENTER-PRESS (RESUME SEARCH) and the default key bound to it is "R".

The pilot's sight on the P (and the V) is the ASP-17V, similar to the ASP-17 of the vanilla Su-25. There is no laser rangefinder though, so AFAIK slant ranges will be triangulated from altitude and dive angle - good enough over flat terrain, useless in the mountains - or inputed manually.

Hopefully it also extends far enough south ;).

You are right, but that doesn't change the fact that the modelled plane didn't have an ILS in real life and so it doesn't have it in the game.

Would be nice to have not only the flight plan, but also bullseye automatically copied into the user waypoints database.

I'm attaching my .miz file. NS430.miz

Yes, and that seems to work every time (at least for me). However, AFAIK you should be able to exit FPL mode (when the cursor is not active at least) with a short press of the CLR or FPL buttons as well. I'll try to recreate the problem I had once I'm home.

There was, but the GPS is not showing heading - it's showing track. It has in fact no way to get any heading information. It can only determine where the helicopter is going, not where it's pointing - the opposite of what a compass can do. EDIT: However, if the GPS was erroneously showing heading instead of track, that might be the source of the problem. I'll look into it at home.

Also, I tried to create a waypoint from the WPT user page by inputing a radial and distance from a FARP as a reference point and it placed the waypoint somewhere beyond Caucasus.

Normally I can by clicking the FPL or CLR button but on one occasion it got "stuck" and I had to hold the CLR button until it reverted to NAV 1 page.

I was flying to a waypoint with a desired track of 288. I drifted slightly off course - the virtual CDI "needle" went left and the bearing changed to 287. So far so good. I turned to track 286 (according to the GPS display) to get back on DT. At this point I was expecting the bearing to come up to 288 but it continued to drop to 286. I turned to track 284, the bearing to waypoint continued going down. I had to make a much coarser correction to get back on DT. Once I managed that, I carefully turned back to track 288 and quickly started to go off course according to the GPS. In the map view, it looked like I had to be tracking several degrees to the left of the flight plan leg in order to stay on DT. The entire time I was using only the GPS track/bearing/DT indications, ignoring the gyrocompass.

Since update 3 waypoints are now copied from the ME into the device. Unfortunately there are some problems. 1. Waypoints can't be looked up in the database. They're not treated as user waypoints or anything else - so they have no WPT page, no NRST page etc. 2. Sometimes the flight plan isn't copied correctly. I've noticed this so far when starting on a FARP, starting on an airfield seems to be more reliable. One time the flight plan was empty, another time it didn't have the FARP in it, yet another time there was just the digit "2" where the FARP should be.

The axis you're looking for is "corrector".

There are declutter options in the set already to disable such things, if they bother the pilot.

�Uhuh, I have seen that video. I own the campaign and I'm half way through. Who knows, maybe there's a twist somewhere in there and a big NATO force appears and starts a war with Russia. If that's the case, then I was wrong. But so far - no war. I have finished the Spring Tensions campaign and there's no war in it. An insurgency starts a few missions into the campaign but at no time the restrictions on crossing into Georgia are lifted. Nobody ever declares a war. And while I don't own the Oilfield campaign the description strongly suggest that it's a civilian campaign altogether: So what is it that you want me to take away from that video? This may surprise you, but military aircraft fly according to civilian laws a lot. Particularly transport aircraft. The Mi-8 fits civilian or military in times of peace missions very well. When under fire - probably not. OTOH when training over NTTR or "serving the interests of the oil industry" - I would.

Did it help to recreate the problem? Let me know if you need anything more.

As far as I'm aware, none of the official Mi-8 campaigns involve a war (even if there are some limited hostilities taking place). Certainly the default one doesn't. It does however explicitly prohibit entering Georgia proper - you'll get shot at if you do. Good enough reason to have that airspace marked for me...

Sure. I created a FARP on the hill above Java, where the default Mi-8 campaign starts. Here's the default map view: https://imgur.com/Iru8MWI I zoomed out to show that sea/land is displayed correctly when the map scale is small: https://imgur.com/VaAsy0I I zoomed in and up to this point it looks good: https://imgur.com/mlDCzQQ Then I zoom in once more and get this: https://imgur.com/gBd6BaB - this is the screen showing what I believe to be a bug Coordinates page to help you recreate the problem: https://imgur.com/HlN0888

In at least some regions of the map - yesterday I experienced it when flying from Java to Tskhinvali - if you zoom in close, the display will show you're over water.

In the Open Beta you can now land on moving ships at least :). I just landed my Hip first on the Kuznetsov and then on an OHP Frigate, both moving at 20km/h. No more sliding off the deck.

Landing on moving objects is not working correctly in DCS. Maybe the release of PFM for the Su-33 will change that - since the problem is most evident when you try to land a PFM aircraft on a moving carrier - but that's just speculation on my part, nobody promised anything AFAIK.

Looking great guys, keep up the good work! :)

A-10C, F-15C and maybe Su-33 a little bit once it gets the new PFM. If you're good with the A-10C, you're comfortable with the level of avionics complexity that the F/A-18C will have and you're a competent ground pounder. The F-15C will let you practice your air to air skills, from BFM to BVR engagements. The Su-33 is, like the Hornet, a carrier aircraft and also refuels with the help of a probe-and-drogue system. It also offers a glimpse into the capabilities of the most advanced redfor aircraft currently in DCS (The MiG-29, Su-27 and Su-33 have similar capabilities and limitations). I mostly fly older aircraft and when I tried for the umpteen time to learn the A-10C I noticed I have developed some annoying habits because of it. Like looking at the instruments for information I have on the HUD. OTOH a lot of the skills I picked up in the Albatros or F-5E, like manual bombing, aren't terribly useful in a modern jet.