Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xpmp 2.0 idea: shared animation datarefs #21

Open
oktal3700 opened this issue Jun 19, 2019 · 1 comment
Open

xpmp 2.0 idea: shared animation datarefs #21

oktal3700 opened this issue Jun 19, 2019 · 1 comment

Comments

@oktal3700
Copy link

If two or more plugins that use libxplanemp are active, then one of them will successfully register the OBJ8 CSL animation datarefs, and the other(s) will fail to register them, causing graphical glitches for the unlucky plugin(s), like landing gear being always retracted.

I was pleased to read about what you're doing for libxplanemp 2.0, and I hope it can go some way towards reducing the proliferation of forks of the library. The problem with the datarefs could be solved by using shared datarefs, and libxplanemp 2.0 seems like a good time to make that change, if you were so inclined to do so.

See https://developer.x-plane.com/sdk/XPLMDataAccess/#SHARING%20DATA%20BETWEEN%20MULTIPLE%20PLUGINS

@kuroneko
Copy link
Collaborator

This isn't actually relevant in xpmp2 as far as I'm aware - it uses the XPLMInstance API (https://developer.x-plane.com/sdk/XPLMInstance/) directly (which does all the dataref manipulation inside of X-Plane itself and I believe is not subject to the dataref access rules). The compat wrapper for XP10 may benefit however.

This said, I'm leaning towards making xpmp2 a standalone plugin and putting up an inter-plugin API so that way multiple consumers can use a single xpmp2 installation with only one CSL set installed, and it would resolve more than just the dataref sharing issues, such as shared TCAS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants