DVA7209

Well I knew that much. :PI'm just going to assume the dual battery option is only available on line numbers without the ISFD.

Nice!!!In my shopping cart then. Thanks guys.

Hey ironmaiden, my specs are on the first post of the thread.JJM, no that's not FSX 100% default. I like to install all of my "needs" first, before doing performance testing...which includes: Real Environment Xtreme with 2048 res 3D clouds, 1024 res cirrus clouds, water effects on high 1.x. FS Global 2010 And some other, non performance impacting things like AutoStar X (increases night sky realism), Lumberjack (clears trees before runways...useful for small airports), grass textures from Real Environment Xtreme's website, and ENB series light bloom mod. My FSX settings are:Anti aliasing off (forced through Nvidia Inspector to 4xS).Filtering - Trilinear.Global textures - Very high.No lens flare or light bloom...advanced animations on.//Aircraft global setting - Medium high.//LOD Radius - LargeMesh complexity - 70Mesh resolution - 10 (FS Global requirement)Texture resolution - 1 mWater effects - High 1.XLand detail textures - onScenery complexity - Very denseAutogen density - NormalGround scenery shadows - offSpecial effects - high//Weather - ultra high//Traffic - (Airline/GA: off for now. I'll probably just be flying on VATSIM anyway. Might add a little some day). Airport vehicle density - minimum. Road vehicles - 5%, all others 0%.I did not manually edit my FSX.cfg file. I let Bojote's FSX tweaking site do the work for me...highly recommended. That's what boosted me up nearly 30 FPS from the default fsx.cfg.http://www.venetubo.com/fsx.htmlBy optimizations, I meant using the tweaked fsx.cfg file. I can't attach it to this post because it tells me I'm not permitted, but basically all I did was used that website's auto tweaks, customized for my own hardware. If anyone really needs it, I think these are all of the tweaks it made:[bufferPools]RejectThreshold=131072[Graphics]ALLOW_SHADER_30=1HIGHMEMFIX=1[JOBSCHEDULER]AffinityMask=14[Terrain]SWAP_WAIT_TIMEOUT=2[scenery]SmallPartRejectRadius=4.0When I'm up actually flying and seeing the the planet from thousands of feet in the air, I may decide to increase the LOD radius in the cfg file a little depending on the level of blurries. For now I'm going to leave it alone.Edit - BTW...the flight is the default 737, Boeing house colors, fair weather, in the day time preset, in Seattle on 34R (active runway)...if anyone wants to compare how they're running to what I was getting.

Hey guys...first of all let me start off by saying I'm not an FS2Crew NGX customer (yet) but I've used FS2Crew Voice Edition for the Maddog...and it blew me away.In fact, it blew me away so much, that I now refuse to fly without FS2Crew. Needless to say, being an NGX customer, I'm going to be purchasing FS2Crew for the NGX, but I have a few technical questions about it before purchase that the product page doesn't seem to be able to answer.How does FS2Crew handle alternate equipment configurations? For example...a Honeywell MCP versus a Collins MCP?A user-made flow chart on AVSIM mentions arming LNAV and VNAV before takeoff as part of FS2Crew's flow...however if my memory serves me right, that is only possible on a Collins MCP.Is FS2Crew compatible with a Honeywell MCP/Analog Standby ADI?

Hello Captains...I have a question regarding the 737-800's battery...specifically Delta's.I'm setting up the NGX, and I'm wondering if the majority of Delta's 737-800s have dual or single battery packages.I thought the dual battery package was implemented on aircraft fitted with an ISFD. At this current time, only 2 Delta 737s have an ISFD. That'd suggest the majority have a single battery package installed. However Ryan Schmidt of Delta VA seems to have a different opinion.http://www.deltava.org/thread.do?id=0x192b3So what do you guys think?

Lastly, I did my FSX.CFG tweaks, and things are actually pretty smooth. I feel kind of bad for fixing my own problem and just taking up space here. I don't really know what I did differently this time around. I swear some things just boil down to pure luck sometimes.About 100 FPS after all optimizations.NGX drops me down to about 40 FPS. 60 FPS drop. That's so harsh. But so worth it... lol

Hey Word Not Allowed, from what I know the IME driver is a BIOS extension driver.Without it, the PCI Simple Communications Controller won't be read properly in the device manager...and Windows Update will install a generic version of the driver.It's not a driver that's necessary on all chipsets though.

Hey guys, I redid a lot of things. Even my entire OS. Reinstalled everything....and I've really gotten somewhere this time.That's 75.4 FPS looking north in Seattle *BEFORE* all tweaks and optimizations.Now I know it's not in stormy weather, so it's not really a controlled test. But the picture taken on the first page of the thread was in south Seattle, looking towards the south. For anyone who's unaware of the area, looking north in Seattle is harder on a system than looking south, because you're looking at several complex airports (KSEA and KBFI) as well as downtown Seattle itself with tons of building autogen, 2 stadiums, and many tall buildings.I'm hoping to be able to get close to 80 FPS after doing a defrag and tweaking my FSX.CFG a bit. That is going to be *way* better than 34 FPS when switching over to the NGX.I'll post a final shot after all tweaks are done. Hopefully I'm able to get up there at 80. I think it just all comes down to luck haha.Also I installed a different version of Intel's Management Engine, messed with Nvidia Inspector a bit, and my PC is just all around cleaner..and seems to be healthier.

