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

Thank you for your great work! Partial solution for MSFS 2024 in Go #8

Closed
vsychov opened this issue Jan 1, 2025 · 4 comments
Closed

Comments

@vsychov
Copy link

vsychov commented Jan 1, 2025

Hello,

I just wanted to say a huge thank you for all the effort you put into this project. Your work with MSFS 2020 and EFBConnect has been incredibly helpful, and I appreciate the time and expertise you invested.

However, I noticed that EFBConnect doesn't seem to function correctly with the new MSFS 2024 release. Since I'm not a .NET developer, I ended up creating my own partial solution in Go and C/C++ to capture and broadcast the necessary data for MSFS 2024.

If anyone else finds this helpful or wants to expand upon it, I’ve shared my repository here:
https://github.com/vsychov/msfs-2024-skydemon/releases

Thanks again for your original code and for making it available to the community. Hopefully, this information can be useful for others who need MSFS 2024 compatibility.

Best regards

@ollyau
Copy link
Owner

ollyau commented Jan 1, 2025

Very neat! Though, I'm curious: what happens with MSFS 2024?

I no longer have a ForeFlight subscription (I haven't flown for real lately, and I can't personally justify the subscription cost for using it solely with flight sim), so I haven't tested it myself since the new sim's been available -- but I do have other SimConnect addons that still work, so I'm wondering what seems to be the issue?

@vsychov
Copy link
Author

vsychov commented Jan 2, 2025

@ollyau ,I’m not sure what changed, but EFBConnect stopped working with MSFS 2024. Perhaps something in the API was modified. I couldn’t build it for debugging, as the new msfs 2024 SimConnect DLL version requires a newer .NET version, and there seems to be an issue with the project dependencies.

@ollyau
Copy link
Owner

ollyau commented Jan 10, 2025

I couldn’t build it for debugging, as the new msfs 2024 SimConnect DLL version requires a newer .NET version, and there seems to be an issue with the project dependencies.

As noted in the readme, as well as issues #2 and #3, EFB Connect uses a third-party SimConnect client (BeatlesBlog.SimConnect by Tim Gregson), not the version provided in the Asobo SDK. If you want to build/debug your copy, I provided instructions for building the project in issue #3 (comment).

I’m not sure what changed, but EFBConnect stopped working with MSFS 2024.

I'm still not sure what you mean by "stopped working" -- does the EFB Connect application crash? Does it open, but fail to connect to the simulator? Do you not see anything in ForeFlight?

The SimConnect server in MSFS 2024 maintains backwards compatibility with FSX SimConnect clients (including BeatlesBlog SimConnect), which I've confirmed in other projects as well as EFB Connect.

Additionally, I've specifically just tested EFB Connect with MSFS 2024 (version 1.2.11.0, released yesterday, January 9th) and it seems to be functioning as designed for me -- the application opens, connects to the simulator, and sends the XGPS (position), XATT (attitude), and XTRAFFIC (traffic) datagrams over UDP, as specified in ForeFlight's Simulator GPS Integration documentation. Though, as previously noted, I no longer have a ForeFlight subscription, so I can't currently test that ForeFlight receives the data correctly (or complies with what their documentation outlines).

Have you tried both the Broadcast and IP Address options? I've heard anecdotes from other users that despite ForeFlight's documentation (or perhaps some configuration with Windows / .NET?), ForeFlight may no longer be working with the Broadcast option. Perhaps try setting the IP address of the device that's running your copy of ForeFlight (i.e. your iPad / iPhone)?

@ollyau
Copy link
Owner

ollyau commented Feb 2, 2025

Since I haven't heard back and haven't been able to reproduce the issue, I'm closing the issue for now. If anyone has further context, feel free to let me know!

@ollyau ollyau closed this as completed Feb 2, 2025
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