NGXu seatbelt and no smoking lights not recognized

[pgspy18]

I'm having some weird and frustrating behavior where the FCDU will show that it's getting a 0 signal for the seatbelt and no smoking lights regardless of what the actual switches are set to. I've got FSCaptain 1.8.3, P3D v4 (specifically 4.5.14.34698), and NGXu 2.91.0830. As far as I can tell, all the other signals are working (nav lights, landing lights, etc...), it's just those two.

Going into the Offline > Information page, it shows PMDG/737NGXu (so the specific plane is recognized), and both BELT SIGN and NO SMOKING SIGN show "0 A/C" regardless of the switch position.

Reading through this thread, I double checked the lvars in LINDA, and they haven't changed, and after that I'm sorta out of ideas. I'm hoping there's something simple I've overlooked, haha.

[peter]

Hello Pgspy,

I am sure Travis will look into this. Can you send us (see blue link below) a zip file with your FSCaptain\Data\Log folder? Please send the email to all of us and copy the address of this thread into your message so that everyone on the FSCaptain team knows what the logs are for.

Cheers,
Peter

[pgspy18]

Email sent, thank you!

[Travis]

PGSpy,

I see nothing in your post or logs that would indicate a problem.

I'm assuming that you know both of these LVAR values are keyed to 0 as "off" and 100 as "on."  Their "Auto" values of 50 are ignored.

If you use LINDA to set the LVAR values to 100 and to 0, is that recognized in your FCDU?

Best,

[pgspy18]

Hey Travis, sorry for the late reply.

Not really, setting them to 0 turns them off, and 100 turns them on (and for the seatbelt, 50 does set it to auto) in the cockpit only. FDCU still reports "0 A/C" regardless of the value set in LINDA: imgur.com/DZOjecF

[Travis]

Your screenshot reminded me that the NGXu may have taken a different approach on some things.

I need to look at the code after my lunch and get back to you.  There may be different LVARs in play and I'll likely ask you to perform some other tests.

Best

[Travis]

We're not looking at the "[...]73X" LVARs for the Smoking and Belt signs, so your test makes sense.

Now those two LVARs you showed in your LINDA screenshot reminded me that the NGXu introduced a new set of LVARs, which for some Captains some of which seem to work and others that don't seem to work.

Our NGXu interface looks at these LVARs and values for OFF and ON:

     // Smoking & Belt Signs
     //
     CabinAlerts(0, 100, "(L:ngx_switch_103_a,number)", "(L:ngx_switch_104_a,number)");

"[...]103[...]" is the smoking sign and "[...]104[...]" is the belt sign.

And if I interpret your screenshot, you changed "switch_104_73X" to have the control in the VC to move.

Could you monitor the values of both "ngx_switch_[...]" LVARs and both "[...]73X" LVARs as you change the VC control knobs and let me know the values of all LVARs for both OFF and ON states?  (We ignore AUTO.)

It could be that one of the groups is 'get' and other set is 'set' or any other possible combination.

Best,

[pgspy18]

Hey Travis,

I did some testing, and here is what I found:

1) Toggling the switches in the cockpit log events for the switch_xxx_73X variables, but not the ngx_switch_xxx_a variables.
2) Toggling the switch_xxx_73X variables in LINDA moves the switches in the cockpit.
3) Toggling the ngx_switch_xxx_a variables in LINDA has no apparent effect.
4) The 737-900 variant of the NGXu doesn't even have ngx_switch_103_a and 104_a variables.
5) The FCDU reported "0 A/C" the whole time.
6) I couldn't tell if setting one variable in linda logged an event for another, as selecting the LINDA window would log a "LogOptionProtect Access Violation in module LINDA.exe" and promptly disable the "Log LUA events" option, so while I can't tell if changing xxx_73X affects ngx_switch or not, given that FSCaptain is apparently looking at ngx_switch and getting nothing, I'd hazard they are not linked, or my installation is completely borked?

[Travis]

I doubt your system has been el-kabonged, as it seems that the _73X LVARs work for you.

I'm puzzled as to why the ngx_switch_ LVARs work for others, but not for you.  But that's something beyond my pay grade or a setting in the NGXu installer(??).

I'll change the LVARs we're looking for here and you should see that in the Release Candidate I hope to have ready by this coming weekend.

If this change works for you, but other NGXu Captains report problems with the change then I'll just make a separate interface and one set of NGXu Captains would only need to specify which interface to use in their Override Configuration files.  Easy peasy.

Best,

[pgspy18]

I’ll keep an eye out for a RC this weekend and I’ll let you know how it goes.

Thanks so much!

[Travis]

The RC should be out this weekend, and MSFS Test Build 2 should be out on my Thursday afternoon.

Our heatwave has abated a small bit today; hurrah for better sleep!

Best,

[Travis]

I'm actually on schedule for a change.  Yippie!

This issue can be marked as closed, and email has gone out to MSFS Testers about Build 2.

I've purchased MSFS and plan to install it this weekend after 1.8.3 SP Release Candidate goes out tomorrow.  It took quite a while for my first install a year or so ago, and with more updates since then I expect it to take longer this time.

Best,