FsPassengers Forums
Mini display and FS2crew for 737 NGX - Printable Version

+- FsPassengers Forums (http://www.fspassengers.com/forum)
+-- Forum: FsPassengers (http://www.fspassengers.com/forum/forumdisplay.php?fid=3)
+--- Forum: FsPassengers Support (http://www.fspassengers.com/forum/forumdisplay.php?fid=5)
+--- Thread: Mini display and FS2crew for 737 NGX (/showthread.php?tid=8902)



Mini display and FS2crew for 737 NGX - gporzio - 18-03-2012

Hello,
I know there is another topic with an issue concerning the minidisplay. This one, however, is slightly different.
Until now, FSPAX was working just fine with the 737NGX by PMDG. I have now installed FS2CREW for the PMDG737NGX and the minidisplay just
stays empty. I have tried to modify colours, etc., but to no avail. I can change the level of transparency, but no cigar when it comes to buttons and
text, verbose or not.
FSPAX is definitely working. I can access it via the menu bar and I can click (for instance the seatbelt sign). Though I cannot see the button, I know
where it is, so I just click in the area of the blank display where it should be. Also, all crew announcement and co-pilot comments are just fine (I made
a death dive on purpose just to see if he and the passengers would complain: they did Worry




Re: Mini display and FS2crew for 737 NGX - Kebas - 16-04-2012

Same problem here.
Not found a solution yet Rant




Re: Mini display and FS2crew for 737 NGX - Kebas - 16-04-2012

Searching on the FS2Crew support forum gives a possible workaround:
http://forum.avsim.net/index.php?showtopic=365637&hl=fspassengers

It seems that the problem is a combination of PMDG737NGX and FSPAX.

Quotation from BYORK FS2Crew support forum:
"What happens is that if you add a Window 25 or greater to the Windows Titles section in the NGX’s Panel.Cfg file, FSPassengers stops
working properly.
What’s especially strange is that the mere existence of Window25 in the Windows Titles section by itself will trigger this behavior, even if
there are no other non-PMDG NGX entries added to the Panel.Cfg!"

Hopefully the developers of FSPAX can fix this very soon!