In a default 172? Mate...imagine trying to fly in a payware PMDG aircraft. That'd be in the teens. That's horrible on a Sandy Bridge system at 4.70 GHz! :(

I used Diskeeper, because I have it purchased and don't want to throw it away now...I believe it uses roughly the same defragmentation method as O&O...and that shouldn't really be making too much of a difference except for loading times AFAIK. I didn't skip anything, I just replaced the defragging tool. I even followed the Windows 7 optimization guide, by optimizing the prefetch service, and performance counters. Also..Nick's video is not edited. It's uncut. :)The changes I made to FSX.CFG (other than Bojote's) were adding a Poolsize=50000 line. It helps remove black lines that flash around on the screen and helps dramatically with stuttering for me.Also I increased the LOD Radius a little to help with blurries.Also, I did OC my GPU. Default core clock is 720. As I said I have mine at 800. ^_^ I'll post it...but do you guys really think some FSX.CFG tweaks would help that much? I expect to be seeing frame rates of 50 at least. NGX should knock off about 20, and get me running at around 30 FPS I believe. I'm also looking to upgrade to a GTX 580 after I get paid, which I'm hoping to squeeze an extra 10 FPS out of.[bufferPools]RejectThreshold=131072Poolsize=500000...[GRAPHICS]AC_SELF_SHADOW=1AIRCRAFT_REFLECTIONS=1AIRCRAFT_SHADOWS=0ALLOW_SHADER_30=1COCKPIT_HIGH_LOD=1D3D10=0EFFECTS_QUALITY=2GROUND_SHADOWS=0HIGHMEMFIX=1IMAGE_QUALITY=0LANDING_LIGHTS=1NUM_LIGHTS=8See_Self=1TEXTURE_MAX_LOAD=4096TEXTURE_QUALITY=3Text_Scroll=1SHADER_CACHE_PRIMED_10=1693500672SHADER_CACHE_PRIMED=1693500672[TrafficManager]AIRPORT_SCENERY_DENSITY=1AirlineDensity=14FreewayDensity=0GADensity=8IFROnly=0LeisureBoatsDensity=0ShipsAndFerriesDensity=0...[JOBSCHEDULER]AffinityMask=14...[TERRAIN]AUTOGEN_DENSITY=3DETAIL_TEXTURE=1LOD_RADIUS=5.500000MESH_COMPLEXITY=75MESH_RESOLUTION=22SWAP_WAIT_TIMEOUT=2TEXTURE_RESOLUTION=25WATER_EFFECTS=3[sCENERY]DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=4LENSFLARE=0MAX_ASYNC_BATCHING_JOBS=3SmallPartRejectRadius=4.0 Edit - FSX and Windows 7 are both on the same partition...to answer your question.

Alright guys. I've spent...a lot of time getting a nice, all around stable system for some NGX flying.I bought the NGX when it was released, but my i5 750 system wasn't really giving me satisfying performance.So I built a new system, using the excuse that one of my DIMM slots were going bad anyway...much to my bank account's dismay.After months of trying to get into a rhythm with this new build, I've finally grown frustrated enough to feel hopeless.Here's the system I'm running now:ASUS Maximus IV Gene-Z/Gen3Core i5 2500k @ 4.70 GHz (H80 Cooler) 12 Hours Stable Custom Blend8GB of G.Skill 1600 MHz DDR3 RAMWD Caviar Black 750GB SATA III 6GB/sEVGA GeForce GTX 460 1GB @ 800 MHz CoreCorsair HX850 Watt PSUWindows 7 Ultimate x64Now I know my GPU could use an upgrade. I'm working on that. But it shouldn't be *that* bad, I don't think. I still play ArmA II and BF3 flawlessly...I installed Windows 7 x64, completely optimized my system...running no more than 35 processes at idle, all of the latest updates...and followed the "Setting up FSX and how to tune it" guide...using Nvidia Inspector, used Bojote's FSX.CFG tweaker (making a few adjustments myself). Defragged with Diskeeper...Then I proceed to installing my addons...FS Global...which is really just more accurate terrain. No enhanced, higher res textures or more objects to load or anything. REX. Active Sky. Just the basics. Sure they could cause a small performance drop combined, but nothing serious.Then I run Game Booster, killing all unnecessary apps, including Windows themes, print spooler, etc.Time to do a dry test, in default scenery...with moderate FSX settings...water effects turned *off*, bloom *off*...all the things that really kill performance turned off. Default Cessna 172, flying around in default scenery, with Active Sky running to give me some stormy weather. Shouldn't be too bad, right? Default scenery in Seattle, in a default 172?Oh yeah...that's right. 34.1 FPS. Obviously it'd be impossible to take it up a notch and take the NGX for a spin at 10 FPS.I really don't get it. I see videos like http://www.flyaoamed...ws-impressions/ of a guy with roughly the same system (only difference is an upgraded video card)...running a 2500k clocked LOWER than mine...and he's getting seamless, fluid frame rates over some of the most demanding scenery available for FSX (ORBX), in the NGX, with Fraps running. How is someone like that getting twice the performance out of roughly the same system with a GTX480 compared to a system with a GTX460 in it?

