Does anyone not see these problems?

[ryanf]

Hi All,

I recently reported some airbus software issues to PM. They are very busy at present and therefore could not verify whether or not the issues I reported were faults or configuration problems.

Jonathan said they were not doing any airbus work at the moment and it was ok if I reported them here to see if anyone else was aware of them. However, I would like to ask the question in a different way; does anyone not have these problems? - if so, then I would really appreciate it if you could help me figure out what I am doing wrong!

This is what I see:

1. In SRS mode with a flex power take-off, the FD commands a pitch that allows the speed to exceed V2+10 knots.

2. At acceleration altitude, the thrust momentarily goes to idle and I loose too much speed before the thrust comes back to climb power.

3. When I engage AP, the aircraft severely pitches up suddenly and then goes a little crazy trying to recapture the correct pitch.

4. T/C, T/D points are never shown correctly and keep changing the whole time even though I am in a steady climb or steady cruise.

5. When in open climb or descent, the AP often captures an altitude that is somewhere between 100 and 200 feet before the correct altitude - I often have to Alt pull several times to get the climb or descent to get to the selected alt.

6. In approach mode with managed speed, as I deploy flaps, the speed will never reduce below F speed i.e. 180 knots so I have to go into selected speed mode to achieve the correct approach speed.


Thanks,
Ryan.

[luisgordo]

Hi Ryan,

What aircraft model are you using? I ask because I had the problems you describe (1,3,6) using IFDG, though I never really identified when exactly because they did not always happen.
I now use Project Airbus, an am quite happy with it.
I also have problem #4 and #5, but in my case, the captured ALT may even be 500 above the selected one.
I am still collecting my findings of bugs of the Airbus PM suite so that they have things easier when they retake the development on "the bus".

[ryanf]

Hi Luis,

I am using the latest IFDG A320 model.

I will try the Project Airbus model instead - can you give me a link to where I can find a recent version of it?

It's a relief to know that I am not the only one to see these problems - and more importantly that there are ways around some of them!

thanks,
Ryan.

[pdpo]

Hi,

I use the IFDG A319 model and have no issues with capturing the right altitude. The only thing in flight which I have is that the plane tends to oscilate during an open climb. I have been some time ago (when enrico was working on airbus) in close contact with Enrico from PM and he had this improved. (on the downloads section of PM site you can find A319 Alitalia)
But still it is not yet perfect. A lot of the stability of the plane under project magenta depends on the load balance of the plane. I get better result when I put more load towards the front of the plane. This is due to the fact that PM controls the plane only by controlling the trim.
For ToD and ToC ... same issues ... and many other issues ....
I remember that the problem of the throttle going to idle at acceleration ...I had that too but found a workaround for it. I dont remember it 100% anymore but it had to do with what you do before takeoff (are you using the latest FCU?) When I pressed the FD button, then pulled the speed and pulled the heading I did not have this, when I pressed the FD button only (all modes in managed) I had this too.
SRS mode, same here
Green dot speed and flap extension work badly
Autotune does not work properly
calculation of efob works poorly
navdata entry has bugs (entry of sid, if in the sid a waypoint is used which exists more then ones, it seems to take the first occurency even this is far away, entry of airways fails due to aiways/waypoint mismatch eventhough the waypoint belongs to the airway...)
I have gotten a whole list of bugs and Enrico knows about them ...but they are busy ...just not with airbus...

Greetz Peter

[luisgordo]

Hi Ryan,

Here's the link: http://www.avsim.com/projectairbus/

Hope it helps!

[ryanf]

Thanks Guys for your advice.

Given that there are problems with the PM airbus software, how do you actually fly the airbus in your sims so that you avoid them while flying as realistically as possible?

Have you developed any special procedures to deal with these issues? I can imagine in the real world that there are often technical problems with the aircraft or airport equipment that requires different procedures than normal - however, they probably don't have as many technical issues all at once!

Anyhow, I'd like to know about your procedures if you have any that you have developed in order to fly with PM.

cheers,
Ryan.

[brianwilliamson]

