Seems to me  the fsim world is divided into obsessive tweakers and those who haven't enough confidence to fiddle with the system. Myself, I haven't tried any of the many and various suggestions for importing Fs9 aircraft into FSX , because I'm fearful of screwing up.

However,  I've found that simply copying an  Fs9 aircraft folder into the FSX SimObjects folder, and from there to the Airplane folder,  can  do the trick. Not always, obviously - FSDS and/or GMAX aircraft seem  the most likely to succeed.

Perhaps we could build up a list of those that can in fact be so easily imported? To start the ball rolling, Rick Piper's beautiful De Havilland Chipmunk [Avsim]  works fine for me.

Sound good, R.B. Thnx for the tip. I've added FS9 planes to FSX but did it the old-fashioned way.

Tricky one that. I've only tried the 748 once and I used the VC which was fully clickable for that. Hard to do a complete flight though because so many switches are difficult to reach.

But here's something that might be relevant. With many aircraft in FS2004, I find that when I first go into cockpit view, I can't click on many (all?) of the clickable switches such as the GPS toggle, the light switches and so on.

If I then place the mouse in the middle of the panel and right click...close screen, everything then works OK

The conclusion I've come to is that in some panels, there are overlays with switches etc in them which are placed precisely in the panel by putting them into a full-screen full black (ie transparent) background. However, my graphics card/drivers 'see' this overlay and make it an invisible barrier between my mouse cursor and the switches in the panel. By closing the screen, I'm removing the barrier.

Something like this might be happening for you in FSX, especially if you've updated your drivers recently, but I don't know for sure.

Quote:

Make sure that the panel or sound is not aliased to aircraft not in your fs9Aircraft folder. If necessary you can re-alias the CFGs or add panel/sound files.

While on this topic I was wanting to install my Aerialfoundery F18.
Did the folder and cofig as you mention Rollerball but am curious about the gauges, this aircraft comes with custom gauges in a cab.file.

Do I make a gauges folder in the fs9aircraft folder and place this cab file in it? I looked at the panel config and I don't see it listing a file path to the gauges if it did i figured I could change the path to the location of the cab file.

Same issue with a Stearman Package I love, gauges are in a cab file. So i guess the short version of the question is where to place cab files for gauges?

I wold like to get these working if they will and then try the MAAM SIM DC3.

Thanks Hagar was hoping that was all but figured I better check first.

PI - as I say, I recommend that you paste the gauges (and CAB files are dead easy) into the aircraft's panel folder initially.

The reason is that many panels that work well in FS2004 include 'old' gauges from earlier sims. These won't work in FSX, so you don't want to copy a whole load of 'loose' gauges into your nice, pristine FSX gauge file only to find that several are not compatible and have to be removed again. Or at worst, you have to find a complete new panel for your plane so all of the ones you've copied in are redundant.

Could get very messy very quickly. And if you leave 'bad' gauges in there you get non-stop warning messages every time you start the sim.

If you put the gauges into your plane's panel folder, if they all work OK, fine, then copy them into your main FSX gauges folder. If not, it's easy to knock out the ones that are bad until you can do something about replacing them or the panel.

Should be no need to edit CFG files. If  the aircraft is listed it will find the gauges. Suck it & see.

Thanks will give it a go later today!

Phiz. Did you read my earlier comment? I'm sure that explains your problem. You don't say which aircraft you're having problems with but I wouldn't mind betting the sound is aliased to one or more FS9 default aircraft. If these aircraft are not installed in your new fs9aircraft folder any aircraft aliased to them won't display.

Quote:

This can be very useful for various reasons. You can add as many "Aircraft" folders as you like providing you add a new fsx.cfg entry pointing to them.

Quote:

I only have the FSX Demo but from Felix's original tip posted on this forum I don't think that FSX has a default Aircraft folder.* ---> What happened to the Aircraft folder?

*PS. Quote:

I suspect you used the auto-install for these aircraft. If they were for FS9 this would have created that Aircraft folder. If your addon aircraft work in your Aircraft folder I would use that.

It's a hidden/system file skid. Check out the sticky at the top of the FSX forum for how to find it

(Check out the sticky at the top of the FSX forum)

What is a sticky???????????????????????????????????????????????????????????????????????

Quote:


Whoa!  That really SUCKS big time. This has got to be a bug as
no one in their right mind would have created this restriction
intentionally!

In FS9 I have my addon scenery, scenery and fsfsconv folders
on a totally seperate logical/physical drive so that they are
shared between the 4 seperate installs of FS9. Most all of
my panels are in that fsfsconv folder along with alot of sound
folders. Looks like FSX will negate this sort of architecture.

    Paul

Aliasing has always been to an aircraft in the same folder or to a file in a sub-folder of the folder.

As far as I'm aware you can't alias to anything that's outside of the immediate directory tree and that's always been the case.

So.....

You can alias to the panel or sound of an aircraft that's in the same folder as your aircraft

or

you can alias to a panel or sound that's in, say, fsfsconv SO LONG as fsfsconv is INSIDE the folder that your aircraft is in

but

you cannot alias anything to anything that's either above the folder that your aircraft's in or in a totally different directory structure (ie sideways) because you can't specify the complete directory path in aliasing, you can only specify a RELATIVE path downwards

Hope that's clear... ???

Doug, I bet you don't know that that's the kind of notation you use on a Unix server (or indeed a Windows server as well nowadays)

Quote:


After my post above I did some checking and concur that aliasing
in FSX works as it did in FS9, thank goodness.

As to your  "don't see any practical use for it" statement,
well, I see a very practical use for that sort of statement. As I noted
in my post upstream, I created  common "addon scenery", "scenery"
and "fsfscov" folders on my F: drive to be used for the 4 instances
of FS9 on my E:, G:, I: and J: drives.
This common repository of shared files saves alot of space.

In FSX I just moved a FS9 777-300 into my "Aircraft" folder
and aliased the sound to the 737-800 in the "Airplane" folder.

"alias=..\Airplanes\B737_800\sound"

As more aircraft become available for FSX I suspect I shall be
doing alot of aliasing to folders of my own creation in locations
of my own chosing. Right now it's not a big issue but with FS9
my aircraft inventory ( AI + flyable ) grew to 700+. Addon scenery
also became unwieldly and FS9 bogged down. At that point I created
a "clean" install of FS9 for testing, and FS9_Europe and FS9_USA
installs to differentiate the two areas where I do the majority
of my flying. Each has it's own scenery.cfg file and aircraft suites.

I suspect I shall be doing the same with FSX at some point as well.

    

This is going to sound odd.. but i don't have an FSX.cfg..

[Edit:] Nevermind, got it