July 16, 201015 yr I know there are some very nice looking A319/320 planes out there, but I can't seem to find one with a comprehensive cockpit simulation (full FMGC etc.)I've read pretty poor reports about the Wilco/Feelthere PIC product - is there a good plane/panel combo you'd recommend?Thanks.Toni.
July 16, 201015 yr Currently the Wilco/Feelthere A320 family is the one game in town in terms of complex systems in FSX. I'm not a fan of it's external model, but that's easily correctable by merging it with the Project Airbus model. System wise it's not too bad, It models all but one realm of fly by wire protection laws. (Overspeed). I have a few videos of it, both in cockpit, and external on my youtube link below. All merged with the PA A320 (JetBlue and United). There are 2 in the works, one from Aerosoft, and the other from Flight Sim Labs. The latter I think holds the most promise, but I think it's a ways off. Thanks Tom My Youtube Videos! http://www.youtube.com/user/tf51d
July 16, 201015 yr I know there are some very nice looking A319/320 planes out there, but I can't seem to find one with a comprehensive cockpit simulation (full FMGC etc.)I've read pretty poor reports about the Wilco/Feelthere PIC product - is there a good plane/panel combo you'd recommend?Thanks.Toni.The aerosoft A320 is due next month. May be worth holding on till then, and see what everyone thinks. I'm definitely going to give it a whirl. And if it falls victim to the usual FS Airbus curse, then the Wilco offering will still be there! Ian
July 16, 201015 yr The feelthere(wilco) airbusses are actually pretty good, I've decided. I've had them a long time and still fly them.
July 16, 201015 yr The feelthere(wilco) airbusses are actually pretty good, I've decided. I've had them a long time and still fly them.I have the ft version myself.I bought mr marciano's upgrade and now it is decent. Fuel prediction is not as bad as it was.Without it was the typical wilco ...you-fill-the-gap.. addon!
July 17, 201015 yr Currently the Wilco/Feelthere A320 family is the one game in town in terms of complex systems in FSX. I'm not a fan of it's external model, but that's easily correctable by merging it with the Project Airbus model. System wise it's not too bad, It models all but one realm of fly by wire protection laws. (Overspeed). I have a few videos of it, both in cockpit, and external on my youtube link below. All merged with the PA A320 (JetBlue and United). There are 2 in the works, one from Aerosoft, and the other from Flight Sim Labs. The latter I think holds the most promise, but I think it's a ways off.I'm interested in how you merged the PA Airbus with the Feelthere model. If possible would you post how you done so.Thanks in advance Bill McIntyre Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64
July 18, 201015 yr Commercial Member I second the Wilco feelThere Airbuses.For the average user, they're good.Of course some of the nitty gritty nuances the 1 percent hard-core guys are after aren't there.FYI, FSLabs is working on an A320. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
July 19, 201015 yr I'm interested in how you merged the PA Airbus with the Feelthere model. If possible would you post how you done so.Thanks in advanceBasically it's the same for any FSX type aircraft. You can merge panel to model or model to panel. With complex aircraft, like the Wilco I normally recommend the latter, but after thinking about it, I think this will work better, and with less impact.Create your Project Airbus folder. Make it separate, from other PA folder(s) that you don't want to merge.1. rename or delete the PA folder panel folder.2. Copy the Wilco/Panel folder to the PA folder.3. Copy all the VC and interior textures, from a Wilco texture folder to the PA livery texture folder.Note: If you are going to create multiple liveries, you should create a texture fallback folder with a texture.cfg file You do this by A. rename the PA texture folder to a livery folder ie: texture.jbu (for JetBlue) B. recreate a texture folder and then do step 3 above. c. Copy the texture.cfg file from the default 737 to the texture liveries folder()This way you won't have to copy the interior files for each livery you create.4. rename the PA aircraft.cfg file. (You will need data from this file)5. Copy the interior model from the Wilco model folder to the PA Model folder.6. edit the PA model folder's model.cfg file and add the line INTERIOR=xxxx.mdl - (Where xxxx is the name of the interior model file) 5. copy the Wilco .air file to the PA folder6. copy the Wilco aircraft.cfg to the PA folder.7. Edit that file removing all the flightsim entries.8. copy the Flightsim, contact points, lights, and view sections from the original PA aircraft.cfg file in step 4.9. Make sure the flightsim entries reflect the new .air file you copied in with step 5. Same with panel, model and texture entries.That should do it. Thanks Tom My Youtube Videos! http://www.youtube.com/user/tf51d
July 19, 201015 yr Definitely the Wilco/Airbus Series Vol.1 package. Too bad I had to remove the whole thing since it wasted all of my framerates. But I did enjoy the PA models the best anyways! "It goes without saying that when survival is threatened, struggles erupt between peoples, and unfortunate wars between nations result." -HIDEKI TOJO
July 19, 201015 yr Basically it's the same for any FSX type aircraft. You can merge panel to model or model to panel. With complex aircraft, like the Wilco I normally recommend the latter, but after thinking about it, I think this will work better, and with less impact.Create your Project Airbus folder. Make it separate, from other PA folder(s) that you don't want to merge.1. rename or delete the PA folder panel folder.2. Copy the Wilco/Panel folder to the PA folder.3. Copy all the VC and interior textures, from a Wilco texture folder to the PA livery texture folder.Note: If you are going to create multiple liveries, you should create a texture fallback folder with a texture.cfg file You do this by A. rename the PA texture folder to a livery folder ie: texture.jbu (for JetBlue) B. recreate a texture folder and then do step 3 above. c. Copy the texture.cfg file from the default 737 to the texture liveries folder()This way you won't have to copy the interior files for each livery you create.4. rename the PA aircraft.cfg file. (You will need data from this file)5. Copy the interior model from the Wilco model folder to the PA Model folder.6. edit the PA model folder's model.cfg file and add the line INTERIOR=xxxx.mdl - (Where xxxx is the name of the interior model file) 5. copy the Wilco .air file to the PA folder6. copy the Wilco aircraft.cfg to the PA folder.7. Edit that file removing all the flightsim entries.8. copy the Flightsim, contact points, lights, and view sections from the original PA aircraft.cfg file in step 4.9. Make sure the flightsim entries reflect the new .air file you copied in with step 5. Same with panel, model and texture entries.That should do it.Hi,I managed to merge the wilco/cls a340 but i can't figure out how to install the liveries. i tried installing some cls liveries but it doesn't work !How do I go about installing the liveries ?Thanks !!
Create an account or sign in to comment