Ramsay

It seems to be generic to the NS430 (especially in the PG) and effect all modules to a greater or lesser extent. I always assumed the general 10-15 fps loss I saw on my old system was the "cost" of effectively running 2 modules simultaneously i.e. F5 + NS430 Re: PG Stutters/freezes Upgrading from an i7 860/16GB DDR3/GTX1050Ti/SSD ---> i9 9900K/32GB DDR4/RTX2070/M2 SSD (Persian Gulf map is on 860 EVO) reduced the length of the stutters/screen freezes from 2-4 sec to under 1 sec. but it still stutters. These are from a F-5E SP track with no other units, GFX settings were optimised for 66 fps (ASO=ON, GPU load 97%) as I usually use V-sync (turned off for this test) With the terrain map displayed on the NS430, during flight the screen freezes (less than second with i9 9900K) and the recorded FPS can dip to 8-18 fps (note the drop in GPU load) With Nav page 2 open (no Terrain mapping), fps was a stable with little to no lag spikes except when interacting with NS430 buttons, menu, etc. IIRC the NS430 by it's self "costs" ~5 fps in the F-5E i.e. without the 2D NS430 performance would be ~70 fps. Track replayed in Open Beta 2.7.1.6430 F-5 PG, NS430 Framerate Stutters, 2_5_5_33552.trk

Not in DCS, currently the smaller flares now fitted to the Hornet and Viper are about 70% as effective as the dual cartridge modelled in the A-10C, etc., so you need to use twice the amount of flares for the same effect. https://youtu.be/9O75Sue8n-c?t=121

AFAIK ATC's active runway direction and the ILS used to be coupled i.e. once there was a tailwind of ~6 knots (3 m/s), ATC would change the active runway direction and turn off the ILS for the opposite direction (regardless if it was the only system/direction or not). This was somewhat logical as, Caucasus airports often use common frequencies for both directions with a change in audio ID's to confirm the active ILS/Marker direction (if the opposite direction did not turn off they would interfere with each other). DCS's ATC has never supported flying a localiser "back course", though you could always ignore the AI's instructions if the signal was present. This changed with DCS 2.5.0 and the active runway and ILS logics were separated. Unfortunately the logic for the 2 decisions isn't consistent and DCS's ATC can, and often does, choose (desync) different directions for the active runway and the ILS when there is a moderate headwind 1-6 knots (1-3.5 m/s). This effectively breaks the ATC/ILS combination in any "normal" mission made using realistic METAR data or dynamic weather unless the mission creator/player is extremely lucky. Surprisingly (for a combat flight simulator) fixing this is a low priority for ED and is something we've had to learn to live with (I gave up trying to using real world METAR data 3 years ago).

Still works for me, Cold Start at Batumi, Open Beta 2.7.1.6430 I can't add any more than I've already said here ... Perhaps post a track but if you've already disabled "Easy Coms", I'm not hopeful

Yes, there's lots of free space once you remove the map box This Mi-24 has a Garmin GPS 155XL TSO and Tactical Radio? fitted where the doppler map box once was ... https://youtu.be/2kC3tWzwD_A?t=146 ... not sure who the operator is. I wouldn't mind an older Garmin option like this in the DCS Mi-24 or UH-1 but only if it functioned correctly. The current NS430 is little more than a toy and IMHO would spoil a high fidelity DCS Mi-24 if fitted as standard, so should be left as a 2D popup (unless ED ever bring the NS430 up to standard)

I couldn't find a good description in ED's manual and don't recall if it's covered in one of the included training missions. The paid "Oil Field Campaign" makes extensive use of the Mi-8's doppler system, so mission 1 covers the need to set a magnetic course, rather than the true/F10 map bearing. It's also important to note that DCS's NS430 Module is only superficially like the GNS430 and has many broken/missing features including how it displays Magnetic and True bearings. For example in DCS, Batumi to Tbilisi is at 81°True (75° Magnetic) but the NS430 wrongly displays 81°M (default) 87° (True set on the AUX page) Only a FC3 aircraft would display 81°T as magnetic, so it seems not even the dev's were clear if the NS430 was a full fidelity module or FC3 level. Ground track displays correctly but the map does not. https://forums.eagle.ru/topic/164843-trackdesired-trackbearing-not-working-correctly/?do=findComment&comment=3614705

Nothing I'm aware of that hasn't already been mentioned in the "South Atlantic" forum. This video interview from February has the latest asset list I know of https://youtu.be/oEuG9HjqcxU?t=1331

AFAIK PC don't use Discord to "release" updates, rather it's used to allow subscribers to "informally" discuss the Kiowa, ask questions, etc. The Kiowa twitch stream a couple of months ago was an informal non-scripted event arranged with a streamer to show German viewers the WIP Kiowa, Sven was kind enough to let subscribed discord users know (a couple of hours in advance) that a stream had been scheduled, these WIP streams are temporary and get deleted after a week or so. For those fearing they "missed out", nothing significant was shown/discussed that hadn't already been shown the previous Christmas (in English). If you want "every" titbit of information or speculation, you'll have to follow discord, facebook, etc. and put up with the memes, jokes, trivia and off topic that go with those platforms. OTOH if you only want "official" updates, this is place to come. The only "official" update I'm aware of is that work is ongoing and that PC "hope" to release the DCS Kiowa before the end of the year.

