Premier

Hello all, Enjoying the 737NGX very much, but thought I would post this to see if the developers or forum members have any clues as to why this is happening. A quick background: This has been happening with all types of monitors and resolutions, in both FSX and P3D with both the FSX and P3D versions of NGX (all regularly updated) I have 2 monitors in use with FSX and P3D, a 3440 x 1440 widescreen which always displays the flight deck and a 1680 x 1050 monitor that is located physically above the main monitor to permanently display the OH panel (as seen in screenshots) I save all flights in this configuration, but you will see by the first picture, some of the OH Panel is not displaying correctly (Has sections duplicated and missing sections) when I start a flight. (See Pic 2) You will also see that the majority of the overhead panel does display correctly and all the click spots work. The only way I can correct this is to go into 2D panel and click the click spot on the windshield centre which stops the OH window from showing in its saved position, then click it again to restore it to its saved position and then the OH panel displays correctly (See Pic 3) It's just very strange that pic 2 is scrambled slightly in places I can then return to the VC and everything displays as it should I have tried it with a 1920 x 1200 monitor overhead, but the same results happen Its just a nuisance having to keep going into 2D to correct this each time I start a flight The other option would be to somehow create a click spot in VC that I could click that would do the same action as the click spot in the 2D panel, but have not been able to find or workout how this is done Edited to add: This same behavior occurs without the pushback gauge/window installed (ie, a standard Widescreen Panel / Panel.cfg) Sorry for all the pics, but feel it explains the problem better :-) Any ideas chaps? Thanks, Chris Morgan Perth, Western Australia

Hi all. have just installed SP1d and all is good apart from 2 things I noticed. My default is always CLDDRK on next startup, but I noticed that the L1 door loads up with the door opened. I worked out a fix for that, in the CLDDRK.sav file look for the line: Door 1L Position=0.200000 1.000000 1.000000 1143.110430 Change it to: Door 1L Position=0.200000 0.000000 0.000000 1143.110430 and SAVE I also notice that the top beacon light seems to permanently glow with CLD and dark activated, with all power off Should it be like this? Many thanks, Chris Morgan

Thanks for your reply Maarten. Thanks for the windows tip. That one had me baffeled, LoL. As far as the slow loading times, i'll try your suggestion. i have put disablePreload tweak in my FSX.cfg file, but it still takes forever to load FSX when using the Fly Now button in SLX. I may also try renaming my default flight to Default.FLT and see if that speeds it up. I will also set FSX up to stop the initial welcome screen loading, so it "should" load straight to my default flight. Cheers Chris Morgan

Hi Maarten, Firstly, thanks for producing such a fine product! I have a couple of issues which I hope can be resolved. I notice when I launch FSX thru the "Fly Now" button, FSX takes ages to load up (around 2 mins approx) If I launch FSX from its default icon, it loads in around 30 seconds. When it does finally load FSX (via the "Fly Now" button) FSX is running in the taskbar, but its no where to be seen on any of my four monitors. I also notice that if I go to the forum button within SLX, no browser window opens up or if a window is embedded in SLX nothing shows up.. Very Strange I have several other programs running, FSK and STB etc and when I click on them in the taskbar, they appear on the screen, so not sure why FSX isn't showing up. Many thanks for your help, Chris Morgan, PERTH, Western Australia

Thanks Maarten Just one more Q, LoL My 2 ORBX airports and 1 Aerosoft airport only have Blue STD icon for the airport (s), and nothing in the Publisher column. Should they be green and purple icons? They were installed in the default locations and active in the scenery.cfg. Database was rebuilt. No big deal of course, just thought I would ask :rolleyes: Cheers Chris

LoL, sorry about that....must have been that last glass of red or suffering from the oppressive aussie heat we are currently getting down here (Perth)...I'll blame that. Thanks for your explanation and SteveW's as well. So AM 14 (In FSX.cfg) and HT OFF in BIOS is the correct setup? (i7 4790K)

Hi Maartin and thankyou for a wonderful program. There is just soo much to see! I only have one question. My FSX cfg has Affinity mask set to 14, but in the tools menu in SL, it says Affinity Mask 15 Many thanks, Chris Morgan

