Koosh

Seems like I can't control my rudders with my previously working controls with the Airbus X? With my Attack 3 joystick. I've set my left and right buttons to yaw the rudder left and right accordingly. With the Extended, the rudders seem to be held down centralized. I thought it may be the auto rudder but it's turned off in settings>realism. And I've even tried to toggle the auto rudder on and off in flight. I'm still unable to steer the plane to taxi. Anyone having this problem?

I'm sure its because you reset your default flight with a new set of flight plan.

The problem doesn't lie with your addons or any 3rd party installations. It is as simple as re-doing your flight plans and saving it again (most of the time with this problem, you're using this flight plan as a default). You must have changed something along the way and then overwritten the file. FSX is just telling you its having problems finding the initial file as you have over written it with a new file. It knows when you did that and it doesn't recognise it as the same file even though its the same location or waypoints. Simply delete your flight plan (usually your default one, or the most recent one) and re-do again. To make sure you delete all recent "saves", at Free Flight menu, click the Load button and delete the most recent save that you have made before things got messy. I'm quite sure it will solve your problem as I have just fixed mine.

I'm guessing this is not possible?

Hello all! I'm using the Logitech Attack 3 joystick and I was wondering if I can tune / calibrate that tiny piece of throttle on the joystick to be able to activate the reverse thrust when I pull the throttle all the way back? E.g: Close (-) Full (+) -----------|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Reverse| 0% <-- Regular Thrust --> 100% | Thrust | 0% <-- Regular Thrust --> 100% | Is it possible for this setting to be done on my Attack 3? Rather than using a push button I can use the "throttle" to engage my reversers.

It almost feels as though my FSX has mood swings. I just flew a complete flight without crashing whatsoever even when doing settings, changing views to top down for taxiing, opening controls while in flight, alt+tabbing. So I really don't know what is wrong!

Just when I thought I have sorted things out, I was too quick to think so! I've just received my new computer chair (irrelevant I know) and thought I'd give FSX a spin after the new RAM settings. From starting up FSX to just taking off, I crashed three times. First time was when I was tuning my controls before I even started the flight. Second time I forgotten when but it was before I got into the flight, still at the free flight or config page. The last time was right after I took off, about 10 seconds after lift off it hung and crashed. Two out of the three crashes in this short span of time was caused by ntdll.dll, and the last one after takeoff was caused by MSVCR80.dll! I feel like my FSX is really messed up. What should I do now? Jay Just as soon as I finished typing this and posting the reply, I tried to run FSX again and it crashed. :Cry: This time, g3d.dll failed on me. Am I doomed for a full reinstall?

From my little experience with FSX, I've already been having problems runnin it smoothly, and adding aircrafts and utilities like EZDok and sceneries. And honestly I feel that things shouldn't be so hard! I was just wondering if I could get any recommendations for a much more stable flight simulator software. At the same time, I'm curious to know what softwares does RL flight schools use for their simulators? And what softwares does the authorities use to do regular flightchecks with the pilots?

Hey Jim! I've successfully changed the AI OC Tuner settings to XMP Profile. Saved and reset my computer only to find my computer telling me to connect a device to boot into. Had a minor heart attack but stayed calm and reset my computer again. Went back into BIOS to check my boot sequence. I don't recall changing any boot settings, let alone even clicking the boot tab. Went back into BIOS and tried the AUTO profile setting, still can't boot. Went back and tried the MANUAL profile, still can't boot. Went back and found out that my M4 Crucial SSD isn't detected in my boot sequence! (Now I'm not sure if its really not there or not because at this point in time I was already in a state of a small panic.) So I called my "computer guy" and he told me at the most calmest voice,"just set the hdd bbs priority to ssd first." While he was saying that I was going through another round of restarting my computer into BIOS again. So when I entered, I changed the Tuner settings back to XMP profile, and checked the HDD BBS priority sequence and found my SSD! So here I am, with the new RAM settings. Memory freq @ 1600MHz and AI OC Tuner @ XMP Profile. Hopefully it solves the CTD/fatal error issue! The most recent few times this ntdll.dll caused my FSX to crash was when I exit the flight after landing and shutting down my plane. Its when I click "End Flight". Just for read sake, here's the most recent crash log from AppCrashView! (after I successfully landed my A320-200 ILS from WSSS to WMKK for the very first time! ^_^ ) I've only make changes to my RAM after this very crash and have not tested anything yet. So this crash log has no relation to whether the RAM fixed the CTD/fatal error issue. Heading out for a Tuesday night beer now so I'll report back with how things are with my FSX when I make my next flight! B) Cheers! :drinks: Jay

So I couldn't figure out where is what and I took some screenshots of what I think is where I should be editing or changing. The secondary and third timings are set to auto. Could that be the one I'm supposed to change? What do I change to?

Took down the settings and figures from the SPD tab of CPU-Z. Will check out my memory config in my BIOS and config it if it isn't set! So basically having the uiautomationcore.dll in your system may or may not help in running FSX? I recall someone recommending me to use this fix as I recall seeking help after CTD when changing views (in one instance) and pressing the menu button to change view or controls (in another instance). Though I forgotten if I actually went on to download that .dll as a fix. If this does not come by default then I must have downloaded it myself! And if it helps, its not in my main FSX folder. Its here.. "C:\Users\BERNIE\AppData\Roaming\Microsoft\FSX" I would think my system can take quite a fair bit of high settings for the graphics in FSX? Or am I underestimating the power of FSX and how much it "needs". Haha. Well after the last crash, I stumbled across THIS THREAD and decided to give it a try. The whole layout of the post was so messy I don't know where I was after reading it for about a minute. Haha.. so I scrolled down until I saw a few screenshots that caught my eye. I saw screenshots of the video config and all the graphics, scenery, weather etc... So I gave it a try and followed the tutorial in how to "set up FSX and how to tune it". Haven't gone back in to FSX to test it yet though. I'm saying this because as I was changing my settings to follow the tutorial, I realized that my settings were actually not that high, as most of the time I would be sliding the slider up instead of down; from my previous settings to the tutorial's settings, I had to slide the slider up. So that said, it was already 'down' for the very most of since I installed FSX up until now and if that didn't work out for me, I'm sure it wouldn't be recommended to have the sliders pushed "up"? Yes I have 8GB of RAM. What is page file and virtual memory settings? Settings in windows? If I'm going to keep a page file, make sure I set what to what? Yes I recently posted somewhere asking if there was any problems like such before I proceeded to update my FSX with SP1 and SP2. Anyway, I have a "Microsoft Flight Simulator X Service Pack 2" entry in my Add/Remove Programs @ my control panel. I was wondering if uninstalling here would just uninstall SP2? Or would it uninstall the whole FSX? Where can I download a reliable SP2 update installation file?

It seems that the most recent crash wasn't logged and AppCrashView can't see or find it. It happened a few days ago, FSX crashing in the similar or even same circumstance and it was logged and AppCrashView can find it. So there.. If you're interested to know what is that Fault Module Name that is "unknown", here is the log. I would very much appreciate it if we can solve this together! EDIT (Add): ---------------------------------------------------- Careless me didn't check the whole list properly. Apparently it wasn't sorted by the date and I didn't look through the whole list. Here is the most recent fatal error that brought this thread up!

What kind of details is the Wilco more detailed in? Do you mind stating a few if there are just too many minor specifics? State the more major ones, or the ones that you feel matter!

Seems like there's something wrong with my ntdll.dll?

Use uninstallation methods recommended by the developers. Usually they have the uninstall done in the Add/Remove Programs folder at your Controls Panel.