fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 It is the overtunning issue that is not being addressed. I would delay the 1.15 until fixed Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted September 21, 2013 Share Posted September 21, 2013 I would delay the 1.15 until fixed So you are me.... okay. Link to comment Share on other sites More sharing options...
Airbus339 129 Posted September 21, 2013 Share Posted September 21, 2013 Well... honestly I don't understand what this shot means ... Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 So you are me.... okay. It is just my opinion. I bought the product and have all the rights to give me opinion. I even offer some help but no one address ithttp://forum.aerosoft.com/index.php?/topic/73367-autopilot/ Link to comment Share on other sites More sharing options...
Patrick1246 353 Posted September 21, 2013 Share Posted September 21, 2013 its not thats simple LNAV isn't written in XML and its not so easy to fix the overshoot Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted September 21, 2013 Share Posted September 21, 2013 It is just my opinion. I bought the product and have all the rights to give me opinion. Sure, and its decided no, it wont be include in 1.15 and that is final. No, you cant help because we dont use any default FSX Autopilot systems. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 Thanks Joshua. Just BTW, sent an email to Mathijs that was never addressed to help him for free. I program in C++ for the last 20 years Link to comment Share on other sites More sharing options...
mrhoward 8 Posted September 21, 2013 Share Posted September 21, 2013 LOL! Persistent, this one. Link to comment Share on other sites More sharing options...
rjord 86 Posted September 21, 2013 Share Posted September 21, 2013 I for one am very happy with the airbus as it is and am grateful that the developers are releasing another update to add much more to our airbus experience. The airbus a320/a321 was never meant to be comparable to the ngx 737........ or we would have payed a whole lot more for the airbus. Roy Link to comment Share on other sites More sharing options...
DuvalM 2 Posted September 21, 2013 Share Posted September 21, 2013 I for one am very happy with the airbus as it is and am grateful that the developers are releasing another update to add much more to our airbus experience. The airbus a320/a321 was never meant to be comparable to the ngx 737........ or we would have payed a whole lot more for the airbus.Make it the PMDG price with the PMDG quality and I'll gladly pay for the little difference there is between the prices.Now, don't take me wrong, I feel that I have a better experience with the Airbus and I like it, but it has many flaws and I pulled my hair a few times with at the begining. Even with the latest versions, it still won't extablish on ILS08L at EGLL and there are many times where I have to take "manual" control of the aircraft just to keep on with the restrictions.EDIT: Just FYI, Aerosoft Airbus = 39.99 euros. PMDG 737NGX = $69.99 = 51.76 euros. Where do I send the 12 euros ? Link to comment Share on other sites More sharing options...
fly2012 2 Posted September 21, 2013 Share Posted September 21, 2013 Ok then it's delayed, definitely? Link to comment Share on other sites More sharing options...
Rafal Haczek 1612 Posted September 21, 2013 Share Posted September 21, 2013 Ok then it's delayed, definetly? Please read the reply from Mathijs given this morning: http://forum.aerosoft.com/index.php?/topic/72997-new-release-115-pending/?p=525014 In my view it cannot be explained better. A few issues are being worked on and it will be released as soon as developers and beta testers are sure everything is fine. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 there are many times where I have to take "manual" control of the aircraft just to keep on with the restrictionsIs this true about not complying to restrictions? Link to comment Share on other sites More sharing options...
DuvalM 2 Posted September 21, 2013 Share Posted September 21, 2013 Is this true about not complying to restrictions?I have had many cases where it did not. Less since 016b though, but still enough. Link to comment Share on other sites More sharing options...
jewel777 0 Posted September 21, 2013 Share Posted September 21, 2013 Absolutely not true ... with V1.10 is perfectly flyable. Most STARs are correct (I visit many airports on IVAO and FSX...) Then how you can explain this: It's KIAD/CYUL route. As you can see after ARVIE at FL230 goes in 1 min to HABBS at 9000FT! Also the DECEL point is wrong and not changeable. I have 1.10 version and HotFix 017b. I reinstalled with Admin Rights and the same happens. Link to comment Share on other sites More sharing options...
jewel777 0 Posted September 21, 2013 Share Posted September 21, 2013 Now, don't take me wrong, I feel that I have a better experience with the Airbus and I like it, but it has many flaws and I pulled my hair a few times with at the begining. I agree. Less hair and more nerves. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 I have had many cases where it did not. Less since 016b though, but still enough. Have you filed a Ticket? What did the support say? Link to comment Share on other sites More sharing options...
Patrick1246 353 Posted September 21, 2013 Share Posted September 21, 2013 those are predictions, and we said many many many times they are currently wrong, but it doesn't affect the VNAV, its only a issue with FMC alt predictions. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 those are predictions, and we said many many many times they are currently wrong, but it doesn't affect the VNAV, its only a issue with FMC alt predictions. is the VNAV working 100% fully? Link to comment Share on other sites More sharing options...
Patrick1246 353 Posted September 21, 2013 Share Posted September 21, 2013 yes Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 yes Thanks. Is this with the 1.10? Or with the upcoming 1.15? Any differences between both? Link to comment Share on other sites More sharing options...
AviatorX60 0 Posted September 21, 2013 Share Posted September 21, 2013 Could someone please clarify more specifically what "DH changed to RADIO, MDA changed to BARO" means, with respect to the left MCDU change? Does this mean that the MDA/DH fields on the approach page are being re-named to BARO/RADIO (which seems awkward) or does it mean that the system will properly differentiate between pressure altitude and radio altimeter, respectively? I am only asking because I would hope that UI fields aren't being purposely "mis-labeled" to compenstate for user errors. Otherwise, the other changes look promising. Thank you for providing us with this update! Link to comment Share on other sites More sharing options...
DuvalM 2 Posted September 21, 2013 Share Posted September 21, 2013 Have you filed a Ticket? What did the support say?I did not file a ticket, so they said nothing. Every hotfix, and releases makes it better, but at times it can be annoying. Link to comment Share on other sites More sharing options...
Patrick1246 353 Posted September 21, 2013 Share Posted September 21, 2013 Could someone please clarify more specifically what "DH changed to RADIO, MDA changed to BARO" means, with respect to the left MCDU change? Does this mean that the MDA/DH fields on the approach page are being re-named to BARO/RADIO (which seems awkward) or does it mean that the system will properly differentiate between pressure altitude and radio altimeter, respectively? I am only asking because I would hope that UI fields aren't being purposely "mis-labeled" to compenstate for user errors. Otherwise, the other changes look promising. Thank you for providing us with this update! Yes, MDA/DH is re-named to BARO/RADIO, on the APPR Page and on the FMA Link to comment Share on other sites More sharing options...
Zgredd 21 Posted September 21, 2013 Share Posted September 21, 2013 those are predictions, and we said many many many times they are currently wrong, but it doesn't affect the VNAV, its only a issue with FMC alt predictions. Will it be fixed in the future? Link to comment Share on other sites More sharing options...
![Aerosoft Team [Inactive Account]](https://forum.aerosoft.com/uploads/monthly_2023_09/Aerosoft_Social_Media_Profilbild_Neu23.thumb.jpg.03721825e6a434ed4af0c8b2b73a5898.jpg)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.