GraemeBr

Occasionally when I begin my takeoff roll the autothrottle will disconnect when I select TOGA. I follow the same procedure each time i.e. establish 40% N1, select TOGA. When it happens I just rearm it and continue but I would like to know what I'm doing wrong.

To find the default tail numbers look in the directory for each affected aircraft livery. You will find a file named something like GVABA.ini . The root filename (in this example GVABA) is the tail number which should correspond to the entry in the ATC tail number menu which you can access via the multiplayer page in FSX. G-VABA for example is the British Airways 738-WL

I had this problem too. For me even reinstalling didn't fix it. After much troubleshooting I realised that during an online ATC session I had changed the tail number of some of my NGX aircraft from the default. This stopped the aircraft initialisation routine when loading and resulted in the 2D panels being non functional

If you have installed SP1C then the tutorial will be available in the PMDG menu from the Start Menu.

As has been mentioned previously, the brake temp gauge does not give an actual temperature reading. It is just a scale from 0 to 10. It also takes a fair bit of braking to get it to register and there is also a delay which simulates the time taken for the heat to spread to the sensor.

Since installing SP1C I have noticed a problem with cockpit lighting. When I turn on the dome light all the 2D panels go black. I also lose the digits on the MCP.

en englais, s'il vous plait

I have heard this too not only on the NGX but also in RW. I think it might be an addition in SP1C as I haven't noticed it until recently.I believe it is the fans turning freely due to the wind while parked. I seem to recall seeing a mention of this in one of the manuals as a consideration for engine start when this occurs.

Best to look at the FS2Crew forum. I believe there are some tutorials available or to be released along with SP1

The different responses for left and right sides for runway entry and pin removal on pushback are a nice touch.

The tail number of each livery is different i.e for the British Airways it is G-VABA. The tail numbers are set by PMDG are in the ATC tail number menu which can be accessed in the multiplayer preflight menu. The problem occurs when you change the tail number from this default. I did this on my during an online ATC session.If you have changed any of these tail numbers you will have problems with that aircraft. You need to change them back to the defaults. You can find the default tail number by looking at the name of the ini file in each livery directory i.e. G-VABA.ini

I had this problem too last week. Took me 2 days to solve and even after completely removing and reinstalling the PMDG it didn't fix it. I finally worked out the problem was I changed the ATC tail number of a couple of my NGXs during an online session Even when then flying in free flight afterwards where the ATC tail number is not an option the problem persists. This has the effect of removing the ID that it needs to run the panel initialisation setup. I reported this to PMDG and they are looking at ways to fix it in the future.Hope this fixes your issue.

I assume this is a question rather than a statement, or do you know something we don't?

If I recall correctly, the key you need is, 'z'

I think I have resolved my issue. After trying uninstalling and reinstalling the NGX completely with no success I thought again about the circumstances of when the issue started to happen. I realised that it happened when I tried to fly online and it only affected the liveries that I tried to use during that session. I remembered that I had changed the ATC tail number on each of them. However once I had the issue I went back to free flight to try to resolve it, where the ATC tail number is not an option. When I looked in the aircraft folder I noticed an ini file which has the tail number as part of the file name. This file appears to setup all the displays. I went back into multiplayer and changed the tail numbers back to the defaults and now the panels initialise properly again.It looks like PMDG aren't aware of this issue.So in summary to avoid this issue: Don't change the default ATC tail number when flying online as it will corrupt that aircraft even in free flight.Thanks for the suggestions on this issue.

I have now uninstalled both the 800 and 600 packages and then deleted all the PMDG folders from within the FSX directoriesReinstalled the 800/900 base package and a few liveries. I had the same issue, some liveries (including PMDG created versions) have corrupted 2D panels.As the problem appeared to be deeper I tried to do a system roll back. Now I have a real mess. I have two versions of all PMDG folders and I am not able to select any PMDG NGX aircraft from within FSX. And now when I try to uninstall any of the packs I get an error.I have raised a ticket, hopefully they can help me out.

Just uninstalled and reinstalled the 800/900 base package and SP1C and it didn't fix the problem. The 800 WL liveries that I used previously have corrupted 2D panels and don't initialise on loading. The rest seem still to work OK.Perhaps I need to remove the 600/700 package too.

Which procedures? Do I use the add/remove progs in control panel?

Up to now had very problems with the NGX although tonight when starting up I did not get the initialisation countdown. I then found the 2D popup panels were corrupted.This only seems to happen on some variants and some liveries. The others start fine. I have tried to remove and reinstall the liveries and also to reinstall SP1C. This didn't fix it.How do I fix this?If I need to uninstall the entire NGX how do I do it? Will I need to reenter the activation code when I reinstall?Thanks

I have never got too concerned over getting the trim setting exactly the same as the value in the FMC. I don't think its necessary to be too precise

I'm just lazy and like novelty of having someone to boss around in the cockpit :Kiss:But seriously though I also have the autothrottle and autopilot disable mapped on my yoke and usually use them. However what I haven't worked out is a way of silencing the associated alarms without having to reach for the mouse to cancel them on the panel.

That's interesting. This might explain why I can't get the FO to turn the autothrottle off even when the command is recognized in the green bar.

+1

First off, let may say as a new FS2Crew user I am very impressed with this software. It has brought a whole new enjoyment to flying this already fantastic aircraft. I have found the voice recognition very accurate, however there are 2 commands that I just can't get to work.The first is the command to keep the flaps up after engine start during taxi. When I say it I get nothing at all in the green barSecond is how to turn off the autothrottle. When I say it the FO acknowledges it but the 'arm autothrottle' on the MCP remains on. Perhaps this is a misunderstanding on my part of how this works. Does turning of the autothrottle on the throttle quadrant not have any affect on the arm autothrottle on the MCP? Up til now I have always used the switch on the MCP to return the throttles to manual control.ThanksGraeme

To go some way to answer some of the points asked above.FSCrew does have a small banner window as a user interface but it is not necessary to have this displayed at all times to use the voice functionality.I have found recognition works very well even with my Scottish accent.I agree that some sort of a video tutorial would help to support the manuals, but even as a total new user to FS2Crew after a couple of flights I am really getting it to work well for me.