This is a general DCS problem introduced with 2.5.x where ATC's active runway and active ILS desync (at most AB) when there is a moderate headwind (1-6 knots). Here the 8 kts / 55° crosswind gives a RWY 23 headwind of 4.6 kts (8 x cos (55°)), increasing the crosswind to 10 knots fixes the ATC/ILS desync as 10 kts x cos (55°) = 5.7 kts which is enough for Incirlik's ILS to switch to RWY 23. I confirm the missing ILS glide slope signal at Bassel Al-Assad Tested Open Beta 2.7.1.6430

I'm guessing the dev's have taken notice of "the glass half empty" screenshot complaints and have stopped posting anything until it's closer to being finished/passing their Q&A. Likely PC weren't as near to completion as they thought and COVID, DCS, feature creep and life made things even more complicated. Another dev might have given an "Early Access" release but PC always said they want it feature complete with a leading tech FM, verified by SME's who flew the real, so IMHO not odd at all. Everything shown has been WIP, PC is clear they want to avoid an "Early Access" release (if at all possible), if one aspect of the FM needs adjustment - it can easily effect other parts of the FM, it's an iterative process that's "done when it's done" and takes time/SME feedback. It's almost impossible to balance the "show us what you're working on" crowd vs those in the "it looks so complete" crowd - GIB Kiowa NOW requests, hence (I'm guessing) another reason for the current reduction in forum posts/updates.

No notes on the small (~6.5 MB) Steam Open Beta update, AFAIK there was no change in DCS version and the only files updated were • dcs_manifest.bin ... files, the exact number will depend on the number of modules, maps, campaigns, etc. owned i.e. in my case 136 files of varying size from under 1 KB to the largest at ~2.5 MB were updated.

When I tested last year (2020-05-02) vs a single Neutrashimyy missile cruiser, the CM-802AK flew @ 168ft (50m) and ~Mach 1, IIRC approx. 1 in 4 got through it's CIWS, etc. defences when fired en masse. No Harpoons got though in the same test (as they descended from 5,000 ft @ 5 NM / Mach 0.7 and were shot down).

Have you actually tried to use the 430 in any meaningful way ? It's missing so many features - I'm almost tempted to ask ED to remove it from sale if they don't intend to support or fix it.

Yes, if engine power, auto-rotation and flight model bugs were fixed and a AN/APR-39 RWR added. Obviously I'd want lighting and textures to be improved to work with 2.7 as the old textures feel dated and/or have issues i.e. matt vs shiny liveries, etc.

You can install open beta in parallel, if not doing an in place command line "upgrade/branch switch", the open beta installer will try to copy common files form your stable install to save bandwidth, so it's best not to delete your stable files.

No issue here in Open Beta 2.7.0.5118, both the 3D model and 2D pop-up (LShift+LAlt+B) are working in a hot started Mi-8 in Syria. Settings to disable the NS430 are found in • Options>Special>NS430 and in the ME • for each player Mi-8 under it's "•••" properties tab. AFAIK the NS430 is enabled by default but some missions, such as those in the "Oilfield" campaign, disable it to force the use of radio navigation, etc. You could perhaps check the NS430 and Mi-8 model files are present and that "DCS World\Mods\aircraft\NS430\bin\NS430.dll" hasn't been blocked/deleted by an anti-virus or similar. • DCS World\Mods\aircraft\NS430 • DCS World\Mods\aircraft\NS430_Mi-8MT

I had the opportunity to install Syria onto my lower spec install, so for info this is what a single hot start Mi-8 looks like DCS Open Beta 2.7.0.5118 System spec. i7 860, 16GB DDR2, GTX 1050ti (1TB SSD for OS, 2TB HD for programs, data and DCS) Syria's RAM footprint was between 13 and 15.5 GB

Unfortunately it's a default bind, perhaps it's an inconsistent English --> French translation, as the same stick/mouse buttons are used to fire the mini-gun AND canon/rockets. You can test by arming the L's canon • Master Arm ON • Armament Panel ON • RH pylon SELECTED • HUD gun sight DOWN ... and switching to mouse look (LAlt+C), pressing the left mouse button (SOURIS_BTN1) should fire the canon. If it works, the question becomes - does the HOTAS-X column show for the "minigun" and can you bind a button.

The missing key binding seems to be an indeterminant bug that some players see, it's been suggested on discord that unplugging your throttle (assuming it's a separate device) will allow the "Fire Gun or Rockets" binding to reappear.

I'd need to see a track showing the INS issue, otherwise it'd be just wild guesses. The radar standby bug is known, AFAIK the flashing "P" can be ignored and it's safe to switch the radar to silent or emit.

Are you using DOP mode on the ADI to show the needles for lateral and longitudinal drift, they along with the VVI are the key to easily entering auto-hover. • Ground speed lower than 18 km/h • Roll and pitch lower than 30° • Vertical speed lower than +/- 0.6 hm/min The controls display (RCtrl+Enter) is also handy as it gives instant feedback on when Auto-hover engages and what mode it's in i.e. Collective and Slave https://www.youtube.com/watch?v=Ch_ZRXieGKk&t=154s

The module is WIP and ED have changed how strong the dust cloud appears. This is from a 2.5.6 stream last year. https://www.youtube.com/watch?v=D4RJMfZ0o34&t=2120s

Combined Arms has never been "good" at the best of times, unfortunately AI path finding pretty much broke in 2.5.6.x, with units getting stuck or "lost". AFAIK there's not much campaign makers can do to fix their missions until ED fix the core AI / maps.

Yes, the 10's selector goes up to 12, so you can dial to channel 129

It's a MagVar bug when the EHSD is in magnetic heading mode, UFC data entry is still using true, switching the EHSD mode to TRUE is a work-around until the bug is fixed (or entering the true heading in the UFC).