schmo

No problem, thanks a lot for your time!

That´s the only line that I was wondering about too. But to change it like you told me brought no success.

Nope Kyle, sadly even the reinstallation didn´t change anything. AOA repaint works like a dream, everyting else is unuseable. In the unuseable planes, if I go with my mouse over the speed selector (for example) and start scrolling the mousewheel, the cursor changes to the hand symbol, but that´s all what´s happening. Don´t know if this clould be a usefull information.

By the way, after uninstalling I´ve manually deleted all remaining PMDG folders under simobjects as well as directly under the fsx root. After that I´ve cleaned my registry by using TuneUp Utilities. I think I probably had everthing from PMDG kicked of the disc before reinstalling, altough I can´t be absoltely shure about that. Should the tailnumber match the little sign below the clock and left to the captains PFD? Because there is no tailnumber to see on the AOA repaint. That´s the situation right now: Installed repaints: PMDG standard from 600 to 900, AOA for the 800WL. 737-800 standard repaint (not working) - fsx menue: "N738PM" - below clock: "N738PM" - tail: "N738PM" AOA repaint (working) - fsx menue: "NAOA01" - below clock: "N738PM" - tail: nothing to see All necessary ini files are in the folder (N738PM.ini, NAOA01.ini) These are the (only) two livery entrys in the 737-800WL cfg file: [fltsim.0] title=PMDG 737-800NGX PMDG House Winglets sim=B737-800WL model= panel= sound= texture=pmdg kb_checklists=Boeing737-800_check kb_reference=Boeing737-800_ref atc_airline=PMDG atc_id=N738PM atc_flight_number=738 atc_model=737-800 atc_parking_types=GATE,RAMP atc_type=BOEING ui_createdby=PMDG ui_manufacturer=Boeing ui_type=737-800NGX ui_typerole=737-800 ui_variation=PMDG House Winglets airline_name=PMDG Flight Test description=Boeing 737-800 powered by CFM engines v 1.0\nPMDG Simulations\nwww.precisionmanuals.com \n\nProduced under license from Boeing Management Company.\n\nBoeing 737, 737-800 & Boeing are among the trademarks owned by Boeing. visual_damage=0 [fltsim.1] title=Boeing 737-8CTNGX Angle of Attack sim=B737-800WL model= panel= sound= texture=AOA kb_checklists=Boeing737-800_check kb_reference=Boeing737-800_ref atc_airline=PMDG atc_id=N738PM1 atc_flight_number=738 atc_model=737-800 atc_parking_types=GATE,RAMP atc_type=BOEING ui_createdby=PMDG ui_manufacturer=Boeing ui_type=737-800NGX ui_typerole=737-800 ui_variation=Angle of Attack airline_name=Angle of Attack description=Boeing 737-800 powered by CFM engines v 1.0\nPMDG Simulations\nwww.precisionmanuals.com \n\nProduced under license from Boeing Management Company.\n\nBoeing 737, 737-800, 737-900 & Boeing are among the trademarks owned by Boeing. visual_damage=0

@ Cristi_Neagu I have tried both ways. Normaly I load the default cessna at an airport and then change to any complex aircraft I´m going to use. This also worked for the NGX all the time. (But I´m aware of it that the manual recommends to load the 737 directly in the menu and then start the flight.) However either way of starting a NGX flight leads to the same result, which I described in my postings. @ Kyle The AOAl ivery comes as PTP file wich does´nt make it necessary to edit the config manualy, as you shurely know. At the moment I have only installed the standard PMDG repaint. Since I have reinstalled the NGX completly, I din´t change anything in the cfg by hand so far. But I will have a look at what the tail numbers are saying.

Bad news. It did not help. I´ve moved my position forward by changing my EZDOK pilotes view using the 2 key to overwrite it to be (a lot) more near to the windshield. I´ve also disabled EZDOK and moved the position with the standard fsx key commands to do so. Both had no effect. Everything is still the same. The AOA repaint works perfect, but as soon as I use any other repaint lots and lots of switches are simply dont reacting to my mouse anymore. I´ve also done a complete reinstall not only of the NGX but also for all other PMDG planes I have. It´s absolutely strange, since basicaly the plane seems to be working. I have realy no idea how a repaint could influence the VC in such a way.

To be honest, if you take it seriously, you would not use the FMS for fuelplaning. Instead the FMS numbers are there to figure out, how your fuelplan works out along the way. Of course, its a quick solution and it can be done in the simulator, but for a real fuelplaning I would also suggest to use PFPX (wich is payware) or to register and use the free service at simbrief.com to generate a flight plan there. In both cases you get a great briefing wich also includes the needed fuel. The 777 just isn´t a flight- or fuelplanner. It´s an airplane! (Believe me! I´ve seen some in reality. :lol: ) Regards, Schmo