Hi there. I currently run 2 monitors, the main monitor is 1920 x1200 and I use another monitor, which is physically placed overhead which is native 1680x1050. I have tried starting a flight in both default 2D and VC. I save a flight with the overhead panel sized and displaying properly on the overhead monitor. When I restart FSX and load the flight via the FSX menu, the size and positioning of the overhead panel loads OK, but as you can see in the pic, the flight control panel is duplicated and stretched over the panel containing the battery status etc The only way I can fix it, is to switch to the 2d panel (If I was in VC Mode) and clicking on the windshield centre O/H toggle switch, off then on again and then it displays OK. Is there any adjustment in the panel config I can setup so its saved to display properly? Also, I notice there is a lot of panel cfgs in the panel folder. If I'm using widescreen, do I have to rename the panel_widescreen.cfg to panel.cfg? Thanks Chris Morgan

Hi all. I just finished building my FSX PC (Specs in profile), and have been happy with it so far. Now for the daunting task of reloading all the stuff on it. I have noticed in a lot of posts, screen shots of various tools (GPU-Z, CPU-Z, Hardware Mon, etc) and was wondering if there was a program that would aggregate all of them. My idea is that you could no a shortish flight, and it would log all the performance related parameters, such as video card memory usage, temps, core usage and performance related stuf over the period of say, 1 hrs flying, even in a graph form or something like that. I understand that you can have 5 windows open for standalone programs, but would be great to have just one, doin all the graphing and monitoring. Thanks for reading Cheers Chris

Hi and thanks all for all your replies. OK I understand now. I was just thinking that I was setting up something wrong on the NGX. Cheers Chris

Hi all. im referring to the CIREBON ONE CHARLIE SID out of WIII that states 9000 @ HALIM and 11000 @ NUREN and FL 190 @ PURWAKARTA. When I fly this SID in the NGX, I seem to be hitting the required ALT 10nm before the actual waypoints (In all cases). From my (limited) understanding of ALT constraints, the FMC states 9000.11000 and FL190 without an AT or Below. Just wondering my my NGX is getting to the stated alts "early". Is it something to do with my CI? Should the aircraft get to 9000 on the NAV display (VNAV PATH) AT 9000, not before? My FMC displays HALIM 250/9000 Cheers Chris

Sorry for the delayed reply. Yes it did, thankfully. Thanks for the advice :rolleyes:

Hi Henry, and thanks for your comments. How do you move your seat forward? Do you use the Opus zoom feature or some other key command? Thanks Chris

Hi there. Thanks for your excellent software. From what I have seen, I wished I hadnt bought AS and Ezydok! Only have one issue. If I start FSX, load up the pmdg737NGX 738W which I usually use, select VC and all appears OK, buttons and switches can be clicked and turned. Once I run Opus, and the VC loads, none of the switches/rotarys are clickable or working. I did change the Captain 737 default view, changing only the zoom to 1.00, so the outside view is not like fisheye view and used the opus zoom in the live panel to zoom in slightly...otherwise all stock. As a by, I also created a throttles view (still in VC) from the captains seat perspective and all the switches and knobs work. As soon as I switch back to captains view, no knobs or swirches will rotate/click.....strange. Thanks, Chris Perth Western Australia

Cheers Greg for that Viper. did the same flight again yesterday and everyone survived :-)

Thanks Barbs, yes I now understand the green/white on the annunciators. So pressing the VOR/LOC early (ie; out of range) wouldnt have done anything (system wise), as there was no green or white VOR/LOC illuminated on the annunciator when it was pressed? There is a few charts here: http://www.cyberair-yssy.com/charts.html Nadi is at http://www.cyberair-yssy.com/NFFNALL.pdf Cheers Chris

Thankyou both for your valuable input!!l Viper writes: "On occasion I have had a IAN approach come up instead when I arm earlier but I clear it and make sure LOC and G/S arm and/or capture instead." Yes I may have selected the LOC button a bit early (No LOC light came up on the annunciator). As for the G/S G/P, I'll have a closer look at the FMC again tonight as I'll be doing that sector again. Anyway, I have some reading to do, but I have been changing the baro @ 18000, which is incorrect (For Nadi), so I learnt something there. Many thanks, Chris

