gospadin

You should be able to install 1.5 from the stable installer, then update it to 2.5 "open beta".

Sorry, "this morning" came and went, and I didn't get to this yesterday as planned, was working on other stuff. Will see what I can do "soon"-ish. --gos

If you're asking about the NS430, yes you can fly real IFR procedures (departures/arrivals/approaches) but only in the Mi-8. Support for other aircraft has been hinted at, but is not confirmed at this time. BST has not published any approach charts with their module, but you can still get free charts from either the Russian IAP (Caucasus map) or the FAA (for NTTR). They will match in most cases, though magnetic declination may be slightly off due to the declination of the current maps being older. Note that LPV isn't presently supported in the Mi-8 because there's no slaved CDI. You only have the CDI page on the NS430 itself, which has no vertical guidance, limiting you to LP / LNAV or VOR/NDB overlay-style approaches. Many other aircraft (A-10C, most FC3, M-2000C, L-39, MiG-21 etc.) support ILS or RSBN or INS-derived instrument approaches of one sort or another. Modern approach plates will work just fine for these, since all you need to do is get yourself within the ILS or RSBN signal cone to pick it up. For older craft without VHF (VOR/TACAN) receivers (non-NS430 Mi-8, L-39/MiG-21 to airports without RSBN, etc.) you can fly NDB approaches just fine. --gos

Are you sure you're not using version 8 of my mod? Version 8 had name. Version 9 used display_name properly, aligned with the changed format. Update: Okay just realized what was happening. I never updated the main download link to v9 (it only ever existed attached to a post mid-thread), so the top post still had v8 beacon data in it with the old format. This is now fixed for NTTR. I also don't have updated data for Normandy yet, will generate that this morning. --gos

Per ED's NS430 product page, it is not yet available on Steam, sorry. https://www.digitalcombatsimulator.com/en/shop/modules/ns430/ --gos

Are you running the most recent version? the display_name stuff changed a long time ago. positions (2nd parameter) is the elevation, which in a few cases has changed by a few centimeters. (positions are in meters) sceneObjects parameter changes with each release, I try not to chase that too much. --gos

Can you be more specific? I don't see the difference you're talking about. The mod should still work properly. --gos

Would need to measure the distance at which a sidewinder missile changes tone from a wide range of aspects. Conceptually easy, just time consuming.

Okay so to clarify, you're seeing 60fps when the NS430 popout window is closed. (But the NS430 in the dash is still active, and you can see it in the navigator panel, correct?) When you enable the popout window, your FPS drops from 60 to ~49? If that is what happens to you, I can confirm there's presently a frame rate penalty for enabling the pop-out window. Some graphics settings seem to modulate the magnitude of the impact, I'll check mine tonight. Either way, though, I agree 15% is a pretty heavy framerate hit, so I'll file it and maybe a dev can look into some optimization. --gos

Can you be more specific? Were you using the popout window or not? What are your frame rates both with and without the NS430? What are your graphics settings?

Agreed. There's a lot of aircraft that might find it useful. Even Su-25s in Syria were shown with Garmin handhelds mounted on their glareshield. If we get CDI and radio integration, that'll be even better.

Flight plans made in the mission editor will automatically become the default NS430 flight plan once in-game. I think you're limited to 31 waypoints in a single flight plan. You can enter new user waypoints via latitude/longitude coordinates, or radial/distance from a waypoint, or the intersection of two radials. A number of bugs have been fixed recently in this area, but I think one still remains that is being worked on. User waypoints can be edited. I don't believe mission-editor waypoints can be edited in-flight, but I haven't tried to be honest. User waypoints are not currently stored permanently. Yes, the NS430 will not act as a TACAN/VOR receiver per-say, because the Mi-8 has no CDI on which to slave the radio receiver information. It does have all navaids in its waypoint database, so the on-screen CDI will provide course information. Without a CDI, there's no physical knob for adjusting the radial of a course leg via OBS mode, but the OBS mode on-screen should work correctly with leg course adjusted through the menus. If not, please report and I'll reproduce and file a bug in the tracker. Thanks! --gos

There are apps built on the google translate platform and others that'll do translation, but I don't have much experience with them. In general, they get the job of translation done, but don't create anything that is written like a native-speaking author would write. You're welcome, appreciate the positive feedback. --gos

We have not released anything yet, and when we do it'll be free. As to testing, we have enough folks on the team finding issues that at this time we don't need any more help. Thank you for your interest though! --gos

Me too, I think. Hopefully they come up with a good way to expand their mesh boundaries without losing too much detail. Would be nice if we had options to setup longer-ranged missions.

There's always a deeper level you can go in simulation. Imitation vs simulation A vs simulation B is never going to have discrete boundaries. That's one of the challenges with DCS modules in general. If a module behaves properly in all test vectors, the internals of how they got there are black magic and really don't matter. It could be newtonian equations, fluid dynamics, or a giant lookup table.

I believe ED stated that upgrades to ATC were planned for after the merge, not as part of it.

Heh, yea, NTTR at least has been on some variation of the real-life frequencies for a while, since the major update to the map last year. Hopefully with new ATC they are able to add even more capabilities.

I believe a lot of that is caused by the 2.x/1.x split. Once 2.5 brings us to a single engine, there will likely be a lot more servers with NTTR in the map rotation.

I would expect leg altitudes (if that's what they are) from a briefing to be MSL not AGL. That way the pilot is assured of terrain clearance with a single glance at their altimeter. They do look more like minutes to me though.

You're correct that it doesn't currently connect to other instruments in the Mi-8. My assumption (no inside info) is that they're developing the base technology 430 that other aircraft may be able to hook up additional input/output signals. In this sense, doing a 430(W) makes more sense than a simple 400 in the event they ever implement NAV integration. --gos

Completely agree. So fat and ugly the first time, but those nose-on views showing the humps in the "shoulders" are amazing. --gos

The PL-12 Airtruk would like a word with you.

No ILS receiver, but as others said, you can approximate a GPS overlay by programming waypoints into the NADIR. This will allow you to essentially fly any NDB, VOR, VOR+DME, or LNAV approach correctly, even if the data source is a bit wonky.

If you're looking to use pre-defined iCommand behaviors, I think that only works for SFM aircraft. For EFM (using ed_fm_set_command) I believe the command numbers are just integers, the names are arbitrary for what you're trying to do. The key is to send the same integer that you're listening for.