Hi Joe,
That's a good change. You never want to be doing XPLMFindDataRef() on a frequent basis. A good pattern to follow is the deferred startup pattern, where you register a flightloopcallback to happen, say, every ten frames. That way, when your callback fires for the first time, you can guarantee that the sim has fully loaded all plugins. That's a good place to do the XPLMFindDatarefs, then you can unregister your deferred callback function.
[FYI] CommViewer plugin
-
- Posts: 9942
- Joined: Sat Oct 09, 2010 8:38 pm
- Location: Pompton Plains, NJ
- Contact:
Re: [FYI] CommViewer plugin
Hey Keith,
Great info! Thanks! It's the first plugin I've done that checks for the existence of
another plugin. And I only caught the continuous calls to XPLMFindDataRef because
I'm playing around with Rust and Nim language ports of the plugin.
Great info! Thanks! It's the first plugin I've done that checks for the existence of
another plugin. And I only caught the continuous calls to XPLMFindDataRef because
I'm playing around with Rust and Nim language ports of the plugin.

Re: [FYI] CommViewer plugin
I just posted a new release (v1.6.0). The output window now includes your PilotEdge aircraft type and N-number when connected to PE.
The project repo (includes pics): https://github.com/jpoirier/xplane-commviewer-plugin
The release page for downloads: https://github.com/jpoirier/xplane-comm ... n/releases
-joe
The project repo (includes pics): https://github.com/jpoirier/xplane-commviewer-plugin
The release page for downloads: https://github.com/jpoirier/xplane-comm ... n/releases
-joe