Simconnect not working
Bokepacha opened this issue · comments
Hello!
I only used your program once on the previous version (0.3.2 maybe?) and it worked like a charm. I installed today 0.3.3 from scratch (deleting the old version) and it's only detecting the SIM, but nothing else.
I decided to reinstall everything from scratch (your program, the WASM module and the .NET7 libraries (restarting the PC after it). The WASM module's .json file follows the expetec path of Community\mobiflight-event-module\layout.json.
GSX is on the latest version (updated today)
Debug.log says nothing to me.
debug.log
Ad this is how the program looks all the time
I am probably missing something silly, but for the love of god I can't see it :)
EDIT: I launch the program via FSUIPC, but I didn't add any info on that as the program launches correctly.
Hmm, that is interesting. It do acknowledges the Ping but does not get a Connection. That's new.
- I would need the Logs called Fenix2GSX.log
- What happens if you start the Program manually when MSFS is in the Main Menu? (Although it should be fine through FSUIPC when implemented like shown in the Readme)
- Maybe I overlooked something silly: what Happens if you use the Captain Seat Position
Fenix2GSX20230920.log
I hope this is the correct log you request.
I have started the program manually too, before starting the sim. There is no different behavior.
Captain position is where it sits by default. I just switched it to first officer right before the screenshot.
Edit: I retested the behavior by removing the lines from FSUPIC.ini and run your app by hand after the sim was already opened. No changes at all. The logs show the same information too.
My lines in the INI file are just:
[Programs]
RunIf1=READY,KILL,G:\MSFS\Utility\Fenix2GSX\Fenix2GSX.exe
I hope this is the correct log you request.
Yep :)
I have started the program manually too, before starting the sim. There is no different behavior.
No different Behaviour as in "there is no different Behaviour when starting it manually in the Main Menu"?
Captain position is where it sits by default. I just switched it to first officer right before the screenshot.
So you mean you had the same Messages with the Captain Position?
ONE Question: what did you do with you old .config File?
I am testing the previous version 0.3.2 and I see the same issue arising.
No different Behaviour as in "there is no different Behaviour when starting it manually in the Main Menu"?
Correct, the program presents the same issues and same behavior trying to connect.
So you mean you had the same Messages with the Captain Position?
Yes, you can see it in the new picture
ONE Question: what did you do with you old .config File?
Delete it.
Fenix2GSX20230920.log
Strange Indeed!
The Logs don't really give a Clue sadly:
- Please send me your .config File
- Please enable Verbose Logging (loglevel in the .config to "Verbose"), start Fenix2GSX again and retry
And which Version of the WASM Module are you using? 0.7.1?
Oh and: you are still on SU12, not on SU13-Beta, right?
0.7.1 indeed. I reinstalled everything today from scratch
Where is the config file? I can't find anything in the folder with a search of config, apart from 3 json files.
I am not on any beta, so SU12.
It is the File
Fenix2GSX.dll.config
(If your Windows Explorer is set to the Default of not showing File Extensions, it would be Fenix2GSX.dll I guess)
Maybe this is the one?
Fenix2GSX.dll.config.txt
Yes-No 😅
Yes that is the File: but where did the .txt Ending come from? And it seems that is the File from 0.3.2 right?
I added the .txt otherwise I was not able to upload it. Github was not allowing me to.
I will install 0.3.3 again
Ahh! Alrighty! 👍
Oh well...I reinstalled 0.3.3 and now it works :/ hahaha
Uhm - okay!? Apparently must have been Gremlins or something 😅
Let's hope it stays that Way! 👍