BBQ Posted May 20, 2013 Posted May 20, 2013 Beslan has only one taxi-way to the runway, roughly in the middle of the runway. In order to takeoff, the pilot must taxi (on the runway) to either end, and then takeoff. There is a little skirt/apron at the threshold that allows aircraft to turn around. At 17:03, I couldn't set my altimeter QFE to the required setting -- it wouldn't go below the setting equal to 500 ft. That's bug #1. I continued on and tried to troubleshoot the problem with the takeoff (practically that is), and this time I waited at the threshold until #2 could get clear and wait on the apron. However, he wouldn't move onto the apron even though he had plenty of room to do so. He just sat there a bit short of the threshold. I moved around, giving him even more room -- but alas, he wouldn't budge. I was able to scoot past him, maybe a meter of wingtip clearance between us. So that is bug #2 (AI won't move to apron). After I took off, #2 began his roll-out and of course #3 requested clearance, which was given, and as #2 passed him they each gave up a wing, and both ejected! So that's bug #3. Finally, I noticed #2's aircraft took on some rounds, which is a mystery, as #3 hadn't unloaded his gun to my knowledge. That's bug #4. Bug #1 occurs at 17:04. (and after I get clearance to takeoff -- verify ATC QFE setting) Bug #2 occurs around 17:28 (Sorry, didn't write down time, but it happens a few minutes before Bug #3). Bug #3 occurs at 17:33. Bug #4 occurs either instantly at 17:33 or a minute or two later (see screenshot below). Attached files: Track
Grimes Posted May 21, 2013 Posted May 21, 2013 Due to Beslans setup, its is not exactly the best airbase for AI in the game. They used to taxi in pairs so that one would sit on the shoulder while the other takes off, but it appears this has changed. Yet for whatever reason when the player reaches the end of the runway a wingman will think the "taxiway" is clear. On their own AI will take off (slowly) from the base without issue. Bug 4 is simply how the damage model works. It detected damage to that part of the aircraft and it renders the appropriate level of damage, but the visual damage is not based on what causes the damage. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
Eddie Posted May 21, 2013 Posted May 21, 2013 At 17:03, I couldn't set my altimeter QFE to the required setting -- it wouldn't go below the setting equal to 500 ft. That's bug #1. No bug. QFE is not used by western military aircraft, not only that but setting QNH for takeoff in the A-10C is REQUIRED in order to calibrate the IFFCC for accurate weapon delviery. As such the altimeter settings simply don't go low enough for QFE to be set at high altitude airfields. QFE being given by "ATC" is just a limitation of the currect ATC implementation, or the lack thereof.
BBQ Posted May 21, 2013 Author Posted May 21, 2013 aha! So I'm getting the old "It's a feature not a bug" thing (I'm a software tester by trade.) So let's call them legitimate gripes. Gripe number one is a wish that the damage model would be more accurate (as to the cause). Gripe number two would be the ATC AI would be better. Gripe number three would be that AI pilots would taxi and take off better! Not really gripes really - just wishes - as I can't see how anyone could possibly complain about this awesome piece of software!
Recommended Posts