UnitedExpress4180

That's odd. I have a similar problem only my fog is red(!). If I set visibility below a mile, it looks like I'm flying on Mars during a dust storm.

Am I the only one keeping my high expectations for this? I mean, in the past, most people got their expectations stomped on because Microsoft kept releasing a flawed product that was under-tested and poorly developed, but we should keep in mind that P3D is NOT a Microsoft product. It is by a government-contracted company which specializes in aviation and aerospace technology. Not to mention their target market isn't consumers, it's professionals, and that market is far less forgiving when it comes to software such as this. Remember, they are selling this for a lot of money to a lot of different people, all of whom expect it work and to work (very) well, so LM has to raise the bar, whereas Microsoft could release any old crap and be no worse off. LM has more invested in this, so I think this time it's safe to assume that they'll release a superior product. Maybe not in terms of graphics, which for us average Joe's is a shame, but this is supposed to be a training aid, not a game, so even if it doesn't look as nice, at least it'll be more reliable than MSFS was... ...But to cover my behind, I'll add that we'll have to wait and see.

I don't know about the rest of you, but I'm fed up with FSX. Not that I don't like it, it's just that it seems like no matter what I try, I just can NOT get it to run stable. Doesn't matter what plane I fly, what location, weather, addons, utilities, etc, it just loves to crash on me randomly, and only after I've gotten everything set up and ready to go, then it says, "you seem well-prepared for this flight. It would be a shame if something were to...stop working." And I've been dealing with this basically since I started simming almost 7 years ago. So the moment P3D v2 comes out, I'm jumping on it.

The 777 has been engineered to not work in P3D. As for the 747 and 767, as I neither own P3D (for now) or those two aircraft, all I know is that I've heard they work in the new sim. Whether they will for you comes down to trying it out for yourself.

Personally I just wear my headset over my hat when I use TrackIR. Gets the job done, and I can't say it's any less comfortable.

I don't have the iFly model, but I can tell you that PMDG's is lightyears ahead of theirs in terms of functionality and overall quality. I would stick with their model if I were you. As for switching to P3D, I have heard that with some modification it is possible to run the PMDG model in it. Not that I have tried it (or that I intend to), and I certainly don't advise it as it violates their EULA, but it is doable.

I would presume it's because they are not officially licensed by the manufacturers that their aircraft simulate, unlike PMDG, which has been working closely with both Boeing and airlines for years now. If their product was found to be at fault then that could also put Boeing in the hotseat for allowing PMDG to release a training aid that might not meet accuracy standards. It's too big a risk for both companies, whereas most other addon developers are not licensed or endorsed by their respective manufacturers, so there's a lot less red tape.

Unless LM adds a section in the EULA for home users (general consumers), then PMDG isn't likely to support P3D. Which is a shame, honestly, since it's, in my opinion, the next logical step from FSX once version 2 is finished. But since Lockheed is catering primarily to the commercial sector right now, PMDG probably isn't gonna jump on board due to the liability. If a plane were to crash and the NTSB found out the pilot had trained using a P3D-based simulator running a PMDG addon, guess who would be the first one on the chopping block? Yep, PMDG. So it's easy to see why they won't go for it. Not saying I agree with their choice, but the fact is they have to protect their best interests and this is the safest way to do it. But make no mistake, the mouse has to follow the cheese. PMDG is a business, and they're in the business of making money. They're smart guys over there, so you can bet that if the cheese turns out to be P3D, they may well reconsider. And if not, then that's unfortunate, but the community will go on whether they are exclusive to FSX/P3D, X-Plane, or some combination thereof.

What can I say? I'm a child of the '90's. My favorite liveries are now and forever will be relics of the past. :( *cough*United*cough*American*cough*

They aren't as bright as in DX9, but they are still overblown.

Theoretically it should work, as Windows 7 and 8 are pretty much the same in how they execute code. The only difference is how the system uses available resources. Oh, and also that stupid Metro UI.

The ENB series, sadly, doesn't work in DX10 because it is coded specifically for DX9 only. I wish it weren't the case though, it can still make the graphics look much nicer <_<

