Gliptal

I'm not an expert in modeling, but nowadays I really don't think 400.000 polygons are that many. Having played around with Maya myself, I'm actually surprised they managed such a good looking aircraft with only 6000.

It may be. But the parking swap did fix that TEW mission. It's quite hard to find a culprit without knowledge on how the underlying AI works. Do they even actually communicate with the ATC? If it only appears with large numbers of aircrafts at the same time, it may be a matter of deadlocking. Each one basically ends up waiting for the next to move in a circular pattern.

I wasn't criticizing anyone, I'm sure the testers are working at the best of their ability. Still, issues are bleeding through for a lot of people, hence something wrong is happening somewhere down the line. EDIT: Look, I'm sorry, as a programmer myself I have a lot of respect for you guys, testers and devs. It's just I came home after a long day hoping to fly around, and ended up fighting and dealing with bugs and bug reports instead.

This was a fine reasoning in an Open Beta environment. It's not anymore, and these "other bugs" are breaking payware DLC campaigns. And there should be no need for a fix to be applied on one of the most basic functionalities of the sim. But alas, the new additions are definitely good.

Great. On my end, it seems to be an issue for aircraft parked in adjacent spots, if the first one to taxi is has to move in front of the other one. Further testing will follow. EDIT: Nevermind, it fixes one of the TEW missions but I can't replicate on a new test one.

Thanks, added.

Yep, still there on 1.5.4 stable. See this thread: http://forums.eagle.ru/showthread.php?p=2835416#post2835416

Incidentally, Skatezilla's workaround still works.

This is an issue that was corrected in a previous 1.5.x release, but now it's back. Basically the AI stops along the taxiway for no reason, breaking missions and campaigns. I'll do some testing and see if I can reliably replicate. As an example, mission 20 of The Enemy Within campaign shows this behaviour.

How did this go past QA this time guys? I don't want to be negative, just asking. It took me and quite a bunch of other users about five seconds to realize TIR is still broken in what is now 1.5.4 stable. I'm genuinely happy for all the amazing additions, but come on. :cry: EDIT: Oh, and the AI is back with the taxiing issues again: http://forums.eagle.ru/showthread.php?p=2835412#post2835412

Same for me. Opened a thread in the Stable release subforum, since we're all supposed to be on stable now. http://forums.eagle.ru/showthread.php?p=2835400#post2835400

Track IR view still broken See for example: - http://forums.eagle.ru/showthread.php?p=2834416#post2834416 - http://forums.eagle.ru/showthread.php?p=2835309#post2835309 I'm having problems in the A-10C, the base view is angled upwards. Previous Open Beta thread: http://forums.eagle.ru/showthread.php?t=169026 To those testing the sim internally, can you please keep an installation free of any custom files you may have so that you can actually test this stuff? It's getting tiring. And the "you shouldn't be applying to Open Betas if you can't deal with bugs" argument isn't valid anymore.

This sounds like a problem that has plagued 1.5 for quite some time before being fixed with 1.5.2 or 1.5.3. I'll see if I can replicate as well. EDIT: Unfortunately, I just replicated. I'll create a new thread in the bugs subforum. Let's hope for the best. God this is becoming tiring. Here's the thread: http://forums.eagle.ru/showthread.php?p=2835412#post2835412 EDIT: Fixed for Mission 20. Open the mission in the editor, and move the lead F-16 (Colt flight) from parking spot 10 to parking spot 12.

Are you using the coalitions mod by any chance?

I'm having problems with the A-10C, the view is angled upwards.

Are you using any mods?

Is it just me, or is the Track IR head position still bugged?

I've been beta testing it for the last couple of months, I've flown it all more times than I can count. You'll have to trust me obviously.

Thanks!

Apparently. I created a thread in the bugs subforum, let's hope we get an official answer on the issue now that the problem is in stable (after weeks of being in Open Beta). :D Still, great work with the rest of the update.

About the lighting issue, thread opened in the bugs section: http://forums.eagle.ru/showthread.php?t=169872

See the following threads: - http://forums.eagle.ru/showthread.php?t=169778 - http://forums.eagle.ru/showthread.php?t=169631 - http://forums.eagle.ru/showthread.php?t=169549 - http://forums.eagle.ru/showthread.php?t=169134 - http://forums.eagle.ru/showthread.php?t=169566 The issue presented itself since the first 1.5.4 Open Beta iteration.

Yes I know of that particular issue, but the whole night lighting was bugged, with in-cockpit lights being completely dimmed and generally much darker nights. I hope the issue was connected with the sun glare, because it currently makes it very hard to fly at night with some modules. I'll have to wait and test it myself.

Does this mean the nighttime lighting issues are corrected as well?

Another point in favor of the M-2000C: the campaign is very good.