-
Notifications
You must be signed in to change notification settings - Fork 60
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
Program crash when running on no UE editor PC after package. #22
Comments
Hi, did you fixed it? I have same problem.... |
@alonezhby not yet~ i hope the developer has the solution to save my project : ) |
Hi, was this ever solved? Encountering something eerily similar in my project. Wondering if it's a Windows 11-specific issue? |
I also have this problem. Is there a solution? |
For anyone else still having this issue, it is because the Mosquitto DLLs ( If you want to use this plugin on a system without the MSVC toolchain installed, you'll have to replace the Mosquitto DLLs with ones that are built in the RELEASE profile. These are not dependent on the debug DLLs and will work on any Windows system with C++ runtimes installed (which is required by Unreal Engine anyway). |
Any update? I have tried release dlls as well Installed VS as well but of no use |
@ahsan4313 Did you rebuild Mosquitto from scratch yourself to get the release DLLs for mosquitto.dll and mosquittopp.dll? If not, I would suggest doing that. In the case you can't get that working, I've attached my DLLs here. Downloads will expire after 180 days though. |
Sure. Thank you very much for sending me yours. Let me try these. Can I get your code how you have build from start that will be a great help for me and how I can make this work for quest APK as well any help |
Didn't work for me. the above dlls you shared |
Android third party files end with “.so” not ".dll" |
for .dll i am talking about its not working in the system where unreal editor is not installed. And yes for quest 2 apk, i have only .apk after packaging, i have installed in quest 2 but its not working. |
where should i place .so file? i have found in binaries of the project help me out @MonsterGuo |
Same as the title.
I tried install vc++2010 to 2019, but it doesn't work.
[2022.06.27-01.59.27:636][226]LogThreadingWindows: Error: Runnable thread MQTT crashed.
[2022.06.27-01.59.27:636][226]LogWindows: Error: === Critical error: ===
[2022.06.27-01.59.27:636][226]LogWindows: Error:
[2022.06.27-01.59.27:636][226]LogWindows: Error: Fatal error!
[2022.06.27-01.59.27:636][226]LogWindows: Error:
[2022.06.27-01.59.27:636][226]LogWindows: Error: Unhandled Exception: 0xc06d007e
[2022.06.27-01.59.27:636][226]LogWindows: Error:
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x000007fefd75a49d KERNELBASE.dll!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x00000001475afa4e AirsimProj-Win64-DebugGam!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x0000000146822e5e AirsimProj-Win64-DebugGam!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x0000000140aaa285 AirsimProj-Win64-DebugGam!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x000000014195a73f AirsimProj-Win64-DebugGam!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x0000000141950c50 AirsimProj-Win64-DebugGam!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x000000007760652d kernel32.dll!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error: [Callstack] 0x000000007773c521 ntdll.dll!UnknownFunction []
[2022.06.27-01.59.27:636][226]LogWindows: Error:
[2022.06.27-01.59.27:636][226]LogWindows: Error: Crash in runnable thread MQTT
[2022.06.27-01.59.27:650][227]LogExit: Executing StaticShutdownAfterError
[2022.06.27-01.59.27:650][227]LogWindows: FPlatformMisc::RequestExit(1)
[2022.06.27-01.59.27:650][227]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3)
[2022.06.27-01.59.27:650][227]LogCore: Engine exit requested (reason: Win RequestExit)
The text was updated successfully, but these errors were encountered: