Jump to content

Der Michel

Member
  • Posts

    123
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Der Michel

  1. still an issue in 1.07
  2. still an issue in 1.07
  3. fixed in 1.07. Thank you!
  4. The ADIRS has to provide the temperatures at the SD together with the barometric data. So, the temp indication has to be available together with the altitude indication at the PFD.
  5. The GRID TRACK is not indicated, when it should. If you have a problem to determine how to calculate, below are two slides for northern and southern hemisphere with some examples. Northern Hemisphere: Southern Hemisphere:
  6. Check the blue triangel, green diamond and AFS value: PFD is buggy AFS CP: HDG TRK window: should also display now the TRUE value: 105 in this case
  7. @Eddie I reported now several bugs in this forum, but not all got an answer. Are they tracked? Is the forum the wrong approach to submit bugs? Somehow it would be usefull to get a feedback from the ini staff/admins. Thank you!
  8. Der Michel

    ZFWCG zero

    Had it today, with 1.06 and GSX.
  9. Wasn't there in 1.05 as I noticed it yesterday and today after update to 1.06 it's still not there. What we have is the initial (T/C), but not the one's after (S/C).
  10. As mentioned in the titel, in the F-PLN the (T/C) is missing for stepclimbs.
  11. The reference is from A350 FCOM. You can find it at scribd.com
  12. Currently a - sign is mandatory to enter a negative value, but the system has to consider the entry as a negative value if no sign was entered. So a sign is only required, if you want to enter positive temp.
  13. When entering a 3 digit TROPO the system has to add two zeros!
  14. When the CPNY WIND was uplinked, the TRIP wind has to be dashed:
  15. Even, when no performance data is avail (weights not entered) the F-PLN has to indicate the uplinked wind or the TRIP WIND. Currently there is none:
  16. @haza2 or @Eddie is this also reported to the dev-team?
  17. When a F-PLN is loaded and an ALTN is entered at the INI page: There has to be a complete ALTN F-PLN. How has it to look like at the F-PLN? Well, currently a blue EDDH followed by DISCONTINUITY is missing in the ALTN F-PLN section. It should be possibel to select a departure runway for the ALTN. Also the magenta dashes have to be blue! Real thing:
  18. I have this setup: When I now enter the route selection for the ALT RTE, I get the option to select all routes that are stored in flightplan folder. That's wrong! Notice 1/8 routes selectable: For example I can select a route EDDM/OMDB as ALT RTE for EDDH/EDDV...that's wrong. For the setup like in picture one the green icao pair at top of the ALT RTE selecetion page has to be fixed to EDDH/EDDV. That's the current "filter". As such the system should only offer routes matching this filter. In this example there is only one matching route, so it should offer 1/2 route. A NONE selection is always to be offered! The blue icao city pair field indicates the routename. If there are two routes for the same citypair stored it would be usefull if the system would add a number behind them. It would also be usefull, if this might match with the filename. You are currently storing the imported routes also in the folder. Maybe just use EDDMEDDXxx.fpl with xx a rising number? Instead of the "_INA_1742049696". Some pictures from the real thing:
  19. Hi, when spawning at the gate, the GPU stands byside the Aircraft and the cables are not connected. But according OVHD the EXT PWR is avail. How can that be the case, when the cables are not connected? If I now select the ext pwr, ... ... the cables are visible. The cables have to be visible/connected, when the OVHD indicates avail!
×
×
  • Create New...