NS-430 issues so far

[gospadin]

All the same in 1.5.7.10175. Can anyone confirm it?

 

FYI, I confirmed XTX is broken in 1.5.7.11476.394 (stable) but working properly in the nightly build. The fix(es) related to XTK should make it into publicly-available builds soon .

 

--gos

[gospadin]

Might not be a realistic implementation (don't know the actual real-world device) but the ADF/ARK needle can't be coupled to the direct track of the GPS? To have the actual line/track you would indeed need an HSI to see your drift; but if flying straight to the waypoint you only need a single needle like with ADF / ARK.

 

I thought about this a bit more, and in the real GNS430 you should be able to define an arbitrary track to your waypoint either when setting up a direct-to, when adding a Flight Plan waypoint, or by using the OBS button. This would allow you to fly a route relative to any radio beacon using only the GNS430. The NAVdefault CDI will show you displacement from the "ideal" track, as will the XTK field.

 

In this way, if you wanted to setup an approach course for a non-published approach in zero visibility (using your radar altimeter for terrain clearance), you could still overlay that track on the map and fly it as a final approach course to said runway.

 

--gos

[Rex854Warrior]

it seems that in the latest 1.5 update i cannot create waypoints anymore. I cannot edit the coordonates in the last WPT page and i cannot create one when moving the cursor on the map.

 

EDIT : Also the Direct to page has changed alot, don't know if it's normal.

Edited November 11, 2017 by Rex854Warrior

[ody81]

it seems that in the latest 1.5 update i cannot create waypoints anymore. I cannot edit the coordonates in the last WPT page and i cannot create one when moving the cursor on the map.

 

EDIT : Also the Direct to page has changed alot, don't know if it's normal.

 

This sounds like an issue I reported. If you can give a little more detail I can be sure.

 

Cheers.

[Rex854Warrior]

This sounds like an issue I reported. If you can give a little more detail I can be sure.

 

Cheers.

 

For the Direct-to page i'll make some more testing, as for the waypoint creation :

 

When using the cursor on the map to create a waypoint this happens,

 

 

Then when i press enter as i used to do in order to create a waypoint on the cursors position (the coordinates for it are displayed in the top right corner) it sends me to the waypoint creation page as it used to but,

 

 

There is nothing in the ref wpt, rad and dis slots, they cannot be edited and the waypoint coordinates don't match with the ones that i had where the cursor was, they cannot be edited aswell. Rendering waypoint creation impossible (question is, am i doing something wrong ?).

 

EDIT : It does the same thing when going directly to the waypoint creation page.

Edited November 12, 2017 by Rex854Warrior

[ody81]

For the Direct-to page i'll make some more testing, as for the waypoint creation :

 

When using the cursor on the map to create a waypoint this happens,

 

 

Then when i press enter as i used to do in order to create a waypoint on the cursors position (the coordinates for it are displayed in the top right corner) it sends me to the waypoint creation page as it used to but,

 

 

There is nothing in the ref wpt, rad and dis slots, they cannot be edited and the waypoint coordinates don't match with the ones that i had where the cursor was, they cannot be edited aswell. Rendering waypoint creation impossible (question is, am i doing something wrong ?).

 

EDIT : It does the same thing when going directly to the waypoint creation page.

 

Also reported.

 

Cheers.

[j0nx]

I just bought this module lastnight and havent had a lot of time to mess with it yet but I have a few questions.

 

In the manual it says, "The CDI button is used to toggle between the navigational sources (GPS or VLOC) which provide output to the external indicators of the horizontal situation indicator (HSI) or the course deviation indicator (CDI.) This mode is maintained inside the instrument, and external subsystems may use it." but everything I am reading online says that the 430 does not link to the HSI or CDI. Does it provide a link to these gauges or not?

 

Do the com and nav features of the 430 actually work and provide coms or do we still have to use the old radios? Everything I have read online says the 430 does not work for coms or nav.

[Chic]

No link to the "external indicators".

Comm/Nav not modelled currently. GPS Nav working.

[j0nx]

Does shift alt b not work in VR? I only see a little tab that says gns430 when I do it. If not then I think I might be asking for a refund for this module. Not really even a beta imo with all the missing features and bugs and in VR it’s VERY difficult to read in its current dash location.

[ody81]

Does shift alt b not work in VR? I only see a little tab that says gns430 when I do it. If not then I think I might be asking for a refund for this module. Not really even a beta imo with all the missing features and bugs and in VR it’s VERY difficult to read in its current dash location.

 

Hmmm, well I'm not the guy for VR (I'd never get off the computer :/), I'm happy to go over any bugs or missing functions that aren't already noted in this thread that you may have found, don't be shy :book:.

[Gizzy]

...... in VR it’s VERY difficult to read in its current dash location.

 

A higher PD helps, rig dependent of course.

 

One workaround I use a lot is to have Camera Position UP/DWN & IN/OUT mapped to spare hat. In the Co-Pilots seat I move the 'camera' position forward and down a bit.... with PD of 2 in 1.5xx and 1.5 in 2.2xxx works well for me. An alternative is to set up a snap view to a close in view as possible (in VR snap view only relative to camera in/out left/right up/down... your head still moves as normal) and then just jump in and out on a toggle using LWIN + NUMKEY...

[rrohde]

Does shift alt b not work in VR? I only see a little tab that says gns430 when I do it. If not then I think I might be asking for a refund for this module. Not really even a beta imo with all the missing features and bugs and in VR it’s VERY difficult to read in its current dash location.

 

+1

 

I don't know why the large screen overlay does not work in VR (yet). But this is a must-have in VR, and should work.

[gospadin]

But this is a must-have in VR, and should work.

 

I filed the request in the internal tracker.

 

--gos

[j0nx]

Hmmm, well I'm not the guy for VR (I'd never get off the computer :/), I'm happy to go over any bugs or missing functions that aren't already noted in this thread that you may have found, don't be shy :book:.

Yeah I saw this bug from 3+ months ago but assumed by now it would have been fixed?? I guess not...

[gospadin]

Yeah I saw this bug from 3+ months ago but assumed by now it would have been fixed?? I guess not...

 

The best thing a user can do to help something get fixed is to report it. Ody and I do read this forum basically daily, so when we see something new that isn't fixed yet, we can make sure it's properly reported to bring it to the attention of the developers.

 

Yes, other testing is going on, but my use cases for the NS430 may not match someone else's, so reporting can only help. Worst thing that can happen is that we'll tell you it was already reported.

 

--gos