There is a bug that ends the game when the airport is preparing to receive its first commercial flight. I’m using MAC. The game closes unexpectedly. When I do not program commercial flight in the flight planner the game does not have this bug.
3 Likes
What are your hardware specs?
1 Like
Hello Olof,
this is my first post so, first of all, thanks to you and all the team for this jem of a game you have been (and are) working on.
I have recently updated to the Beta, and I happen to have the same exact problem described by AllanFelippe.
In the previous months I played without any issue and was able to design one very big and complex airport and had 0 problems.
After downloading Beta, that saved game simply would crash directly the game.
I thought it was an issue with compatibilty with the new features, so I started a new airport from scratch.
As I plan the first commercial flight, as the public bus of cars with the first passengers start to arrive as soon as the first vehicle stops, before any passenger desembarks the game would crash. Every time in that exact moment.
I’ll post part of the error log, as it contains all my Mac’s tech spec.
I’m sorry if it will be long.
Process: Airport CEO [1322]
Path: /Users/USER/Library/Application Support/Steam/*/Airport CEO.app/Contents/MacOS/Airport CEO
Identifier: unity.Apoapsis Studios.Airport CEO
Version: 1.1-2 (0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Airport CEO [1322]
User ID: 501
Date/Time: 2020-10-11 20:01:16.232 +0200
OS Version: Mac OS X 10.14.4 (18E226)
Report Version: 12
Anonymous UUID: 0E3D340A-194F-09F7-EFCE-6D3E15A17BE7
Time Awake Since Boot: 4800 seconds
System Integrity Protection: enabled
Crashed Thread: 24 UnityGfxDeviceWorker
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000000c
Exception Note: EXC_CORPSE_NOTIFY
Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133
Model: MacBookAir5,2, BootROM 255.0.0.0.0, 2 processors, Intel Core i5, 1,8 GHz, 4 GB, SMC 2.5f9
Graphics: kHW_IntelHD4000Item, Intel HD Graphics 4000, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463235363634485A2D3147364D3120
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463235363634485A2D3147364D3120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (7.21.190.33 AirPortDriverBrcm4360-1325.2)
Bluetooth: Version 6.0.11f4, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM128E, 121,33 GB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 3.0 Bus
USB Device: USB Optical Mouse
Thunderbolt Bus: MacBook Air, Apple Inc., 23.4
2 Likes
Hello and welcome to the forums. Thank you. Yes there does seem to be a strange exit pattern for Mac users. I’ve reported myself. I’m thinking it’s to do with the unity update more than anything else.
Keep up reporting. :).
2 Likes
I have been unable to reproduce this myself, could anyone provide a more detailed explanation of what exactly is happening?
1 Like
My last couple of sessions, I never got this, but will keep an eye or two on it for you.
2 Likes
Crashed again on quit. Sorry.
I need a lot more information unfortunately… log files? What exactly happened? What save? Etcetera… 
2 Likes
Happens with me fairly regular, message me and I can send you a stack trace
Yeah you can go ahead and e-mail us that dump to support@airportceo.com when it happens again!
1 Like
I still get this, which logs are the most relevant? The Crash report file or the Unity ones?
Crash file, Unity is not interesting.
1 Like
just sent per your request
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.