spearlman

And, in response to Pils, can you confirm you are actually loading the DRT plugin in-game and using it?

It works for you, with the Hot Start Challenger 650, without configuring DRT to ignore any DataRefs?

Yes, I found the errors in the X-Plane log. Glad to hear it's working.

It's simple. The file drt_ignore.txt goes inside the plugins directory, not inside the DRT installation directory. For me (on Mac), that is: /Users/Shared/X-Plane 12/Resources/plugins/drt_ignore.txt The file should contain a line-separated list of datarefs to ignore. The dataref in this case is: CL650/glass/heat_on You can find some examples in the DataRefTool FAQ at https://datareftool.com/faq

Hey @RonMont, Did this fix work for you?

I experienced a crash, so I looked at the forum to find many such instances involving the DRT. I removed it and sure enough, no crash. Poking through the log, I found the following line: 2024-03-15 11:04:29 CL650[dr.c:553]: assertion "dr->value != ((void*)0)" failed: CL650/glass/heat_on So I added that dataref to Resources/plugins/drt_ignore.txt. Sure enough, no more crash on load and DRT works with the CL650. According to DRT FAQ, that could point to some bug in CL650: FAQ: Using DRT causes X-Plane to crash DRT reads every dataref published by every aircraft and plugin, on every frame of the simulation. Sometimes, they haven't fully been debugged, and may crash. (If you're a developer, the best way to do this is to run X-Plane in a debugger and look at the backtrace of the crash- if you see RefRecords::update() in the backtrace, this is likely what happened.) In any case, I find DRT is much more useful than the official Data Ref Editor, so I'm happy to be able to use it now.

OK. Reading a little more, looks like Gizmo is just a general purpose Lua integration plugin, and it looks like the license stuff is done by Gizmo only because that's how X-Aviation has implemented it. Please disregard my comments re: license activation.

Hello, @Ben Russell. Any ETA on porting Gizmo64 to macOS-arm native? It's the only plugin forcing me to use Rosetta. Another suggestion while I'm at it. I'm not sure if this is a Gizmo choice or an X-Aviation one, but might you consider making license checks less aggressive? Every 2 weeks seems unnecessary to me. License checks could happen on first activation and subsequently on updates (not update checks, but actual updates).

I have similarly excessive cockpit reflections to the OP on XP12 on macOS-arm (maybe it's specific to macOS Metal graphics APIs?). Here's the thread I started before seeing this one: I think it adds some detail not covered by the OP, specifically relating to the Environment Maps. Hope it helps, @David_M

Sorry, I see that this is a duplicate of: I'll link it back here, in case any devs think my feedback is helpful.

Yes, my guess is that cockpit reflections are implemented by Environment Maps, and that would account for these reflections in the bathroom. It may be possible to swap out the environment texture when leaving the cockpit, but it may be tricky or impossible since it is against the design of X-Plane. Are the PBR materials properties not configurable by aircraft developers? Even if fixing the environment maps are a no-go, the materials could use a few tweaks if possible.

At dawn and dusk I'm getting some really excessive and distracting reflections on the windshield and all the wood surfaces in the C650 (in XP12; I haven't tested the C650 in XP11). Here's an example of cockpit display reflections showing in a very illogical place in the bathroom: I understand this may be a limitation of X-Plane, since it's not designed for you to walk around the cabin. However, I think it demonstrates an unrealistic reflection on a wood surface. The PBR rendering is wrong. It should be duller, much less like a mirror. There's too much specular lighting with other surface materials, also, but it doesn't show as well on a screenshot as the wood does.

I've already reported this bug under the C650 support section. FYI it applies to the TBM900 as well.

There is a bug in Gizmo64 which doesn't properly handle a failed HTTP request. I get this error every time I try to fly the C650 offline.