lodestar

Actually there is a pinned guide on Airsimmer forums about how to install A320. No problems if you folow this

where is your fsx installed? Is that correct patch "c\program files (x86)\microsoft games\microsoft flight simulatorx"? And after you get this message, did you tried just to click ok? What happens if you click ok?

That's good suggestion. Go to FSX main folder, right click on FSX.EXE and select "Properties". Then go to "Details" tab, what is under "Product version"?

Worked just fine for me, and i applied this fix to 3 other systems without problems. I also advised some people here on forums about this fix, and worked well for them too. So, maybe fix is not applied correctly? There is a description for Windows XP... Maybe this can be a problem for some people, to find right folders on Windows7?

Download registry repair tool here: http://www.flight1.com/view.asp?page=library And use it ^_^ I never heard about this error, if not work - go to PMDG website and submit a ticket, they have excelent support

You have nice colection of planes there(except that Captain SIm )... I own all of them, if you like realistic simulations - my advice is to go for maddog. This is still my best purchase for any flight sim. You can go for Majestic Q400 as well, very detailed, modern textures+excelent external FDE

i know what JSBSim can do... Try Majestic Q400 There are some minor buggs to be fixed, but FD is awesome. This is why i asked about flightgear, i know what FDM was used. Thanks

Windows 7 64bit + google for "Word Not Allowed's Flight Simulation World", you have there all settings, the best for your sistem. Don't use automatic tweaking tools etc... You may consider to tweak windows 7 too http://www.tweakhound.com/windows7/tweaking/index.html

How is aircraft handling / physics in flightgear? I thing this is the only flightsim i never tried

This happened to me when i tried acceleration pack earlier this year. I just uninstalled it and installed SP1+SP2 and SDK, and everything back to normal, steady 30fps, no spikes. Same settings in both cases, but fps about 21-22 and spikes with Acceleration

where have you heard about autothrottle? I saw NTBS statement that autopilot was turned off, but nothing about autothrottle so far. And +1 for autothrottle just armed

Ok, we can try 2 more things: 1. right click on "my computer" again, select "properties" and on the right hand side click on "Advanced system settings". That will open the new window, go there and under "Advanced" tab you will find 3 sections. In "Performance" section click on "settings" then select "advanced" tab. In "Virtual memory" section, click on "change". Then set it like in picture and click "ok" , "apply" "ok" until you close all windows 2. Check your screen resolution, and ensure that you have corect resolution selected in fsx. I saw once OOM errors becouse of this. Send me your FSX.CFG file, i want to check it. Your GPU is pretty weak for fsx, but this would not give OOM. BTW, do you get a message when FSX freezes? Maybe this is not OOM error at all. I'll send you PM with some more recommendations, to make fsx stable

Must check this, If you right click on "my computer" and select "properties", what is under "windows edition", "instaled memory" and "system type"? Also, go to FSX main folder and find FSX.EXE. Right click on "fsx.exe" and select "details" tab. What is under "file version" and "product version"? This will tell us if there is a problem with windows/fsx versions.

Quote from another forum: The autothrottle can support stall protection if armed and not engaged. If speed decreases to near stick shaker activation, the autothrottle engages in the appropriate mode (SPD or THR REF) and advances thrust to maintain minimum maneuvering speed (approximately the top of the amber band) or the speed set in the mode control panel speed window, whichever is greater. The EICAS message AIRSPEED LOW is displayed. Note: When the pitch mode is FLCH or TOGA, or the airplane is below 400 feet above the airport on takeoff, or below 100 feet radio altitude on approach, the autothrottle will not automatically engage.

Yes, but this is the first deadly crash (after more then 5 millions flights) for 777

download AppCrashView http://www.nirsoft.net/utils/app_crash_view.html Just run it and find the latest fsx entries. Paste here a few of them. It's probably OOM error, but is good to check what exactly happens. To avoid OOM eerors: - apply this microsoft patch: http://support.microsoft.com/kb/947246 - open FSX.CFG and set your Texture max load to maximum 2048(you can leave to default 1024 too) - If you have REX, use DXT optimized REX clouds - disable all scenery which is not used for current flight, all addon and especially payware scenery. If you fly in Europe, you don't need Africa, Australia etc. And there is no need for more then 2-3 airports enabled for current flight. Get used to enable just scenery which will be used, every time before you start FSX. Here is the great tool for that: http://sourceforge.n...r/files/v1.1.1/

I can understand that was a long flight and ATC contribution(still, he could refuse "slam-dunk" approach BTW)... But some things cannot be overlooked and forgiven - he was not in stabilized approach at 1000, not in stabilized approach at 500, and not in stabilized approach at minimums! Then, at landing, after copilot warned him about low speed(7seconds before impact acording to NTBS), there was no room for waithing, thinking, assessing situation etc. It's only one posible response - TOGA! There was no immediate response at copilot warning(7 seconds before impact) and stick shaker(4seconds before impact)! Acording to NTBS throttle was advanced just a few seconds before impact... You can try this if you want when you're alone in your cesnna, but not when you are responsible for 300 lives

No, AppCrashView reads all applications crash logs. Just start it and search for FSX entries entries(you will see FSX icon). Search for recent logs(there is a date and time for all logs)and post a few of the latest logs. Just copy/paste

Just saw something interesting in other forum, about 777 "FLCH trap" - If you are above GS and need to descent quickly, FLCH is a very tempting and usefull. If they used FLCH and FD was left on, Autothrottle would have been inhibited and the thrust levers would have stayed at idle. No excuses, but posible explication on what happened

Download AppCrashView http://www.nirsoft.net/utils/app_crash_view.html Just start it and find FSX, post your latest FSX crash reports

If so, get Flight1 ATR, there is no better ATR for FSX/FS9 http://www.flight1.com/products.asp?product=atr1

absolutely, this was a warning, i have some screenshots :lol:

I remember this advice from some overclockers forums - never use two applications to measure the same thing - assus monitoring and CPU-Z like you did. Before i uninstalled Assus monitoring, i saw CPU temp of -60c and some other bad readings(i'd wish -60, but is not posible with air cooling ). Stephen has right, it's probably monitoring error

one more thing, you have great hardware to run FSX at high settings, google for "Word Not Allowed's Flight Simulation World" and folow his recommendations

I share your opinion. My experience was the same, i can't get better combination of graphic qulality and smoothnest then using BF tweak. I tried also Nick's set of recommendations and i get a 10fps less and nice slideshow at any bigger airport. I'm not saying that Nick is not good, but we must try all approaches and see what works best. Different systems - different experience For John, to answer OP: Go to Nvidia Control Panel and check in Display section that your refresh rate is 60Hz. If so, use nvidia inspector https://www.dropbox.com/s/92g87a4ri15yeym/nvidiaInspector.zip and set FSX profile like here: http://imageshack.us/a/img163/7515/capturelfo.png For this profile to work, start fsx, go to settings and under graphics tab - set filtering to "Anisotropic" and limit FPS to 30.