I like most of us are have problems as well, but I am using Vista and FSX, so all problems may be slightly different.
Most testing of late has been doing Cat III landings and ILS approaches, so here is what I have seen so far.
Do not use severe turbulence. It will not keep up.
Do not do a touch and go ILS and try to do another one.(won't capture G/S)
Do not use clear weather for an ILS or it will sometimes land short on some runways if you are doing a Cat III.
Make sure you start your next flight from the end of the runway and do a complete cockpit check.
Hope this helps.
...........................Brian W.

[3202b]

Hi Ryan, I have these problems and a 1000 more unfortunately. I have not flown with PM software now for almost 10 months. I have to say I'm really disappointed with the lack of updates, this software was not cheap. It's a shame to see it shelved while I am waiting for critical updates. I can't wait to the day where it's all working correctly - I'm sure it could be very impressive.

[Matt Olieman]

I have to tell you guys this, and this comes from a good source :)

PM Airbus Software is not dead. I know for a fact, all of your issues are logged and seriously considered.

I think in general, we as customers were spoiled, when Enrico, Jonathan and Thomas sat at their computers and immediately answered (IMMEDIATELY) every concern. In my opinion, that hurts a software company, it ties them up from developing the big picture.

It's my understanding the Airbus software is very important to them, but developing it in large steps rather then tiny ones. Which BTW make a lot more sense, business wise.

I'm an Airbus customer, and I trust PM will come through.

[pdpo]

Hi matt,

I agree with you that they need to work on the big picture but as someone posted above,
paying such an amount of money and having to shelve it for 10 months , this is also unacceptable for a software company.
On top of that the customers of the airbus suite are left with little communication from PM, thus we start thinking they have stopped working on it.
I have informed myself with Enrico about the status many times and reported many many issues... they get filed but when we will have a software which makes us enjoy are airbus cockpits that is something else.
If only I would have not spend that much for PM I would have changed already to AST you know...and I think I'm not the only one.
(they also have issues, believe me, but currently many of the flights I make is more frustration of a bad landing because the autothrust started to spool up on final...or some other weird bevavior... or a crash because of lack of power for a go around....or....)

Greetz Peter

[ryanf]

Thanks Guys for information.

I agree with Matt that prioritisation is very important for a software company to ensure quality and I hope this works out for PM. I myself never experienced being "spoiled" by PM support but I am looking forward to when they will release updates.

My main focus in starting this thread was to find out if other Airbus PM users had found workarounds or "fixes" (via configuration) to the problems I posted.

I am determined to keep using the airbus PM software and not to let the problems spoil it for me. So I was hoping that there is a way of either configuring the software or flight model, or a way of flying the airbus (in terms of customised procedures) that you guys have found work for you and that still allow you to fly and enjoy!

cheers,
Ryan.

[NicD]

Last I knew my idea to have a comprehensive PM bug and work-around list was going to be hosted here. But haven't heard anything more ... any news guys?

[NicD]

Yup ... that figures :roll:

[Matt Olieman]

Nic, folks working on this site, accept the server administrator, are volunteers. There is a new version of vBulletin 3.7 (that's in Beta) that will give us more flexibility with search capabilities. That may not be enough, we'll have to wait and see.

It would be nice to have a bottomless pit of cash and say, I'll hire someone to do it. It's just not there. Although we're slowly adding more advertisers, more income. Still not enough to pay all the bills.

Our (MyCockpit.org) intent is to have a comprehensive PM bug report, and we will.

Matt O.

[NicD]

Yes understood - but I'd volunteered to do it originally. In a technical sense all it would take is an HTML page with a few tables. If site upgrades present a better technical solution later on then that's great, but we could do something simpler in the interim.

[Matt Olieman]

Yes understood - but I'd volunteered to do it originally. In a technical sense all it would take is an HTML page with a few tables. If site upgrades present a better technical solution later on then that's great, but we could do something simpler in the interim.


FANTASTIC!!!!! DO IT!!!! :) :) :) :) I'll create a link from the PM section to the HTML page.

Very much appreciate it Nic. :) :)

[Tim]

Please remember that Pm software has been in development for a very long time, upwards of seven years now. The irritating part is the suites are still not finished, and we wait ...........

[luisgordo]

Please remember that Pm software has been in development for a very long time, upwards of seven years now. The irritating part is the suites are still not finished, and we wait ...........

