Dreamfleet 727 installs ok, and flies reasonably well. My only problem is that I have to cycle between he VC Panel and 2D Panel in order to make any changes to secondary panels. A bit of a pain. Shortcut implementation is a bit strange for some windows as well. She does fly well if you can put up with a little hassle. On my old system a little bit of a framerate hog (Fine in FS9). I hope a reasonably painless update is possible for this fine bird.The old Flight One Iron Knuckles DC9 also installs and flies manually ok. I have not found a way to get any kind of logical auto Pilot control thus far. The heading bug has no effect, nor now does GP or VOR guidance. Speed and Altitude control work fine. Once I thought I got her to follow a GPS controlled flight plan, but I cannot get her to duplicate this. It appears to me that the wing leveler function is a permanent fixture if the autopilot is engaged, but it could be something else.I was unable to get the Level D 767-300 to install without error messages, so I passed on this one for the time being (influenced by similar posts by others).As someone else said, the Dreamfleet Cessna 177 Cardinals, both fixed and retractable gear models seem to install and perform well with no problems noticed thus far.I would suggest that for those that work and have managers (i.e. load) that they be installed rather than simply copied. The utilities seem to work for most. An exception for me so far has been the Dreamfleet Text-O-Matic utility for repaints. It did not seem to work for me so I simply copied the applicable textures from FS9 and edited the aircraft.cfg's accordingly. Thumbnail.jpg's are needed just like everybody else.The old Corenado V35 Bonanza installs and performs beautifully.Don't know about everybody else, but this old mind has a little trouble remembering just how to set up some of the old timers that I have not flown for a while. I went back to FS9 on each one for a refresher course just to be sure it wasn't all me when problems like those mentioned above occured. They all still perform flawlessly in FS9.Happy Flying:RTH

I have tried installing the PSS/IFDG Airbuses by the multiple options recommended (Installing and/or copying with the recommended edits). I find that manual control is reasonable, but trying to make approaches with the autopilot is essentially not useable. Response is so sloppy that the autopilot is constantly searching and overshooting headings. Somewhat disappointing as the FMC does seem to work (Only one I have found so far)FSD - All early versions as follow:Both the Piper Cheyenne 400 and Navajo Panther fly about as well as they do in FS9 to me. (Again, these are not version 2, they are probably even better if that is possible).The Porter seems to fly manually ok, but the autopilot will not activate, radios cannot be tuned, alarms cannot be reset, and some gauges (i.e. torgue) do not work. Some of this may possibly be because I had to rem the "pc6vars" gauge or FSX would exit when this bird was selected. Happy Flying:RTH

Radar Contact Version 4.3 has been released, which will run with FSX. information about 4.3 can be found at www.jdtllc.comjd

Bump in case there is some new stuff that may have been missed.:)

Bump again, don't let this one become obscure guys?

IMHO the new updates for the MAAM R4D/DC3's and Briefing Time B25J are about the best thing going for FSX at the present time. I love them.Some have said they had issues, but they perform fine for me although a few textures would not come through. There are many others that are fine though.I have upgraded my system since my original replies to this post, so am in the process of reinstalling those I already mentioned. Thanks for this post to help this old memory to know what has already worked for me, much less what has worked for others. Kind of embrassing to have to admit that I can't remember what worked and what didn't. I have since originated an Excel spreadsheet to take the place of this old memory which I would recommend for others to do.With the new system the only bird that I have tried so far that is unflyable to me is the CS757. Everything is there and everything works, but it is such a framerate hog that it is virtually unflyable IMHO. With all other aircraft I have tried, I am getting a framerate of between 25 and 30 (my limit setting) with all sliders at max with the exception of traffic which is set at 50% (And that is a bunch). An exception would be somewhere like KJFK and over NY. There I get in the mid to high teens but they fly well. With the CS757 I am in single digits even under conditions where I am getting 30 with all of the rest of the aircraft. This bird does fly beautifully for me though on my new system in FS9 with a framerate of 30.Happy flying:RTH

Bumping of an old post is not considered proper net etiquette, if you feel this is so important then ask Tom or one of the moderators to make this a sticky post!!

Can you refer me to the net-etiquette page then?This forum is for US, as well as you. Never in your self opinionated mind, forget that?

