gospadin

Okay, reported the procedure bug specifically. It seems to affect any procedures with disjointed flight segments connected by standard rate turns.

I reported the DTK/DIS errors with flight plans, since DTK should always represent the waypoint-to-waypoint track and DIS should represent leg distance (with the exception of the currently active leg destination) Regarding the procedures itself, it seems that the RWY22 TUNOT3 departure indicates a standard rate turn at 10 DME from the end of the runway, followed by a flight track of 121 for 15nm. With the garmin sim, you can see these two segments are disconnected. In game, I am getting 132 for 17nm. This would appear to be the direct track assuming no implied position change in the turn. I don't know if they plan to implement that in their embedded procedures, but I'll report that too.

it works in win10 too

For now, you must create flight plans each time you spawn. --gos

I believe the beta test is for the Mi-8-specific NS430, presumably to focus testing on a single platform. I don't know about future L-39 enabling plans or timeline, sorry.

I'm not sure of the source, but it has data for airports, navigation beacons and IFR waypoints. I don't know how they found or filtered their data choices, but if you can't find a waypoint you're expecting, please speak up. As to data sources for Normandy or Caucasus, I don't know what the data source would be. FAA data is freely available covering the US. You cannot slave the Mi-8 autopilot to the GPS that I know of. You'll need to hand-fly your approaches using the NS430's CDI and stepdown altitudes based on GPS reported DME. There's a doc folder that comes with the module that has a manual. As far as tutorials, you should be able to use any GNS430 tutorial from youtube. I'm sure the community will create DCS-focused tutorials in the future too. (And of course, please report bugs in the bug forum if you find issues, thanks!) --gos

Note that if you force download on the stable branch, you'll be getting an older version of the NS430 than the one currently published as part of the beta. Just be aware of that if you're reporting a bug.

Mi-8 doesn't have an HSI in the normal sense. It really just has an ADF indicator. I have no idea if BST plans to model one, though the request is probably worth a separate thread. --gos

Need to wait roughly a week until the changes from the beta branch make it to stable.

ok reported, thank you

Can you be more specific? I can't reproduce this so far.

I reported this one tonight, along with a video from a real GNS430W showing the behavior you mention and how it's supposed to work. Thx! --gos

Reported, thanks.

Will reproduce and file tonight. Thanks

Can you be more specific, with a screenshot or two? I believe this is a known issue, if not i'll make sure it gets filed. Mi-8 doesn't have an actual HSI or CDI, so not sure it's possible. I did read on the Russian forums (via google translate) from someone (can't remember who) that the ability to have mission editor waypoints automatically loaded as a flight plan was in the works, but I haven't heard it officially. --gos

Click on the small right knob. Scroll to a point on the map. Direct - Enter - Enter. Follow the cult of the magenta line! --gos

GPS is simply a data source used to help keep an inertial navigation system aligned. Needed? Who knows, but should increase accuracy. Would also allow you to perform in-flight alignment like on the A-10C.

Since $15 is not a sale price, you can use bonus bucks on it. I think I paid $11. Doesn't actually "solve" the issue, but does make it a bit cheaper for people with bonus bucks lying around. --gos

True, though many of the Normandy airports were already memories before GPS was invented.

I agree that it would be nice if ED would publish their general intent with this add-on, hopefully in the Friday newsletter. --gos

The 6-o'clock position on the VVI is 5 m/s, as I can see he doesn't exceed 3m/s except for a quick burst while still moving forward.

Version 0.93 posted, re-syncs with RAZBAM's latest material names. This fixes all warning lamps and indicators, as well as adding an alpha channel to the countermeasure panel so you can see it at night. Follow my sig below for the link to the main thread in the livery forum. --gos

Version 0.93 posted, main download link in the first post has been updated. Fixes all the lamps which were broken due to the change in material names. Fixing that also added a new alpha layer for the countermeasure panel so you should be able to see it at night now. --gos PS: I tried to get the cockpit working in the Saved Games folder, but was unable to do so. Doesn't seem like RAZBAM has added the proper lua code yet. On the bright side, my modification still passes the integrity check, so there should be no issues using it on IC-enabled servers.

The "CoreMods" folder, which is part of your main DCS installation, contains all of the airplane external elements... model, textures, simple flight model, etc.. everything needed to instantiate it as an AI. Everyone in DCS gets CoreMods for all aircraft, even ones they don't own. If you own the module, then you'll also get data for the airplane in your "Mods" folder, again, in the main DCS installation, which contains all the internal elements... cockpit, scripts, and usually the EFM and ASM binaries, used when you're flying it as a player. Within the Saved Games folder, think of that Mods directory as an overlay for locally-installed content like skins/liveries. It needs to take on the same structure, and it's parsed at startup, but it doesn't actually modify your original installation locations. I wouldn't expect anyone to have a CoreMods folder within Saved Games. If they do, something is probably wrong. --gos

The base avionics package for early A-4Es didn't have any RWR. AN/APR-25 was an option with the proper AFC, which also required the avionics hump. A-4F models which were retrofitted with the fin tip pod at the top of the tail got an even newer RWR system. --gos