Tower!3D Pro - LAX Peculiarities

[crbascott]

Had a good hour long session working the north side of LAX tonight and thought I'd pass along a few peculiarities I ran into:

1. Tried to have CPA897 (77W) take off from 24L but was told the runway was too short, so I sent it to 25L. With 24L being over 10000 feet long, is this a plane issue (Nyerges I assume) or a runway issue?
2. AVA85 taxied and took off like normal, but was "frozen" on the strip and ADIRS, I tried to delete it, but nothing happened. And then later I got a 50 point wait penalty. I guess the game engine thought it was still at the gate. I've attached pictures (all taken at the same time when AVA85 was about to take off) and the game log. 

Thanks for looking into the above.

 

game.log

[Avwriter]

Truly weird.  Never seen that one.  If you go back to that same hour, does the issue repeat?  Is this with the default RT schedule, or with a modded schedule?

[crbascott]

The schedule file I used was a subset of the RT schedule. Yep, I may have to try that hour (10:00) and schedule file again and see what happens. 

[crbascott]

Tried it again and the same thing happened, but I think I figured out the issue. The RT schedule for LAX has two entries for AVA85 departing at 10:22. One is a 77L and the other a 788. So, as mentioned in other threads, Real Traffic could use some cleanup and refreshing.