Padonis

Today's patch unfortunately did not fix the problem.

No, 100% operational, newly acquired machine, attack on the few remaining trucks. Others randomly had similar problems, clear shot line, 500m altitude, target in the middle of the field. There was no such problem before the last update.

The problem is that a couple of times I encountered a situation where the target was in an empty field, was marked, in range, there was a sound, and the bullet did not fire. Petrovic said nothing. I did a few airstrikes on the target and nothing. Only the exchange for a new helicopter works. The problem is not just me.

I confirm.

I confirm. When I set the GUI to a value other than 1, Petrovich's crosshair moves from the center of the screen to the side. Unfortunately, my friends are the same.

Probably why they made two versions, because they were aware of the problems and needed more testers.

I'm not talking about the EW you display on the DDI, but about the RWR, which is also the case with the A-10C, F-5 and F-18. It's on the right under DDI.

Unfortunately, the RWR export does not fix the A-10C II, F-5 and F-18

Has anyone been able to fix RWR export?

Has anyone been able to fix RWR export?

Exactly - it's not about hard-to-see trifles, but about obvious mistakes.

Why am i not surprised? And none of the teko testers noticed? Incomprehensible?

I think that a map of the Baltic Sea with the countries adjacent to it would be very successful. Privately, I'm tired of more maps with a cat litter box. Many DCS customers come from this region.

I really like the Mi-24, a natural rival of the Ah-1W Cobra would be very useful, not to mention a harmonious duo with Huey.

The problem is that they didn't say the size of the map's GB on medium settings. Maybe the average quality is already 80GB, if they multiply x2 it will be quite a lot. They omitted important information that could be quite important.

It looks like the functions of BHOT-WHOT are inverted. On WHOT, where heat should be displayed in white, it is in black.

The new FLIR rendering system has brightened everything up, but not the vehicles. Everything is working the opposite of what it should be. The A-10C is still good, the F-18 flir is broken. Are the vehicles black and the surrounding terrain terribly bright? Is it only with me?

The radar doesn't even work on the gunzo. The helicopter can sit in your bow and the radar is blind anyway.

I'm not talking about fox 2, but following the helicopter, finding it. As you can see in the video, I can't even use the radar using Vulcan.

In total, I made several raids from different sides on the Mi-8, trying to target it with the radar and shoot it down with the Vulcan. Unfortunately, the helicopter is completely invisible to the radar in any operating mode.

I cannot lock the target at low altitude in any way.

Of course not a problem, if it gives me stable DCS operation, and the graphics card works stably and consumes less power, it does not bother me.

Using the "XTREME GAMING ENGINEZ" software, I reduced the GPU frequency to ECO mode, i.e. to 1830 MHz, I just made a 45-minute flight without crash DCS. Unfortunately, after disabling "XTREME GAMING ENGINEZ", the display drivers restore GPU frequency 1936 MHz. The card is overclocked at the factory. Factory frequency should have: Boost: 1860 MHz / Base: 1721 MHz in OC mode Gain: 1835 MHz / Base: 1695 MHz in gaming mode I have no idea why it comes default to 1937MHz?

I have the latest Nvidia drivers, a new Seasonic Focus 850W power supply, only the graphics card is older. However, it passes the test in FurMark. Other games, IL2, Witcher, Arma are working fine. The frequency and temperature are given in the file "GPU-Z Sensor Log" GPU-Z Sensor Log.txt