I think PM is a great quality product, but have to agree with your statements.

Will have to wait and see how long it will take to see some development on the airbus family suite.

[NicD]

Ok, well I'm right in a busy period now with work, but will get to it when I can.

I'll source the information from this forum so that it's simply a one-stop list of what's already publicly known amongst builders. It's not meant to be a political thing - just something by builders for builders. So I'll be inviting everyone to submit information so we can keep it all up-to-date.

[luisgordo]

I gathered this list regarding PM Airbus Suite. Many things missing, but it may be used as a base to add more things. Hope it helps.

MCDU

BUGS

- IMM Exit button does not work (ie. aircraft does not exit the holding pattern when getting to the fix). How can you exit the holding pattern? Currently, as the IMM Exit is not working, I select DIR TO the next waypoint (but in this way, the airplane fails to follow the LNAV inserted in the MCDU). “Resume HOLD” does not appear when selecting “IMM Exit”.

- How can a missed approach procedure (MAP) be inserted? Theoretically, the MAP should be implemented in the navigational database (here, Navdata). Since I guess this is something we will not see in the near future (if at all), it would be helpful to be able to insert waypoints, fixes, etc. AFTER the destination airport.

- The OVERFLY of a fix seems not to be working (the aircraft will not overfly, nor it is indicated on the ND or on the MCDU).

- SID procedures do not appear on ND map before being inserted (they should appear in yellow).

- Only 3 types of manual braking a re present in an Airbus (MIN, MED, MAX). The MAX is selected before takeoff. It is automatically deselected when disarming the speedbrakes. No need to manually turn it off after take-off.

MISSING FEATURES

- Alternate flightplan.
- Temporary Flightplan (yellow lines)

FCU

BUGS

- When cruising, you should be able to select a lower altitude and later push the knob to initiate descent. Currently, if a lower altitude is dialed with the knob (no push or pull), the airplane initiates descent immediately.

MISSING FEATURES

- Fly By Wire (FBW) module & flight protection modes.
- Side stick priority management.
- AutoLand offset.

GLASS COCKPIT

BUGS

- When the magenta circle is shown during descent (the one that indicates the planned VNAV on the MCDU) there is a horizontal line dashing through the whole diplay (also magenta).

- The descent arrow does not appear on the ND when navigating to it, and the point is never reached (ie. “Deccelerate” never really shows up on the PFD FMA area nor does the point come closer on the MCDU – it seems to move further on).

MISSING FEATURES

pmSYSTEMS

BUGS

MISSING FEATURES

- ECAM actions upon failures.

- Master Warning and Master Caution implementation.

[A320 East]

Luis-

Re: "FCU MISSING FEATURES
- Fly By Wire (FBW) module & flight protection modes.
- Side stick priority management.
- AutoLand offset."


-FBW modeling & flight protection modes are handled very well by FS Communicator and work well with PM FCU. I personally think it will be a very long time if ever when PM implements a full FBW setup as it doesn't really seem to fit the scope of what they do.

-Sidestick Priority functions are also handled with FS Communicator. I have them hooked up now and working 100% including the glareshield indicators.

-Autoland works through FSC and operates fine with PM FCU. Autoland particulars can be modified in FSC to take into account differences in setups and flight model used. I have it running and my sim lands and rolls out on the centreline with no issues.

-Autobrake function is modeled through FSC and fully configurable.

Robert Fischer has agreed after several requests to update FSC so that the indicators for Sidestick Priority functions, "Decel" and "Autoland" can all be realized through FSUIPC offsets generated within FSC and handled by most of todays interface solutions vice having to use an EPIC hardware setup. I am currently beta testing a trial version of the first updates for Robert. When all the indications are tested and working he will make the updated version available to all registered users of FSC. This is a great step forward for a great piece of software!

Thomas Richter as most of you would already know is working on a standalone Autobrake program for the Airbus - I can only guess that it will be flawless and fully functional knowing Thomas' skills.

Also, lets not forget that AST is making great progress with their suite and unlike PM it does model all the FBW functions, Auotbrake, etc....

Personally- I use the full PM suite and have spent a considerable amount of time learning about and configuring FSC which I am very impressed with. The changes being made by Robert to update it make it all the more worthwhile a package to use.

