Can't fly AV-8b after update to 2.5 release

[Mirtma]

After updating to 2.5 release version, I can't fly AV-8b. Quickstart puts me on the map instead into the cockpit. I can view plane from outside (F2, F3). Same with missions. I created a custom mission, same effect. I uninstalled module and installed it again.

I've also uninstalled DCS 1.5 and 2.6 beta, so that now I have only 2.5 release version. No change. Any suggestions?

[thrustvector]

silly but, if youre doing a custom mission in the ed, you have set plane to player?

[strikers_blade]

Would you mind attaching your mission to your post so we can look at it?

[Mirtma]

Yes in a custom mission I set player. But the problem is also with quick missions (and their missions). I've only tried custom mission after found problem with quick missions.

Edited April 6, 2018 by Mirtma

[davidp57]

It looks like DCS thinks you haven't bought the Harrier module.

This is what happens if you try and use a slot in a MP mission for a module you don't own, iirc

[Mirtma]

I've opened a ticket. I don't play MP missions, and I own a module.

[104th_Money]

It is a bug. If you cold start, you have no issues...Starting on runway gets me map view only as well. Funny thing is that some older missions that I havent opened in the ME and resaved still let me start on the runway. Anything new made with the ME maps me...

[Mirtma]

@104th Money: Can you send me some mission that works for you? Whatever I try, I get a map.

[Mirtma]

Problem solved. It was antimalware program HitmanPro.Alert. First I've completely uninstalled HitmanPro.Alert. Then deactivate and uninstalled AV-8b module from all DCS World versions. And then installed it again. Now it works. It seems to me, that new system of authentication and HP.Alert doesn't like each other. I've also written about this problem to HitmanPro support. It seem that similar problem existed before.

Edited April 8, 2018 by Mirtma

[Mirtma]

I posted solution how to keep HitmanPro.alert and DCS World in this post. Is really simple. Just add DCS.exe to exclusions. I've searched for it before, but I didn't find it. With help from HPA I excluded DCS.exe.