Hi all! It seems there is no way of saving co-routes after typing in manually even a long haul flight which this plane is designed for. But there are additional issues I have experienced during my flights.
1. In the pacific regions (while flying from Perth to Auckland) the vario stripe on the PFD continuously flickers, jumping anywhere between 2-300ft, even while standing at apron.
2. When in DES phase, after I set the target to descend, it goes into a real fall, it goes up to -6-7000ft/min and spoilers often don't work. Voice confirmation comes well saying it is at half or full, but you can't see them from outside and also they have braking effect. This happened fairly often, usually after a long haul flight.
3. Last time when I flew from Perth to Auckland, when reached FL100 during descend, the sim stopped for a couple of seconds, then I found myself in a desert, with engines stopped and AP saying: Next time landing should be good. When I checked the map, I realized I am standing in the desert of Arizona! near the mexican border! A few mins later XP11 crashed. I got a photo of standing there.
4. The fact that I cannot find any flightplanner that could export in a format that this plan's FMC could read is really annoying. Especially because there is no possibility to save the FP I typed in manually. I usually fly long hauls with a LOT of fixes, VORs to fly through, so it takes a LONG time to type in and if there is anything happen in the meantime, I have to start it again. Why there is no description of the file format that it reads without a problem so I could make a script or so, to import from other formats? EFASS claims they export to JAR's a320 but a320 cannot load the plan EFASS exports, neither does A330. I tried a lot of flightplanners, spent a lot of money on PFPX, EFASS, X-FMC and so on and still I can't get a tool that would make it easier to load a flightplan into this a330. It is REALLY bothering, because solving this issue won't need much effort, JAR should only release the format that a flight plant has to follow in order to be readable by A330's FMC. It's all about input, nothing else, so no difficulties are epxected. If I type it in manually then almost any flight planner is suitable. But no, I have to type it. I am really angry about this, because otherwise it would be a nice plane to fly, but as we usually say, only a very small piece of shit can spoil even the most nicely prepaired dinner table ![sad](http://jardesign.org/forum/img/smilies/sad.png)
4.