[Matt Olieman]

I bought FSCommunicator several years ago, unfortunately, it was beyond my scope and was not friendly with the interfaces I was using.

Looking at the program and it's potential, I would say it's marvelous, it just never worked for me and the support was limited.

I'm glad to hear, FScommunicator has come back alive, and I only hope, that the new additions to FScommunicator makes it more compatible with the new variety of interfaces available today.

I look forward to hear of Robert Fischer's progress :)

Matt O.

[luisgordo]

Chris,
Thanks for your reply. I have also tried the demo version of FSC, and spent some time with the configuration of the FBW module. It does have a great potential, and I have considered several times the purchase of licenses. I was already aware of the new development being made on the implementation of offsets for interaction with hardware (w/o Epic cards, that is).

The greatest drawback I am experiencing with FSC is that the communication in my network is not as fast as it probably should be, and hence the lag between a joystick input and the corresponding reaction in FS9 is for my taste too long. I am in the process of testing in a faster computer, if that may be of any help.

I would like to get FSC configured properly, because I have seen its potential, and because of the new development talking place. I hope I can post good news to this respect soon.

BTW, any idea/suggestion on getting better network performance with FSC? (I read it has to be running w/o any other program using WideFS, and that it shouldn't be placed on the same computer as MSFS). Any other tips?

Thanks!

[A320 East]

Luis,

I'm no expert with computers - and surely there's more qualified than me on this forum to advise you how to maximize the performance of your network, but here's a few "global" things I do on all my machines...

1) Thoroughly read and follow Pete Dowson's technical guide for setting up and configuring WideFS. Many important tips in this document.

2) Use TCP IP and assign individual IP addresses to all computers.

3) Update NIC driver if possible and set your connection to run at 100MPS Full Duplex mode.

4) Use the same operating system on all your machines. Clean up your machines, turn off unnecessary services, defrag your drive (I use O&O), buy, install, and run Registry Mechanic. There is a very good and thorough tweak guide I posted on the FDS forum a while back detailing this whole process.

I found that once I had done this on all 11 of my machines there was an improvement in both network and therefore sim performance.

Finally, you can adjust the network timing parameters in FSC that will give it more network access - details are in the manual, this could help solve your problem also.

[luisgordo]

Thanks for your reply, Chris.

I followed all your tips and read through all the docs, and managed to get a satisfactory networl performance.