The site for the tweaker and the shader mod are down. :sad:Hope it's just a temporary thing.

Hey everyone, I don't post here, only read (actually was surprised to see I was registered), but I have a question about this too.I have the Wilco Airbus V.1 for FSX, but I don't have it installed. I'd like to use it, since the only other option for an A320 is the Airbus X (verrryyy simple), but I'm wondering what all is affected by this corruption Wilco causes. Are you guys saying the products actually corrupt a Windows DLL file? Or are you saying it ONLY corrupts the dll.xml file of FSX. I've seen both terms "DLL file" and "DLL.XML" file used. Also, let's say I back up my DLL.XML file, and install a Wilco product. Is there a way to fix the file so everything is functional again WITH the addon?

Thanks Ethan but FSX isn't listed in Revo Uninstaller.

Sorry if this isn't the right section. I couldn't find a dedicated support area for FSX. Okay here's what's going on:I had FSX installed on a dedicated HDD. Unfortunately I made the mistake of reformatting that drive without removing FSX/Accel. first. Now I'm unable to install FSX again, because the only options I get in the installer are to repair the installation, or remove the installation.Repairing gives me a 1610 error, saying the installation is corrupt.Removing tells me it cannot find a gameuxinstallhelper.dll (or something similar).I've removed every trace I could find of FSX in my registry manually. I've tried cleaning the physical disk itself. I've also used CCleaner, RegCure, RegCleaner, and Advanced System Care. I've also done a registry search for any keys with names containing the words fsx, flight, and simulator. I've cleaned my OS hard drive of all FSX traces including temp directories and AppData directories. I've tried downloading the DLL it gives me in the error. I've tried using the Windows Install Cleanup tool, however FSX isn't listed. I've tried going into the control panel to remove it, however FSX isn't listed there either. I've tried using the software licensing reset tool from Microsoft, with no joy. I've also tried searching these forums, however nobody seems to have solved this issue before in the past.I was wondering if anyone knew of a solution yet, before I reformat my OS drive and FSX drive again.

Here's a video I was able to capture from my phone:

*bump*

I'd just like to say that this thread cured me of not being able to fly in FSX ever since building this rig back in November. THANKYOU Paul J and J van E

The problem occurs regardless of where the sliders are. My frames stay at about 70 FPS when looking dead ahead, then drop to the lower teens to single digits when panning specifically in spot view, but also in the cockpit view. The autogen spikes everywhere and flashes like a giant 2D barcode taking up my entire screen. This is a DX9 only issue.Also, when you describe running out of memory, are you referring to video or read access memory?

At the moment, FSX is unflyable because of glitches and artifacts related to the autogen (I think?). The problem is extremely hard to capture with a screenshot or video, because as soon as the Fraps recorder is engaged, the problem goes away (while frames are slashed in half), and getting a screenshot is like trying to capture random lightning strikes. The best I can do for now is to try and describe it in a very detailed fashion, until I can somehow get a screenie on here.The issue only comes up usually when panning around in spot view, however also shows up in the cockpit, and while turning. I get clouds that flash, and my autogen (mostly the trees) spike up to the top of my screen, making them look like flashing bar-codes. Sometimes when in areas with alot of autogen buildings, I get odd 2D polygons and triangles, usually the color of the building itself, mixed in with these bar-code flashing trees. As a result, my framerates may stay locked at 30, but will immediately drop to single digits when I move my view, even the slightest amount.It goes away in DirectX 10 mode, but I think everyone here knows about DX10 incompatibilities and invisible lights, etc...so that's not really a great option. System Specs:HDD: Western Digital Caviar 640GBMB: ASUS P7P55D DeluxeCPU: Intel Core i5 750 @ 3.0 GHzGPU: EVGA Nvidia 9800GTX+ 512MBRAM: G.Skill 1333MHz 4GBPSU: Corsair TX 650W OS: Windows 7 Ultimate x64I installed FSX using the method described here:http://www.simforums.com/forums/forum_posts.asp?TID=29041Also, I tried the FSX.cfg tweaks described on that page. I've tried setting up Nhancer to the settings shown on that page. I've tried a reformat, a different HDD, and Windows XP Pro x64. The issue occurs with every aircraft, in every part of the FSX world. Please help guys!