Speedbird 217

I'm sorry but the first picture looks 100 times more realistic than the second, which reminds me more of somebody applying to many "instagram filters" to his pictures. Next time you're on a real aircraft - look out the window during dusk/dawn. It'll look a lot more than the first "HDR Off" picture.

I highly doubt that, unless you turn half your other sliders down to the minimum. Again, the stuttering is a result of you overloading your system. Your system is playing catch-up because you demand more from it than it can handle. I'm well aware of AIG and custom AI. As said before, your system TRIES to handle your massive volume of AI, hence why you see stutters. P3D is a Flight Sim, not a Traffic Sim. As others have mentioned, if you want to continue flying with 100% you have to seriously reduce your other settings and probably set autogen to off. You complain that your sim is not performing well but completely ignore anybody recommending to reduce your AI setting. Just for fun, try turning your AI slider to something lower, maybe 30% or 50%. And then try turning it off. I bet you won't see any stutters and you will probably double your framerate in the process. Your expectations and the reality don't match here, so until you accept that you will continue to see problems.

Your hardware simply can't keep up with everything you're throwing at it, made worse by the fact that FSX/P3D in general is very bad in handling AI traffic - it was never designed to handle large volumes of customised traffic. You can't expect everything to run smoothly if you overload your system, and I would not be surprised if the "17-22" FPS you're seeing comes at the expense of other issues such as blurry ground textures etc. - not even to mention all the VAS all that traffic consumes. Let's assume you are sitting on the runway in LHR with your "real-world" AI at 100%. It will load hundreds, if not thousands of AI aircraft in Heathrow, Gatwick, Stansted, Luton, City Aiport, Northolt, Southend and anything that's flying over. When you have default FSX/P3D AI you get a handful of aircraft parked somewhere, so expecting the sim to deal with thousands of them is simply not going to work. You can either accept the fact that 100% is overkill and get a smooth sim experience, or you can stick to it and keep having stutters and problems. I understand that AI is nice, I always loved it in my FS9 days and had it all set up nicely with customised and realistic traffic in all the airports. When I moved to P3D I tried using AI traffic in the beginning, but I have simply given up on it now and fly without it. The result is a wonderfully smooth experience with FPS rarely dropping below 30 even in a bad weather approach into LHR in the PMDG 777 with most sliders full right or 3/4 right. It's up to you, hang on to something that will cause guaranteed issues or compromise and enjoy the sim. If you want 100% realistic traffic, go to your local airport and do some spotting

Apologies for hijacking this thread; for those of us who use REX4TD with Soft Clouds - would it be possible to add an option to only consider Soft Clouds when randomly generating themes based on weather and disable all "non-soft" cloud textures?

Yes it does. I'm running at 50nm upper visibility and I get the good ol' skies I know from previous versions.

It's been posted by Damian in this thread http://www.hifisimtech.com/forums/showthread.php?5819-Hazy-Sky-with-Volumetric-Fog-enabled-in-Prepar3D-v3-2/page3 Fixed the haze/vol. fog issue for me - even for visibility settings <100nm.

Have a read here: https://scruffyduck.screenstepslive.com/s/help_docs/m/20268/l/199756-setting-taxi-link-draw-flags-to-default-values If you follow the steps it should fix the issue.

Sorry to reopen such an old topic. I tried flying LHR-PHL twice now and everytime I get to the point of entering the STAR (VCN8 on ILSZ17) with the latest SP for the 777 and 1601 AIRAC the FMC freezes, as well as the ND and other displays. I couldn't resolve this and 1 out of the 2 times I tried I even got an ntdll.dll CTD. So it seems this old problem is still existent.

Have you just copied over the core EDDM folder? I don't remember if that applies to Munich, but a lot of aerosoft sceneries put files in a folder called AFD. Check if you have this folder after installing and copy it to P3D, activating it in the library above the airport. I had Munich working fine in v2.5, haven't tested yet in v3.

Thanks for your detailed response Rob. I'm using an i7 4790k with HT off on 4 physical cores without any AM setting. Any ideas what to look for in the two files you mention? I did a quick check and the only custom entries I could find were from ORBX products and libraries.

Just to provide an update; I flew LHR-AUS today and the same thing happened over Canada - VAS going from 1.1 GB to 400 MB. This time I had OpenLC Canada turned off, so that doesn't seem to be the cause. Thanks to P3D I could still land without an issue as it released VAS as I was approaching the airport, however Canada still uses 700 MB of VAS. The only other addon that is active and affects Canada would be Vector. As said before, I only use highways and main roads and not many other features plus the fact it's working fine in other regions. No idea what is causing this, it seems to be some sort of memory leak in the area.