However, the reaction time between the input at the sidestick and the actual movement of the plane is to my taste too long (and doesn't seem realistc). Moreover, it makes precise manouvers quite difficult, especially at landings. The feeling through FSC is quite different than via direct input, which I supposed it would be, but not this way :(

Do you have any idea of what parameter I may change to make response more "immediate"? What are your findings to this respect?

I am using FSC v2.0.12, demo. May there be a significant difference with respect to version 14 and/or with the registered version with respect to this issue I have?

I would really like to get this working well, as I think FSC is a very powerfull tool, and if I managed to get things right I would definitely buy licenses! Specially knowing about current development.

THANKS!!

Edit: I just saw the info in the FSC docs of how to modify the sensitivity of the analog inputs. May this help?

[A320 East]

Luis,

It would be hard for me to describe how or what to change in FSC to gain optimum performance in your specific system. The functionality and configurability that makes the program so effective and worthwhile is also a major drawback in setting it up. It will react differently in every setup dependent on network performance, computer parameters, and connected hardware.

Lots of people ask the same thing you do but I don't think there really is a magic bullet here other than to spend the time learning the manuals and thus the product inside and out. Then following carefully the described setup and calibration procedures. It is stated in the manual early on that the user will get out of the program only what he/she puts into setting it up. This is a very true statement. I know of another A320 builder who used the software with limited success until he really took the time to fully calibrate and tweak it out - he remarked that it was a night and day difference in performance....

I would hook it up with it's own screen and keyboard attached and budget 3-4 weeks of flying and tweaking before you can pull the monitor and keyboard and leave it to run on it's own.

Flight model used makes a big difference to FSC - use the one of the recommended ones in the manual.

Register the software - it's not a big price to pay for the features in relation to the big picture of your sim.

I will gladly try to help with any specific questions you have relating to the setup and calibration.

Remember the A320 is not a light aircraft - it does respond rather slowly to commands. I have multiple hours in a real level D A320 simulator and have the opportunity to go back several times a year. This has helped immeasurably in the setup of my sim and configuring the FBW performance. A buddy of mine is a 320 captain, he regularly crosschecks my sim to the real thing and confirms that it is very close. If you use the correct flight model and calibrate to the suggested performance goals of the manual you should be close too.

[luisgordo]

Hi Chris,

Once more, thanks for your reply. I decided a couple of days ago to follow your advice, and take some time to configure FSC. Right now I am at the process of configuring the G-force(1) control loop. It's going to take some time, but I already have seen a better performance of the software so far.

I'll keep you posted.

Thanks!

[luisgordo]

An update to the previous list. Just remembered I missed one thing out. I left the Autobrake, FBW, etc. items, as I believe PM is (should be) a complete package (comparable to AST, at least in price), and these are features that SHOULD be included.

Of course, there are alternatives as of today (FSC, TSR Autobrake, etc. and AST itself).

MCDU

BUGS

- IMM Exit button does not work (ie. aircraft does not exit the holding pattern when getting to the fix). How can you exit the holding pattern? Currently, as the IMM Exit is not working, I select DIR TO the next waypoint (but in this way, the airplane fails to follow the LNAV inserted in the MCDU). “Resume HOLD” does not appear when selecting “IMM Exit”.

- How can a missed approach procedure (MAP) be inserted? Theoretically, the MAP should be implemented in the navigational database (here, Navdata). Since I guess this is something we will not see in the near future (if at all), it would be helpful to be able to insert waypoints, fixes, etc. AFTER the destination airport.

- The OVERFLY of a fix seems not to be working (the aircraft will not overfly, nor it is indicated on the ND or on the MCDU).

- SID procedures do not appear on ND map before being inserted (they should appear in yellow).

- Only 3 types of manual braking a re present in an Airbus (MIN, MED, MAX). The MAX is selected before takeoff. It is automatically deselected when disarming the speedbrakes. No need to manually turn it off after take-off.

- Activating the APPROACH PHASE in the MCDU does nothing. Speed should be automatically reduced, etc.

MISSING FEATURES

- Alternate flightplan.
- Temporary Flightplan (yellow lines)
- Approach phase modelling (automatic speed reduction).

FCU

BUGS

- When cruising, you should be able to select a lower altitude and later push the knob to initiate descent. Currently, if a lower altitude is dialed with the knob (no push or pull), the airplane initiates descent immediately.

MISSING FEATURES

- Fly By Wire (FBW) module & flight protection modes.
- Side stick priority management.
- AutoLand offset.

GLASS COCKPIT

BUGS

- When the magenta circle is shown during descent (the one that indicates the planned VNAV on the MCDU) there is a horizontal line dashing through the whole diplay (also magenta).

- The descent arrow does not appear on the ND when navigating to it, and the point is never reached (ie. “Deccelerate” never really shows up on the PFD FMA area nor does the point come closer on the MCDU – it seems to move further on).

MISSING FEATURES

- DECEL Point (circled D) not shown. See also missing Approach Phase in MCDU.

pmSYSTEMS

BUGS

MISSING FEATURES

- ECAM actions upon failures.

- Master Warning and Master Caution implementation.<!-- / message --><!-- sig -->

[NicD]

Thanks for the update ... that's the sort of detail that's needed.

Do you guys think we should compile the list before or after the next major PM release? Seems that the remaining major CDU / VNAV issues (Boeing) are being worked on now so I was thinking to leave it till the next release is out. Trouble is... who knows when that will be.

[luisgordo]

Yet another update to the list. Some findings regarding the MCDU (ZFW, CG and Trim calculations).

MCDU

BUGS

- IMM Exit button does not work (ie. aircraft does not exit the holding pattern when getting to the fix). How can you exit the holding pattern? Currently, as the IMM Exit is not working, I select DIR TO the next waypoint (but in this way, the airplane fails to follow the LNAV inserted in the MCDU). “Resume HOLD” does not appear when selecting “IMM Exit”.

- How can a missed approach procedure (MAP) be inserted? Theoretically, the MAP should be implemented in the navigational database (here, Navdata). Since I guess this is something we will not see in the near future (if at all), it would be helpful to be able to insert waypoints, fixes, etc. AFTER the destination airport.

- The OVERFLY of a fix seems not to be working (the aircraft will not overfly, nor it is indicated on the ND or on the MCDU).

- SID procedures do not appear on ND map before being inserted (they should appear in yellow).

- Only 3 types of manual braking a re present in an Airbus (MIN, MED, MAX). The MAX is selected before takeoff. It is automatically deselected when disarming the speedbrakes. No need to manually turn it off after take-off.

- Activating the APPROACH PHASE in the MCDU does nothing. Speed should be automatically reduced, etc.

- ZFW seems not to be calculated correctly on the INIT B page. I get about 2 tonns more than shown on FS9 (using Project Airbus).

- ZFWCG is not calculated.

- Trim setting for take off is always DN1.5, independently of the TOW (Take Off Weight). Furthermore, on the PERF TO page, you should be able to limit the max Trim setting (where it states to introduce the Flaps position and the Trim). However, no matter what value is introduced here, the Trim always is set at DN1.5.

MISSING FEATURES

- Alternate flightplan.
- Temporary Flightplan (yellow lines).
- Approach phase modelling (automatic speed reduction).
- ZFWCG calculation.

FCU

BUGS

- When cruising, you should be able to select a lower altitude and later push the knob to initiate descent. Currently, if a lower altitude is dialed with the knob (no push or pull), the airplane initiates descent immediately.

MISSING FEATURES

- Fly By Wire (FBW) module & flight protection modes.
- Side stick priority management.
- AutoLand offset.

GLASS COCKPIT

BUGS

- When the magenta circle is shown during descent (the one that indicates the planned VNAV on the MCDU) there is a horizontal line dashing through the whole diplay (also magenta).

- The descent arrow does not appear on the ND when navigating to it, and the point is never reached (ie. “Deccelerate” never really shows up on the PFD FMA area nor does the point come closer on the MCDU – it seems to move further on).

- On the TO memo, whatever the flaps position, I cannot get the Flaps OK (no blue).

MISSING FEATURES

- DECEL Point (circled D) not shown. See also missing Approach Phase in MCDU.

pmSYSTEMS

BUGS

MISSING FEATURES

- ECAM actions upon failures.

- Master Warning and Master Caution implementation.

[luisgordo]

Anybody adding anything else to this list lately?

Just didn't want to loose track of this thread. It would be good if we could "keep it alive". Maybe it could get pinned... just a thought.

[Matt Olieman]

I think an additional post once in a while, just like you did, will help remind us all of this thread :) :)

