-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[bug] "Command failed with exit code 3221225781" and "Command failed with exit code 4294967295"? #6924
Comments
Could maybe the simconnect_sdk developer help out? @mihai-dinculescu |
I'll have a look 👍 |
I have done my research and have gotten and figured out that it's something with the |
as in it doesn't implement Send |
That shouldn't be a problem because nothing from SimConnect is sent between threads in your case. Also, I would expect the compiler to complain if that is true. Please try and download the MSFS SDK and place |
By the way, I do have a working example of simconnect-sdk + tauri if you're looking for inspiration. |
well tauri uses tokio and if I switch to tokio::spawn(async {}) then it gives me issues |
That gives me this
|
and this is the reason why I brought you in @mihai-dinculescu as it has to do with your thing Not trying to sound offensive sorry if I did |
that function is the same as Your only options are 1) Wrap this type in a Send type or 2) create this type inside a thread or inside the async closure and communicate with it using channels or something similar. This looks more like a "help me with rust" issue and not something specific to our API so I would suggest asking in our discord for help or in the rust discord server. |
This is where we started. I asked them to open an issue so we can loop in you, Lucas, and more importantly the simconnect maintainers if needed. Since the discussion here derailed a bit from the actual issue we were facing on discord i'll explain again what we're actually facing, and ignore the The issue we've had was that once you added Sim::new() anywhere in the tauri app, even in a command that's never invoked And for this issue it didn't matter if i used a std thread, tokio task (via tokio or tokio::async_runtime) or straight up used the main thread. The only issue i found on the internet with the same error code was about vc redist so i made sure i have various versions installed and prevented Tauri from statically linking the runtime |
Thanks for helping out btw :) And that indeed worked for me! Though i still don't get why |
@FabianLars, that is a very good description of the behavior. Btw, Tauri release builds also require the DLL to be specified as a resource. |
Okay thx adding the dll to the resources of tauri.conf.json fixed it |
Describe the bug
Reproduction
No response
Expected behavior
The app should start and print sim connect data
Platform and versions
Stack trace
No response
Additional context
main.rs
events.rs
sim_connect.rs
cargo.toml
More context can be gotten from discord -> https://discord.com/channels/616186924390023171/1105525711453827152
The text was updated successfully, but these errors were encountered: