Guys,I'm trying to get a picture of for how many people the Airbus Volume 1 does not display the SIDs and STARs on the FMGC for a review I'm doing of this airplane package for simflight.com. I myself have this problem and I'm wondering how many other people have it too. How can you see whether you have the problem or not? Easy: go make a flightplan and enter it into the FMGC. Now click the left LSK of either the departure or arrival airport. On the page you get, click either ARRIVAL or DEPARTURE (depending on what airport you chose in the flightplan), and see whether you get a list of SIDs or STARs with the appropriate runways. I myself get a blank screen with no SIDs, STARs or runways listed. You'd help me greatly if you'd check this and post here (don't forget to vote in the poll. This will enable me to get a quick view of what you guys have been coming up with).IMPORTANT NOTE: I should add one detail: make sure you have any of the more recent Navigraph updates installed! These are the ones causing trouble for me. The 0610 AIRAC cycle does work, but who would want to use that highly outdated version is beyond me.Many thanks!

I believe that they do not come with it. You must have the Navgraph update to get SIDS/STARs at every available airport. It might come with SOME airport procedures, though I can't remember which. However, last time I saw something on the Navgraph forum about feelthere/Wilco, I think I saw a statement saying that they no longer actively supported the Airbus series because they believed there was some kind of bug in the software/incompatibility issue that raised potential problems with updating the Nav database. I believe it went on to say that they (the Navgraph people) had tried to contact Wilco and/or feelthere and got no response, a behaviour which mirrors many of my issues with them as a company (that being an incosistent level of support).I found that I had regular crashes when using their software after a Navgraph update, usually just after landing, and could never get a solution to the issue. I may have solved it myself by completely wiping out the contents of the Navdata folder in the feelthere folder BEFORE installing the Navgraph update. You must also wipe out the FMGS (or whatever it's called) file in the Airbus folder, or you'll get a conflict/error/incompatibility/whatever.You must also realize that once you choose a runway and a STAR that your descent management will be screwed up (altitudes and speeds do not update). So you have to manage your own descent for any degree of accuracy. Eric Marciano offers an upgrade for the product (read: charges you for what essentially is a patch) but - for me and a few other I know of - it created more problems that it solved.Shocking issues for a payware product, in my opinion. I don't believe the product will ever be patched further, either, so they are issues that will remain forever. This is why I will not buy another product from feelthere/wilco.Hope this leads at least in the right direction, but please do your own research in case I have made any erroneous statements...- daniel

Yes, I have the Navigraph updates. The package does come with a Navigraph AIRAC that also has SIDs and STARs, however, and they do show up, but any subsequent releases of the Navigraph navdata offer me no SIDs and STARs in Airbus Volume 1, while do so in Wilco PIC 737 and Airbus Volume 2, so I'm not sure what the problem is. I'll try to wipe out the Navigraph data, as you suggest and then reinstall it, perhaps it helps.By the way, I'm also reviewing the upgrade by Eric Marciano. I have been doing test flights with it and I'm not quite sure what to think of it...

Try this with his new upgrade and see if you get the same result:After setting the aircraft up for flight and getting ready to taxi, hit the "W" key twice to move to a full screen mode, and then advance the throttles to taxi.I got substantial throttle surging, which was one of my major complaints.I did not really much improvement in the LNAV and VNAV functions of the aircraft, although I do think it sometimes managed to recalculate the descent profile (but not always).- daniel

What do you mean with "going to full screen mode"? You mean that you start up FS in windowed mode, and then go to full screen during the flight, before taxi? I have always been in full screen mode, and I have never seen the behavior you describe. Do you get the same result if you start FS in full screen mode?

Sorry, not full-screen mode as in "... versus windowed mode".Situation:FS9.1Airbus Volume 1, completely patched up.Eric Marciano's "upgrade"2D cockpitaircraft ready to taxipress "W" twice. (Once you'll be in mini-panel mode, second time you'll be in, for lack of a better term, no panel mode)Advance your throttle (I have Saitek throttles) while in this mode, to say 25% and hold them there.Wait and see what happens.I'm sure not everyone gets the same results, but I was in contact with someone on a forum somewhere (could have been here) and they had the same results. On my sim the throttles surged out-of control, likely meaning the gauge that controlled them was tied to the main panel and could not keep up with changes when the main panel was not present. I don't land or take off with the main panel active, usually only the PFD, because this gives you the proper perspective of a pilot looking out over the nose (I find). Also; it helps with fluidity during these critical phases, as the Wilco/feelther Airbus panel is an FPS hog.This did not happen with the plane BEFORE the "upgrade".Hope I was more clear this time, apologies...- daniel

Ah! Okay, I'll try that out. I have never used the mini-panel mode, which sort of explains why I never found this issue... I'll try it out and see what happens.