Jump to content

RALF9636

Members
  • Posts

    2,214
  • Joined

  • Last visited

  • Donations

    0.00 USD 

Reputation

2,136 Excellent

About RALF9636

  • Birthday 09/14/1973

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Recent Profile Visitors

6,753 profile views
  1. Have been away for a while and could test only today. Now MCE does not reply the checklist item at [ ]Before Start to the line -- complete //2 despite the "//2" but keeps repeating this line after a few seconds (like a normal checklist line). When I reply with "complete" MCE then confirms along the lines of "checklist to the line confirmed, continue below the line", but then after a few seconds asks again for "Before start to the line", starting an endless loop.
  2. I did. Still the same. No. I just see my responses to the checklist items.
  3. Err... no... 8700K, 1080TI here. Desperately waiting for hardware comparison tests with MSFS2024 to finally get a new PC...
  4. This looks very interesting. A competitor for GSX can't come soon enough. If SI manages to provide ground services without a menu failing to load on every second flight and without service vehicles running through each other and the user's aircraft, SI will clearly be a winner. To be a complete substitute for GSX a follow me car and parking guidance like VDGS would also be necessary though. Hopefully these things will be added later as well.
  5. Trying to find the changelog I found that version 2.2.42 actually was released already August 19th 2024. From their discord: Roy Kro — 19.08.2024 18:06 Hey Captains, FSRealistic v2.2.42 is now available for update To update, run FSRealistic, go to Update tab, and press the Update button. Fixed Memory leak, causing occasionally FSRealistic to crash during long flights 10 different sounds were broken and not playing as expected Thanks, rkApps.
  6. I miss the option "Provide ready-to-go-presets with optimal results like shown in the promo screenshots so that users don't have to spend hours fiddling around with all kinds of parameters".
  7. Confirmed. I see the same behaviour as described and shown in the video (I always set the altimeter myself so I never bothered.).
  8. No luck with 3.1.0.3. Same as before. Confirmed. I see the same behaviour as described and shown in the video (I always set the altimeter myself so I never bothered.).
  9. There is no forum (anymore), just Discord. You find the link to their Discord channel right next to the "Support" button in the FSHud main UI.
  10. It seems this is related to the "Sync Displays" option in the Fenix app. After activating this option the MCE callouts are again roughly in sync with the IAS indication on the PFD.
  11. Probably not necessary. The issue only occured since one of the latest updates of the Fenix. Previously the IAS indication was correct. So obviously this is a new bug in the Fenix and I'm sure they will fix it.
  12. So I also changed the flaps speeds in the A320_ref.txt and A320S_ref.txt files and now MCE uses the correct flaps speeds in the A321. But now obviously theses speeds would also be used in the A320 (which would be wrong). MCE seems to use the same ref.txt file for both the A320 and the A321 (and presumably also the A319).
  13. I changed this section [FLAPS_MAX_SPEEDS] 1=235 2=215 3=195 4=190 in the files A321_ref.txt A321S_ref.txt AirbusA321_ref.txt But MCE still complains "Speed to high" when going to flaps 2 at 210 kts. Can I see somewhere which ref.txt file MCE uses for the current aircraft? For the A320 MCE recognizes the correct speeds, so complains with flaps 2 at 201 kts but accepts it at 199 kts, so this does not seem to be reated to the following issue: Indeed it seems it is a Fenix issue. I monitored IAS (on the PFD) and GS (on the ND) during the takeoff run and there are some discrepancies (wind included of course). The MCE callouts are correct when I calculate IAS from GS and wind. The IAS indication in the Fenix seems to be lagging behind a little.
×
×
  • Create New...