Pils

Can you post some example screenshots showing PFD, MFD, and first legs page on the CDU, please?

That error is unrelated. But did you also check the X-Plane sound settings?

Make sure you have an active audio device selected in Windows and sound is enabled in X-Plane settings.

There is a password box missing. Change your display’s scaling and/or text rendering back to 100%/normal size.

Yes.

Remove DataRefTool.

Once the F/O’s go-around procedure (not a checklist, technically) has been initiated it must be completed or cancelled via the top Challenger 650 menu, before advancing the F/O checklist automation (which is the function of the “check item” command). Any crash is a bug. But may be part of larger fragility in the automated F/O system. Thanks for passing on the log. Unfortunately it ends abruptly and doesn’t provide much useful debugging info.

Getting XP 12 and installing 1.7 only to that sim would be a good way of retaining 11/1.6 intact as a backup. Good idea.

What operating system? If Windows, you can do so via the Add and Remove Programs interface. You can always manually backup the prefs file and liveries from the current version. But the uninstallation should preserve them.

As it says, airport database is damaged, specifically the CL650's. Go to Output\caches\CL650 and delete airport.db.

LWR MENU on the CCP.

Suggest uninstalling the previous version manually.

Correct. HUD is now rendered by X-Plane. Feature. I think I can say with almost certainty that won’t/can’t happen (but I’m not the developer).

It is still relevant, yes. LR haven't made any significant changes that I know of.

Can you post a screenshot of the error, please? Also can you confirm you have V1.6 installed? If so, try manually uninstalling it before running the V1.7 installer.

Remove DataRefTool.

Remove DataRefTool.

There is still no way for the Challenger to get the detailed weather data it needs to properly simulate the weather radar, so no, still waiting on Laminar to provide this.

A little misleading, sorry. The Challenger is ARM-compatible, Gizmo is not (yet). It was decided not to hold up the release of the former to wait for the latter.

Welcome to X-Plane 12's whole new lighting engine.

As Cam says, these are generally all X-Plane limitations or "features". The blurring of 3D cockpit panels comes from a blooming effect and should reduce with brightness, from what I understand. These are rendered directly by the Challenger itself, so don't get affected by X-Plane effects. These are both likely artifacts of the way X-Plane does screen-space reflections, and there's nothing an addon developer can do about it. This is again an X-Plane effect. It's simulating the brightness of displays being overwhelming for one's eyes at night time. The answer, again as Cam said, is to reduce the brightness to very low, as one would need to do in real life. (The effect isn't perfect, it's probably a bit overdone, but it is what it is.) Possibly turning down texture quality one notch, depending on how much VRAM your GPU has. But, probably not.

Days, possibly hours.

The next version should be released this week.

You won’t even be given an option to register a new machine identifier.

What "issue" are you referring to? There were multiple in the thread before I split it up.