No dice. Tried reinstalling the fix and it's just the same as before: it pulls up the splash screen for about 10 seconds then does a faceplant. EDIT: Okay, this is unbelievable, but apparently the cause of the crashing was none other than the good 'ol ENB series mod. As soon as I removed it, the thing ran and just wouldn't stop for anything but the little red 'x' in the corner... Edit #2: Well after about two minutes of looking into this further, I have discovered that I've once again been foiled by the PPIT mod. Apparently the D3D9.dll version it uses doesn't play nice with the new shaders. After switching back to the original one that I was using...it's like there was never anything wrong.

Just saying, if you are using FSX with the Post Process Injection Tool, it can cause FSX to crash when loading in DirectX 10. I was having the same problem as you describe until I removed that mod, and then presto!

I have tried letting FSX rebuild the config from scratch, have scanned my computer for viruses and disabled my antivirus to no avail. And also, that was the only relevant dump log from FSX. I have many more of them, but the majority of them were caused by Airbus X. the rest of the crashes produced the same dump log as this one, line for line. I think I will also try removing the shader cache and let FSX rebuild that as well. Could that help? *Edit: tried flushing the shader cache...nope, didn't help :|

Okay, here's the dump log it came up with. Version=1 EventType=BEX EventTime=129946188167839783 ReportType=2 Consent=1 UploadTime=129946188168569825 ReportIdentifier=df5106c0-1551-11e2-b75e-8c89a5136e5a IntegratorReportIdentifier=df5106bf-1551-11e2-b75e-8c89a5136e5a WOW64=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61637.0 Sig[2].Name=Application Timestamp Sig[2].Value=46fadb14 Sig[3].Name=Fault Module Name Sig[3].Value=unknown Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=00000000 Sig[6].Name=Exception Offset Sig[6].Value=09a8f1c8 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.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 UI[2]=C:\FSX\fsx.exe UI[3]=A fatal error occurred. 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]=C:\FSX\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\system32\USERENV.dll LoadedModule[30]=C:\Windows\system32\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\iertutil.dll LoadedModule[37]=C:\Windows\syswow64\WININET.dll LoadedModule[38]=C:\Windows\syswow64\Normaliz.dll LoadedModule[39]=C:\Windows\system32\MPR.dll LoadedModule[40]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[41]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[42]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[43]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[44]=C:\Windows\system32\mscms.dll LoadedModule[45]=C:\Windows\system32\DDRAW.dll LoadedModule[46]=C:\Windows\system32\DCIMAN32.dll LoadedModule[47]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[48]=C:\Windows\syswow64\IMM32.dll LoadedModule[49]=C:\Windows\syswow64\MSCTF.dll LoadedModule[50]=C:\Windows\syswow64\WS2_32.dll LoadedModule[51]=C:\Windows\syswow64\NSI.dll LoadedModule[52]=C:\Windows\system32\msi.dll LoadedModule[53]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[54]=C:\FSX\language.dll LoadedModule[55]=C:\FSX\API.DLL LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[57]=C:\FSX\ablscpt.dll LoadedModule[58]=C:\FSX\flight.dll LoadedModule[59]=C:\FSX\ai_player.dll LoadedModule[60]=C:\FSX\acontain.dll LoadedModule[61]=C:\FSX\controls.dll LoadedModule[62]=C:\Windows\system32\DINPUT8.dll LoadedModule[63]=C:\FSX\fsui.dll LoadedModule[64]=C:\FSX\atc.dll LoadedModule[65]=C:\FSX\facilities.dll LoadedModule[66]=C:\FSX\demo.dll LoadedModule[67]=C:\FSX\main.dll LoadedModule[68]=C:\FSX\fe.dll LoadedModule[69]=C:\FSX\util.dll LoadedModule[70]=C:\FSX\simprop.dll LoadedModule[71]=C:\FSX\g2d.dll LoadedModule[72]=C:\Windows\system32\d3dx9_34.dll LoadedModule[73]=C:\Windows\system32\d3dx10_34.dll LoadedModule[74]=C:\FSX\d3d9.dll LoadedModule[75]=C:\Windows\system32\d3dx9_43.dll LoadedModule[76]=C:\FSX\g3d.dll LoadedModule[77]=C:\FSX\panels.dll LoadedModule[78]=C:\FSX\multiplayer.dll LoadedModule[79]=C:\FSX\ui.dll LoadedModule[80]=C:\FSX\sound.dll LoadedModule[81]=C:\FSX\sim1.dll LoadedModule[82]=C:\FSX\simscheduler.dll LoadedModule[83]=C:\FSX\visualfx.dll LoadedModule[84]=C:\FSX\window.dll LoadedModule[85]=C:\FSX\terrain.dll LoadedModule[86]=C:\FSX\weather.dll LoadedModule[87]=C:\Windows\system32\DSOUND.dll LoadedModule[88]=C:\Windows\system32\POWRPROF.dll LoadedModule[89]=C:\FSX\symmap.dll LoadedModule[90]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[91]=C:\Windows\system32\MSIMG32.dll LoadedModule[92]=C:\FSX\xuipc.dll LoadedModule[93]=C:\FSX\livingwater.dll LoadedModule[94]=C:\FSX\fs-traffic.dll LoadedModule[95]=C:\FSX\gps.dll LoadedModule[96]=C:\Windows\system32\MSWSOCK.dll LoadedModule[97]=C:\Windows\system32\SHFOLDER.dll LoadedModule[98]=C:\Windows\system32\d3d9.dll LoadedModule[99]=C:\Windows\system32\d3d8thk.dll LoadedModule[100]=C:\Windows\system32\CRYPTSP.dll LoadedModule[101]=C:\Windows\system32\rsaenh.dll LoadedModule[102]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[103]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[104]=C:\Windows\syswow64\MSASN1.dll LoadedModule[105]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[106]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[107]=C:\Windows\system32\wbemcomn.dll LoadedModule[108]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[109]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[110]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[111]=C:\Windows\system32\NTDSAPI.dll LoadedModule[112]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[113]=C:\Windows\system32\dxgi.dll LoadedModule[114]=C:\Windows\system32\nvd3dum.dll LoadedModule[115]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[116]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[117]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[118]=C:\Windows\system32\d3d10_1.dll LoadedModule[119]=C:\Windows\system32\d3d10_1core.dll LoadedModule[120]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[121]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[122]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[123]=C:\Windows\SysWOW64\d3d11.dll LoadedModule[124]=C:\Windows\system32\winbrand.dll LoadedModule[125]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[126]=C:\Windows\system32\WINSTA.dll LoadedModule[127]=C:\Windows\SysWOW64\gameux.dll LoadedModule[128]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[129]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[130]=C:\Windows\SysWOW64\wer.dll LoadedModule[131]=C:\Windows\System32\Wpc.dll LoadedModule[132]=C:\Windows\System32\wevtapi.dll LoadedModule[133]=C:\Windows\System32\msxml6.dll LoadedModule[134]=C:\Windows\system32\SAMLIB.dll LoadedModule[135]=C:\Windows\system32\netutils.dll LoadedModule[136]=C:\FSX\uiautomationcore.dll LoadedModule[137]=C:\Windows\system32\OLEACC.dll LoadedModule[138]=C:\Windows\System32\MMDevApi.dll LoadedModule[139]=C:\Windows\System32\PROPSYS.dll LoadedModule[140]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[141]=C:\Windows\system32\RICHED20.DLL LoadedModule[142]=C:\Windows\system32\HID.DLL LoadedModule[143]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[144]=C:\Windows\system32\wdmaud.drv LoadedModule[145]=C:\Windows\system32\ksuser.dll LoadedModule[146]=C:\Windows\system32\AVRT.dll LoadedModule[147]=C:\Windows\system32\msacm32.drv LoadedModule[148]=C:\Windows\system32\midimap.dll LoadedModule[149]=C:\Windows\system32\dinput.DLL LoadedModule[150]=C:\Windows\System32\wship6.dll LoadedModule[151]=C:\Windows\System32\wshtcpip.dll LoadedModule[152]=C:\Program Files (x86)\FlightSimTools.com\Addon Converter X\AddonConverterX.dll LoadedModule[153]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[154]=C:\FSX\bglmanx.dll LoadedModule[155]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[156]=C:\Windows\system32\inetmib1.dll LoadedModule[157]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[158]=C:\Windows\system32\WINNSI.DLL LoadedModule[159]=C:\Windows\system32\snmpapi.dll LoadedModule[160]=C:\FSX\Modules\GPSModule.dll LoadedModule[161]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[162]=C:\Windows\system32\MSVCR100.dll LoadedModule[163]=C:\FSX\Modules\FSUIPC4.dll LoadedModule[164]=C:\FSX\MD80.dll LoadedModule[165]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[166]=C:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll LoadedModule[167]=C:\FSX\Modules\A2A_Feel.dll LoadedModule[168]=C:\Windows\SysWow64\XAudio2_6.dll LoadedModule[169]=C:\FSX\Modules\AccuFeelMenu.dll Sec[0].Key=LCID Sec[0].Value=1033 State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=BEX AppName=Microsoft® Flight Simulator X AppPath=C:\FSX\fsx.exe

