denthibbe

Wait a minute, do I here an alternate formulation of "Just be very very (as in 'extremely') nice about it, and then (maybe) we will do what you ask" ?! Honestly, I said goodbye to the MD-11 several months ago, understanding that this project would enter the history books as a monumental failure. So is your post really meant to bring a spark to our hopes? Or just a way to play with our emotions?

What I've never understood and probably never will is the pickiness of some about the exterior model. I for one never ever switch to outside view. Hell, if PMDG did sell a cockpit only version of their products (at lower price) I would be the first in row the buy it instead of having an exterior model I have no use for and which is sucking up precious resources... on top of that, it would reduce development time (I reckon the exterior is not the biggest part of development but still, it would help)

What is it that you are missing when simply logging into your account on the precisionmanuals.com website and opening your order details there? I may be wrong but afaik the content of that mail confirmation is only just a copy of your order details?

2 hours in flight from KATL (ImagineSim) to KLAX (FSDT). In a normal situation the amount of free VAS at this point would be something around 1.5-1.6 GB. Right now I am at 700Mb and it's still decreasing... I reinstalled ASN on my networked PC. It will ask you to manually reset all shaders by deleting all files located under %LOCALAPPDATA%\Microsoft\FSX\Shaders\Misc and %LOCALAPPDATA%\Microsoft\FSX\Shaders10\ShadersHLSL\misc For a moment I really thought this would do the trick but unfortunately it does not seem to help. Slowly losing hope...

Same setup here, never had any issue with VAS usage since release of the 777 and also didn't change any setting for the last year or so. About a month ago I downloaded a new livery for the 77W and during the flight KORD-RJAA (both stock) my VAS decreased steadily until after like 4 hours in flights (over the north pacifique) the sim just froze... I remade that flight the day after with the same result. After this I flew another route (FSDT's CYVR to YSSY) in Air Canada livery (which was installed several months ago) and I had no VAS problems whatsoever landing with more than 1 Gb of free VAS. After some more testing I came to the strange conclusion that all newly installed liveries caused that "leak" in VAS usage. When flying in an "older" livery the VAS issue did not occur. So it was (sort of) OK for now... Everything changed when lately, after updating the Operations Center, I downloaded the latest PMDG 777LR/77W installers and installed both of them. Since then the "leaking VAS" issue occurs on every flight I make regardless of the livery I fly in. My ASN is installed on a networked PC so I only just uninstalled the "AS Connect" which is the only AS related piece of software installed on the FSX PC and made a flight without running ASN (fair weather theme), but the VAS leak still occurred so I thought ASN could not be at fault here, but reading Dan's post I will definitely make the complete reinstallation of ASN. Although I can not remotely figure out how a non-running ASN (on a networked machine) could cause FSX to "bleed" out of VAS I am now reaching the point where I will give anything and everything a go (even if it does not make sense) because I am out of (logical) options. This kind of issue drives me mad and desperate because it pops up out of the blue with no apparent reason and it completely destroys the experience... Not blaming anybody here because I really think this is nobody's fault. FSX is just too old I guess? Maybe the time has come to step over to P3D...

What I've started to do since a couple of months now is refreshing the scenery about 10 minutes after t/o. I've mapped the 'refresh scenery' option to a key and just press it to have the scenery reloaded. Usually (and depending on which scenery I am using) this will free up 200-300mb of VAS (I am using a tool through WideFS showing me my current free VAS). The only (but very annoying) problem I sometimes do encounter when doing the refresh is that every now and then it gives me a black screen (you know that black screen when everyting seems to be still running perfectly well except for the graphics...). As an example: when I make a trip like KATL to FAOR right after taxiing to the rwy holding point my free VAS can drop below 1000Mb (ImagineSim's KATL is quite a memory hog in that aspect). If I would try to make the whole flight starting with VAS being that low I could get in trouble. After t/o the free VAS will increase a bit (let's say about 100-200mb to level up at about 1.2Gb). After 10 minutes (when I am sure the t/o airport scenery is out of range) I do the refresh and this will increase the free VAS up to 1500+Mb. In my case this is plenty enough in order to end my flight (including taxiing to the gate) without having to think about my free VAS. Personally I am very uncomfortable with free VAS decreasing below 500Mb (it's that treshold I cannot accept to trespass ) From my personal experience FSDreamteam, FlightBeam and the V2 Flytampa sceneries do a very good job in optimizing the VAS usage (the increase in free VAS after the scenery gets out of range is very noticable even without reloading the scenery manually) Truth be said, I just realized that I actually rarely fly from payware scenery to payware scenery but rather stock scenery to payware scenery (or reverse)

+1 Same problem occurs on Aerosoft's Nice Côte d'Azur scenery landing on 04L Setting mesh resolution on 19m solved it for me too (10m was already too low as I still crashed when landing a bit too low) This is what happened :

I have the impression that you are actually stuck with the config of 1 specific installed livery of yours. Therefor make sure you don't have a 'fixed config' value set in your aircraft options : PMDG SETUP--> AIRCRAFT --> fixed config : this should not contain an aircraft registration code otherwise wahtever the livery loaded, you will end up with the same aircraft config over and over.

OK I found out why the livery specific options were not applied correctly. It turns out that in the PMDG SETUP--> AIRCRAFT section I had the option ''fixed config'' set on D-AALA. That's why every livery specific option set was overridden by it. I cannot remember when but I must have mistakingly activated that option while having a look around in the CDU option (during the first hours of use I guess...) Hope this info can be useful to anyone else.

It seems that right now there's something not working exactly as it's supposed to be (at least not on my system). For example, I have both the Delta airlines and Aerologic liveries installed. When I start FSX --> load up the T7 with Aerologic livery all weights are expressed in KGS and temps are displayed in C°. Now I close FSX --> restart FSX --> load up the T7 with Delta Airlines livery --> still KGS and C° used... I close FSX --> open the Operations Center --> check the aircraft systems settings for Delta Airlines --> the 2 last lines show LBS for weights and F for temps. So I start FSX again --> load T7 with Delta Airlines livery --> change KGS to LBS and C° to F --> end of story? No. After closing and starting FSX again and loading up the Aerologic livery again, now it shows everything in LBS and F... :blink: . Checking in the Operations Center the settings for Aerologic are still set to KGS and C°. I have uninstalled all liveries and reinstalled them but the above described behavious still occurs. So I am thinking that if any modification is made directly in the FMS (in sim) that this will override any settings set in the OC. Maybe it has something to do with the use of saved flights... I don't know. Is anyone else having that issue?

Kyle Rodgers' tutorial about flightplanning is what you need to read : http://forum.avsim.net/tutorials/article/81-a-guide-to-routing/ to get started and http://forum.avsim.net/tutorials/article/82-a-guide-to-playbook-routing/ when you understood the first one

I voted yes as I am an unconditional fan of this plane, but the result of the poll (globally 50/50) unfortunately again proves that PMDG is totally right about the MD11's unability to be commercially successful. Even if we had more than 75% of yes on this (which would mean 75% of an already poor amount of initial sales) I believe that wouldn't be enough to change PMDG's opinion on the matter, which is totally understandable.

My OCD senses are tingeling... ^_^ In my world a new (FSX dedicated) hard drive means a fresh FSX installation.

+1 Praying for the 777F to be included in the base version.

Then I am afraid you are already there my friend. With that CPU there is as good as nothing that any other GFX card can do to get better performance.