Closed Berzerker closed 1 year ago
Hmm, interesting π€
In the first moment it looks like something with the runtimes though. Please run the Commands dotnet --info dotnet --list-runtimes and send/attach the Output so that we can safely exclude the Runtimes.
The debug.log is from the embedded Chromium Browser (CEF) - the warning is normal.
What would be interesting: are there Logs from Fenix2GSX itself? Would be named like "Fenix2GSX20230420.log"
dotnet --info:
.NET SDK:
Version: 7.0.203
Commit: 5b005c19f5
Runtime Environment:
OS Name: Windows
OS Version: 10.0.22621
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\7.0.203\
Host:
Version: 7.0.5
Architecture: x64
Commit: 8042d61b17
.NET SDKs installed:
7.0.203 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
None
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
dotnet --list-runtimes
Microsoft.AspNetCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
The F2GSX log doesn't look very interesting:
2023-04-20 10:52:00.247 [INF] [ App:InitLog ] Fenix2GSX started! Log Level: Debug Log File: Fenix2GSX.log
2023-04-20 10:52:00.248 [INF] [ App:InitSystray ] Creating SysTray Icon ...
2023-04-20 10:52:00.345 [INF] [ App:InitCef ] Initializing Cef Browser ...
2023-04-20 10:52:00.434 [INF] [ IPCManager:WaitForSimulator ] Simulator started
2023-04-20 10:52:00.446 [INF] [ MobiSimConnect:Connect ] SimConnect Connection open
2023-04-20 10:52:00.446 [INF] [ IPCManager:WaitForConnection ] Connection not established - waiting 30s for Retry
2023-04-20 10:52:00.565 [INF] [ MobiSimConnect:SimConnect_OnOpen ] SimConnect OnOpen received
2023-04-20 10:52:05.825 [DBG] [ MobiSimConnect:SimConnect_Receiv ] Sending Ping to MobiFlight WASM Module
2023-04-20 10:52:05.934 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Ping acknowledged - opening Client Connection
2023-04-20 10:52:06.041 [INF] [ MobiSimConnect:SimConnect_OnClie ] MobiFlight WASM Client Connection opened
2023-04-20 10:52:15.460 [INF] [ IPCManager:WaitForFenixBinary ] FenixSystem is running
2023-04-20 10:52:15.746 [FTL] [ ServiceController:Run ] Critical Exception occured: System.Private.CoreLib - Element not found. (0x80070490)
2023-04-20 10:53:10.797 [INF] [ App:OnExit ] Fenix2GSX exiting ...
Ah okay, yes the Runtimes are correct! Would also not have understood why it starts and then crashes later because of that π
Do you start it in any special Way? Through another Tool / Script? Do you start it normally or "as admin"?
I tried both manually and using the FSUIPC method of the [Programs]
block.
I didn't try running as admin, would that have been necessary? Edit: tried both regular and as admin, same error
Very strange indeed. Running it through FSUIPC does work very well for me and definitively when started manually.
Some of the strangest Errors I have seen is because People run Stuff as Admin. It is not required for any of my Tools to be run as admin. So MSFS is therefore also started regularly?
The Fenix2GSX Log is interesting though - it does not say much, but it clearly shows the Area where this Crash is happening. None of the Outputs show "Starting Service Loop" - so it is after successfully waiting for the Session to be ready and before the it can run this Loop. So it must be something in the Initialization that happens in between.
Did you change any of the Settings by Chance? If yes: which to what? In the GUI or the config File?
So MSFS is therefore also started regularly? I donβt to anything special with regard to starting MSFS, just through Steam
Did you change any of the Settings by Chance? If yes: which to what? In the GUI or the config File? The only setting I changed was to disable calling Catering, in the GUI.
Really really strange indeed!
Please attach the current .config File you have. Maybe the GUI has an unknown Bug and somehow "saved Garbage"!?
The only other Theory is that somehow the Library to access Audio-Devices and -Sessions is somehow not working in your Setup. But I need to make a special Build for you with some extra Log-Entries to analyze that further. What you could try in the mean Time: if you disable the GSX Volume Control and also the VHF1 Control (by setting it to empty) - does it work then? (Note that you might need to configure VHF1 manually in the .config File by setting it to an empty String "" )
Sounds like the VHF app is indeed the problem, I didn't have vPilot open, if I open it before the app launches, then it all starts up fine.
Ahhh okay!!! π
Then use that Workaround a little longer (hours / 1-2 Days). I'm currently finishing and testing the new Version 0.2.8 which improves the whole Audio Controlling! I'll specifically test if these Changes have fixed that Bug of course π
No worries at all.
I did also have an issue where the door didn't close (I have auto door simulation disable) when boarding/fueling was completed. I verified the parking brake and beacon were both on as well, and GPU disconnected (from overhead). Anything else I missed?
Hmm hard to tell like that. Since Asobo decided to add some own automatic Door-Handling-Code with SU12 - which does not help anybody but annoys everybody - it could be just a MSFS Glitch. The only Situation I could think of is that you don't have waited for the Final Loadsheet? Only after that LS was triggered, the Tool will react on Ext Pwr+Beacon+Brake to remove the Ground-Equipment and Close the Door. Or maybe it even was not triggered at all - it will only be triggered if Refueling and Boarding are recognized as finished.
Do you still have the Log from that Situation?
Boarding and fueling were both finished, and I believe I got the loadsheet before flicking the switches.
The log isn't very interesting:
2023-04-20 13:19:15.657 [INF] [ GsxController:RunServices ] Boarding completed
2023-04-20 13:19:16.772 [INF] [ GsxController:RunServices ] Sending Final Loadsheet in 117s
2023-04-20 13:20:47.424 [INF] [ GsxController:RunServices ] APU Bleed enabled - removing PCA
2023-04-20 13:21:26.100 [INF] [ GsxController:RunServices ] Sending Final Loadsheet
2023-04-20 13:21:51.619 [INF] [ GsxController:RunServices ] Preparing for Pushback - removing Equipment
2023-04-20 13:21:51.793 [INF] [ GsxController:RunServices ] Removing Jetway
2023-04-20 13:21:52.888 [INF] [ GsxController:RunServices ] State Change: Depature -> Taxi-Out
2023-04-20 13:33:51.117 [INF] [ GsxController:RunServices ] State Change: Taxi-Out -> Flight
2023-04-20 15:52:58.172 [INF] [ GsxController:RunServices ] State Change: Flight -> Taxi-In (Waiting for Engines stopped and Beacon off)
Well in that Case, yes ^^ The Log shows the normal Process as it should be. At "Sending Final Loadsheet" the Tool commands to close the Door (no toggle Command, so it will close or stays closed).
Do you have the Auto-Jetway Simulation also disabled? And you're 100% sure that it did not close at all? Or could it be that you did not see it close and then triggered to open again by something else maybe? And: you did not trigger anything in the EFB in terms of Loading, right?
Does that happen every time everywhere? Or in which Situations does that happen?
Version 0.2.8 is now available - please check if it works without Workaround now! :)
Just tried and yep it seems to work fine now! Thank you.
Nice! Another Case closed :)
Hello, I'm trying out this app, have verified I have the .NET runtimes, WASM module and GSX Pro installed, but am getting the following error when it tries to start up
Also noticed this error in the debug.log
Any pointers?