Hotel Tango

Hi, sorry if I didn't make my point clear. I'm using MSAA 4X. The issue is related to mip maps and texture files, when exporting them on the liveries in question, they are missing. This creates a "shimmering" effect with many black dots and white dots specially in the pannels of the aircraft. It's hard to spot in the screenshot, but if you download the image you can see those dots. I can create a video as well showcasing the issue.

@Vibora Awesome job on the reworked textures! Can I ask you to take a look at this issue, I have several shimmering as well... It's an issue that can you can fix with mipmaps while exporting them.

Hi! Where can I find this livery?

Can confirm, I have the same issue here. It happens every time you go to F2 view. I don't have any mods or a split throttle.

I've noticed that the rotor doesn't tilt much at max speed flights, even with 100% torque applied. Is this as expected? In my understanding, the angle seems too shallow.

How to reproduce: With FCR in TWS, it takes a long time and a large number of hits to create a Track Target. As per the F-16C Early Access manual says, "These targets disappear after a few sweeps if a track cannot be obtained. If a valid track is obtained, usually after being detected on two consecutive sweeps, the contact automatically becomes a Track Target.". In the example, I was using a scan of 10º, with 1 bar elevation. This is the smallest scan possible and the fastest update rate as well. Even with the target well below 20 miles, it took a large amount of hits to upgrade it to Track Target. F-16 radar.trk

Here's a complete list of the liveries in question: - 132nd Wing Iowa ANG, Des Moines AFB - 152nd Fighter Squadron 'Las Vaqueros' - 174th Fighter Squadron ANG, Iowa AFB - 36th Fighter Squadron Osan Air Base - 80th Fighter Squadron, Kunsan AFB

Some F-16C liveries have an artifact caused by the lack of mipmap compression when exporting the livery file. To fix it, you can open them in Photoshop and save again, this time with auto mipmap enabled. This is present in some liveries, as show in the screenshot below: It might be hard to see, recommend downloading the screenshot. It shows several small black and white dots that "shimmer" when viewed in game.

Im gonna be honest with you, I didn't notice any diminushing in shaking since I bought the Apache. If they increase it, I would slide it down, because this is very much subjective to each player.

Thanks for the reply, Raptor! Yes, 100% agree that this is no reliable data to compare.

This is interesting. Do we know if he's talking about an AH-64E or D?

As Raptor and others have stated here in this forum, yes, the FM needs fine tuning, specially with the rotor torque/anti-torque and SCAS. HOWEVER, the power available and engine torque margins are, as far as the feedbacks from people who used to fly it IRL, very close, if not on point. The AH-64D had a lot of weight added on in avionics (some 2000 pounds in empty weight alone, iirc), without much improvements on the engines/transmission end of it. As a result, it lost some performance compared to the A model. This, and other reasons, are why they developed the AH-64E Guardian now, with much better performance. That being said, plan your mission acordingly and this issue is severely mitigated. And I do agree, FM is a very important aspect of a good module, and I do have hopes of ED delivering a great one.

This is... FANTASTIC!

Squadron: Harpia Timezone: 1500z-2200z Aircraft: All Maps: Caucasus, Syria

I've got another crash today, this is what I got in event viewer:

During some missions, my DCS closes to desktop with no warning, no error message. Also, there's some IC issues happening with random files. I've run several repairs by now. dcs.log

Nice catch, hope they can include sub variants of the F-5 with smaller LERXs, dorsal ADF antena, or the refueling probe

How to reproduce: Scan with FCR in RMAP mode behind a building, you can clearly see the map being scanned, with no shadow due to the obstructed LOS. AH-64 RMAP bug.trk AH-64 RMAP bug.miz

I'd love to have this implemented into DCS!

I'm having this issue for some time now. It's completely random. Various repairs and some uninstalls have not fixed it.

It didn't change. There are still the same issues as before...

Can confirm here, same issue.

Hi, any news on this issue? Excessive "crabbing" and too much torque could really be looked into soon, as the rest of the module is pretty much superb.

Interesting... ED, could you take a look at this?

On a side note, should modern long range SAM's operate in TWS on most of the flight time?