I generally shy away from sharing e-mails… but this one doesn’t contain anything private and explains A LOT. You guys can judge for yourselves.
Dear Customer,
We apologize the horrible impression you have of our model. With respect to your alert using different displays, we aren’t secure what is your affirmation or based in what information, because MSFS works with SAME CODE for all process, displays only follow RESULTS not EVENTS. If you are using an external software to test, I can not promise this work. But the inconvenience you mentioned with Autopilot is not you are indicating. We change complete the Autopilot because nor Airbus nor Boeing works with Embraer logic (at least with Autopilot setting included in panel). Additionally, we don’t modify or send code to PFD in CJ4, you can use both models at this time, and this does not affect nothing. We are only calling the gauge to send information INTO our model, NOT modifying CJ4 gauge or its behavior.
Our Autopilot does not use NAV to adjust route or follow a flight plan, NAV and APP are used as LOC mode only or manual approach for ILS (VOR/LOC). As this MSFS remove the option GPS/NAV for Airliners code, it’s necessary separate both codes. We separated with FMS button, and this is the only command used to follow FMS flight plan as it was indicated in Video tutorial 5. Just read the last comment of user @Israel, who corrected his review in simmarket when follow our indications.
“ If you wish would avoid this “abruptly down”, you need first set Altitude, VS value and button activated (not ALT) or FLCH with a speed inserted in FMS first and after modified in SPEED KNOB if you wish adjusted it, also FMS button activated too and after all this select AP. Take in mind, the button NAV is not used with FMC navigation, please use FMS. NAV or/and APP is used only to follow VOR LOC frequency or ILS, replacing the old GPS/NAV in FSX because in MSFS the airliners do not use this option now.”
The PFD used in our model was most close to real used by EJETS, for this reason we selected it because we are working in our own PFD, but this is a loooooong work, securely for the next year. However, it works very fine with our model and shows information we requested as the code ask to it. Take in mind this is a new Flight simulator, Asobo and Microsoft removed several codes used through 20 years, this obligates to all developers on market, to use several parts of them, approved by Asobo too, while we work in a new gauge. If you comment after all this is use as example AEROSOFT and their CRJ, this is not applying, AEROSOFT and Asobo are partners begging the project MSFS, they have years of distance to all of us.
Just see Captain Sim, to release their 777 with own code, they will need 2 years at least to release a decent product as they used to their clients. They only tried to provide one of their models momentarily as the new code allows, while finding a solution to the complexities of the situation. We are still experimenting and the only way to do it is on the fly. If not, would not exist more than props using as example the Diamond DA62 included as example in SDK and with analogue cockpits. Including PMDG in their DC6 recently used the GPS default in C152, why? Because create one currently is very delayed and high cost.
We don’t modify the CDU A320 for two reasons: First, we developer for Begginers and Flight simmsers it’s our mainly target, we search avoid instructions additional. If you know A320 FMS, don’t worry, you can use this, it’s the same. And second because we are obliged to respect the copyright of the Asobo, who made it, we cannot modify and add as our own, ungauged that is not ours. Same for the PFD and MAP used in our EICAS. In 737 they included the code of 787 because not all have Deluxe MSFS who include it and with the permission of Asobo they included the code modified in their product, but the logic it’s the same, they had to use what exists, there is no other way to do it for now.
This message is not searching bad relations or inconvenience with you, unlike, we search you understand why we development this product so and what is our flight plan to respect. See our Beech 99, the first turboprop for MSFS. Result of this test, our partner NextGen (my Son) created his Bandeirante working fine. Now we are working in an overhaul with all logic found for this product and securely before to end this year our ERJ will be updated and improvement.
God bless you!
Kind regards,
JOSE J GONZALEZ