Dick

Hi Angelo, To answer your question: no a TOCG that is too much forward is not a problem when landing. TOCG however is not the cg condition of the aircraft in flight, as you state, but only the cg condition of the aircraft at TO. (with the fuel at to) The factor that changes the cg during the flight is the burning of the fuel in relation to the stored location of the fuel. Fuel in the center tanks will make you noseheavy and therefore if fuel is used from the center tank in flight the aircraft will become less nose heavy. If the aircraft has a tailtank it would be the opposite. Fuel in the wings normally does not change the CG a whole lot. For the 747 in general there are 3 cg envelopes. The ZFW envelope. The CG of the aircraft in ZFW condition (=no fuel) needs to be in that envelope. Then you have a TO envelope, the CG of the aircraft with the fuel at the moment of TO needs to be within that envelope. During flight your CG will be changing depending of which tank is delivering the fuel. Then you will have a landing CG envelope, That would be the CG of the aircraft with the remaining fuel at landing. The envelope as mentioned shows (mostly in a graphical way) the CG limits applicable for the related aircraft condition. b rdgs / Dick = and please don't kill the airbus. They are also good aircraft.

A search for Rob Barendrecht in the Avism Library gives me this https://library.avsim.net/search.php?SearchTerm=+ rob+barendregt&CatID=root&Sort=Name&ScanMode=0&Page=4 b rdgs / Dick

What checklist do you use ? If I have a copy of it I will run a cold and dark from it and see what happens... Have you tried starting P3D with a cub or other default aircraft before you load the dash ? You mention P3dV4 but I take it you use 4.1 ? You really should be able to enjoy this top aircraft ! b rdgs / Dick =

Do you start from a saved panel state ? if so something could be wrong in there. Otherwise: is your trim set ? and the antiskid on ? are all the lights on the waning panel just below the overhead off ? What happens if you do the T/O warning test before you take off ? Does that trigger an alarm ? I do not believe that what you experience is a bug. I myself can take off happily, once all the conditions are met. b rdgs / Dick =

Alan, you are aware that Alexander is the flight dynamics engineer from PMDG for the DC-6 ? b rdgs / Dick Knight -

Is there something that is not clear on the mentioned FCOM page ? Without having seen your flightplan It is impossible to know how to solve it. But you will need to change a speed or altitude restriction in your flightplan on the RTE Legs page in the FMC in such a way that the FMC can construct a descent path.

Can you confirm it said "NO DEST PATH AFTER" .. or did it say "NO DES PATH AFTER" ? "DES" in the latter would stand for descend and would indicate that the FMC does not have the correct information to compute a descend path, which is in line with your observation that you could not engage VNAV. FCOM2 page 1134 (11.60.16) provides the cause and the corrective action b rdgs / Dick =

Well,.. contacting support of course never is a bad thing but this issue can easily be corrected by yourself. Go into you Flightsim directory. Look for Simobjects > airplanes > PMDG 777-300ER. Open the directory and look for the aircraft.cfg file. Open the cfg file with e.g. Notepad. You will have a [flightsim.xx] entry that corresponds to the Air Canada livery. Correct in the first line (title=) whatever you want to correct, save.. and your are done ! good luck / b rdgs / Dick =

Simbrief has an option to export flightplans into the Dask

As far as I know the sequence of installing is not important. ORBX will itself arrange the proper scenery order provided you set in FTX central / settings the "library insertion point" . I took the first (from the bottom) third party airport that I have and FTX central did a nice job of placing all the ORBX stuff below that in the right order. b rdgs Dick =

You can certainly unload them. Go to top/main menu Options > addons and you will find all your XML entries ready to be disabled.

Just an idea, why don't you make regular backups ? I have Macrium, programmed so that it makes automatically a daily backup at the start of the day. It keeps these daily backups for 2 weeks. When something goes wrong ( or when I screw up things ) there is no pain. I just go back to an earlier date like e.g yesterday... This way I beat whatever update comes on my path.. I updated Denver to V2 P3dV4 without any ill effect on my FSL A-320.. b rdgs / Dick =

