2 hours ago, marcom said:

The FMC TIMEOUT message is visible until aviaServer connects with the 777.

So, MSFS needs to be running and the 777 needs to be fully loaded. Then only will the message disappear.

I'll try it again in a while to double check but it seems that if aviaserver loads too soon in the list of all the things that load up then the FMS timeout message will appear. if you restart it it works fine.

so....Just started MSFS (as admin..always do). during start up Aviaserver launched and went to system tray. When 777 had loaded at gate and had settled down. I opened the FMS on my tablet and had the FMS timeout message. I closed both the  browser on the tablet and aviasever. ran aviaserver manually and then opened the browser on the tablet and all was good.
It's not a bg deal for me I just thought it might help diagnose for anyone else having the same issue.

Edited July 4, 20241 yr by BrianT
additional info

Indeed, it works when you start aviaserver twice after the 777 has loaded and sits at the gate.
Not a big deal but perhaps it can be fixed in a future update

 

Yes can confirm also need restart

Hi guys,

not really sure yet what's going on.

Anyone experiencing this, can you please test this version:

http://www.aviaworx.com/files/not_released/aviaserver_05-jul-24-134604.zip

It won't fix it, but it adds more message logging.

So after doing the same procedure, please send me a help request so I can take a look.

Thanks!

I have sent a help request as you suggested. I didn't close and open aviaserver before sending the request as I thought it may lose the logging on restart but I can do it again if you need me to.

Thanks Brian.

So what's weird is that MSFS (via SimConnect) is not reporting any aircraft loaded.

Are you using any special tool to load the aircraft? Or is it the default opening screen where you choose the 777 and go from there?

It might turn out to be a bug in SimConnect but let's see.

You could also try loading a different aircraft (with aviaServer running in the background) and sending a help request, just to see if it's related to the 777.

No special tools just loading in via the default. Just trying it with the PMDG 737 but I'll need to close it all down first to keep the test the same

Bizzarly I tried loaded the 737 without closing anything down and got the same problem. closed and re-opened aviaserver and it starts working 🤷‍♂️
would it help sending you the log with it working?

 

Edited July 5, 20241 yr by BrianT

Sorry cross post. If it's any help it doesn't happen with the FBW A320 that works fine straight off. I'll restart the sim and send you a log with the 320 loaded.

Working Log sent

I don't support the FBW A320 so not sure what is working 😉

But the log file shows the same behavior: MSFS is simply not reporting the aircraft type! This really seems to be a SimConnect bug introduced in SU15.

Just now, marcom said:

I don't support the FBW A320 so not sure what is working 😉

But the log file shows the same behavior: MSFS is simply not reporting the aircraft type! This really seems to be a SimConnect bug introduced in SU15.

ah my bad sorry I remember they have their own server.
Well if there's any other test I can do let me know but at least a restart of Aviaservver fixes it.
I've just sent another log this time after restarting Aviaserver.

I can confirm the wrong behavior.

What is truly strange is that it is working fine on my side.

Are you using Steam by any chance?

Because I'm not...

no I'm just plain old vanilla MS Store version

Last time I used it it worked well when I started aviaserver and remote CDU after the 777 was powered up, battery on and APU running.