PGBosak

Have to correct myself. Return flight LOWW-YSSY worked fine. So that issue wasn't related to the aux-tank option, as thought before.

haven't any troubles with my settings, thanks however

Hi Ahmet when using P3D make sure you have set this line to your p3d.cfg [Main] AlwaysFullLoad=1 also make sure you have this fix installed when using windows 7 64bit https://support.microsoft.com/en-us/kb/947246 If you still have OOM then feel free to share your complete setup. We will find a way to avoid OOM cheers

Hi Jordan, did a lot of really long flights with 347.88 driver without any issues (P3Dv2.5). Changed to 352.86 and had 2 G2D events within 5 flights. So i changed back, and the issues were gone. As this driver seems to be really stable and compatible (referring p3d lights issue) i didn't upgrade to 353.06 anymore because there is no further increase in stability when already stable. ^_^ G2D events are hard to solve. If one is being confronted with that i'd start to rollback the driver at first. Thats what i've been trying to say before. cheers

would anyone with OOM like to share his vector settings? That's a real VAS eater! :ph34r: just tick highways primary roads small rivers wetlands and nothing else wenn flying IFR with a complex airliner It is possible to end every flight in fsx and p3d without OOM it is always a matter of setup. But there are meanwhile some very detailed airports out there, which don't let you the margin to use excessice ai traffic anymore. :ph34r: If you still want to use it you have to reduce LOD, TML; cloud drawing distance, soundprecaching, etc...

Hi Kyle, I left the computer with FL300, when i came back (several hours later; total flighttime was 18h 21min, no time acceleration, it stuck with FL340 when the opt. alt suggested FL380. No manual adjustment in the meantime. Normally the auto step climb works fine (200LR, F, 300ER) but it was the first time i had chosen the 3 aux tanks and that seems affect the ASC feature in a negative way. I don't know when i start the return flight but i am sure this will happen again on an odd level. (btw. this issue is no big deal, i just wanted to let you know. The info was taken from a 777 Cockpit DVD years ago. They demonstrated what will happen on a flight where no inputs are given for a long interval, in that case it was 5 hours, as far as i remember it was a flight form YSSY to KLAX or vice versa. I would be happy if i only had to react once or twice during a pacific crossing, regardless how real this is today. The alternative is to deactivate it totally, but i'd prefer to control this interval on my own. B) Hi Mike, i got it, will prepare my ini before the next flight, thank you very much. fsuipc is really a mighty tool. :wub: cheers paul

Hi Mike, will look into that, thx

Gents, I did my first YSSY-LOWW with 3 auxilary tanks on the LR yesterday and noticed auto-step-climb stopped working, when reaching FL340. It worked fine between FL 300 and FL340, but when the 77L should be leveled at FL380 already it still was at FL340. (P3Dv2.5; W7 64 bit, ASN) Btw. if someone else experiences G2D events with the last Nvidia WHQL driver, give it a try to go back to 347.88 WHQL. (it seems to be really stable on extremely long flights) Some thoughts: "Crew Alertness Monitor" i normally don't use this company option, because i can't set the idle trigger myself. If i could set it to e.g. 5 hours like i have seen it in real i would let it more likely enabled. But its annoying to push every hour a button between KLAX and YSSY. I hope we'll get the chance to personalize this option anytime soon, at least in future PMDG aircrafts. And my last thought refers to operations center: As i spend lot of time doing long hauls with the lovely 777 and saving my flight status cyclic with fsuipc autosaves, literally tons of files are being generated in PMDG panelstate folder. It would be handy, if the whole folder could be cleaned via OC GUI (except the standard panelsaves) when pressing a cleaning button. Maybe also a feature recovering unintentionally cleaned standard panel saves through OC (caching them) without using the aircraft installer again. cheers Paul

Maybe someone with P3D experience would like to share his favourite ingame :ph34r: simulation settings here with PMDG 777? Is NI still in use or isn't it necessary anymore? thanks

maybe someone can answer this: Are the installers compatible with every P3D v2 version. (academic, professional,..) or are they limited to academic plattform? thanks

thx for your effort, Kyle

Thx for the reply. I still hope this will be natively supported. As we know it from autostepclimbs in the 777

Will the 747v2 have an optional automatism with reference to cross-feeds (for those who still have a life and need to sleep sometimes )?

If your available VAS is less than ~150mb you will lose your exterior model, too. Regardless if you put the highmemfix line in your fsx.cfg You should monitor this VAS parameter on your flights, with tools like VAS monitor (available at avsim library, but wideFS is needed) FSUIPC also tells you if your are below 250mb VAS left with aural warning beeps.

happened to me twice with SP1b in KIAD. My thought on this is, that GSX (airport caching, whatever) had interfered the PMDG initialisation process. Those modules are all busy after loading fsx, simultaneously

tried to reproduce the "FLCH Freeze" and thank god the aircraft behaves like it should and not how i was being told here partly. that means: Instantly changes between FLCH VNAV and V/S (regardless if i am off- VNAV profile) The VNAV and the FLCH Button illuminates just for an eye movement simultaneously, not permanently as seen in my screenshot of initial post. (really don't know how i triggered this, just did what i had written before) No (permanently) shown simultaneously active/armed Situation between VNAV/FLCH in FMA (like seen in my screenshot) Hope you guys will agree, just one of the 2 situations mentioned here can be real BOEING logic. i am used to the one described in this post :ph34r: Knew i wasn't totally drunk that day. ^_^

This is all being known But in that situation there was no chance to deselect any active mode I said the status of my picture was "frozen" regardless what i've pressed on MCP I tried to: deselect FLCH press VNAV (no reaction on FMA nor MCP press V/S ( no reaction on FMA nor MCP) And thats what i put still into question. i wouldn't steal your time for that.

Hi Kyle, I haven't any problems reading the FMA properly, of course i was being confused by the parallel enlighted FLCH and VNAV on MCP upon entry but this isn't any mystery anymore. But still a problem is why this situation prevented me from leaving FLCH. I am not flying at the moment but from recall i did uncountable instantly changes between FLCH and V/S with NGX. i tried not just VNAV to leave FLCH with 777 i also tried V/S (forgot it to mention) no change of indication in FMA no change of ilumination of buttons (MCP) And that fact seems still not being Boeing logic to me. That was my mistake,too :blush: But that doesn't explain the "frozen" FLCH.

You got it, guys. Just for fun i tried to switch over to VNAV after FLCH to see whats happening. But not chance to unlock by switching back to VNAV. Even disconnect A/P and activating it again had changed that situation. LOC and G/S did it finally. base of operation: heading select (end of star)/FLCH below 10.000ft following downwind, direct/to FAF, LNAV VNAV with the result in FLCH lock LOC G/S (FLCH unlock)

happened on one of my last flights

Some of them just want to have just the latest installers and don't like to grapple with RTM installer, service-packs, hotfixes and sometimes veryhotfixes, i know at least one of them.

You should go for the update even it is beta to proof you're right with your suspicion. (btw i've never seen any weather engine freezing the sim) Before this patch there was a change to crash ASN due to specific setup in options menu. This is gone with the beta patch. But even this issues (apphang) did never affect the sim (FSX) itself (at least on my sim, but i use the networked setup on a second pc i just had to start asn again) long story short, this beta is worth trying, you can still go back to rex if it doesn't satisfy you.

my primary goal isn't "optimal" flaps/thrust config but rather a margin of 800-1000m. So i manually set thrust/flaps/assumed temp. to minimum required setup which gives me that margin. trim calc and speeds are done by fmc. Work fine on every flight because it covers any possible inaccuracies.

that doesn't say much. Most freezes i've seen over the years were based on unstable overclocking. There is always a stress situation when a freeze occurs first. I wouldn't start FSX before my system can't withstand a prime95 custom run with 960k FFT (min/max) over at least 12h todays CPUs are easy to OC but hard to get really stable. So if you are overclocking i'd investigate on that.

Did you check the proper connection of your USB control device?