You start process monitor with P3D running. . You should see ( on top ) of Process Monitor a command "filter". Select that. Select again filter in the popup. Click on ":Architecture". A list should pop up. Select "Process name". Then after the "is" in the next box you have an empty box. Click on the box and you should see all the processes that are running on you computer. Select P3D, add and you are done. You get a huge list with everything that goes on in your computer. You need to know the exact time your CTD occurs. If you have a relevant CTD entry in your event viewer you should have the exact time. You now search what happened in your system at that time. The result column in the output should give you an indication. In my case I found a buffer overflow of the soundcard that started the CTD. I would have never thought that my soundcard was the culprit of my trouble... Got it fixed now. b rdgs / Dick

Yes, I also think you need to get it. It gives you clear breakdown of everything that goes on in your computer. You can further specify that the program only logs P3D activity. That reduces the log size. As mentioned earlier I had a CTD while process monitor was logging and it showed that my CTD started with a buffer overflow in my soundcard. Never in the world I would have expected that.

Have you ever tried to log a CTD with "process monitor" ? That should give you a lead into your problem.

ORBX scenery will (re)arrange themselves within the library once you have set the insertions points on the settings page of FTX central. Even you do rearrange them by hand now next time the sequence will be a mess again. And indeed, without proper sequencing things will not look right ! b rgds / Dick

Check your PMDG ops center, There is an update to correct this faulty startup state. If you do a search you will find various messages about this topic b rdgs / Dick =

Jim, indeed chaseplane does take over this view. In your camera,cfg [cameradefintion.006] should end with "HotKeyselect=4" Any other hotkeyselect=4 options should be hashed out .. that is to say you put "//" in front of the line As far as I remember Chaseplane added the hotkeyselect=x to their cameradefintions and effectively override the default views. So I hashed out the chaseplane one's Does chaseplane still work after rebuilding your cameras.cfg ? b rdgs / Dick

I am also on V4.1 and it still works as before. I have in the key assignments "view camera 4" assigned to F12 and that gives me a top down view. Did you recently install something new ? some aircraft or tools reassign this. b rdgs / Dick =

I have the same problem and I do not have FS2crew installed. Used the short panelstate straight and unchanged from PMDG. Had an PMDG ops center update installed earlier today.. b rdgs / Dick =

I got it as well. ( 400ERF) No Fs2crew installed. P3Dv4.1. Failures off and FMC does not not show any active failures b rdgs / Dick =

Yes, there is indeed more. After having changed the texture setting in P3dv4 I crossed the pond again. Made it safely west and eastbound. Did another one westbound and this time I got hit with CTD (ntdll.dll) various times, mainly over Canada, Very strange, same aircraft ( PMDG 772), same route etc. But I was able to "catch" one with process monitor ( as Jim explained). Turned out I had a whole series of Buffer overflows, the one that started it all seemed to be: C:\windows\system32\XAudio2_4.dll That was unexpected. Found some other advice from Jim how to deal with this and I fiddled around with the sound drivers and settings. Back over the pond again I guess.. At least I have a lead now into my problem and a nice way to record these CTD's in detail. b rdgs / Dick =

Very interesting Jim. Thank you for sharing. I can add to this that my ctd's mostly happen when p3dv4 runs at 4x speed. I guess that would also attribute to "choking" p3d when on too low settings ( if I understand correctly what you are explaining ) For me it was a natural tendency to be conservative in the settings for texture resolutions in the sim. In the past we have all been punished for settings that were too high. It's a change in mindset now to realize that we are now being punished for too low settings. Previously I was running on 1024 or (mostly) 2048. I have changed this to 4096 texture resolutions in the sim settings and I am on my way now over the pond on 4x speed to see what happens ! Much appreciated Jim ! best regards / Dick =

@ Jim, thanks for the tip about about Process Monitor. Gives indeed a wealth of information. @ Miquel, I did some flights over the pond the weekend and all passed Greenland without a problem. I did copy the settings as you recommended earlier but when reading your experience this doesn't always solve the problem. I did get CTD's though. One on a EGLL/KSFO flight. I was approaching TOD and had process monitor on for the while flight ( gave a huge file ) But there was no information in the event-viewer so I had no exact time of of the crash. The return went without a problem. KMSP to EHAM went fine but 2 CTD's on the return somewhere over Canada, running FSUIPC autosave made it possible to restart and eventually I arrived. Will repeat the flight with the 777 and see if that makes a difference. Otherwise lets hope that 4.1 brings us relief here... brdgs / Dick =