alfamike

Hello Don, you get eight different commands as you can manage eight different engines, so it could be very possible that you're using the command tied to the right engine. I'm not using these commands so I could be wrong, but try to use either sim/engines/thrust_reverse_toggle or sim/engines/thrust_reverse_hold instead.

He should be referring to Standard->Engine Specs->tab Description->left column (general engine specs), there're both hi idle and lo idle adjustments.

Thank you Kristoffer! Altitude problem: there are two possible configurations about how to set the altitude on the FGCP, one requires that you turn the knob and the altitude is instantly armed (no need to pull the knob, that's the configuration used on our plane) and one that requires to pull the knob in order to arm it: you can see the difference as with our plane you see the altitude on the FMA as soon as you turn the knob, else you'd see it only after pulling the knob. In both cases you can disarm the armed altitude by pushing the knob. That said, was you in V/S or in IAS? What the FMA was showing? Did you get the aural 750ft before the planned altitude and the orange light was on? The best would be to have both logs in order to check it in a better way, specially the one about that flight that you have in the logs folder (even the log.txt is important, but maybe in the meantime you have overwrite it). IAS mode: you can apply more thrust using the throttles if the FMA throttle is in CLMP mode, else you must set the speed through the SPD/MACH knob Magenta line: this is something that make me crazy.

Sorry Andrea but I totally disagree. First of all we have clearly stated that the plane is not fully compatible with XP11, you can use it but not all functions will work as planned, this doesn't mean at all that our plane will not work at all with XP11 so I'll not write it because that's not true. If physical throttle control doesn't work as planned because the incompatibility you can use the mouse in order to manage the 3d throttle levers. If physical speed brakes control doesn't match with the 3d speed brakes lever because the incompatibility you can move it using our custom commands. This doesn't mean that the product does not work with XP11. I remind you that XP11, although publicly available, is still in beta and this mean that every update could suddenly change something (as a former developer you should understand this very well), we're still waiting for the very first version declared stable and this is the reason that other developers are still waiting before to update their products... I also remind you that those developers that already have published an update have had all the time they needed to check, develop, test, re-check, re-develop, re-test and so on. 'work perfectly' and 'nearly perfectly' is not the same, following your same reasoning what is 'nearly perfect' should be declared 'not working with xp11' as that's not fully functional. Thank you very much, we're working hard for obtain this goal (time to come back to the code). Best regards AlfaMike

Thank you very much Bob! Now I have to come back at work to fix that hydraulic issue (actually the only one I was able to recognise as a real bug), then I'll continue to check for the other reported issues.

Andrea, as Bob quoted that part of our product page and as Mario explained you the reasons we don't support XP11 right now you should understand why it's impossible to investigate problems with XP11 right now, we have to wait at least the first stable version the we'll can start to work for compatibility.

Andrea, as the real MD-80 disengage parking brakes by pressing the toe brakes our plane do the same, in the same way you have to press them when you want to engage them before to pull the knob. Trim setting: which commands have you assigned to those two joystick keys? If you have used the standard commands those are not the right ones, you must use our custom commands (we have created two commands to manage the long trim handle, two to manage the switches on the C/M-1 yoke and two to manage the switches on the C/M-2 yoke), the list is in the documentation. About the speed brakes lever, was the axis assigned to speed brakes before to load the plane or do you have assigned it right after?

Thank you very much Gösta! I haven't watched that (or those) stream so I can't give an opinion, as far as I know later today there was another stream where the simmer started with XP11 (bad thing) then he changed to XP10 and after some hints he understood more and more things and then he enjoyed our plane a lot... I know that bugs are present, but for me it's extremely important to understand what is really a bug and what is 'just' a procedural problem. Now it's evening here and we're really tired because this day, tomorrow we should re-release the plane and in the meantime I continue to check the code in order to start to fix initial (and real) issues. Again, thank you very much for your support! Thank you Richie! Problem is that negative 'word of mouth' (I don't know if is the right expression, sorry) runs much more faster than the positive ones, it's difficult to reach and correct all of them.

Thank you very much Kristoffer, your words are indeed a breath of fresh air. Thank you Papelino!

X-Plane 10 does use Navdata files in order to allow the GPS navigation, those files are different than the other default format (such earth_nav.dat) and those are the files that our plane needs in order to use our custom FMS system. Unfortunately X-Plane 11 no longer have those files as default due the features of the new version, but those files are still needed by a great number of free and payware aircrafts... even more unfortunately our plane is not yet fully compatible with X-Plane 11 due our customisations and the problems that are still present in the beta versions, so until XP11 will be declared final we can't start to understand why something doesn't work as planned as they do with XP10. We can't say that Navigraph data is 100% compatible as they never, never, never answered our information requests regarding their data format (Aerosoft did that in almost real time), some of our beta testers does use Navigraph data I was able to fix the incompatibilities we encountered but we can't say that we found all of them, if any... anyway like I already did if something strange will be found I'll fix that. Yes, we do know that some customers doesn't have received the confirmation mail with the serial number, I know that the store is fixing this problem but I don't know how many are now ok so if you are still waiting for the code please let me know. Yes, but only because this morning we told Nicolas that that was an early and unplanned release (we weren't ready for the release), not because problems with the plane or any complaint done on the .org (bugs are always possible and I'll fix them as soon as possible, but I really can't do too much when complaints are caused by wrong procedures, ours it not that load'n'fly kind of plane). Sales will be reopen as soon as we'll do every activities we had planned for today, those activities already planned to be done before the release.

Hello everyone, first of all I'm deeply sorry for my lack of posts today but I was (I am) truly shocked due the unplanned release of our plane, we weren't ready for this so I was unable to prompt react, I've no difficult to admit that. I sent the package to the store yesterday evening in order to short times, given the file size and my not-so-fast connection, planning to 1) check the upload this morning, 2) change our infrastructure configuration from test to release, 3) do latest checks and then 4) send all the activation codes to the store in order to make the plane finally available, so you can well imagine how I was surprised this morning when I noticed that the plane was already sold to some customers. After all of this we're now facing problems given by people that doesn't know how the plane work and/or using it on XP11, making videos and/or streams, that are given everyone read and/or watch they the worst possible message... in short four years of work are under heavy risk, not a good day at all. As you have probably noticed right now the store have stopped the sales (not sure it was a good idea, lot of people could think that the plane does have so many problems to require such a intervention) so please give us the time to sort things out and make appropriate communications. Being a piece of software bugs can be found when the plane is being used by a greater number of people on different situations and, of course, those bugs will be fixed, while it's pretty hard to explain and convince someone that something is not a bug but the result of a wrong procedure. Please be patient, and sorry for the inconvenience. AlfaMike

Thanks to all of you! That's our goal, but customers will have the last word on this!

Gentlemen, we're very happy to say that our site is finally online, another step forward the release of our MD-82! The site is available here: http://ats-simulations.com/ Other than the announcements here, you can subscribe our newsletter in order to receive our news by e-mail. Please feel free to let us know what you think and if you find any kind of problem with the site, thank you very much. AlfaMike

Very easily that plugin is a 32bit version of a third-party plugin and for this reason it isn't loaded (XP11 is only 64bit). Third-party plugins should indeed be located into their own folder so you can identify them in such a situations (not a fat-plugin type, I'd say).

Hello all, later this week we'll give some news so stay tuned!