mfastx

FSX snow effects are probably one of the most unrealistic things about the game. It's quite strange to approach the airport in a blizzard and seeing all of the taxiways and tarmacs in perfect clear condition. Also, there is no snow on the roofs of autogen and other buildings.

I like how they are splitting up the services, so if you just want textures, you can get just textures. Same for the weather.

Haha, I thought you mean that AI traffic was "listing" meaning they were flying off to the side.

ENB and FXAA work great, until I fly with the NGX. Guaranteed crash everytime. If someone is using one of these with the NGX, I'd really appreciate an explanation of how you got these two addons to work together. TIA

I'm thinking about trying to set the nVidia vertical sync setting to "refresh rate" and locking 60 fps in FSX. Or when flying around big cities set the FSX fps to unlimited and keeping the "refresh rate" or "1/2 refresh rate" in nVidia. Has anyone tried this?

Any pics of this you'd like to share?? Seems pretty cool.

Thanks a bunch, will do!

To the OP, I have two questions. First, I am assuming you are using REX textures for clouds? They look fantastic. Secondly, what are your nVidia Inspector settings? Your graphics are so amazing even along the horizon, no blurries at all. Great shots BTW.

Thanks for the response! I'll check out the manual for more info.

I have a couple of questions about this before I buy it. First, is there a manual somewhere I can download and check that out? Second, I realize that this is not a landclass addon, but are scenery glitches like the Thames in London (rocky mess) and other scenery errors fixed with this? If not, is there something that fixes those glitches? Lastly, does FTX Global update city limits? For example, many cities have grown outward since FSX was released, does FTX extend "city" textures further out than default FSX to reflect this? Thanks a lot to anyone who answers these questions!

I am from Houston and it is certainly lush and green here. Other parts of the state, not so much.

That's really strange, is that specific to the KLGA ImagineSim addon?

I think you need to turn your "mesh resolution" to a higher setting.

I fly the PMDG all the time and it doesn't make a difference whether I use FXAA or ENB, I get loads of crashes every time. It really is a shame, because I had this one absolutely perfect FXAA setup and ENB 24hr was basically perfect as well. Sigh... I wish there was a way to apply these effects in video editing, since I make vids for YouTube I wonder if there's a way to add this effect in Sony Vegas or something.

Yeah I've been trying forever to use that FXAA tool in FSX (results are absolutely spectacular) but unfortunately that and the PMDG 737 aren't the best of friends lol. Crashes every time I fly with it, usually when I'm piddling around the menus, such as recording with FSRecorder, or going from full screen to windowed mode. Without it I get no crashes.

Dear God that's awful, lol. Default planes have more detail than that.

For those having those random crashes with 310.70, is the issue fixed with 310.90? I guess I'll just see for myself.

Yes!! This is exactly what happens on my system. I haven't been able to find many other users with the same issue. For now I am just not using the 310 series drivers.

Just happened again. That little bugger is killing me. Happens about once every 20 times. This usually happens when I click "fly now" and right when I reach 100% loading, I get the CTD. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: nvd3dum.dll, version: 9.18.13.1070, time stamp: 0x50b976f2 Exception code: 0xc0000005 Fault offset: 0x0065938a Faulting process id: 0x1180 Faulting application start time: 0x01cde736884bf3c8 Faulting application path: F:\FSX\fsx.exe Faulting module path: C:\Windows\system32\nvd3dum.dll Report Id: f3fbe710-5329-11e2-8e4f-10bf4885b864 I have concluded that it is the latest 310.70 driver, this crash never happened on the 306.xx drivers. I can't seem to figure out how to make ther current driver work correctly, theoretically the newer drivers shouldn't make any difference in FSX.

Unfortunately I experienced another crash. They happen very rarely, but occasionally they do happen. This is basically off of a clean FSX install, with Bojote's Shader 3.0 Mod installed. The crash has only happened once since I updated to the latest driver and removed the ENB "d3d9.dll" file (and all other ENB files). I experience this crash only when I click on a menu in-game and reload the sim from a changed setting (for example, I'll change from "day" to "night" and when the sim finishes reloading, it'll crash. Or, when I click on a menu item, it will mysteriously crash.) This is the message I'm getting: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: nvd3dum.dll, version: 9.18.13.1070, time stamp: 0x50b976f2 Exception code: 0xc0000005 Fault offset: 0x0065938a Faulting process id: 0x548 Faulting application start time: 0x01cde6f0d4f06b2c Faulting application path: F:\FSX\fsx.exe Faulting module path: C:\Windows\system32\nvd3dum.dll Report Id: 4792e3bb-52e4-11e2-9923-10bf4885b864 I am on a modest overclock, do you think that could be it? What does this exception code usually mean? (BTW, my CPU is overclocked but my graphics card is not.)

Thanks for the response Jim. I did what you suggested and actually installed the 307.97 driver and since have been unable to recreate the crash. I tried to get it to crash by doing all of the usual triggers but was unsuccessful. So for now I'm hoping the issue has been solved. I will report back if I experience any other issues. Thanks again.

After a new install of FSX on Windows 7 x64, FSX is randomly crashing when clicking on in-game menus. Note: this is not the UIAutomationcore.dll problem, FSX is not crashing because of clicking the menu bar, it crashes if I, say, change the weather theme and click "ok," FSX will load and when it's at 100%, it will crash. Also, I am occasionally getting crashes when clicking "end flight" but I believe that is due to the ENB series that's installed, as it references "d3d9.dll" and NOT "nvd3dum.dll." I believe that "nvd.3dum.dll" is a nVidia problem but I have the lastest driver for my 660 Ti. Should I try and use an earlier driver? Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: nvd3dum.dll, version: 9.18.13.1070, time stamp: 0x50b976f2 Exception code: 0xc0000005

Have you tried this guy's 24 hour ENB config?

I've sone dome 4-5 hour flights. Always uncheck "pause on task switch" in the general options tab. Then I just piddle around on the computer, visit some forums etc. But in case ATC contacts me I have it so that I can see when an ATC message pops up.

A few years ago, when I was just starting out with more advanced planes, for some absurd reason I spent about $25 on "SEA Checklist X." Still have no idea what I was thinking.