Just thought I would update on this. I did the flight again yesterday, this time without high drama. I changed 2 things, and would like to know if either would have made the difference. Firstly I noticed that when the aircraft captured the G/S, it showed "G/P" on the annunciator. I slowed the aircraft down to 150kts (was 165kts) and it captured the G/P as before. The other thing I did was checked AS2012 for the baro reading, which was 29.80, so I set the baro to 29.80. Previously it was set at 29.92. Would this have affected the botched landing previously? I think I need to read up on the differnce between G/P and G/S as there is obviously a difference. Cheers Chris

Hi Fabo, Um not sure now. I had APP mode engaged on MCP, but have a feeling that G/P showed up just below the annunciators. To be honest, I'm a newbie at this ILS business but have done many ILS approaches, but never seen the G/P indicator come up on the PFD. The Chart is at: http://www.cyberair-yssy.com/NFFNALL.pdf (Page 14) if thats any help. I am going to do this flight again tonight, and take some screenies if it happens again. If I was in IAN approach mode, then I need to do some more reading up Thanks Chris

Thanks for the reply hopskip, but says video unavailable :mellow:

Hi all, doing a flight last night YSSY-NFFN. All looked rosey and sweet. Was established on the G/S and LOC ILS 02 at around 165kt, the aircraft appeared to be following the ILS/LOC (Both Magenta diamonds centred) but it suddendly looked like I was still too far from the threshold (around 2-300 meters) and was going to land short. Neither diamond moved from the centres of the PFD. needless to say, disaster occured as my throttle and buttons stopped responding (separate issue) I did notice a G/S inhibit light illuminate, but was at the last minute, so not sure why that happened or why it came down short, when all appeared to be good.. I also notice when I select the Nav 1 and 2 ILS freq (109.90) it says G/P on the PFD. Not sure Just out of curiosity, I used the program called FS Instant Approach, with the FSX 737 and it followed the G/S perfectly, so i guess its not a scenery issue. Any advice would be appreciated. Cheers Chris

Yes I think that was it Stefan, I have redone the view and its all good now :rolleyes:

Hey thanks Lek. Ill investigate this option and see if I can get it to work. Cheers Chris Yes that worked great, thanks! Did it thru fsuipc.

Hi all. Flying the NGX 738W and have come across an unusual thing, that I am sure has an easy explanation. I am using EZYDOK to switch between views in the VC. When I am in the pilots eye view, I created in EZYDOK, none of the buttons or switches work or animate (Doesn't change to a hand cursor) Yet if I switch to any other view inside the VC (also created in Ezydok) All the switches animate and turn/click etc. Just wondering if I have missed something. Also, I would like to assign Toggle1/Toggle2 on a Saitek x52 pro to the idle/cutoff levers. Cant see the settings in the assignments in FSX. Is this possible? Many thanks, Chris Perth, Western Australia

Hi all,Just a quick bit of background. I am using an android 7" tab as extra screen space for my FSX install. Specifically, I am undocking the FMCDU window to the 7" tablet, effectivley making a 'Hardware, touch enabled FMC" The extra window (Tablet) does not appear in Displays.I have tried 2 programs, iDisplay (via USB) and Screenslider (WiFi) and iDisplay works better connected via USB. iDisplay is installed onto your tablet, as well as to Windows.This program works flawlessly with FS9. I run iDisplay, press connect to desktop and after connecting, run FS9 and undock the FMC to the tablet. Any input into the FMC registers immediatley with FS9.With FSX, If I start iDisplay, connect with desktop then run FSX, I get the message "The graphics card does not meet minimum requirements for shader support. This product requires a geForce3/Radeon8500 class or better graphics card. Flight Simulator will now exit." and FSX CTD.If I Run FSX first, then connect iDisplay, I get no error message. When I undock the FMC to the tablet, I just get a black screen, the size of the FMC. When i resize the FMC window on the tablet, its still a black screen, but the touch panel is live. (If you run the mouse over where the keys of the FMC are, it changes to a hand. So it looks like the FMC bitmap just wont display. Same thing happens when I drag say the throttle panel to the tablet.It would seem that this then is an FSX only issue and as the error message states, a GPU issue, as it works good in FS9. I am hoping that there may be a work around, to fool FSX. Maybe a FSX.cfg entry? Its such a shame, as if you have a cheap crappy android 7" tablet, you just scored yourself a budget touch enabled FMC.