[luisgordo]

Just though an "open issues" thread would be handy in a "support" forum...
Could even be useful to PM folks?

[brianwilliamson]

Gooday Luis, I notice you say you cannot exit a holding pattern. Well I have just spent most of the day trying to enter a holding pattern !!
No matter what I do, it will show the racetrack on the PFD for a couple of seconds as soon as I press the button and Poof..........it disappears. Result no hold.
Not sure why we have different problems.
Regards................brian W.

[Michael Carter]

Question: does PM know what type of entry to make based on your position relative to the holding pattern type and direction of the hold?

[brianwilliamson]

It should do . It is a computed hold.

..............Brian W.

[Michael Carter]

Ah, just curious. Thanks Brian.

[ToTom]

Gooday Luis, I notice you say you cannot exit a holding pattern. Well I have just spent most of the day trying to enter a holding pattern !!
No matter what I do, it will show the racetrack on the PFD for a couple of seconds as soon as I press the button and Poof..........it disappears. Result no hold.
Not sure why we have different problems.
Regards................brian W.

Really, there is incorrect still. Now I have checked it.
Has this project support?
http://www.projectmagenta.com/products/airbus.html - We provide detail rich and fully functional flight simulation software, ideally run on a PC network using our Glass Cockpits and flight systems on dedicated PCs...

There is cheating for big money!

[JonathanRichardson]

>There is cheating for big money![/QUOTE]

Hi

