RickB1293

FS2Crew has the same problem on the NGX. I can't remember what the fix is but I never got it right. Maybe you can check their forum for suggestions. Sent from Rick 's iPad using Tapatalk

Come on Guys- I think there are three or four REAL T7 pilots out in SFO that want one more than you do! Sent from Rick 's iPad using Tapatalk

I take it that MSE v2.0 is the common denominator. Try loading ProcessExplorer and run FSX through a failure. PE gives more informaton about what's going on in the computer than any similar program I've tried. You can isolate .EXEs, .DLLs and .NET calls. I have seen this type of complaint in PMDG, REX and MSE forums. I'm surprised that MSE hasn't responded to you. Maybe you should label your post something like "MSE CRASHES MY SYSTEM EVERY TIME I RUN IT (And I want my money back)! You'd be surprised how something like that gets their attention. I loaded up your flight from KASE to KBCE in a Carenado C182T and flew it at 3,000 to 4,000 AGL with no problems so I agree that you must have some corrupt files. MSE told me that they default to FSX standard BGLs if they detect load errors. You really have to get their input. I took a look at common solutions to your app crash and this is the easest solution from http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htm. Cause of Ntdll.dll ErrorsThe causes of ntdll.dll error messages can vary greatly. However, most ntdll.dll errors result from a corrupt or damaged version of the ntdll.dll file itself, corrupt hardware drivers, or issues between Windows and other programs. Ntdll.dll errors can sometimes mean that a piece of hardware in your computer is malfunctioning, but this is rare. How To Fix Ntdll.dll Errors Restart your computer. The ntdll.dll error you're receiving could be due to a one-time, temporary issue and a simple reboot may resolve the problem completely. Reinstall the program if the ntdll.dll error only displays when you use a specific program. If the software program has any updates or service packs available, install them too. The software's programmers may have identified an issue with the program that caused the ntdll.dll error and then issued a patch for it. Note: Third party software programs that have been installed on your computer are almost always the cause of ntdll.dll errors. The remainder of these troubleshooting steps resolve ntdll.dll issues only rarely. This is a Bit-- of a problem and I'll check around to see if anyone can come up with something. I will follow this post and hopefully you can get to the bottom of this. Rick

Download this http://download.cnet.com/Process-Explorer/3000-2094_4-10223605.html and run it while FSX is up. Right click on the headings to open the select columns menu. Go to Process Memory and check Virtual Size. I place it next to the CPU and GPU columns. Because FSX is a 32bit application it has a limited memory space of 4Gb. If FSX Virtual Size starts to approach 2,400,000 K then you are setting up for an OOM and CTD. I use MegaScenery Earth in several states and only load those that are in my flight path. Also consider that flying over a state at say FL350 isn't going to give you the kind of detail that photorealistic apps like MSE are designed for so consider turning it off for your commercial cross country flights. Weather programs like REX also take up the program VAS when loadingweather into FSX. Take a look at the discussions here http://forum.avsim.net/topic/412418-looks-really-great-but-i-cant-buy-it/. This is happening when you use apps with high demand such as PMDG 737-800 NGX, REX Essential + Overdrive and MegaSceneryEarth at the same time. The last app to feed at the trough gets blamed for the crash but it is really systemic and a limitation of FSX and any other 32bit app. Good luck,

I have a lot of Drs in my family and when the grandkids ask: "Why aren't you a doctor?", I tell them that when a person gets sick you have to be nice and soothing and help them get better. When a machine gets sick, you grab a hammer and beat it till it works!

All this whining about waiting is due to just plain ignorance. These people don't have a clue about software design, responsible testing and bringing a product to market that can and must be instantly supported. PMDG puts out some of the greatest software I've ever seen and they rely on an archaic platform to do it. FSX is a 32bit program that hardly supports the DX10 standard and doesn't even come close to DX11. Making an airplane like the T3 fly in FSX is like trying to hit a target at 2,000 yards -- with a flintlock. If we give these guys a break and let them get on with the important stuff the T7 will get here -- but it will only get here when PMDG is sure that it isn't buggy and they can support it. What would you have them do, release the Service Packs first? Vertical Reality Simulations went through the same painful process with the FA18-E for FSX and with their TacPac. They made it and so will PMDG. Keep up the good work guys, your products are superior and your support is the best.

I use FSCommander on a separate monitor but you can always go to the outside overhead view (S,A). DevGrp - does that mean what I think it means? Go Navy!

Indeed

Here's my donation to a good cause. Just won the Virtual Powerball Lotto so am flush with cash. You can get the PMDG T7 for around $35M plus upgrades like bathrooms. seating - you know. I sent my donation via virtual email so you should get it virtually any time now. Regards :lol:

I've had my build up and running for about nine months and the OC is stable and FSX runs a pretty consistent 28-30FPS. I recently installed and activated the Intel Rapid Start, Rapid Storage and LucidLogic MVP motherboard features. I use a 16Gb partition as a hibernation mirror in front of my system drive (WD 1Tb Black). I also use a second 20Gb partition as my iRST cache. My Win7 load times are about 1/3 of their previous WD 1Tb drive times. A cold and dark restart takes less than a minute after the WIN7 blossom screen opens. My question is other than speeding up the system loading from cold and dark or from hibernation, is there anyway to benchmark these features as alternatives to exclusive SSD system and FSX drives? I can switch the SSD cache from supporting the system drive to supporting the FSX drive which is a WD 300Gb VRaptor. My FSX starts are really long because I use quite a few photorealistic scenery areas and third party airports and aircraft. I've experimented with the 120Gb SSD as the system drive and also as a lite build FSX drive. I don't notice much of a difference between the SSD system drive and using iRST with a 20Gb cache. I haven't tried FSX from an exclusive SSD because my Photorealistic Scenery and REX Essential + HD and all of my other addons take up close to 400Gb and my SSD isn't big enough to hold everything. I know that the SSD for FSX will only help load times and won't improve my FSX benchmark by much. I was just wondering if anyone else has experimented with these features? I also enabled my registered FSUIPC and a WideFS client on my i3 laptop to handle FSCommander,charts, plates and my POHs and route planning. I can move things like REX Ess+OD over to a Q9550 media computer and enable that as a client also. Any experimenting dne along those lines? The iRST technology has some promise to it and I would like to see if there is any point in using it. My ASUS Sabertooth Z77 also supports Lucid's Virtu MVP graphics utility. This lets the system off load some of the GPU overhead and shares functionality with the onboard iGPU 3000 graphics platform. I have another question along the same lines mentioned above whether or not there is any benefit to enabling it. All of these features setup quickly and seem to be very stable so if they add any performance edge at all, they might be worth adding to the FSX mix. Let me know if any of this has merit. Thanks,

Gentlemen, Let your efforts in search of that most perfect of FSX tweaks be guided by these simple fundamental principles. They are part and parcel of any graduate level study of Applied Mathematics. I learned them at the knee of one bloody professor or another and are, therefore, the god-awful truth. The Theoretical Definition of the "Optimal" Solution The optimal or "best" solution to any given problem is the one that draws a mathematically precise line from an unwarranted assumption to a foregone conclusion. Likely Outcomes In Heuristic Computatonal Models (Binary) 1 - Saying something is when it ain't or 2 - Saying something ain't when it is. And to those among you who would rather be flyin' than tweakin' -- Go buy an Apple and fly that! :p0503:

God smiles on the man who loves his job!

Sorry for the duplicate post.

