Taver

I have just returned to flight simming after a long break. This suggestion is great except for one problem I have encountered. If you use a second monitor and undock and drag items (such as your GPS) to the second monitor you will half your frame rates. For me I use unlimited frame rates in Prepar3d and no frame rate limiter. I get stutters from time to time but I can deal with that more than a 50% frame rate drop.

I use ASN. (Active Sky Next) It has a map that shows your current position and route if you create a flight plan. The ASN command center as it is called has no effect on frame rates.

I have an eyefinity + 1 setup running 5760x1080 with the + 1 running 1980x1080 all on a R9 290. I tried a second card to improve performance for the 4th monitor and it did not help. I have learned that the 4th monitor for gauges is not a graphics problem but a CPU problem. I have an i7-4770k at 4.4 and still see a big hit when I turn on my gps and move to the 4th monitor.

Here are my specs. Intel 4770k 4.4ghz 16gb RAM AMD R9 290 5760x1080 Windows 8.1 ASN (5 layers) REX 4 I have been testing lately as I too have had a FPS drop in heavy clouds. I can confirm with my rig that it is the maxing out of the graphics card that causes the FPS drop. When in heavy clouds or thunderstorms my FPS can drop as low as 11fps at 5760x1080. But to alleviate this problem if I am on approach I minimize the screen to 1980x1080 (1 monitor) and my FPS goes up to around 25-30 FPS. The graphics card is maxed out at 100% GPU. On a side note I have found the two things that hit the CPU the most and GPU the most for my rig. Heavy clouds hit the GPU the hardest and LOD hits the CPU the hardest. So in large cities I lower my LOD to achieve the frame rates I need to take off or on approach. Once I am away from the city I boost the LOD to max. I have no FPS problems away from major cities unless there are heavy clouds or thunderstorms.

I have an AMD R9 290 running 5760x1080. I too had problems in clouds until I figured out a few settings. I have max clouds and max could distance. Shadows on low and set to 40,000. FXAA is ON MSAA is None Texture Filtering is Trilinear. (this is the setting that made the biggest difference.) Texture Resolution is Ultra 4096x4096 HDR is on Flare is on I have REX4 Texture Direct installed with all clouds set to 2048x2048. Now I get on average 22FPS flying through the clouds in ORBX Weather 1 theme. (Thunderstorms)

I am running 5720x1080 with an AMD R9 290 and I have seen 3.4gb. This was over Seattle at night with REX, FTX Global, 50% road traffic, extremely dense, and max distance clouds. I was in the Carenado 337 Skymaster holding steady at 22 fps. I did have plane traffic at 50% but there was not many planes for some reason. I am afraid when My Traffic X Pro gets updated for Prepar3d V2 and I get it installed I may have to dial back some settings. I will say though if you have FTX Global and can crank the road traffic up to around 50% at night it is spectacular. I was stunned at how good it looked with all the headlights on the highways.

Simple question. I have FSGenisis mesh. Which folder do I need to point the installer or is the default ok?

More than likely your carburetors froze up. Make sure you turn on your carb heat.

I may get this program and try it out. I need to do some more research since it seems to launch fsx. I am an avid Air Hauler user and Air Hauler must be the program to launch fsx.

What has been said is correct about the default ATC but let me clarify. When you make and IFR flight plan you will set a maximum altitude when you make the plan. When the ATC gives you the direction to ascend to that maximum altitude that is your cue that all you need to do is acknowledge the next ATC call to change frequency but don't contact the ATC for the next frequency. As you move through the ATC zones you will see the "contact ATC in your ATC menu switch through the ATC zones as you fly through them. Do not start your descent until you contact ATC near your destination airport. Make sure you don't wait too late to contact ATC or your descent will be too steep. Hope they helps. I find doing this works really well on long flights. I have left my PC running all night and picked it up in the morning in a 10hour flight with no problems.

Just make sure you have a full version of FSUIPC and be prepared to use that as your sole source to configure your controls.

I installed the vista patch and still the same problem. Pro Flight 2000 launches fine. Here is the crash log if anyone has any idea. Version=1 EventType=BEX EventTime=130205743154386809 ReportType=2 Consent=1 UploadTime=130205743154699327 ReportIdentifier=3a169e9c-0162-11e3-bf0e-94de806b67f2 IntegratorReportIdentifier=3a169e9b-0162-11e3-bf0e-94de806b67f2 WOW64=1 NsAppName=PF_Emulator.exe Response.BucketId=f96b2d7efdd51fa5036bd38f897c30c4 Response.BucketTable=5 Response.LegacyBucketId=1254330896 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=PF_Emulator.exe Sig[1].Name=Application Version Sig[1].Value=2.14.0.0 Sig[2].Name=Application Timestamp Sig[2].Value=4bc39465 Sig[3].Name=Fault Module Name Sig[3].Value=PF_Emulator.exe Sig[4].Name=Fault Module Version Sig[4].Value=2.14.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=4bc39465 Sig[6].Name=Exception Offset Sig[6].Value=002bb001 Sig[7].Name=Exception Code Sig[7].Value=c0000005 Sig[8].Name=Exception Data Sig[8].Value=00000008 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.2.9200.2.0.0.256.103 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=5861 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=5861822e1919d7c014bbb064c64908b2 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=f3d5 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=f3d5be0cad2787556264647dc02181c3 UI[2]=E:\Aerosoft\PFE\PF_Emulator.exe UI[3]=ATC added on for FS9 or FSX has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=E:\Aerosoft\PFE\PF_Emulator.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll LoadedModule[4]=C:\Windows\system32\apphelp.dll LoadedModule[5]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[6]=C:\Windows\SYSTEM32\msvcrt.dll LoadedModule[7]=C:\Windows\SYSTEM32\USER32.dll LoadedModule[8]=C:\Windows\SYSTEM32\GDI32.dll LoadedModule[9]=C:\Windows\SYSTEM32\SHELL32.dll LoadedModule[10]=C:\Windows\SYSTEM32\SHLWAPI.dll LoadedModule[11]=C:\Windows\SYSTEM32\OLEAUT32.dll LoadedModule[12]=C:\Windows\SYSTEM32\MPR.dll LoadedModule[13]=C:\Windows\SYSTEM32\SETUPAPI.dll LoadedModule[14]=C:\Windows\SYSTEM32\sfc.dll LoadedModule[15]=C:\Windows\SYSTEM32\WINSPOOL.DRV LoadedModule[16]=C:\Windows\SYSTEM32\RPCRT4.dll LoadedModule[17]=C:\Windows\SYSTEM32\combase.dll LoadedModule[18]=C:\Windows\SYSTEM32\CFGMGR32.dll LoadedModule[19]=C:\Windows\SYSTEM32\DEVOBJ.dll LoadedModule[20]=C:\Windows\SYSTEM32\SspiCli.dll LoadedModule[21]=C:\Windows\SYSTEM32\sfc_os.DLL LoadedModule[22]=C:\Windows\SYSTEM32\CRYPTBASE.dll LoadedModule[23]=C:\Windows\SYSTEM32\sechost.dll LoadedModule[24]=C:\Windows\SYSTEM32\bcryptPrimitives.dll LoadedModule[25]=C:\Windows\SYSTEM32\SortWindows6Compat.dll LoadedModule[26]=C:\Windows\system32\IMM32.DLL LoadedModule[27]=C:\Windows\SYSTEM32\MSCTF.dll LoadedModule[28]=C:\Windows\SYSTEM32\msvbvm60.dll LoadedModule[29]=C:\Windows\SYSTEM32\ADVAPI32.dll LoadedModule[30]=C:\Windows\SYSTEM32\ole32.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=BEX AppName=ATC added on for FS9 or FSX AppPath=E:\Aerosoft\PFE\PF_Emulator.exe NsPartner=windows NsGroup=windows8

After you buy some mesh it should then show up in your download library. You should not have to add it to your cart to get it. Atleast that is the way it was a year ago when I bought my mesh.

Has anyone had any luck installing PFE on windows 8? The program installs but when I go to launch PFE it acts like it does nothing but appviewer shows an immediate crash. I have tried all of the different operating system modes and no luck. I am usually good at figuring these things out but this time I am stuck.

If you are using FSUIPC make sure your controllers are turned off in fsx itself. I am using windows 8 and I have to use FSUIPC exclusively. But sometimes when I startup FSX the controllers option will be turned on and I always know this because no matter what aircraft I have loaded the flaps go to full including the CS727. Hope that helps.