Who is cheating who? I'm a bit amazed by the comment in a public forum -

What re holding patterns is not working, which software and what is your customer name please? I have no idea how to see the history of the above comment and what it refers to without your name to cross ref e-mails..... ideally this kind of comment should be sent direct to the developers if you have such a serious issue or are making an allegation as such, this is a technical support forum not a venting ground, if it is used correctly this forum can be benificial to those that use it as such.

Regards
Jonathan Richardson
Project Magenta

[Matt Olieman]

There is cheating for big money!

I don't appreciate the sarcasm/crticism and agree with Johathan, go directly to the developer if you have a complaint. This is not the place for that.

We're here to help each other, not to start wars!!!!

Matt Olieman

[ToTom]

I has not was answered on mail. Never... On forum today very fast...

I waited on correcting bugs (on B737 software too) very long.

A propos hold: this function (and other functions) in free software (ex VASFMC) act very well.

PM software - It does not cost 100€...

Happy new year! And many next in expectation on correcting error in MCDU, FCU, GC, PMSystems:
http://www.mycockpit.org/forums/showthread.php?p=52755#poststop

I apologize for my english...

Regards.

[JonathanRichardson]

Hi

If you have a technical problem contact support, if you require assistance from other users then of course post here. Best to direct this to support I think unless you think other users can help you. 99% of e-mails will be answered, sometimes some get caught in spam filters - but it is unlikely to happen.

Regards
Jonathan Richardson
Project Magenta

[ToTom]

In our cockpit (b737 in Warsaw) we don't have any technical problem. We use PM (my surname - Tomasz Toboła - is on Your " pay sheet " - please, check it) with our "sys" file.
Now I want to build new cockpit (A320). I search software. I can write "sys" file to PMSystems. But I will not repair the rest bugs.

I wanted to say it only.

You write that program is full. I see that it is not full, and list of error is long. Errors are known from year. I do not want to wait next year, I will buy other program.

I prefer PM because I know it and I like. But in Airbus software is a lot of bugs.

[JonathanRichardson]

[QUOTE=ToTom;73091]In our cockpit (b737 in Warsaw) we don't have any technical problem. We use PM (my surname - Tomasz Toboła - is on Your " pay sheet " - please, check it) with our "sys" file.

Hi

Well then it is not cheating is it?

We simply say we provide detail rich simulation software - which we do. It does not say it is 100% type specific - which would be an impossible goal.

On the *first* and product pages of the website it also states:
"Important: this software is in no way affiliated to or endorsed by Airbus, Boeing or any other aircraft or avionics manufacturer. In no way is the software reflecting specific aircraft systems in their entirety."

>I prefer PM because I know it and I like. But in Airbus software is a lot of bugs.

There have been several updates to Airbus this year, but if you find a better solution then simply use it for Airbus. We have also invested thousands in the Airbus development last year, and this work is on-going. What you see on lists posted here, or perhaps on reports to support re any software, may not tally with what we consider is important re our development processes. As such they may take longer to appear or be looked at. This is not cheating, it is simply that we can't conform to several thousands of different change requests per year to every customers time line.

Regards
Jonathan Richardson
Project Magenta

[ToTom]

Well then it is not cheating is it?
OK. You have reason. Sorry.


On the *first* and product pages of the website it also states:
"Important: this software is in no way affiliated to or endorsed by Airbus, Boeing or any other aircraft or avionics manufacturer. In no way is the software reflecting specific aircraft systems in their entirety."
But it does not mean it, that old program (for example MCDU from PSS) can be better than Your!


There have been several updates to Airbus this year, but if you find a better solution then simply use it for Airbus. We have also invested thousands in the Airbus development last year, and this work is on-going. What you see on lists posted here, or perhaps on reports to support re any software, may not tally with what we consider is important re our development processes. As such they may take longer to appear or be looked at. This is not cheating, it is simply that we can't conform to several thousands of different change requests per year to every customers time line. Then it is necessary to wait for effects of Your work.
Regards.
PS. Perhaps, I have used bad word (cheating) because I use translator ( http://translate.pl/ ). Please, it don't be angry.
But I be glad, that you have written opening about Your work. It gives hope me, that sometime program will be good.