I've tried searching the forums to find out if this plane works in FS2004 - mixed answers (ranging from "its FSDS - it'll never work" to "no problems at all"). Since the last message was pretty old, I thought I'd ask again: Does the Yannick Lavigne / Fred Banting / Rob Young Falcon 50 CAEA work in FS9? Any issues/crashes (the software kind!)?Thanks,sg

I'm still running FS2002 so cannot offer any concrete evidence one way or the other. Having said that, if you have the plane and FS9 try it and see. Since it is FSDS -- not FSDS2 -- it is not supposed to work, but evidently some folks have found the magic formula.Racartronit means something, but I just can't remember what

Yeah - that's what I'll do unless someone tells me that I'll have to uninstall everything and start from scratch with FS9 if I do...downloading the files now...sg

I installed it sometime ago and found that the landing gear was missing. Made for an interesting hover craft! Did not proceed any further with it.Of interest, I have installed the FS9 Falcon 900 for which I did not particularly like the panel, so I took the panel file from the 50 and installed it in the 900. Works perfectly although you don't have a VC cockpit & cabin that was available in FS2002.

Thanks for the info. The VC is the biggest reason I wanted to install this bird. Any talk of an update?

I have the Falcon 50 working on FS9 pretty well, and by pretty well I mean everything works (Doors,Landing Gear, Flaps Etc.) except the upper panel on the 2D cockpit.You can get the wheels to show on almost all 2002 aircraft but so far there is no way to show the props on the older aircraft. You have to open the FS9 Cfg. file (Not the individual aircraft Cfg. but the main FS9 Cfg.) and go down about half way, From there look for a line with the following, {FrameCallNoWarn} <-- Brackets of course and the name of the plane you want to fix. I'm at work at this moment and can't remember what the numbering is but you have to change a 0 to a 1 or the other way around. At this point reboot and try out the aircraft. This works very well with the jets because there are no props involved. Give it a try. Best regards,Jan

Good news indeed - I'll give it a go tonight. Does the VC work as well?sg

The VC works perfectly. Also try this with Kirk Olson's F1 Mirage and A-10. Both look and fly very well in FS9.Jan

Generally speaking, you will find that FSDS aircraft will work fine with FS9. There are always exceptions though. The things about FSDS aircraft that seem to not work are the animations. You may not see the landing gear, propellers, and anything else that has animation. Gauges and stuff may work just fine. The bottom line is, you will have to load it to see if it works or not.....

An update:I downloaded the relevant files and a few repaints from work yesterday and installed in FS9 at home last eve. Plane with default textures looks and flies great - VC looks even better than I remember it in FS8! Some minor issues - haven't gotten the door to close yet and the FEDEX repaint was a mess (No windows/wheels). I have not altered the FrameCallNoWarn parameter yet, this may cure that issue...otherwise, I'd say a very positive experience with this plane. Thanks for all your input.sg

Gridley:Did the same as you did last night. I altered the FrameCallNo Warn parameter in the FS9 config file from "0" to "1" and everything is now just as it was in FS2K2. It looks and flys like a dream. The upper panel works flawlessly and my Fed-Ex textures are perfect. Try re-installing those again. Full VC and cabin textures, however I have noticed that when selecting a side window view in the 2D panel, it drops me to the VC view. Really not concerned as I now have back this beauty for FS9. The door will close by hitting "Shift L".CheersChris

Small virtual world, huh? Does anyone know what to modify to get the default VC position to be in the pilot's seat instead of first class?

I've been flying the Falcon 50 in FS2004 for weeks now. No problems at all. Rumours that this aircraft can't fly in FS2004 because of the FSDS design are unfounded.Rob Young

>Gridley:>>Did the same as you did last night. I altered the FrameCallNo>Warn parameter in the FS9 config file from "0" to "1" and>everything is now just as it was in FS2K2.Can you give an example of where exactly to insert that parameter and how do I specify it to only apply to the Falcon 50?

There is a section in FS9.cfg entitle FrameCallNoWarn in brackets. Under it, there is a parameter full=1, change it to full=0. Dont think you can make it specific to falcon, and I have no idea what it changes...sg