Easier way: https://forum.pmdg.com/forum/main-forum/pmdg-737-ngxu-for-prepar3d-v4/89110-remotecdu-inop-bbj#post89119

 

Edited October 25, 20205 yr by B777ER

18 minutes ago, B777ER said:

Easier way: https://forum.pmdg.com/forum/main-forum/pmdg-737-ngxu-for-prepar3d-v4/89110-remotecdu-inop-bbj#post89119

I'm am not sure what the remote CDU is. We can only work with the published SDK - most worked out by guesswork. PMDG is not my thing.

1 minute ago, ScotFlieger said:

I'm am not sure what the remote CDU is. We can only work with the published SDK - most worked out by guesswork. PMDG is not my thing.

Post #5 for LINDA and how to solve it much easier than creating a new module. 

The search string PMDG*737 also picks up the old PMDG 737NGX if installed. This is why the original changes were made for those users wanting to use both old and new versions. Now PMDG introduce this BBJ thing (no idea what it is) with a different naming convention. Why can't users just stick with one aircraft? Mine's the C172 or Airbus A320.

BBJ = Boeing Business Jet. And doing it the way I did works as long as you have just the NGXu installed and not the old NGS. Frankly, why on earth would someone have both installed is beyond me. 

Edited October 25, 20205 yr by B777ER

Because some textures are only available for the NGX. I was in that boat for awhile. I finally cut the cord about 2 months ago. 
In any case, I submitted a trouble ticket to PMDG to try to correct the file structure by adding NGXu into the BBJ title. We will have to see if they can/will do so. I have no idea what other changes that drives for them as far as the Ops Center etc. If others are interested in seeing this change too, they should submit a ticket. Greater numbers might tip them off to the impact that change could make.