Jump to content

Incorrect ground speed being shown by NS430


jonsky7

Recommended Posts

6 hours ago, MiG21bisFishbedL said:

What kind of meteorological conditions, namely wind? IAS is indicated airspeed while the 430 would be giving you ground speed.

I think the F10 map shows actual ground speed, so wind is already accounted for in that speed. But in this case this was a very quickly put together mission with just the single helo for making a short track, no wind.

Not just the Mi-24P it seems, Mi-8 also reporting wrong speed

Screen_230103_002117.jpg

Screen_230103_002121.jpg


Edited by jonsky7
Link to comment
Share on other sites

  • jonsky7 changed the title to Incorrect ground speed being shown by NS430
7 hours ago, MiG21bisFishbedL said:

What kind of meteorological conditions, namely wind? IAS is indicated airspeed while the 430 would be giving you ground speed.

TL;DR:

This bug seems to effect all modules tested (Hind, Gazelle and F-5E) - there is zero wind in the supplied track.

• It seems the NS430 is doing a double km/h --> knots conversion.

Detail:

Setting the NS430 to display km/h, and flying at 120 km/h in the Gazelle

• it displays 65 km/h i.e. 65 would be correct if it was displaying knots, as 120km / 1.852 km/nm = 64.8nm = ~65

Screen_230103_002051.jpg

Setting the NS430 to display knots, and flying at a Ground Speed of 135 km/h

• it displays 39 knots/h because
135 / 1.852 = 72.894 (correct answer in knots)
but divides it again
72.894 / 1.852 = 39.360 = ~39

Screen_230103_004041.jpg

Tested in DCS Open Beta 2.8.1.34667


Edited by Ramsay
  • Thanks 1

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

9 hours ago, Ramsay said:

TL;DR:

This bug seems to effect all modules tested (Hind, Gazelle and F-5E) - there is zero wind in the supplied track.

• It seems the NS430 is doing a double km/h --> knots conversion.

Detail:

Setting the NS430 to display km/h, and flying at 120 km/h in the Gazelle

• it displays 65 km/h i.e. 65 would be correct if it was displaying knots, as 120km / 1.852 km/nm = 64.8nm = ~65

Screen_230103_002051.jpg

Setting the NS430 to display knots, and flying at a Ground Speed of 135 km/h

• it displays 39 knots/h because
135 / 1.852 = 72.894 (correct answer in knots)
but divides it again
72.894 / 1.852 = 39.360 = ~39

Screen_230103_004041.jpg

Tested in DCS Open Beta 2.8.1.34667

 

Thank you for confirming my suspicions and doing some fault finding, nice work.

Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...
  • 4 months later...
On 2/13/2023 at 5:56 PM, Flappie said:

The problem has been acknowledged. Now we must wait.

Is there any update on this, currently distance is the only value being displayed correctly when flying on the Caucasus map ?

✔️ Distance 15.2 NM
❌ Ground Speed 64 KTS (correct value ~115 KTS)
❌ Ground Track 185°M (correct value 179°M, what is displayed is the TRUE)
❌ ETE 14:13 (incorrect due to wrong ground speed, should be approx. 7:56)
❌ Desired Track 195°M (correct value 189°M, what is displayed is the TRUE)
❌ Bearing to waypoint 194°M (correct value 188°M, what is displayed is the TRUE)

Screen_230617_221751.jpg

DCS Open Beta Multi-thread 2.8.6.41066

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

  • 6 months later...
On 2/13/2023 at 5:56 PM, Flappie said:

The problem has been acknowledged. Now we must wait.

Open Beta looks excellent with most (if not all) of the NS430 Magnetic and True bearings reading correctly.

I'm not sure about the Ground Speed (perhaps still WIP) as it seems to report a speed higher than IAS but ~5-10% less than the GS reported by other methods i.e. F10 map, INS, etc. this seems confirmed by ETE overestimating the time taken to fly a route leg.

Either way, GS is much better than it was, please pass on my thanks to which ever team is responsible.

Detail:

 ✔ Distance 31.6 NM
? Ground Speed 383 KTS (correct value ~424 KTS)
✔ Ground Track 128°M (IMHO within limits)
 ❌ ETE 8:14 (incorrect should be approx. 4:28)
 ✔ Desired Track 128°M
✔ Bearing to waypoint 128°M (IMHO within limits)

nullimage.jpeg

Tested in DCS Open Beta Multi-thread 2.9.2.49629 using F-5E, F-14B, SA-342L and MB-339A, Caucasus Map

  • Like 1

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

Yes, devs are still working on it. The last time I checked, the "GS" was actually the IAS, but it was in ED internal build. Can you confirm you get the IAS too?

I'll say thanks on your behalf. 👍


Edited by Flappie
  • Like 1

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

5 hours ago, Flappie said:

Can you confirm you get the IAS too?

No, the NS430 GS value can be close to IAS when low/slow, but high and fast it follows the higher GS, under reporting by ~10%

For a F-14B at 0.8 IMN @ 30,000 ft,

• NS430 gave GS = 432 Kt
• Cockpit IAS = ~310 KIAS
• Cockpit Info Bar (LCtrl+Y) IAS = 293 KIAS
• F10 Map GS = 479

NS430 F-14B Ground Speed and Bearing Test, 2_9_2_49629.jpg

For info. 0.8 IMN Airspeed converter

0_8IMN_at_30kft_+20C_at_Sealevel.JPG

https://aerotoolbox.com/airspeed-conversions/


Edited by Ramsay
Add info for 0.8 IMN at 30 kft conversions
  • Thanks 1

i9 9900K @4.7GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

game from yesterday, MT, multi, 109kn on NS430 and 120 knot on the tab, and 250 km/h for the air speed (134kn indicated with face wind).

ETA is really wrong too, even with the speed error. with this screenshot, i supposed to be more like 15min than 24. in real i need 12 min to be on my waypoint.

20231219231758_1.jpg


Edited by Mavkruger
Link to comment
Share on other sites

  • 3 months later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...