>Can you refer me to the net-etiquette page then?>>This forum is for US, as well as you. Never in your self>opinionated mind, forget that?Ok Here it is!!http://en.wikipedia.org/wiki/Bump_%28Internet%29

Ok, everyone. I don't have specific rules myself about bumping. Private messages or contacting administrators are the means I suggest to complain about proper etiquette on the forums.Thanks

Thanks Brian

So, can this be made a sticky?

For FS2Crew users, FS2Crew works in FSX (default FSX 747 and 737 edtions at the moment, more coming...)FS2Crew primarily uses gauges, and compatibility between FS9 and FSX has not been an issue if you're interested in that kind of stuff.FSX however does add a few new things for dev's to play with (such as a real tiller only available via the SDKs), and some other new functionality with the new SDKs.It should be an interesting next two years for everyone.-Bryan

Thought maybe someone would be interested in this. If you have FS9 aircraft from FSD (old versions) and would like to import them into FSX, the following works. I have the Navajo, Cheyenne, and Porters.The problem was that if one simply copies or moves an FSD aircraft from FS9 to FSX, when the aircraft is selected an error window opens saying "FSX, Could not initalize application. Error 15 (IPM) Please contact technical support"When I click ok I get another window: "Runtime error, Tristana Exception Occured."From that time on, I can click ok and it just cycles back and forth endlessly between these two error windows. My assumption is that this is a license security measure from FSD to be sure one has purchased the aircraft. The only thing to do is bring up task mgr. and end the program.The solution for Generation 1 FSD aircraft for FSX (assuming one had them in FS9) is to install them in FSX exactly as one did for FS9. The catch is that in the installation programs there is no way to set a path to FSX. The solution is as follows:1. If you have FS9 installed, rename the root folder to anything else to protect it. In my case, I simply edited it to "Flight Simulator On Hold 9".2. Rename "Microsoft Flight Simulator X" to "Flight Simulator 9".3. Install the selected FSD aircraft with the FS-2004 option. It will think it is installing to FS9, but will put the aircraft in the Aircraft folder of FSX.4. Move both the aircraft and the FSD License Info.text to your Airplanes folder, (or the Aircraft FS9 folder or any other folder you added for these purposes. I personally see little advantage to this, but also have it on my system). You may not need to include the FSD License Info.text folder, but I did it for good measure. Whatever works huh!5. Edit your aircraft.cfg folder to include the line items so that you can see them in your FSX aircraft selections. For the Navajo for example, mine read: ui_typerole="Twin Engine Prop" and ui_createdby="FSD International". This needs to be added to all liveries and of course is required for all imported aircraft from fS9.6. Back to your root folders, Edit "Flight Simulator 9" back to "Microsoft Flight Simulator X" and "Flight Simulator On Hold 9" (or whatever you named it) back to "Flight Simulator 9".6. Add your thumbnails. I highly recommend autothumbnail2.zip for this. Easy as pie.7. Crank up FSX and enjoy the aircraft. They work for me!One note. When you are editing your root folders, you may get a window that tells you that it is a readme file or in use and that you cannot edit it. If so, simply restart your computer and then editing should be permitted.Good luck, and again thanks Chuck.RTH

One adder to this scenario:I have discovered the following problem and solution with the Porter. Need to find a replacement for two or three gauges as well, which is no biggy to me. I have found no problems with the Navajo or Cheyenne yet.The panel will not display correctly unless you Rem ("//") "gauge01=FSDPorter!pc6vars" in the "MAIN_PANEL" Window00 and the "IFR_MAIN_Panel" window 01. If this gauge is inabled, FSX will shut down when you change from spot view to the panel view. I have no idea what it displays. I first thought it was the lower first and third panel gauges, but they were also empty after a fresh install in FS9. I have customized my panels anyway and have an RMS in the left, and RKG Speed and Fuel Stat gauges in the third location. Some of the gauges do not work either (torgue and Prop RPM for example, but I may have replaced them with defaults in my original installation). I will experiment with this later. If someone else beats me to a fix for this, please so reply. It flies well if you can ignore this until we find the solution. There was no such problem with the Navajo or Cheyenne. Everything else seems to work well. A little more parking brake would be nice but this may be true in FS9 as well, I have not checked yet.Hope this is of use to somebody else. I personally like these birds.Respectfully:RTH