TMV45

@danmgro @Cameron what I usually do is fly in HDG mode close to the planned route, than do a DTO to the activated waypoint in order to be sure I am on the route, and then switch to GPSS. However, as soon as I do that, the plane turns to the left and doesn't come back to the planned route. So I end up flying in heading mode. I use the GTN 750/650 Any suggestions?

I try to get the RXP 750 to work with the MU-2B V2. I hoped it would work with the GPSS activated, but if I activate the GPSS, the plane turns in a random direction and continues in that direction, whatever I do with the heading bug. Am I missing something?

@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

@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?

@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?

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.

@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

Any idea yet why it doesn't transfer to ILS?

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

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?

Fine with me. Just noticed that these are the most obvious items that were not reset.

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

@skiselkov I tried the same flight with the TBM and that went swimmingly. I'm happy to hear what I did wrong.

@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.

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?

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

@Pils Thanks

Hi, In Toto's video's I noticed that you can see the landing weight on the MFD. But I do not have that. Is that a setting somewhere? Thanks for the advice. Regards, Taco

So... the installer does not check if it's up-2-date? That is what I expected as it works like that in most other apps. I'll try this, and sure come back if it doesn't work.

Hi, I tried updating to the latest version and get this error: I checked and it happens with both installations, while updating and with new installation. How to solve this?

Indeed, this issue is resolved it seems

Hi, I have unfortunately not been able to load this aircraft as every time XP crashes when loading. - I tested various airfields at various continents; - Loading any other aircraft gives no issue (default C172, TBM, Toliss A321, Q400) - removing all scenery and plugins (and other aircraft) makes no difference - loading first another aircraft and than moving to CL650 makes no difference Please see the log file included. Regards, Taco Log.txt

I've read this one. Only thing I didn't check is the hydraulic. I'll check tomorrow.

Hi, When I use the new 'click & hold' function for speed dialing the DH, I get a negative value. I think it''s because of this: - with single clicks, the value works 'clockwise' - if the icon shows right turns, the DH goes up, if the icon showa left turns (anti-clockwise), the DH goes down till '0'. - with the click+hold, it does nothing if the icon show anti-clockwise (left), and decreases the DH if the icon shows clockwise turns. The decreasing goes even below the '0' and becomes negative.

That's correct, as I mentioned, I tried with both options