Kirkus

Same here, through 80 knots speed starts to drop off.

Supposedly fixed in the A380, but no updates for the A350, need to wait for v2 so it seems.

CPDLC is broken, messages are send by the aircraft and seen in the Hoppies log, and received by the controller, however the aircraft does not receive messages from the controller, they can be seen in the hoppies log, but never arrive in the aircraft.

If it was obvious, people would not need to ask questions.

They are making a V2, will be free for existing customers, when it comes out is anybodys guess, it supposedly has fixes for all these issues.

Not likley, if they release V2 which fixes all the bugs in V1 and charge everyone for it, then under Australian Consumer Law they would be breaking the law, you simply cannot do this. Also if you think Australian Consumer Law does not apply to inibuilds because they are not Australian, then go and ask how that worked out for Steam.

Yet its still broken.

Disgusting, they should release a fix as soon as they know about it, not wait till the A380 releases, we are paying customers with a product that does not work, consumer protection would have a field day.

Hoppies is very broken, the drop down list never shows the actual staions online, and has not done so for some time, along with the pos rep fucntion being inop for some time also. Further more, per one of my posts here, you can request a PDC, but you never get the response back from ATC to the mailbox. https://forum.inibuilds.com/topic/36226-pdc-not-received-by-aircraft/#comment-88020 To be on the hoppies network, you need to have your flight number in the INIT page of the KCCU. You should be able to see your self on this list https://www.hoppie.nl/acars/system/online.html Messages you send and receive are here https://www.hoppie.nl/acars/system/log.html

They call this a ghost WASM crash, and they have no idea how to fix it, and they are putting the blame on Microsoft. However in my research, what is happening is simconnect is getting loaded up to a point where it can no longer cope, and it disconnects from the aircraft. I ran some logging with simconnect logger and found that just before the crash simconnect was getting spammed with requests. This never happnes with the Fenix.

Brake** You need to enable push back raise for the towbarless push back tractors in the GSX menu https://forum.inibuilds.com/topic/30447-moving-forwards-upon-gsx-pushback-being-ready/#findComment-89188

If the station is not providing an _A or _D ATIS then you need to select none from the drop down menu.

You have to output it to a folder that is allowed to write in, for example I put mine in documents/logs The text file goes into LocalState [SimConnect] level=verbose console=1 RedirectConsole=0 OutputDebugString=1 file=C:\Users\(your user name)\Documents\Logs\SimConnect%u.log file_next_index=1

I too noticed the MCDU screen freezing when flying the A340, I simply unplug the MCDU and plug it back in again. However I do not accecp that the soultion is to buy another program.

windows + shift + s to take a sreen shot, or the print screen key.