Guys- I've been a flight sim pilot since ACES put the first Cessna 152 on Miegs Field. That sim required a monochrome monitor and a 16 bit processor running around 3.4 Mhz. It was fed from a single sided single density 360 MByte floppy drive. I also write engineering simulations of complex real world interactions that must be considered in real life high rise architectural and structural design such as the effects of uneven heat and deformation caused by the sun's relative position or climatological variables. Many of these simulations can be represented graphically and lend themselves to large or massively parallel computers such as the Crays and the IBMs. The calculations are also tremendously iterative and deterministic. At some point a relevant range is encountered when additional changes become meaningless. What we are asking FSX and the current stable of addons to do often results in competing goals bidding on finite resources. An extremely complex aircraft such as PMDG's NGX or the VRS FA18-E models complex multivariate subsystems that in real life are handled by separate computers with redundant backup. In the flight sim we ask the computer to create and control the flight envelope around which the graphical representation of the aircraft is built. Now add in the graphical embellishments such as shading and reflectivity that make for life-like models. If these aircraft flew in a dark vacuum FSX would handle them with ease. But we aren't satisfied with that are we. We also want the air they fly through and the ground they fly over to be very close to real life and have all that happens rendered in real time. There's the rub. We expect an aircraft flying at 300 KIAS and 200 feet AGL to give us a sharp and realistic rendition of the envelope so if we were to take a snapshot of our flight, the resulting still picture would look like a Leica wide format portrait. Even the camera system on the SR71 Blackbird can't do that. FSX performance limitations and those of our current generation hardware are capable of providing low altitude, high speed and high alitude high speed realism. Unfortunately they can't do them both at the same time with the same settings. The relative field of view at 300 feet is significantly smaller than the field of view at FL300. The optimal settings for each are quite different so we shouldn't expect even top end systems optimized for say, a military aircraft flying close ground support to provide the same gaming experience that an intercontinental passenger airliner can deliver at FL370. If your hangar is as full as mine, you can take a morning flight in your Carenado Cessna CT182T from Gunnison to Telluride Colorado flying photorealistic mountain canyons courtesy of MegaSceneryEarth. You can land and have a quick lunch then jump into you EagleSoft Cessna CitationX and fly to New York LaGuardia at FL450 and Mach .950 dodging weather created by REX Essential-Overdrive. The next morning you can report as Pilot in Command on an American Airlines B747-8i for a flight from KJFK to EGLL. Oh, and I haven't even had time to clean the windscreen on my Navy F/A18-E by VRS, or qualify for carrier ops. I guess what I'm saying is that FSX lacks the ability to make on the fly changes to critical system variables. Because it can't, it will never be a "one size fits all" platform. That means that the tweaks that work for one of us won't work for all unless we're willing to be satisfied in the "middle" and accept less than optimal performance in several areas of what we call quality. This operates varying aircraft in varying environments without overworking one aspect of your system or another. For instance, be satisfied with 24fps and a 60NM weather range in order to operate a wider set of aircraft in a reasonable though not "perfect" environment. Far too many of us seek the "perfect" optimization and there ain't no such thing.