So I've really been enjoying the tweaks made to DX10 and now that it is finally in a more usable state, I haven't taken another look back at DX9! However, I wanted to compare the performance between the two a bit more precisely and decided to switch temporarily back to the old version, but to my surprise, discovered that FSX is apparently too in love with DX10 to go back! Every time I try to launch in DX9 mode, it pulls up the splash screen then within about 10 seconds, I get the dreaded fatal error. But when I switched it back to DX10 mode via the fsx.cfg, it worked just fine. No crashes, no errors, or anything. Rock solid. So I assume the problem lies somewhere with the DirectX10 tweaks. Prior to adding them, I never had this issue, but now it seems I am stuck on DX10. Not good considering the amount of old addons I'm running! So, any assistance would be greatly appreciated...

I don't know what this means for GFWL, but it certainly can't be looking too good to them right now. They spent the big bucks trying to get it out there, and considering it's been around for more than five years now and is already declining like no other, my guess is that the axe will soon fall on it. However I can't see how losing GFWL is a huge deal, since developers will probably continue to port games to PC anyway. Honestly I am much more worried about the future of the flight simulation genre at Microsoft. They've basically (what they considered to be) two failures in a row now: FSX, and Flight, though FSX didn't fail anywhere near as badly as Flight did. But nonetheless, they also sunk major mula into these games and got comparatively small returns on FSX, and pathetic returns on Flight (I'd be surprised if the made back anything close to what they invested in it), and after two flops in a row, will they still consider rebooting the original FS franchise? My opinion is that it isn't likely. Firstly, they don't get royalties from addons sold for Flight Simulator (any version...at least, as far as I know. Could be wrong), and even though for simulation titles FS has sold very well, as far as games overall go, if they had been part of any other genre, it probably wouldn't have been considered more than a mild success for the number of copies sold. Now that Microsoft has changed it's strategy to selling proprietary addons in their own marketplace, I seriously doubt they'd even think about going back to how things were when FS was still developed. That in mind, I think we may have to accept that Flight might have been MSFS's last chance, and with it cancelled, it's likely that we won't see another full-fledged, or even arcade-style flight simulator come out of Microsoft for years, if ever.

...Guess I need to buy another hard drive then :

Yep. I record the flight with FS Recorder, then play it back (with FS Recorder), and record with Fraps. Yet my FPS drops by at least half with it.

Actually, I'm already using FSRecorder, but I refuse to use the rendering feature because it's so much of a hassle to get the sound right when I edit in post production. And the FPS isn't stuttery, it just looks really low. It's crap.

I have a relatively beefy rig for FSX, and yet whenever I try to record with Fraps, my FPS goes down the tubes. For example - I tried recording a takeoff video from FlyTampa's KBUF with the CLS MD-80, and the best I was able to get was a mere 15 FPS. Is there something I'm not doing right or a way I can improve this? I see tons of YouTube videos by people with slower systems than mine that somehow have a much higher (and smoother) FPS in the recordings.My specs:I5 2500k @ 4.5 GhzNVidia GTX 465 (stock speeds...should I look into overclocking this thing?)4 GB ram7200 rpm drive (don't remember the brand)Windows 7 Home Premium (64-bit)FSX Settings: (see attachments)I have Fraps set to record full-res at 24 FPS.Help please?