MacOs Aerofly FS4 started in Steam, crashes after 7 minutes repeatedly

  • When started in Steam, flight Frankfurt-München A320, Programme crashes triggered by Thread 5 CVDisplaylink roughly after 7 minutes , tried different flight same thing. Funny enough there is no TM.files in Library/Application Support / even no aerofly subfolder. Changed also Display refresh rate to 120fps , no difference. Also tried Flight FRA-Milano with CRJ-900 crash after 17 minutes same error as above

    Started Aerofly out of the steam environment different aircraft, same crash after 7 minutes different failure : Bug in Client of libmalloc: memory corrupted of free block.

    My first impression was, it is related to amore complicated cockpit lay out ...but who knows )-:

    Configuration: mac mini (M2), Studio Display, macOs Tahoe 26.2, Trustmaster A320 Co Pilot

    Thanks for your support ( hopefully)

  • Thank you. The tm.log file looks fine. Could you give us some steps to reproduce the issue on our side?

    Also, are you doing something specifically to trigger the crash or does it crash by itself, with no user interaction on your side?

    If you do give us steps to reproduce please also send us the file called main.mcf ( in the same location as tm.log ) so we do see your settings.

  • I tried it again this morning A320 from Munic same error after 10 minutes I did not do any special it was nearly level flight only controlling pitch/Roll with the stick. I am sending you the tm.file, main.mcf and a PDF which is a copy of the crash report ( roughly 70 % ) All files are from today. Forgot to say, for the flight this morning I removed the USB mouse, just to check it has an influence

    thanks E.K.

    to upload main.mcf through your upload function was not possible I could see the file as hidden but could not upload it, tried hidden file to unlock did not work, copied it outside did not work

  • The version which I play is 4.8.1.18 so latest patch is included. I set the frame rate to 60 fps ..in the Settings in the game ..no change also reset the settings for the A320 Flight stick. Looking in the internet about this failure CVDisplayLink, sometimes it is linked to an external hub when you add another display..which I don't do. Using an HUB from Hama to get the USB-A Connection to my mac mini I even removed it and installed the flight stick with an adapter direct to the mac mini no change, same thing happened after 7 minutes Thread 7 CVDisplayLink ...shit

  • Put everything to Low settings, A320 worked for 32 minutes which is already an improvement but didn´t have more time flying. So what are the main settings which put a lot of load to the processor

    so I can gradually add settings again.

    Just to clarify the Cessna statement from yesterday was without putting everything to low settings

  • We have the exact same Mac computer for testing purposes and do not see these issues, we can fly for over hours. Something must be different.

    Can you please send us the main.mcf will all your settings. We might overlook something. According to the crash log it is some kind of memory problem.

    To verify this, could you just start Aerofly FS but the A320 onto the runway and then do just nothing, just let it stay there.

  • II also have some crashes on my MacBook and have already sent this to Jan. However, I am in the focus of developing the C130 and therefore have no netto version running. But I can do that if it could be helpful.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • ApfelFlieger You could help us by sending your main.mcf file so we see the settings and please run a test with those settings by just placing an airplane that crashes onto a runway and do nothing and observe if it crashes then?

    Like we mentioned we can use the simulator for hours with no issues so it must be something we are 'not doing', Thats what we would like to find out.

  • So as I said I reduced the settings and yesterday had a A319 flight from FRA to Vienna and everything worked for 1 hour 20 flawlessly. On the display I didn`t have on the top left corner the power setting and the flaps setting an on the top right corner the course compass with the flight path ( don't know the right discription for it) .

    Will be interesting to see if ApfelFlieger can copy the main.mcf file with your upload function, which I was unable to do, even seeing it as a hidden file in the corresponding directory.

    At the end..thanks a lot for your quick support !!!!!

  • So as I said I reduced the settings and yesterday had a A319 flight from FRA to Vienna and everything worked for 1 hour 20 flawlessly. On the display I didn`t have on the top left corner the power setting and the flaps setting an on the top right corner the course compass with the flight path ( don't know the right discription for it) .

    Will be interesting to see if ApfelFlieger can copy the main.mcf file with your upload function, which I was unable to do, even seeing it as a hidden file in the corresponding directory.

    At the end..thanks a lot for your quick support !!!!!

    Flight info can be toggled with the default assigned key 'i'

  • ApfelFlieger ... please run a test with those settings by just placing an airplane that crashes onto a runway and do nothing and observe if it crashes then?

    "Unfortunately" I had no constellation with crash yesterday - I will test again.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+