Leaderboard

I understand this - and I also like to have "development updates" on the games I play, stuff that the devs work on, plans for the future, just some chatter to read and follow along with. But we at IXEG are now just a small 2 person team with "real" jobs and families and shifting life priorities. We already talked a bit about what we could envision in the future... right now there is nothing to talk about. Tom is working slowly on converting the sounds to FMOD (which will not make them sound different at all) and we are still planning to fix some stuff like the VNAV and HOLDs, but a timeline can not be given and doing so would just not be reputable. For me the IXEG 737 project at this point is purely a labor of love. The income I get is negligible and my motivation is purely from my love for the aircraft and the good vibes and emotions I get when interacting with the users. If you want to see the 737 get developed further in the future, don´t take that motivation away. Posts like yours are a good way to kill that motivation. So as harsh as that may sound: There is nothing to talk about right now and we are also not some YouTube or Instagram channel who needs to post new content every day to keep his followers engaged.

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.