Thanks, I will try that once I´m at home today an let you know if this does the job. It makes sense that there are differences between the models, but for me at the moment it does´t even work in the same model. AOA 737-800WL repaint --> all is OK. Any other 737-800WL repaint --> most switches don´t work. Thats still confusing, because at least the 800 cockpits should be identical. But this afternoon I will see what will happen.

Thanks for your quick answers. I have already tried to zoom in and out, even to go really close to the switches by useing the + and - keys, but also by changing my position with the arrow keys I´m using an EZDOK profile, witch should mean that I have the same viewpoint and camerasettings in every repaint. In the AOA repaint it works, in all others it doesn´t. Is it possible that there are seperate viewpoints set for the different repaints beside of the EZDOK settings? (I can´t try it out now since I´m not at home for the next 7 hours)

Hi there, since a few days, I have a strange problem with the NGX, which I never had before in any plane in FSX. After using the 737 for a couple of years without any problems, some days ago most of the buttons and swichtes in the VC stopped working. They are ignoring basically my mouse clicks. The coursor changes to the hand symbol, but nothing happens if I click or scroll with the mousewheel. To make it a bit more complicatet, thats the case with a lot of switches, but not with all. On the EFIS for instance, all pushbuttons like terrain, data or also the traffic and standard pressure knobs are working fine, but the scroll knobs can´t be used. On the MCP not a single switch or butten can be used. All capped swichtes on the overhead are unusable, but rotary switches like the autobrake are working completely fine. But it gets even more strange. And at this point, I have absolutely no idea how this could be possible. I have found one single repaint (wich is the Angle of Attack repaint for the 738WL) where everything and every switch is working normal. Only if I install this repaint and only if I choose this repaint in FSX, all switches and knobs in the VC are useable. If I load another repaint (even the standard PMDG repaint) or if I switch to another repaint after loading the NGX with the Angle of Attack repaint first, the same problem occurs again. This hole thing is the case with all models from 600 to 900, with the exception that the AOA Repaint only fixes the problem on the 800WL (They have also repaints for the 600 and 700, but if I use those, the switches still don´t work on these models.) If use the NGX at its lates version on WIN7 64 bit. Does anybody have an idea, what could be going on here? Thanks and best regards, Schmo

Hi again! Problem solved. FSUIPC was indeed the reason. But it´s important to know, that it´s not enough to simply delete the axis assignment, if additional adjustments under the "Joystick settings" tab for that axis were made. (I had to reverse the flap axis in order to work properly.) FO could set flaps only, after I deleted that adjustments too. Now everything works as it should. Thanks for your help, guys! Jano

Hi Bryan, thanks for your quick response. I found some topics about that problem in the button-control-section. Seems like FO can´t set flaps because I have set one axis of my saitek throttle quadrant for handling flaps via fsuipc. When I´m back home today, I will delete that setting and see if it works then.Thank you for your help so far. Jano

Hello everybody!I have a strange problem with FS2Crew Voice edition of the IFly 737 FS9.Everything functions perfect. Set headings or altitudes on MCP? No problem. Set frequencies on nav or com? Perfect!There is only one thing, that the FO doesn´t get right: The FO can´t set the flaps. If I call for takeoff flaps after pushback ("Flaps five"), he reacts on my command as he should ("Takeoff flaps set"), but the flaps maintain retracted. Same thing happens after takeoff and before landing. The FO always reads back my commands, but the flaps don´t move even one inch.I would assume, that there must be a wrong shortkey-setting, but the Ifly-version seems not to use shortkeys as other versions do.IFfly Servicepack 2.1 is installed. I have allready reinstalled FS2Crew. I can set flaps manually by using standard FS-shortkeys (F6, F7) and also via fsuipc. The only one who can´t move the flaps is my First Officer. Any ideas? Many thanks in advance,Jano

Hi Bryan, Hi Benny,thanks for your help.I will try your tips as soon as possible.During the last days I updatet my system with some new hardware. Unfortunately the changes were too big to keep my operating system running. So I first have to reinstall everything and this will take some time.Best regards,Schmo

Hi Bryan, yes, the FS Window is in focus. But PMDGs config manager seems not to save my shortcuts correctly or somehow overwrites my settings again. So today morning the command for decreasing the altitude was lost and the FO was hitting CTRL+U all the time until I stopped him. After correcting this everything worked perfect, no "runaways" anymore. So I guess the rec log file for this test flight would not be very usefull for you. (?)The difference to yesterday was that because of the missing shortkey the FO was unable to change the altitude value in the MCP window. Yesterday he could. Unfortunately I don