Just check the METAR to manually set it or press B to automatically set it to the correct value?

Brilliant, thanks a lot!

You can only capture G/S after LOC has already been captured. Also, you need to capture the G/S "from below", so it won't engage if you try to catch the glideslope from 4,000 feet when you should be at 2,000 at that point. In other words, the purple diamond needs to pass through the yellow bar for it to engage, and that only works after LOC has already been captured.

Are you checking your PICTURES/Prepar3D v3 Files or your DOCUMENTS/Prepar3D v3 Files?

Anybody else notice colour-banding with "Output Dynamic Range" set to full at night? My clouds and other dark areas look like 8-bit at night when turning this on. During the day and in brighter areas everything looks fine. When I turn the feature off all looks normal without colour-banding. No matter if HDR is turned on or off, it doesn't make a difference. I have to significantly reduce brightness on my screen when using this feature and flying at night to hide the colour-banding...

Problem still persists. Just installed 1.31 of the A320/321, rebooted and it messed up my EDGE and Steam fonts. Old workaround still does the job http://www.avsim.com/topic/473640-problem-with-win-10-fonts-aerosoft-airbus/ Delete original file and reinstall with the corrected one...

It sounds very much like an issue I had - with a strong orange-yellowish bright light all across the ground area. Renaming that file fixed it for me, so just give it a go and report back.

If you're flying with HDR on you need to disable a file called "Lichtlayer.bgl" in the scenery folder of EGLL.

Hi, I just did a LHR-SAN and SAN-LHR over the weekend. Enjoying P3Dv3's new VAS management I had between 1.1 to 1.2 GB free after take off on either flight in the PMDG 777 on Rob's recommended settings. After take-off from LHR I had 1.2 GB free until reaching Canada, at which point it suddenly dropped to 800 MB and further decreased down to 500 MB at its minimum. I could still land in SAN without OOM and about 400 MB remaining thanks to the improved VAS management, but it seems very strange that Canada just "swallowed" 700 MB of VAS that would not be released back. Today I did the return flight and again, just as I approached the Canadian border VAS dropped from 1.1 GB free to 800 MB, decreasing to a minimum of 400 MB left while over Canada. As I flew out over the Atlantic it increased back to 700 MB remaining and I could land in LHR with 400 MB remaining. Does anybody have any idea what is causing this? It's not exactly a demanding region, there's not much there in Northern Canada that would result in such a VAS drop, especially considering that in LHR I have 1.2 GB free. It almost seems like there is a memory leak in the region somewhere, my current main suspect is OpenLC Canada. Please see below for the flight path on the way back with the "VAS Black Hole" highlighted in red. Addons used: -AS EGLL -LVFR KSAN -PMDG 777-300ER -ASN Live Weather -REX Texture Direct + Soft Clouds -Pro-ATC X -FTX Global -FSGlobal 2010 -OpenLC Europe -OpenLC Canada & Alaska (I somehow suspect this to be the culprit, even though I don't experience any issues with OpenLC Europe) -FTX Vector with only highways and main roads turned on - not causing any issues in Europe or USA

I just installed it last night and have a similar config to David - only highways and primary roads on, nothing else ticked, no railroads, streams or power lines. Just did a quick test in my stress-test scenario (depart AS LHR with PMDG777, do a circle over Central London and return for a landing at LHR) and I couldn't observe any significant FPS or VAS hit. This was in pretty nasty weather as well with overcast cloud coverage and rain. I guess it's all down to your system and setup but for me it works fine from what I could see so far. I mainly fly high & heavy so I only need Vector for coast lines, elevation correction and better main roads.

I get the same error since about one week using Firefox. No matter what time or file I try to download. I didn't get this error once in 10 years and now I get it every time - I agree with the others and suspect a bug in the library system. Tried as well with EDGE and get a "Hmm, we can’t reach this page." error.

If you have Active Sky Next, try reinstalling it. I had a Kernelbase error the other day and it was caused by ASN. Reinstalling it fixed the issue.

Unfortunately I haven't been able to find a solution so far. This seems to be a common issue...Barcelona works fine for me, just Madrid causing problems with shifting buildings.

No problems with HF11 so far. The CTDs from HF10 seem to be fixed, thanks.