Westcoastpilot

I do not have any mesh installed. Still haven't been able to find a solution to this.

Sorry, I meant ASP4.

Ok. Thanks. My GPU averages about 50-70% load at busy airports, QW787, moderate settings, which yields 20-25FPS. However if I turn antialias settings to 4xSSAA, that brings the load up to 99% and FPS drops ridiculously.

That's what I figured. I usually find that my GPU is working harder than my CPU, often using very close to 6GB of VRAM. However if I'm not going to see any sort of improvement in fluidity with a 2060, then I'm not going to bother upgrading until I can afford a 2070 or 2080.

I'm also using ORBX Vector, LC and Global with ASP4. Did a couple of tests recently, messed around with the LOD but I haven't been able to find a fix. Perhaps this problem is related to ASN as someone mentioned above?

Ok thanks. I guess my question now is, should I go for the GTX1070 with the extra 2GB of VRAM, or the RTX2060 with the same amount of VRAM as I currently have? Unfortunately the RTX2070 is over my budget. I'm just wondering how important the extra VRAM would be considering I usually fly with ORBX & PMDG products.

I'm currently running P3D v4.4 with a GTX1060 6GB and a Ryzen 5 2600 @ 3.4GHz, 16GB DDR4 and SSD. I have a fairly limited budget, and my question is if I would see the biggest FPS increase by upgrading the CPU to a Ryzen 7 2700X, or by upgrading the GPU to a 1070 8GB or RTX2060 6GB. I know these are fairly specific questions but any help would be appreciated.

I recently completed a flight that took me a few miles from the north pole and something odd was happening with the scenery. I've done a bit of research on this but I haven't been able to find a fix. Any ideas?

Recently purchased the qualitywings 787. Great bird, however I'm unable to get the MCP text and glareshield to illuminate. Tried spinning the glareshield knobs with the master light button on, no luck. All the other cockpit lights work fine. Any ideas? I'm using v1.1.2a, and P3Dv4.2. Thanks

Flattening the afcad in ADE fixed it. There are still a few flickering textures on the ground around the terminal, but I'll live with them.

Alright I'll give that a try. Thanks.

I guess I should've mentioned that this an FSX scenery, but I've been converting all the BGL's so they work with P3Dv2. I've converted FSX sceneries before without the problem I'm having. I thought this might've been an issue caused by vector, but it isn't. Maybe there are some BGL's that I missed?

Just downloaded and installed a new freeware scenery and I'm having some issues with the airport textures. When looking at the airport from a top-down view at a fairly close distance, as well as from the ground, there are certain taxiways and apron markings missing, and the runways also change. However, when I zoom out by two notches in the top-down view, everything appears as it should. Any ideas?

Hello Everyone, I know there have been many threads on this, but I haven't been able to find a solution to this problem. I'll be flying along with a good framerate of about 40FPS, yet I'm getting stutters. It's like tiny pauses in the simulation, and I haven't been able to get rid of them. I've tried messing around with the graphics settings in the simulator, locking FPS, but none of the combinations of settings I've tried have gotten rid of the stutters. I'm wondering if there are any tweaks I can do with the .cfg file that would help with this problem? I'm running out of ideas, any would be appreciated. Thanks System specs: Intel i7-2600 @ 3.4GHz, 8GB DDR3 RAM, 2TB HDD, 120GB SSD, Gigabyte Radeon HD7870 2GB

I've been trying to install the Mindstar GNS530 in the Realair Duke V2 Piston for some time now, and I can't seem to figure it out. I've gotten close, but now I'm having other problems with clickspots, and fitting the gauge into the panel. The 2D popup works perfectly. This is what the instrument looks like so far: I've been editing the panel.cfg file to make the Mindstar 530 fit into the bezel, but I can't move it any more to the left, which is where I need it to go. Also, none of the buttons on the bezel are working. Is this a product of the instrument not being fitted properly? I was hoping someone who had the 530 installed into their Duke could share their panel.cfg file with me. Here's mine: [Window Titles] Window00=Main Panel Window01=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE Window02=Blank [Window00] file=2D_Help.bmp size_mm=1024, 95 position=6 BACKGROUND_COLOR=0,0,0 visible=1 ident=MAIN_PANEL [VCockpit01] size_mm=1024,1024 pixel_size=1024,1024 texture=$RAS_Duke_CFG background_color=1,1,1 gauge01=Config!Options, 1020, 1023, 1, 1 gauge02=Config!RealView, 1021, 1023, 1, 1 gauge03=RASDuke!InitVars, 1022, 1023, 1, 1 gauge04=RASDuke!1hzCode, 1023, 1023, 1, 1 gauge05=RASDuke!2hzCode, 1024, 1023, 1, 1 gauge06=RASDuke!18hzCode, 1025, 1023, 1, 1 gauge07=Config!AdfDip, 1026, 1023, 1, 1 gauge08=RASDuke!NavCom1, 1, 2, 509, 61 gauge09=RASDuke!NavCom2, 1, 64, 509, 61 gauge10=RASDuke!ADF, 4, 127, 332, 49 gauge11=RASDuke!Xpndr, 7, 243, 305, 57 gauge12=RASDuke!Autopilot, 5, 177, 292, 62 gauge13=RASDuke!DME, 4, 305, 256, 46 gauge14=RASDuke!Annunciator, 886,131,137,262 gauge15=RASDuke!KA285_Annun, 512,2,337,108 // =============================================================================== // IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' BELOW CAN BE OVERWRITTEN // BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE // IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY // CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22' // =============================================================================== ;gauge19=rxpGNS!GNS530, 1, 660, 504, 364 gauge19=MPI_GNS!GNS530, 1, 618, 504, 394, 1:1:-1 gauge20=RASDuke!Blank, 0, 0, 1, 1 gauge21=RASDuke_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke B60 V2/Panel/Sound/RASDuke_Sound.ini gauge22=RASDuke!Sound_Manager, 1,1,3,3 gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1 Day=255,255,255 Night=225,117,89 Luminous=200,200,101 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=6144 [Window01] Background_color=0,0,0 size_mm=937,910 window_size_ratio=1.000 position=7 visible=0 ident=11013 window_size= 0.340, 0.580 window_pos= 0.660, 0.420 zorder=99 ;gauge00=rxpGNS!GNS530,0,0,100,100 gauge00=MPI_GNS!GNS530,0,0,800,581,1:2:11013 [Window02] size_mm=1,1 position=0 visible=0 ident=15600 BACKGROUND_COLOR=0,0,0 gauge00=RASDuke!Blank, 0, 0, 1, 1