Service Truck deadlocks before loading/unloading action

Getting a weird bug at my airport. Seems that once in a while I’m getting service trucks that seem to be getting stuck just before loading or unloading at a plane or baggage bay.

I’ll attach the screenshot and save folder but to describe it, it seems the vehicles in the game have 3 “actions” they do: 1) pathfind to the stand. 2) enter the stand 3) begin operation. It seems that the Service trucks are capable of getting to the stand, then driving along the red line to enter it, but it seems that occasionally just as they get to the point where they should transition to do their operation, be it loading or unloading, the code doesn’t seem to activate. They’ll just sit there on the red line and not move unless I save the game and reload it at which time they will, I guess, re-initiate the code that takes them from driving on the red line to driving to the rear of the plane to load or unload their baggage.

This bug seems to also occur at the baggage bay where they will drive into it, drive to the correct baggage loading spot and then just stop. Nothing inside the game seems to get them going again and I again have to save and reload the save. At the baggage bay, it does appear to happen both on the unloading and loading sides of the bay.

Could you guys investigate this? Maybe that point between the driving on the red line into the stand and then transitioning to the loading/unloading action needs some kind of double check in the code.

I have not seen this occur with fuel trucks or pushback trucks and have only used the roofed versions of the service trucks so I do not know if it occurs with roofless trucks.

below are links to the screenshot and save folder. let me know if you need more info.

http://www.mediafire.com/view/8a4c6fsom43a7a1/Stuckbaggagecart.jpg
http://www.mediafire.com/file/24okmhb3eacc6r2/KMYR.zip

Hello! Thank you for a detailed and informative report. Would it be possible for you to copy paste this into a bug report via www.airportceo.com and then “Report Bug”? Would help us a lot as we also need some other data collected via that inlet.

ok. Unfortunately, it seems, I have opened the game a couple more times playing that same map and it seems to have overwritten the output file. Should I wait for the bug again and then submit or submit the bug report without it?

The output_log file can contain important information, so I’d be happy if you wanted to wait for it until it occurred again and then just send in the whole package. Makes it a lot easier for me to debug and solve.