denthibbe

Was referring to this more specifically : (he also redirects to another more general answer from Mr. Randazzo in this post) The licensing aspect in P3D has been the very first hurdle that kept PMDG from developing for it initially, so saying that's the first time you heard of it sounds a bit strange. And therefore I said that this could be a reason aside from the business aspect, the sales figures being the main reason I guess...

Would pay in advance whatever the selling price... The problem, from what I understood, is actually about the licensing in P3D which seems to prevent PMDG from developing it (aside from the business aspect) It won't happen, I accepted this a long time ago... There is a developper for XP11 who is planning to make this bird though :)

Although the topic has fallen into the "mine is better than yours" sphere I still wanted to add my honest thoughts about the matter. Since my last post on this topic I still did not buy the QoTS V3 because I want to know what the possible 64bit upgrade of P3D will have to offer exactly and, yes, at some point I really would like to be able to tell a final goodbye to P3D. Why? simply because it's old, expensive and keeps you from updating very simple things like graphics card drivers or I will have to cope with showstoppers like VAS depletion. In a way XP11 is such a breath of fresh air. When preparing your trip you just fill in your flight plan and, if you just feel like it, enter both SID and STAR (including runways) even before starting your checklists... seems so obvious yet these are the things I never do since the last 3 years or so without keeping a stressed eye on my VAS counter for the next 30 minutes in order to check whether or not I triggered some unexplainable memory operation which basically ruins the whole experience.(sorry for the very long phrase !) Do I think XP11 is perfect? Absolutely not. Actually I was surprised to see it being officially released so soon because I really thought it still needed a lot of polishing up. I think that even the most developers where a bit surprised because a lot of addons had to kind of push out patches really quickly to temporarily address only the most obvious glitches in their products. The plugins philosophy is also something I am not that fond of. Coming from a P3D setup where everything (wxr engine, radio, IVAO client, etc...) is run on a networked PC, having to come back to a setup where everything has to run on the Simulator PC is actually very hard to accept... strangely enough. Honestly it is very difficult to try and step away from a sim I have been using for 10 years now (I know that is not even that long...). I feel like I know it inside out (been through the whole FSX tweaking history). Bottom line, the main reasons which made me look elsewhere where the many technical issues really feeding me up to a point where I wondered why I was still coping with it and most important of all, I was paying for it... imho XP11 really needs to evolve and I am still afraid that without a bigger user base (read "higher potential to attract more developers, bringing their creativity and know-how") it will never really get the chance to reach that point where I can really ditch P3D totally... Again thoughts of a random customer A nice day to all of you.

Make a system restore to the point before the installation of the updates? I think this is the best way to determine if your issues are effectively due to the MS updates. Good luck

Let's be honest, the only reason why P3D has been able to sort of take over a lot of FSX simmers (that includes myself) is the fact that the vast majority of addons are almost fully cross compatible (unless some developer tricks in order to block this...). If X-Plane had only half of the FSX/P3D user base all the so called limitations/issues/shortcomings/etc... would almost magically get fixes/workarounds because only then would the profitability justify the research costs... that is the law of a developer's business model. FSX/P3D as an engine might be so old it hurts your eyes after 1 week of X-planing, as long as the user base is sitting on that side, that is where the developers will put their effort. Honestly I can't blame them for that... I installed the X-plane 11 demo about 2 months ago and after 2 days I bought the license as I was literally blown away by it. In the mean time a bought a couple of tubeliners (jardesign, flightfactor,IXEG) and the Xenviro weather engine. It takes only hours to realise how far ahead this sim is when compared to P3D, but again as I said in the first part of my post, that actually doesn't really matter from a developer's business point of view. Anyway, I am not investing any money in P3D (including the 747 v3) until at least the end of the X-plane 11 beta (still months out I guess) and probably not before there is more information about P3D V4. As I expect only a mere conversion to 64bit without any actual technological (graphical) innovation, I will probably fully switch to X-Plane 11 by then (even if that means losing access to addons by PMDG) just the opinion of a random customer. bye for now.

I had updated to 378.49 (24jan2017) and reverted back to 376.33 (14dec2016). After that my VAS leak was gone. Hope this info is useful to anyone.

I can confirm this issue. Last week I suddenly had the VAS leaking like hell (also with Aerosoft's A320 for instance) making a 3 hour flight the absolute maximum. Turned out I had indeed updated my nvidia drivers to the latest version (jan24th iirc). I just re-downloaded the previous one (somewhere december 2016) uninstalled the latest one followed by driver sweeper and made a clean install of the downloaded nvidia driver. It solved the leaking for me. YMMV

I did not read the entire thread (although I've been following it since last November), but I can say that not only approach procedures containing 'intercept radial XXX to FIX' do bring the VAS leak. Also SID's containing it will OOM after 10-11 hours flight after a long and steady VAS leak. As an example try KDFW-VHHH out of either 17C-17R-18L-18R via LOWGN7 SID (do not enter any arrival/approach procedure for VHHH). Same VAS leak will be observed. I had no problem not entering approach into FMC before T/D (that was the first workaround advised by PMDG), but not being able to use any SID containing that intercept radial to fix thingy is another problem far less ignorable than the first one. just my 2 cents, Happy flying!

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 :