Hi Jeroen- It's hard to point you in the right direction without knowing about your system. If you're up against a hardware limitation then none of the tweaks you'll find around these forums will have much of an effect. That being said, it sounds like you may have a bandwidth problem between your CPU and graphics card. Try adding these changes to your FSX.CFG file. Try them one at a time and backup your .CFG before you make any changes. You may want to start with a clean file and make progressive changes. It's time consuming but it might save you a lot of headaches. You'll find some good information here . [bUFFERPOOLS] UsePools=1 PoolSize=100000000 RejectThreshold=524288 You may also want to back down on you framerate setting. Try this: [Display] TEXTURE_BANDWIDTH_MULT=80 UPPER_FRAMERATE_LIMIT=24 WIDEVIEWASPECT=True TextureMaxLoad=6 These changes to your [GRAPHICS] settings can also effect throughput: [GRAPHICS] TEXTURE_QUALITY=3 IMAGE_QUALITY=1 SHADER_CACHE_PRIMED=1693500672 SHADER_CACHE_PRIMED_10=1693500672 D3D10=0 FORCEWINDOWEDVSYNC=1 HIGHMEMFIX=1 MULTISAMPLESPERPIXEL=8 // MUST HAVE FOR GOOD AA CAN BE 8 MULTISAMPLEQUALITY=4 // CAN BE 4 FOR BETTER PERFORMANCE. TEXTURE_MAX_LOAD=2048 // HD textures can be limited to 1024 without impacting image quality ForceFullScreenVSync=1 I fly in windowed mode because I like having FSCommander and REX up on a second monitor. You can also try to back your in game scenery sliders down a little also. If you have a quad core CPU, Fiber_Frame_Time_Fraction won't have any effect on your system. This setting allowed single or dual core processors to balance the time allocated to running the sim and loading scenery. Since MS came out with SP2 or Acceleration, quad core processors don't use this setting. You can experiment with AffinityMask but Intel high end systems manage their resources pretty well on their own. These terrain settings may or may not help. I use a lot of photorealistic scenery and they are optimized for that. The new offerings have native mesh support and you might have conflicts with autogen packages such as UTC or GEX. [TERRAIN] LOD_RADIUS=4.500000 // Photorealistic scenery doesn't "build" the environment, 4.5000 eases the load on the GPU MESH_COMPLEXITY=100 MESH_RESOLUTION=25 TEXTURE_RESOLUTION=29 AUTOGEN_DENSITY=5 DETAIL_TEXTURE=1 WATER_EFFECTS=7 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=4000 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=4000 SWAP_WAIT_TIMEOUT=10 Take a look at for a more comprehensive list of subjects. Good luck, Rick Bertz

Very nice blow by blow account of your flight. The Alaska livery is one of my very favorites. I recently started to use MegaSceneryEarth version 2.0 products. The effect is just outstanding. I have their MN package and flying around is just like the real thing. Blueprint Scenery sells KMSP (Minneapolis/St. Paul) for around $15. The jetways don't operate but the layout and geo referencing is spot on. For me, the "eye candy" is a big part of the sim experience and I appreciate the time you put into this post.

Hi Mark- I've been following your posts and here's my free advice (which is well worth the price). I use Real Temp's i7 Turbo GT 1.30 and Real Temp GT 3.70 to benchmark my systems. Both of these programs give you great performance specs that can either be watched on your second monitor or logged to a file of your choosing. I build computers for both FSX and AutoCAD 3d apps. FSX is the hardest to tweak because the platform hasn't kept up with the improvements in hardware. It allows limited optimization because many of the robust tools supported by your CPU and GPU aren't available or coded for FSX. Here are a couple of hardware suggestions. I apologize if you've been through them but hopefully they'll give you some help if you haven't. Try to increase your CPU overclock. I run my i7-2600K at 4.5GHz with an H100 cooler and stay around 4.0-4.3 running FSX in either DX9 or DX10. Temps stay in the 50-60C range so I don't push the CPU as hard as it can be pushed. Most OC sites don't recommend running steady state at much over 80C so check your performance at a busy airport and see where you end up. If you find abnormal temps you may want to consider a full size tower, if you don't have one already. I didn't notice your power supply spec but make sure it can handle your system. With the GTX580s SLI and the i7 950 modestly OCd you'll need at least 800 watts with the proper power rails. PSUs rarely put out 90% efficiency so remember you have a 75 to 100 watt light bulb smack in the middle of your system. That's a lot of heat. Check ASUS for their recommendations, they are right up to date on the changes in PSU product development. . What temps are your GTX580s putting out? If they are in the 80-90C range you might want to increase your fan speeds so they run at 100% at 80C. If they still run hotter you may want to check your fan I/Os or your case layout. Two 580s in SLI can play havok with air flow within the case making it hard to cool everything. I see your using the Sabertooth M/B which is usually a very cool board. I don't have any experience with SLI installs but temperature can and does hurt performance on high end OCd systems. Is there a reason that you want to lock FSX at 40 fps? Try cutting this back to 30 which still very smooth and it also teams up with your monitor's refresh rate if you have 60Hz, which is pretty typical. I haven't seen many systems that can hold 30fps at busy airports with AI cranked up. BTW, you'll know when you've hit the wall hardware wise when your case fans start running so fast that you'll need a couple of books tto keep the case from launching. I really haven't seen a great deal of difference in performance between DX9 and 10. If you find the sweet spot using DX9 your system shouldn't need much of a change going to DX10. Remember that DX10 isn't fully supported by FSX so many of the isoteric .cfg settings just aren't supported. Find a DX10 site or contributor that you trust and stick with his suggestions. I run a little faster CPU but my 560ti can't keep up with your 580. I currently run FSX with most of the sliders to the right following suggestions on this site concerning AI scenery, weather radius and AI traffic. I run a whole stable of addon aircraft as well as REX Ess+OD, MegaSceneryEarth photorealistic scenery and FSDT airports. I hold 30 fps every place but the busy airports where I hold 20-25 fps with the eye candy on. The biggest drain on the system is from the REX WXPlus during stormy or cloudy weather bu they are working on a SP to help. I'm sure you know that SLI isn't supported by FSX but it is very useful if you have to multitask with other GPU intensive apps while running FSX. My biggest suggestion from a hardware standpoint is keep all of your devices as cool as you can. No amount of tweaking can overcome a hot CPU or graphics card. FSX doesn't push a system as hard as the current batch of D3DX11 games and apps do. You have plenty of horsepower so maybe just take a look under the hood and make sure the system can breath. Again, if you've gone through these steps I apologize but I've been away the site for awhile and missed some of the discussion. Please post any questions and I'll try to get back to you ASAP. Rick Bertz

