av8tor98

It's a shame that this aircraft was not developed with the G1000 package, as all new Caravans built by Cessna have the G1000 and TKS system. Also, any Caravan that I fly in real life has the G600, 530 and 430. Of course the ones I fly are quite older but we have revamped all of the cockpits with the systems I have mentioned. We also removed the deice boots and replaced them with the TKS system.

Yes, it works with the Saitek controller. I have the yoke/throttle quads/rudder pedals. I have the spoiler arming switch mapped to the right hand rocker switch on the yoke....C2 to be exact. Now, bear in mind, this works perfectly with the 600/700 but found out today that it doesn't work with the 800/900. I just bought the 800/900 yesterday and didn't check this out till today. I even set the spoilers to arm with the 2D throttle panel and verified via the "spoilers armed" indication on the cockpit panel, but the spoilers did not deploy on landing (with the -800 version), so I have to try and figure out why they aren't deploying when armed. Like me, you may have to see about making an aircraft specific profile in FSUIPC or the Saitek profile to get the spoilers to arm and deploy. Maybe someone else has already figured this out already?

Wow, what a fast response...thanks, Nathan :( I'll do that on the next approach.

Just curious about this nagging problem I have after disconnecting the autopilot while on approach....the aural warning blares "autopilot" over and over again but if I switch to outside view and then back to VC, the aural warning goes away. Fact is, after disconnect, I should hear the aural warning one time....not continuous.

I've had this happen on some other addon aircraft even after selecting auto brakes to off....the brakes stayed on. Tapping the toe brakes on my Saitek rudder pedals releases the brakes. If you have brakes mapped to a joystick or rudder pedals, try tapping the brakes on either. But, I've not had this issue with the MD-11 upon landing. I never use autoland either :(

Rafal, thanks for the F70 pointers :( I do take great care in keeping FS9 quite clean...proper scenery file structures, no duplicate AFCADs, proper scenery numbering in .cfg file,etc. Also, AI textures are definitely DXT3. I have used AES in the past but it created a headache for me on a different system...duplicated all scenery entries in the library and .cfg file and somehow got the entries out of sequence in the .cfg file. What a mess that was :( I haven't installed it on my current system.Believe it or not, I used the MD-11 successfully from TAPA to KMIA last night...1,154NM trip with a block time of 3hrs 09mins...headwinds of course :( TAPA is an addon airport and so is KMIA(with UT-USA and FS Genesis). I can successfully go this route but cannot even get 30 mins. into a route from TAPA to SKBO. Funny how that works,huh?

Why do people insist the problems with OOM have nothing to do with the MD-11? If a person can run the 747, like myself, without getting OOM errors on XP 32 bit systems on a particular route or routes, but when the MD-11 is used on the same route or routes, an OOM error occurs each time. For me it doesn't happen all of the time but the MD-11 will cause my pc to totally freeze up to the point that I have to shut it down and restart. Other occassions I get the "run out of disk space" message. Yes, I have my system clean, up-to-date,etc. For instance, the past 2 days I have tested the MD-11 on a route from TAPA to SKBO. Got a total pc freeze within 30 mins flying time for each flight. No heavy addon scenery activated, nothing. I then used the 747 and made a complete flight. I used other addon aircraft as well on the same leg...no problems. Now, I do understand the MD-11 is a memory hog, but if switching over to a 64 bit OS and adding a gazillion gig of ram is going to solve the OOM errors, count me out. But, to say the MD-11 has NOTHING to do with a CTD,etc, is disingenious to say the least. The 3 Gig switch is NOT the cure-all for every system either, as I tried it and had zero success. In essence, if the MD-11 was designed to operate on 64 bit systems with a minimum of 4G of RAM, for example, then PMDG should have made it clear, as it seems that I see alot of posts regarding the suggestions to switch over to 64-bit systems. Personally I am not going to switch OS just to run one aircraft.I'm not flaming PMDG at all...I am speaking based on MY experience only. I will continue using the MD-11 on my 32-bit system and deal with the OOM errors when they happen. Life is not lost after all :(

Understood...thanks!

This kind of looks like an Ultimate Terrain problem with the coast lines rather than a GE Pro issue. Have you tried posting these screenshots on the UT forums?

I've had the PSS 777 for a long time and never had an issue with it. Great flying airplane with functional advanced systems. I've added the TSS or SynchroSoft (can't remember which one) sounds to this aircraft as well as the 757....OUTSTANDING. I wish there were different VC textures, as the default ones are less than admirable.

I can confirm V 2.0 is a healthy step from V 1.0. It took me a couple of test flights before I got the hang of V 2.0 but it's a sweet airplane for sure. I do love the winglets on this airplane :( I'm planning on getting Reality XP Wx radar. I assume this radar is an easy fit into this aircraft, correct?

I have found recently that sometimes ASA(FS9) will crash when parsing line items. I'll get an error message that it has to close. Never found out why it happens, but it does. I always start ASA and let it go through its phases before loading FS9. I do not have the beta update either. Maybe I should install it?

I've noticed that any time I install GE Pro textures, the Samoshin Natural World Trees are practically wiped out. It was first evident when the splash screen was changed from Natural World to the default FS2004 splash screen. Upon checking scenery that's typicall heavily wooded, I noticed the NW trees were gone. I don't know how I can use NW trees while changing GE Pro textures to match the wx conditions. I have in the past exited FS9 and reinstalled the trees. But, it sure is frustrating to have to do this extra step.

I can attest that it takes a total of 3 mins. 20 secs. to go from opening ASA(FS9 of course) to completion. Sometimes it takes a bit longer if the main server isn't functioning and has to go to secondary server, but it doesn't happen often. Actually I can't complain about waiting 3 mins. 20 secs. from start to finish :(

Yeah, curiosity got the best of me and I finally opened the manual :(

Well, I decided to buy the ASA upgrade the other day and haven't used the beta update. I have made several flights that were almost 2 hours in length each and have had no issues at all. But, I thought at every update interval, there would be a text message that flows across the screen about current conditions or passing a certain fix or waypoint based on the imported flight plan. It only happens when I start at an airport and says it's initializing and then another after it has completed. That's it.Also, 122.0 only gives current conditions at that moment in flight but doesn't give current conditions at dest. airport. What's up with that?

I've tried seeing what light bloom looks like in FSX but it turns the entire screen white on my XP system. It doesn't matter what views I try, solid white screen. So, I turned it off completely. Never tried to troubleshoot why I can't get light bloom to work correctly.

It's usually the predefined profiles(SLI) tha can't be deleted. I always make a new profile when I change drivers. Works perfectly every time.

Well, I haven't tried the latest ones I see on the Nvidia website... 181.20. The previous set of drivers fixed quite a few things for me. I'm not at home at the moment to give you the specific driver version, but it was the one prior to 181.20. I've been happy with them but I may give the latest ones a try and see if there are any problems. If they don't work out, I can always strip these out and reinstall the previous ones.

I had a similar experience with MSI's 4870 1G card...after having Nvidia cards for quite a few years, I wanted to see how well the 4870 would perform. On my XP system, this card was pathetic. It didn't handle AA well at all...even at the highest settings. I did every setting possible and couldn't get satisfactory AA. Plus, FS9 loaded much more slowly, so I didn't even switch over to my other HD to check out FSX. I ended up taking out the 4870 and returning it to Mwave for a refund. I put my Nvidia 8800GT back in and things returned to normal. Now I'm eyeballing the Nvidia 280GTX 1G card :(

Very good information, thanks! I definitely understand the variations in hardware/software, but I would likely be one of those who gets the dreaded OOM issues :( I did look at ASA extensively and like the myriad of options available now. For the time being, I'll sit on my wallet and see what happens with the update. I'm a patient man :(

Very good info...thanks a mil! I suppose I'll wait for the full SP1 to be released before I upgrade :(

Where is this ASA SP1? If I get this upgrade today, I would like to know where I could pick up the SP as well. I didn't see it on HiFi's website.