Jump to content

TMV45

Members
  • Posts

    31
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

TMV45's Achievements

Apprentice

Apprentice (3/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. @Pils @skiselkov I think I located the cause of the ILS procedures not properly depicted on the PFD (and subsequently not flown). It seems to be caused by custom changes I made in user_*.dat files. I tested the ILS procedures in a clean XP environment with a fresh CL650 install. The default nav data work well as well as a clean install from the recent AIRAC. But when used with the custom changes, the ILS depiction fails of all airports I checked. It only does this with the CL650 and only as of the previous version. I'm curious what mistake may I have made? What to look for? I appreciate your support! user_nav.dat user_fix.dat
  2. @Pils Sorry for the delay, vacation time came in between. Sofar I haven't found an ILS that does work. Here an other example in Greece (LGRP/ILS24Y). How many examples do you need?
  3. @Pils sure, but what are you looking for? Setup? In this case I actually just programmed to fly a pattern with an ILS approach. You want a screen shot al different ILS approaches at different airfields?
  4. Hi, With the latest version I have this strange behavior when flying an ILS. The flight path is not connecting to the IF. I checked a number of ILS approaches and all have the same issue. RNAV and other approaches do not have this issue. The plane also follows the depicted path. What is going on here? Thanks for your help.
  5. @skiselkov I tested again today with latest version. But now I get this at ILS approaches (only). But now I get this (at the IF). This is ILS24Y @ EHRD but it happens at all ILS approaches at EHRD and EHEH. RNAV and VOR approaches are OK. I also flew it, but it follows the approach as depicted. I use the latest AIRAC
  6. Any idea yet why it doesn't transfer to ILS?
  7. So, after iterative testing it appeared that something in the CL650 install got broken. After update it works well again. I tested: - updated GPU drivers => fail - Fresh clean test install of XP => pass - Old install with only global scenery and gizmo => fail - Updated XP again (only 1 light related file updated) => fail - copied CL650 data from fresh install to old install => pass - activated scenery and plugins again => pass
  8. Hi, Today I suddenly experience weird green lights in the CL650: I didn't have this before. I do not have this with other planes (like Toliss, TBM, Zibo). Also system reboot doesn't solve it. I do not use shaders and no night vision or so. Later on the day, all is normal again: Any idea where I should look for a solution?
  9. Fine with me. Just noticed that these are the most obvious items that were not reset.
  10. Hi, If I restart a flight while using the plane in the non-persistent mode, I noticed 2 small inconsistenties: 1. The anti-collision light remains on (other switches are reset to off) 2. 2 covers remain on the plane - this is especially annoying as you get the warning message after starting the engines. I use the non-persistent flights for fs-economy mainly. Regards, Taco
  11. @skiselkov I tried the same flight with the TBM and that went swimmingly. I'm happy to hear what I did wrong.
  12. @skiselkov attached 2 (very poor from XP internal) video's. I hope you can still see enough, otherwise I'll make 2 new ones. 1st is the FMC set-up before departure. I noticed the ILS course is 000 - should be 236 2nd is just after the IAF till (almost) the runway. The FMC does not change to the ILS.
  13. I tested again today (BIRK, rwy 19, ILS Z selected) Took off from BIRK, directly to IAF on the FMS. Nav source on take-off were FMS1 & FMS2. I expected - the localizer frequency selected automatically - but it never happend. So I tuned the loc frequency manually in VOR 1 & 2 - the dashed blue line when getting close to the ILS beam - but it never came - after turning based on the FMS onto the runway heading, the system still didn't automatically switch to the ILS - but manually selecting the NAV source did work well this time The FMS is capable to automatically pre-select the localiser frequency and switch over to the ILS, isn't it?
  14. Hi, I think I saw some videos where the transition from FMC to ILS went automatically. But it doesn't work for me, so probably I missed something. So I'd appreciate some advise. - I select an arrival ending at an IAF of the ILS approach; - I noticed that the localiser was not automatically tuned (while flying the arrival) - The blue dashed lines did not appear, the cyan FMS remained the active nav source - manually selecting the ILS as nav source was not available So, what did I probably forgot? Regards
×
×
  • Create New...