Hi, I'm new to this site, via my quest for Airbuses, and hopefully someone can help answer my questions. I'll start off by saying that I tried to use the search feature, and exhaust other options before asking questions, so hopefully this subject hasn't already been brought up, but if so, I apologize in advance:
I downloaded an Airbus A320 in US Airways livery from the FlightSim.com download website (file 'pa320usnc.zip'). The reason I ask this question on this forum is because I think this started off as a Project Airbus plane (even though it is not directly connected to the A320 basepack that is currently available on the Project Airbus downloads page), so I'm hoping someone might be able to help me.
This download has both the aircraft and the new paints, which are divided up into an "East" variant and a "West" variant... (quite frankly I can't tell the difference-- other than each one gets its own tail number). It looks great, flies great... but here's the problem.
Rather than the sound and panel folders' .cfg files aliasing to the default 'b737_400' (like many other 3rd party twin-engine downloads do), this one wants to alias to something called...
"US Airways East Basepack with A319\sound"
"US Airways East Basepack with A319\panel"
"US Airways West Basepack with A319\sound"
"US Airways West Basepack with A319\panel" ...
respectively, depending upon which of the four combinations in the pack that you open up.
However this aircraft download didn't come with this basepack, so there's no way to utilize it. Therefore, upon loading the aircraft, I hear the propeller and see the panel of the plane I have set as my "simulator start-up default" -- The Cessna 172.
Since I think this was originally a Project Airbus plane, I went to the downloads page at this website to hunt around, but there are no separate downloads for either sound or panels in the form of any basepacks (as are requested in the "alias=" command I mentioned above). I also searched other flight sim websites as well as Google for these specific basepacks, but was not successful.
Can anybody suggest the best way to track these down?
Thank you,
-- John
New Member-- Hopefully not an old question
Forum rules
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Please read the pinned topics and search the forum before posting to make sure your question's not already been answered.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Community-driven support for Project Airbus aircraft only.
Please read the pinned topics and search the forum before posting to make sure your question's not already been answered.
Re: New Member-- Hopefully not an old question
Replace them with
b737_400\panel
b737_400\sound
b737_400\panel
b737_400\sound
Re: New Member-- Hopefully not an old question
Well yes that would normally have been my next move, but I was hoping to access the files intended by the author if they're custom files intended to make the A320 more realistic. I'd like to track them down if it's at all possible. Do you think it's possible to find them, or might these basepacks have been deleted (from their original source) years ago, thereby making my quest next to impossible? If so... then yes, certainly your suggestion is best.esg wrote:Replace them with
b737_400\panel
b737_400\sound
Thank you,
-- John
-
Kyle Schurb
- Posts: 133
- Joined: 29 Jun 2011, 02:33
Re: New Member-- Hopefully not an old question
You'll need to e-mail the author of the file. Likely, he has a custom panel and/or soundset for his A32X's on his computer, but probably removed them before uploading the paint and just forgot to re-alias the .cfg file.