Gliptal

Can confirm.

SkateZilla's solution worked.

Yes, that's how I'd do it. The dev's paradigm is fine too though, the most important thing is consistency.

I did not test it in open beta, I'll hopefully do it today. Let me check your links to see what went wrong. Glad you found it interesting enough to play it on stream! EDIT: The TacView is from a different mission! :D I watched the video and didn't see anything wrong from your part. You received no message because all the infantry must be killed for the mission to continue. It looks like a 1.5.4 bug, I'll test it and report back.

Try a bigger airport, it may have more nodes in the taxiways.

I still think the best option would be calling it "PIP forward" and "PIP aft", exactly how the A-10C module does with HOTAS switches lke the China Hat.

What airfield are you using? It's probably a problem related to taxiing.

I have two questions: - Is there a way to force the AI to park at a predefined spot after landing? There seems to be an option in the editor (the landing waypoint has a parking dropdown), but the AI seems to choose its spot randomly. - Is there any way to spawn a light source on a given point? Other than flares. Thanks!

The alarm will sound if you land with non-neutral trim as well (neutral trim is a DECOL requirement). Double tap the trim temporary disconnect to put it to neutral.

Details here: http://forums.eagle.ru/showthread.php?t=167441

http://forums.eagle.ru/showpost.php?p=2821188&postcount=39

v1.1.0 released. - Added several briefing pages. - Made the required decisions for the AFAC's portion of the flight more clear in the briefing. - Ensured the objectives meet the 3-3 standards. - Added a sparse cloud cover, with very mild winds. Updated briefing accordingly. - Added static planes and vehicles to the homebase for atmosphere purposes. - Switched the "Insurgents" faction for the "USAF Aggressors" faction. Subsequently changed most vehicle types to better suited ones. - Changed countermeasures loadout amounts. - SAMs changed to radar-guided SA-8 Osas. The player must now stay outside the WEZ or else accept the risk of being engaged. Updated briefing, messages, flight plan, and triggers accordingly. - Changed the AG RANGE waypoint's altitude, placing the player more on the fringe of the MANPAD's WEZ. - Made the rotary wing engagement slightly easier. - Highlighted the need to follow the waypoints when RTBing. - Player must now park on the same spot as the starting one. Updated ingame text accordingly.

This should fix the TrackIR problems: http://forums.eagle.ru/showpost.php?p=2822647&postcount=94

Nice Skatezilla, I'll download OB again and see if the isse is solved on my system as well.

Professional curiosity: may you share what the issue is? How did you replicate?

The point we are all trying to make is it's hard to identify any issues when the sim is unplayable. I'm glad you're not experiencing any problems, but 1.5.4 is not an option for many of us. I reverted with no qualms, but it's at ED's loss, not mine. And, given you're an ED representative on these forums, a less patronizing and more understanding approach would be nice. It's even more frustrating when all we get for reporting these gamebreaking issues is snarky comments and "PS" posts on your side. No disrespect, just a friendly suggestion. :D We're here to help with OBs, but it's hard to do so with the current circumstances.

I personally gave up and reverted, I'll wait for an hotfix or the next update. It's strange how only end users are affected, and not devs or testers. My guess is something went wrong with the compiling or packaging of the public version.

This is a problem across most modules, both in SP and MP. The worst thing is that everyone seems to have a different version of the issue.

Now the slope is gone, but it's still way off in regards of limits, and 3d positioning of the POV.

The problem is probably irregardless of the facetracking software and hardware used. Something must be amiss internally.

Did that already, no change. Note that the lateral views my head has no angle in regards to the horizontal plane. I also have to turn it quite further than usual.

About the firs thing, what direction should I be looking towards?

http://forums.eagle.ru/showthread.php?t=169026 There are entire squadrons reporting various issues across SP, MP, and modules. Anyways, I hope if a fix is found we won't have to wait till next Friday for it to be implemented.

Don't despair yet, I may be onto something with that .lua here. I'll report back.

Fine, I have no problems dealing with bugs and shortcomings. The point is this Track IR thing is really major. Like, unplayable levels major.