Berike

The AS16 trial version, can I install it without uninstalling the ASN? I wanted to load the Sim in the same area and compare both before doing the purchase. Another thing, PMDG, Aerosoft and other manufactures are using ASN APIs to have the weather radar, anyone tested the radar with AS16?

Use Cinebench for single core benchmark, and check the performance of other CPUs. What mostly matter on P3D is single core performance.

To be honest, you're original Orange / Blue with the lion was much better, KLM should use your livery haha

My opinion, don't buy pre build computers, buy your own components and build your self. Just saved you some money and got a high end PC https://postimg.org/image/y30105yrr/ You can go with lower PSU (I put the 860W but you can use 600 for a single GPU) Wait a little bit for the custom PCB GTX 1080 releases. But you can see, I only choose high end components and got under 2k

Yes I know the 32bit has the limit of 4gb between vram and ram, my point is, ram usually is low on P3D, about 1gb at most, the bottleneck usually is vram, what about that miracle of managing the memory? I'll keep flying P3D, but my point is, I won't spend more money on this platform, I'm done. ONLY if I see a real miracle or 64bit platform on v4, apart from that, will keep the v3, because I feel I should keep using the v2, the problems still the same.

Before this flight I did LIRF LOWW, but then I closed the sim, opened it again to do the next flight.

When I got the OOM report, EVGA Precison X was showing 2.3Gb of vram usage, nothing else was open in my computer expect by ASN, PFPX, xacars, none of them request more vram than 12gb of my total. That's my point, something is very wrong sim to crash this way. I had crashes before but around 3.4 ~ 3.6 and using PMDG 777 and in heavy scenario areas. Approaching EDDF is very simple scenario.

What settings do you recommend using for FTX Vector?

I have secondary and tertiary roads disabled already

I'm sure it will. Crashing with 2.3Gb vram usage, imagine how low my settings already are haha, it's all set to medium, it's ridiculous, when you get to the point of having Top Tier hardware on CPU, Ram, M.2 SSD, GPU, PSU etc and the software crashes, 100% fault on software and not hardware. I'll stop paying for a next P3D v4 when it releases, I would even ask my money back of v3, honestly I have the same OOM problems that I had on v2

I just had a crash doing LOWW EDDF Using: Aerosoft A320 REX4 ASN Beta 6004 FTX openLC Europe FTX Vector FTX Global Aerosoft Mega Frankfurt V2 FlyTampa Vienna Ezok xacars FSUIPC IVAP Everything is updated and I'm using a GTX Titan X, so 12gb of vram, it's not an issue even for shadow of mordor running at 8k! My settings are set to 2048res on P3D and REX, density is set to dense (all of them). So it's very disappointing when you see representatives of LM P3D v3 saying they testes everything maxed out +150 add-on etc and you go to real usage and it crashes like FSX did. Sure, if you're loading just one airport isolated, pre tested and not an usual IVAO flight, in your VA. I'm using P3D since v2, and I'm always defending it for friends, but the real thing is.. P3D v3 is FSX with few tweak, I'll be only convinced when I don't start to see this OOM crashes. Sorry but I'm really ###### of with this OOM, loosing VA tracked flights, etc

third time I started P3D after the hotfix and it's asking to test the object flow

I also notice that the only overlay that works with P3D so far (Precision X) is not working anymore to check my vram usage. Did anyone notice it?

Damn I just patched my P3D V3 and had to update my FTX Central 2, rolled back as well... why we only see topics after doing an update? Should have a popup before every update "Check avsim forum if someone else had trouble with this update".

maybe it was a cache, got the update now, happy to have airport running back. I also noticed ORBX FTX Central v2 going back and having to Apply Group again

I downloaded the client, didn't see any change for my broken scenarios, I checked the build still 3.3.3.17556, what is the build number for the hotfix?

Upgraded

I'm with 3.2.2.16659 what is the build number of this one?

Titan X is overkill for most of games today, period. I bought it as an investment to don't change GPU for the next 2-3 years, and I was using a GTX 680 for the past 3 years and running everything smoothly. With $500 you can find very good second hand 980 or 980Ti (you will have at most 5fps less than Titan X) and some points it get even.

If you're on budget, the best cost x benefit is GTX 970 from MSI. It's a good GPU with 4Gb of Ram, and you'll be able to run most of the latest games with full specs (not in 4k res) and will be able to use DSR in some of them. I personally have a Titan X and it's totally overkill for P3D v3 or XP10 (I can run it maxed out and up to 60fps) Check this topic http://www.pcgamer.com/the-best-graphics-cards/

What scenery are you having problem? I have many from Aerosoft and they work perfectly with Windows 10

Hey guys, I'm VAFS user for a long time and if P3D crashed, I never had problem, because just to load from FSUIPC auto save and continue flying. Now I changed VA and they use XACARS, my nightmare is that if P3D v3 crashes (yes it's happening sometimes) and I load FSUIPC from it last save, XACARS don't keep tracking from there, it loose FSUIPC connection and I need to be on ground and engines stopped to be able to start it again. Any tips for it? Thanks!

One thing I would love to test (just to see what happens). Replace 747-8i engines with Quad GE90s

It's a font issue, QW had the same problem with Win10, just install the right font and everything will work fine

Thanks Jim! I was using P3D v3 with the default settings, right after I installed, no add-ons at all. Now I have ORBX, FSDT, PMDGs, ASN, REX, FSUIPC I believe there's an add-on saving my machine, I did the same test and no crash at all, then I turned everything to max, dropped my FPS around 25-40, but CPU temp about 60ºC, i7 3770k @ 4.7 with Corsair H110i GTX and GPU about same temp, with stock overclock (I don't overclock it myself). Conclusion, P3D v3 stock = crash driver P3D v3 + lot of add-on = heaven haha It's just weird, but it's what happened here.