kirk7312

I notice there is strange texture on the skin of the plane. I tried to change the graphic setting. but it still there. And this texture is more clear when the mission time is in the moring and evening. if the mission time is 12:00 the texture is not so clear.

I cannot change curve for FFB2 in the AH-64 like MI-8, because that will cause the trim is not working properly. But it is too sensitive for FFB2 in AH-64 It almost impossible to make AH-64 stable in the low speed. It even more difficult than Mi-8.

Just try RC3, But I cannot communicate with AI wing man. No wing man option in the communicate menu. No this issue in RC2. Do I missed any setting?

I don't know if here is the place to report issue. I found two issues. 1) It cannot connect with the Tacan which is set with carrier and portable Tacan device. It works perfectly with the Tacan set in the airfield. 2) Autopilot doesn't work with FFB2. it cannot hold alt if I use FFB2. It seem reset the trim when I set hold alt on.

where I can find and download those C++ library? I got same issue.

same on the Kuzentsov.

Thank you everyone, I found out what is wrong. On of axis on my stick has problem. it cannot set flap fully back. After I adjusted the stick. it is working fine now.!

After I land on the groud or carrier, I push out the wind sweep handle, the EMER on the wing sweep indicator appears, then I set it to 68 degree, but the wings always stop at 50 degree and do not go further. I even tried to sweep the wing before take off. it is same. always stop at 50 degree. Anyone can tell me what is wrong? sweep.trk

OK, That is clear, it is totally same as previous bug! Ai is fine, it always take off from the right position. but if it is control by player, av-8B will be placed in the front of deck. The bug they fixed comes back again! The developer may not merge the fix of this bug in the newest release.

I created a new mission and tried it again in Persian Gulf, it still started in front of Deck. I attached mission file here test1.miz

If you set AV-8B takeoff from the Tarawa, the start position is in the front of the deck. I remember this bug was fixed before. But now, it comes back again. DCS version 2.5.6.58125

Radar is a problem, avoid using radar in any altitute. without turning on the rada, FPS is around 70, but it drops to 15 after I turn it on. and Fps comes back to 70 after I turn the rada off. :mad:

I landed in a stadium, but it seems has a double layers ground. and the heli is laned on the lower ground.

I don't think it is a bug. ED do that on purpose because some guys here think JF-17 is too powerful, they want some kind of balance.

感谢大佬！

E-2D starts from cat 2, F-14 starts from cat1. JBD behind F-14 is not raised.

autopilot is working for me.

Thanks for your replay. I think most of players are fastrated by the recent two big bugs（LMAV and Tarawa takeoff position） after super carrier release. that make a lot of missions unplayable.

Hi ED, I am playing AV8b for now. But after Super carrier, AV8B can not do Short Take Off from Tarawa. after update of last weekend, LMAV is broken. Is it possible for you to confirm the third party production before you release update?

It seems the new supper carrier update casues the taking off position error on Tarawa for non-Ai plane. AI plane still can take off from the normal postion. but non-ai plane is always placed in the front of the deck. https://forums.eagle.ru/showthread.php?t=274073

In mission editor, I added an AI E-2d to take off from the runway, then add a AI group which has 2 F/A 18 to take off from runway too. When I started the mission, both E-2d and F/A -18 started in the same position.

已经等了好多年了。:thumbup:

GO GO MIG28!:pilotfly:

:thumbup:　牛

Down to 6....