Ramsay

Not that I'm aware of, the NS430 2D popup works as expected in full fidelity modules, and AFAIK in FC3 aircraft once the mouse mode is switched from "look" to "Clickable mouse cockpit mode" - (LAlt + C) Tested in Su-25T, Caucasus, Open Beta 2.7.1.6709

No, the 2D NS430 popup is disabled for the Hornet (entry.lua contains ["FA-18C_hornet"] = disabled,) Testing in Open Beta 2.7.1.6709, I was unable to call up the the 2D popup in the F/A-18 cockpit, which is as intended.

Not that I'm aware of, I haven't tested every module but M-8, UH-1H, F-5E, F-14B, Mig-21 and F-16C (by editing entry.lua) have all worked with the 2D NS430 (last six months or so). Would need to see the OP's track to be more specific.

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

Assuming the ILS is transmitting. If the landing waypoint was setup in the ME Select the landing waypoint (CP/PD will already have the Runway Heading and Glide Slope filled in) Contact ATC or check the mission briefing for the QFE and set the altimeter accordingly Set the ILS frequency (adjust ILS volume / check audio ID / HSI flags)* Set APP mode on the PCA Land using ILS and the HUD as you would in 2.5.6 HUD localiser guidance will appear with localiser signal and aircraft heading is +/- 6° of Runway Heading HUD Synthetic Runway will appear when BOTH localiser and glide slope signals are being received. * if ILS is not working you will not have the HUD localiser/synthetic runway symbology If the landing airport has not been set up in the ME Contact ATC and check which runway is active and it's QFE Set the ILS frequency (adjust ILS volume / check audio ID / HSI flags)* set the altimeter to QFE (ATC usually gives it in inHg, so you'll need a table to convert to mbar/hPa) Select the active waypoint you are going to use to land (1-20), it's co-ordinates are unimportant (say waypoint 19). PREP the waypoint runway info on the PCN (PREP 19 INS) turn the PCN selector to CP/PD (RH/DS in the english cockpit) enter the runway's true heading in the left field i.e. 135.0° enter the desired glide slope in the right field i.e. 3.0° Set APP mode on the PCA Land using ILS and the HUD as you would in 2.5.6 This is also covered in Chuck's latest M-2000C Guide (page 248) https://drive.google.com/file/d/1jmp9ueZo9xOPyGzo3YO0AnFYEH-5Iotr/view

You didn't set your barometer to QFE i.e. your altimeter reads 1770 ft, while the Radar Alt reads 220 ft., therefore the system draws the runway as if it is further away i.e. 1770ft/6NM along the glide slope. When set to QFE, barometer and radar altitude will be approximately the same near the runway threshold and the synthetic runway scaled appropriately. In your picture, Vaziani RWY 13, elevation 1526 ft MSL, the barometer is still set to QNH A similar picture approaching Vaziani RWY 13, with the barometer set to QFE (field elevation). Setting QFE is less important where the runway elevation is already close to sea level i.e. QFE and QNH are approximately the same.

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.

Are you sure ILS is active for that runway (the active runway and ILS is affected by wind direction and strength) I've had no issues in Open Beta 2.7.1.6430, check : ILS is tuned correctly ILS is transmitting (adjust ILS volume / check audio ID / check HSI flags) Altimeter is set to the correct QFE the currently selected waypoint has the correct CP/PD (Runway (True) Heading/Desired (Glide) Slope) APP is selected on the PCA and you're in NAV mode Note: the HUD synthetic runway will only display while the localiser and glide slope signals are being received. Please post a short track if you continue to have issues with the ILS.

The Mirage 2000C's A2A Radar is due to be updated (rebuilt from scratch) to be more realistic. AFAIK the current plan is to enable the missing AG radar modes DEC/VISU in the next few weeks and then rework A2A. WIP AG DEC mode

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.

No, this change will be permanent. waypoint 00 is the INS's "present position" and isn't editable in the real, rather it is "updated" using the co-ordinates from a stored WP (01-20) i.e. during the initial alignment or while in flight i.e. INS overfly updates or offset updates to correct gyro drift. AFAIK mission waypoints 01 - xx are loaded from a data cartridge and the real SOP's use waypoint 20 (last editable WP ?) to avoid overwriting a mission WP but there is nothing stopping one of the other WP's (01-20) being used. While the changes may seem "haphazard", a detailed functioning INS is likely important to the AdA (also using the DCS Mirage) to avoid negative training. It's also possible Razbam simply have more information/permissions now they are working with the AdA.

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.

AFAIK engine thrust has been reduced in the latest Open Beta patch DCS AV-8B N/A by RAZBAM Simulations Improvement: Various FM performance adjustments https://forums.eagle.ru/topic/170893-dcs-world-25-changelog-and-updates-of-open-beta/?do=findComment&comment=4652887

Thanks, I suspect the GTX 1050's 2GB of memory might be an issue, perhaps you can check VRAM use using task manager and adjust your DCS settings to compensate or try a different driver ? Hopefully someone more knowledgeable will be able to help. Example 3.6GB VRAM use (low spec system with GTX-1050TI 4GB, Syria map), YMMV.