Thanks Dan, Great links to training aids.

My experience is the same. I've used Newport Scenery's Hawaiian Islands which is a first generation photoscenery package and MegaSceneryXs Oahu which has a much finer mesh, I think its around 1m per pixel. The new stuff from MCE blows me away. It's easy of fraps and if you follw their recommedations, it's as realistic as you could hope for. I have CO, MN and WI. All three are outstanding and so far superior to GEX etc. At $40 a state they are a deal.

I just remebered that VRS doesn't support DX10 with their TacPac which probably means that the Bug won't work either. Sorry for the misinformation.

If you're having trouble assigning throttle axes in FSUIPC, try this procedure. Look for each Saitek device in the notification area of your taskbar. If not there, open Device Manager (right click Computer/Manage/Device Manger) and look for Saitek Pro Flight Yoke and Saitek Pro Throttle Quandrant entries under Human Interface. There should be two entries for each devices, one ending in (HID) and the other in (USB). All four of these drivers must be listed. If not then reload your Saitek drivers or look for updates at http://www.saitek.com/uk/down/drivers.php. Once you see the notification icons, right click on each and select Control Panel. This should open an applet on your desktop showing all of the sliders, switches and hat switch. Move each lever and exercise each switch to make sure they are being read through windows. If all of your controls work properly in their prospective control panels, leave the windows open and load FSX. Select the aircraft you want to setup the yoke and throttle quadrants for then load it into any airport, it doesn't matter which because you won't be flying at this time. Start FSX and go to Options/Settings/Controls. Click on CONTROL AXES. Next to Controller type enter Saitek Pro Flight Throttle Quadrant and delete all of the FSX axis settings. if you're setting up the yoke at the same time then go to Saitek Pro Flight Yoke and repeat. This ensures that FSX won't compete for control of the axes. A note of caution: Unless you're going to use FSUIPC for every aircraft, you'll have to reset the axis defaults when you change airplanes. Take a look at Pete's How To manuals to find the best way to work with FSUIPC and FSX. Once FSX has loaded everything up, open FSUIPC from the AddOn menu. Select Axis Assignment tab. If you are making the assignments profile specific (which I strongly recommend) move your levers on at a time. Click Rescan between each axis movement. You should see Joy# followed by two boxes in the middle of your FSUIPC setup screen. My lefthand throttle quadrant is Joy# 0 and the righthand throttle quadrant is Joy# 2. Each control lever should display a unique number. For instance, my throttles are, from left to right: 0,Z=L1 0,U=L2 0,V=L3 2,X=R1 2,Y=R2 2,z=R3 When FSUIPC recognizes each axis you should see In and Out numbers reel off from -16384 when the lever is all the way down to +16384 when in the up or full throttle position. Make sure these numbers move their full range for each axis, write them down so you have a record of your sedtup in case something craps out on you. You can assign an axis or operate each lever as a series of switches. For instance, for my PMDG 737NGX, I setup the flight yoke and additional throttle quadrant (giving me six levers) as follows: 0,Z (Spoiler) 0,U (Throttle 1) 0,V (Throttle 2) 2,X (Flaps) 2,Y (Landing Gear) 2,Z (Unused) The first four levers are set as follows: Under "This side to send axis values". Tick Send direct to FSUIPC Calibration then tick the first box. Click the right hand selection arrow and choose Spoilers from the drop down menu. Do the same for the next three levers selecting the appropriate action from the drop down menu. Retest by clearing the Joy# box pressing Scan each time. If each axis is properly assigned and the lever range is as above you're ready to move on to calibration. To calibrate the axis select joystick calibration from the FSUIPC menu. Go to Screen 6 of 11 Where the trim, spoilers and flaps are listed. Moving the first lever, should cause the In and Out values to count up and down. The direction should correspond the assignment screen. You'll see three boxes marked Set. Move the lever to the bottom end of travel without going into the bottom switch area. Press Set over the right hand number which should read 16384, it may be one or two lower, that's okay. Now move the lever all the way to the top. The number under the first box should read -16384, press Set. Under the first box you'll see a box labelled REV, for the spoiler control check this box and it will reverse the axis as required in FSX for some unknown reason. On the NGX there is a flight detent on the spoiler lever that you can set near the top of travel. I set mine at-512 but it's up to you where you feel comfortable setting this detent. Press the middle Set button (you may have to do it twice to fill both the upper and lower boxes. This should assign and calibrate lever one as your spoiler axis. Continue as above for the remaining axes. Throttles are calibrated separately on page 3 0f 11. You can setup reversers on the Saitek quadrants by going to the Buttons+Switches page and checking Profile specific if appropriate. Drop throttle one into the very lowest point of travel. You should see Joy#_ | __Btn# listed in the center of the screen. Check Select for FS control to the right of the page. Select Throttle 1 Decr from the top drop down menu. Check the Control to repeat... box and select Throttle 1 Cut in the Control sent when button released box. For setting the flaps lever, FSUIPC recognizes most of the aircraft and will automatically select and program the correct number and location of each detent. The Landing Gear lever is setup as two switches, one at the top of travel, the other at the bottom of travel. I set the active range for each action at around 512. This gave a Gear Up toggle about one inch from the top and a Gear Down toggle about one inch from the bottom. These ranges and functions are entered from the right side of the axis assignment screen for the farthest right active lever by setting the range then selecting the action at point one then doing the same at point two. You can set the lever direction of travel to activate the switch. For Gear Up the switch closes when the lever is moving up and the Gear Down switch closes when the lever is moved down. For unknown reasons the three position mode switch on the back of the right hand yoke isn't recognized by FSUIPC unless the control applet is opened. I use the switch positions to bring up the CDU and the Overhead Panel. The center position is null. I hope the points you in the right direction. Reading the FSUIPC basic and advanced manuals explains in great detail how to use this snap-in. I have different FSUIPC assignment profiles for each of my aircraft. Once setup it gives consistent control operation and very smooth axis movement. Regards and good luck, PS: You have to assign separate USB ports to each of your controllers. When you plug your joystick into the port that FSUIPC just saw as your Control Yoke it assigns a different controller number each time. By using the same port each time you plug in a device keeps FSUIPC from getting confused. For instance, if you plug your Joystick into the left hand port on the front of your computer, ALWAYS plug it in there. Same goes for each of your other flight controllers.