Patrick1246 353 Posted September 21, 2013 Share Posted September 21, 2013 Check the pdf, it is improved Link to comment Share on other sites More sharing options...
AviatorX60 0 Posted September 21, 2013 Share Posted September 21, 2013 Yes, MDA/DH is re-named to BARO/RADIO, on the APPR Page and on the FMA I'm not trying to be difficult, but that design change makes no sense to me and deviates from operational realism in a significant manner with respect to usability. MDA (Minimum Decision Height) is a particular pressure altitude entered, not a BARO reference and of course DH is the . What is the value in making this change other than potentially causing confusement by breaking something that was already modeled and labeled correctly? So, the "train your brain" philosophy doesn't apply to this case, but applies to people wanting the ability to display pounds instead of Kg for fuel? I'm just trying to understand what the purpose of this change is. Please enlighten me. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 21, 2013 Share Posted September 21, 2013 I did not file a ticket, so they said nothing. Every hotfix, and releases makes it better, but at times it can be annoying. @patrick1246 is saying VNAV works 100%? Can someone maybe clarify? Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted September 22, 2013 Share Posted September 22, 2013 I'm not trying to be difficult, but that design change makes no sense to me and deviates from operational realism in a significant manner with respect to usability. MDA (Minimum Decision Height) is a particular pressure altitude entered, not a BARO reference and of course DH is the . What is the value in making this change other than potentially causing confusement by breaking something that was already modeled and labeled correctly? So, the "train your brain" philosophy doesn't apply to this case, but applies to people wanting the ability to display pounds instead of Kg for fuel? I'm just trying to understand what the purpose of this change is. Please enlighten me. Honestly, ask Airbus. We follow their manuals and try to keep to a FMS "version" standard. One example of airbus doing cosmetic changes like this is from the vdev "pink" dot to "green" dot. Reason? I have no idea, just trying to standardize things. Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted September 22, 2013 Share Posted September 22, 2013 @patrick1246 is saying VNAV works 100%? Can someone maybe clarify? Why not try it yourself. It is present in V1.10 for a very long time now. Also, note the difference between VNAV and FMGS predictions. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 22, 2013 Share Posted September 22, 2013 Ok, I will try it. What you mean is that the predictions are being fixed on 1.15? Thanks Link to comment Share on other sites More sharing options...
Patrick1246 353 Posted September 22, 2013 Share Posted September 22, 2013 yes, with V 115 predictions are much more accurate Link to comment Share on other sites More sharing options...
JamesWhite 11 Posted September 22, 2013 Share Posted September 22, 2013 I'm not trying to be difficult, but that design change makes no sense to me and deviates from operational realism in a significant manner with respect to usability. MDA (Minimum Decision Height) is a particular pressure altitude entered, not a BARO reference and of course DH is the . What is the value in making this change other than potentially causing confusement by breaking something that was already modeled and labeled correctly? So, the "train your brain" philosophy doesn't apply to this case, but applies to people wanting the ability to display pounds instead of Kg for fuel? I'm just trying to understand what the purpose of this change is. Please enlighten me. I'll enlighten you. The purpose is to match the same modification which aircraft fitted with FMGS Rel. 1A. If you don't believe us, have a gander at this (from a document listing differences from Rel. 2+ -> Rel 1A); Link to comment Share on other sites More sharing options...
jewel777 0 Posted September 23, 2013 Share Posted September 23, 2013 OK after 10+ crash landings I finally got the "approach logic" of this beautiful bird . I must activate the approach phase 20+nm and push the loc 15nm before landing. I must say that the loc capture make the bird turn strange but it's ok since the approach wasn't straight. I managed at last to make 3 continuous smooth landings to different airports and i'm very happy! The guy above was right. The FMC values are predictions and after takeoff it corrects them by itself. Link to comment Share on other sites More sharing options...
AVFC 9 Posted September 23, 2013 Share Posted September 23, 2013 Any screenshots of the new left MCDU (seperate window shift+2)? Link to comment Share on other sites More sharing options...
Emi 5161 Posted September 23, 2013 Share Posted September 23, 2013 Any screenshots of the new left MCDU (seperate window shift+2)? What exactly would you expect to see? There are not so many visible changes, it is more the way the system operates which changed, but that will only result in a different aircraft behaviour which is hard to capture on screenshots. Best will be if you give us a little bit more time and then you can try it yourself Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 23, 2013 Share Posted September 23, 2013 When it is said that the code for the ND has been optimized. What can we see difierent on this feature? Link to comment Share on other sites More sharing options...
DH2061 3 Posted September 23, 2013 Share Posted September 23, 2013 When it is said that the code for the ND has been optimized. What can we see difierent on this feature? +1 Really want to know the answer . Link to comment Share on other sites More sharing options...
Patrick1246 353 Posted September 23, 2013 Share Posted September 23, 2013 code optimized doesn't mean you can see a difference on the ND, it means only the C++ Code is optimized Link to comment Share on other sites More sharing options...
cgentil 163 Posted September 23, 2013 Share Posted September 23, 2013 News from 1.15? Link to comment Share on other sites More sharing options...
Patrick1246 353 Posted September 23, 2013 Share Posted September 23, 2013 News from 1.15? not yet Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 23, 2013 Share Posted September 23, 2013 code optimized doesn't mean you can see a difference on the ND, it means only the C++ Code is optimized Thanks. Which other systems were recoded/optimized? Ex. Managed Flight, etc? Link to comment Share on other sites More sharing options...
Emi 5161 Posted September 23, 2013 Share Posted September 23, 2013 Thanks. Which other systems were recoded/optimized? Ex. Managed Flight, etc? You can see all the changes made in the PDF by Mathijs. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 23, 2013 Share Posted September 23, 2013 You can see all the changes made in the PDF by Mathijs. Thanks Link to comment Share on other sites More sharing options...
DH2061 3 Posted September 23, 2013 Share Posted September 23, 2013 code optimized doesn't mean you can see a difference on the ND, it means only the C++ Code is optimized OK I see , Can I ask a question though ! is it possible to optimize the formulas you used with MATLAB software in order to get better results ? (maybe you did it already , just wondering) Link to comment Share on other sites More sharing options...
AVFC 9 Posted September 23, 2013 Share Posted September 23, 2013 What exactly would you expect to see? There are not so many visible changes, it is more the way the system operates which changed, but that will only result in a different aircraft behaviour which is hard to capture on screenshots. Best will be if you give us a little bit more time and then you can try it yourself Why is it highlighted if there is no changes compared to current version? View system o MCDU (separate window) o The left MCDU can be opened as a separate window. The key combination to open this window has been changed and is now SHIFT+2. Link to comment Share on other sites More sharing options...
fsfs2 1 Posted September 23, 2013 Share Posted September 23, 2013 OK I see , Can I ask a question though ! is it possible to optimize the formulas you used with MATLAB software in order to get better results ? (maybe you did it already , just wondering) You don't need Matlab for P3D/FSX Gauge Programming, just C++ or alternatively XML programming and I am sure Aerosoft is up to standards on this. Maybe some algorithms could be polished to be more accurate like the LNAV calculator. I am sure they are aware of this. Link to comment Share on other sites More sharing options...
rjord 86 Posted September 24, 2013 Share Posted September 24, 2013 Why is it highlighted if there is no changes compared to current version? View system o MCDU (separate window) o The left MCDU can be opened as a separate window. The key combination to open this window has been changed and is now SHIFT+2. Emi did not say there were no changes compared to the current version............ he said there are not so many visible changes........ so the changes that you mention are made but not a change that can be seen in a screenshot. Roy Link to comment Share on other sites More sharing options...
AVFC 9 Posted September 24, 2013 Share Posted September 24, 2013 Emi did not say there were no changes compared to the current version............ he said there are not so many visible changes........ so the changes that you mention are made but not a change that can be seen in a screenshot. Roy Hi Roy, thanks for clarification, so this meens that all the changes that are made in the left MCDU is also changed in the seperate window left MCDU? :-) Copy/paste from readme.PDF file: MCDU (left) o ALTN Functions significantly reworked o SEC FPLN significantly reworked o Minor Fixes to DME Arcs o GO AROUND phase problems mostly solved o CI Range changed to 0‐999 o Independant Radios for VOR1,VOR2,ILS1 o Added full support for LOC Approach o BRG/DIST in PROG page updated constantly now. o ”CF" waypoint was on the wrong side when selecting a runway without finalapproach o VAPP in PERF APPR page changeable o DH changed to RADIO, MDA changed to BARO o RADIO accepts 'NO' as a field o ALT Predications significantly reworked o PPOS Mode added after discon o Some cases of wrong HOLD exit curved fixed o Vspeeds Fixed View System o MCDU (separate window) o The left MCDU can be opened as a separate window. The key combination to open this window has been changed and is now SHIFT+2. Link to comment Share on other sites More sharing options...
NoiF 8 Posted September 24, 2013 Share Posted September 24, 2013 Hello, I have question, In new update Airbus X EXT 1.15 Have radar terrain? Thank you, 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.