bpcw0001

@Pils Is there no other way than Discord to get access to the Challenger beta? I've never ever been on Discord (an age thing, I guess ...), and created an account with them just for the sole purpose of getting into the HotStart group, only to find that for some reason, I cannot join, no matter what invitation link I get sent by you (thanks again for the patience, Pils). I even tried to delete and re-create the Discord account, upon which I was banned from Discord because they thought it to be "suspicious activity". Not happy with Discord.

Yes, it happens to me quite often. Sometimes(occasionally!, but by far not reliably), I am able to halt the movement by doing the following: Let's say my D-key (moving to the right side) gets stuck, and I continue to move to the right side. Then, I press and hold the opposite movement key (here, the A-key) to keep me somewhat stationary, and continously spam the stuck D-key (rapid press/release sequences). That may trick the sim into finally picking up the required "keyup" event from that D-key to make it un-stuck and halt the undesired movement. If this works or not, might also be highly dependent on your keyboard model.

Hi, I usually take a little pride in parking the Challenger right on the yellow line of the parking spot after a successful flight. That effort is kind of thwarted sometimes when I resume the flight next day, use the "restore position and trajectory" checkbox and find the aircraft parked a bit off from where I left it in the first place in terms of lateral displacement and heading. What could be the reason here? Are there limits as to how precise I can expect the aircraft position to be restored? But then, why is the heading sometimes off by up to 5-10 degrees?

Ah, I found it. M0.83 is max allowed Mach in RVSM airspace accoding to the manual, so Bombardier has apparently opted for some safety buffer.

in my case, "not work" would mean what I observed: - using Gizmo-LTS requires a serial - when waiting out the Gizmo nag screen, the Challenger asks for activation again -> so Gizmo-LTs it is not a drop-in replacement for the version that ships with the Challenger in the sense that you just replace it and everything just works as before, only better.

Ok - thanks for the info!

I tried that, but Gizmo requires a serial number. So I suppose just dropping a new Gizmo version as replacement for the existing one does not work?

Can the new Gizmo plugin also be installed into the 1.7 Challenger release? Would this even be of any benefit?

I experience occasionally failing window heat tests too in X-Plane 12.0.9-rc 5. No need to create new airframes, I can tell you from my experience that it will happen again. However, it is not a big deal in my case. I usually get it fixed by cycling the window heat from low to high settings, off and back. Sometimes, the window heat test will persistently fail, but I usually get that only when OAT is very hot (like in Riyadh or Dubai). Might or might not play a role here. Like in your case, I too never had an issue in the air.

Great! This has been bugging me all along, since I do a lot of night flying (after work )

Something similar is true for the gauge of the pressurization system: But at "normal", eye-friendly levels:

Hi, some rotating knobs on the lower pedestal don't have their marks backlit, so it is impossible to determine their position at night without turning on overhead lights: However, these knobs have backlit marks in the real CL650: Also, the wet compass lighting only faintly comes on if the brightness controls are turned up to max: While at normal integ lighting brightness, the compass stays dark: Maybe this could be looked into for a future release. Thanks

Yes, it is understood that the system will pick the best available position source. Nevertheless, how is IRS-FMS disagree fixed in flight? Can an IRS-FMS-disagree be fixed in flight at all? Unfortunately, there is no QRH info on that one available to me. Is it just disabling the IRS'es, and re-enabling them in flight, and waiting for a realign? If you fly in the Middle East with a lot of GPS jamming and spoofing, having an unreliable IRS all of a sudden is not a good thing ...

I perceive the whole WXR thing is a bit of a minefield topic. I shall steer clear of it.

I know that you are not to blame. I was hoping that you devs might have some information from Laminar that would not yet have transpired to the unwashed public.

Are there any news regarding the WX radar topic? Got caught in a thunderstorm cell in a pitch black night ... no fun. WXR would have helped.

I know that the CL600-series is generally operated at M0.80 at cruise, and I am personally totally fine with that. Still, out of interest: does any operator ever fly at max cruise? (Bombardier itself specifies a max cruise of M0.82, so I don't know where the MCRZ of M0.83 in the Hot Start FMS comes from). I have the impression that a good portion of operators go even lower, e. g. to M0.78 in cruise, even when not having to squeeze out max range. Is it just a fuel burn/cost issue, or does the Challenger display some unwanted qualities at speeds higher than M0.80?

I give up for now. My account email is verified. I tried various browsers and the Discord desktop app on Windows, and various methods of connecting to the server, but not a chance. Same problem. Some research indicates that quite a number of people who are new to Discord seem to face similar issues. The stupid thing is that Discord doesn't tell you *why* the invite cannot be accepted, so troubleshooting is a bit of guesswork. There is a mention that sometimes, the server might impose certain verification levels, like a valid phone number. Does the HotStart server require anything special? I'll have to somehow sort it out first before I'll ask for a new invite. Anyway, thanks for your help and patience, Pils.

Pils, thanks for your link. However, that one did not seem to last for some 18h either. Sorry for the bother.

Hi, old man like myself just tried to join the Discord server, but no luck. Every link I tried says "INVITE LINK - unable to accept invite". What's the deal, how does it work? Thanks for some help here.

"I noticed that when this issue occurs the temp display on the PFD is showing "--", have no idea if its related or not." I think this very likely to be the case. It appears that the Challenger loses temp information, which is equivalent to changing the temp in the takeoff perf page in the FMS, which will also lead to a deselection of V-speeds, since they need to be newly calculated based on a changed temperature. Are you using any weather addons that might cause a loss in temperature information?

I made it work. For anyone who's interested: it works when using the command phaese command_begin and command_end only, without ever using command_once.

OK, understood.

Hi, I am using FlyWithLua for my own scripting of certain functionalities. I've tried to use the commands "CL650/CDU/1/brt_up" and "CL650/CDU/1/brt_down" from within Lua scripting, but sending these commands does not have any effect at all. I can, however, assign the CDU brightness control to joystick buttons or keyboard shortcuts from the respective X-Plane configuration UI, and CDU brightness control works. What could be the issue? Are "CL650/CDU/1/brt_up" and "CL650/CDU/1/brt_down" the correct commands after all? I have many other CL650 commands that I use in my scripts, and they work just fine. Thanks

Actually, there is not only the Iridium-NEXT download issue, but the weather-related downloads via CDU have also stopped working for quite a while now. Surely I do not know what it would mean to provide an interim hotfix update, but it would definitely be appreciated if such hotfix was made in order to restore the functionality that once used to work, even more so if the 1.8 version of the Challenger is not expected to be released anytime soon.