some1

I wonder is that really supposed to look like that? In VR the parts of image disappear unless you keep your head perfectly in the middle. It's worse than an ATM with privacy shield.

Only one of the buttons is really lit. Guess which one. Where does this glare come from? The whole panel is in the shadow, yet at some angles the buttons glare like molten metal and the screen becomes unreadable.

When I switch to the rear cockpit, Iceman will not take control over the airplane unless I bring the stick to centre position first. Which is a serious problem with a joystick with no centre detent.

How many enemy aircraft are supposed to be there in this mission? The voiceovers suggest there should be two, but I had four (+transport). In the end I shot down four aircraft, the lead shot the fifth, everyone seems to be happy, yet the final mission score was 80/100.

The attitude indicator is botched in a way that causes it to show progressive bank if you try to follow its directions. It will right itself after you switch back to flying using the horizon outside. That obviously makes flying in the clouds challenging. Considering that the fast erect function is not implemented correctly, and that the device shows the same error as standby ADI that is a less complex and completely independent instrument, I doubt anything in DCS F-5 artificial horizon is simulated correctly. As reported here https://forums.eagle.ru/topic/267104-horizon-fast-erect-no-im-not-selling-pills

Thats highly improbable, because a computing gunsight working in such scenario is much more complex than the one which assumes in-plane motion. So your explanation using JF17 simplicity is invalid. If they really made something simple, it would work in the scenario I described. That's why WWII gunsights work, no computers there. And the Sabre sight works on the same principle, it just uses radar to solve the distance problem, instead of stadiametric rangefinding.

Yes, the same issue is in mission 8. You have to go to the mission options and select the one to display all blue units. The offending AWACS does not actually show in the mission editor on a place it is, but on a stand not so far away. But that stand got probably deleted in one of the latest patches and is no longer valid.

Nothing that you wrote above matters in the scenario described in the first post. The target is stationary relative to the shooter, the only thing the gunsight needs is the target distance from the radar to calculate the bullet time of flight. Even a WWII gyro gunsight will work perfectly in this scenario, and in fact they do if you try the same in DCS P-51 or P-47.

In the M models, which are a different thing.

Right, then unfortunately I'm out of ideas. There's nothing wrong showing on your FPS VR screens, other that you don't have reprojection enabled as your fps is above 45. The GPU is at the limit on the second screenshot, which will also prevent reprojection from working - you need to keep the GPU utilization at around 80% or below to use it.

Do you have hardware GPU scheduling on in Windows settings? (HAGS) It breaks reprojection, you should have it disabled if you plan to use motion smoothing.

Are you on Windows 11? Have you seen this? https://store.steampowered.com/news/app/908520/view/3078767482769046005

I set up a basic mission with 4 AI ships attacking trucks in the valley. Guns only, one aircraft crashed. With rocket pods, three aircraft crashed. It seems that the AI has a serious problem with rocket attacks, but also when rejoining formation after targets have been destroyed. They start doing weird manoeuvres and ignore the mountains around. Maybe they too quickly switch to some "coarse" steering mode used for enroute flight or something. I also had an M-2000C crash into a hill during a mission recently after doing gun strafe attack. It wasn't even a mountain, he just flew into the rising ground while enroute to waypoint. So it may be a global issue, not exclusive to A-10C. crash 3x rockets.trk crash 1x guns.trk

These are the pylons for droptanks, which do not exist in the game. AFAIK these were not used to carry any weapons. The later 'M' models are a different matter.

I'm on latest beta.

ED has probably rearranged some parking spots and the result is that AI can't taxi past the AWACS. I had to edit the mission myself and move it somewhere else.

Thanks, top support

So far I played the first five missions, only the M01 has the issue.

Yes, from the enemy within mission 5.

It's possible. I tried to recreate the issue with a simple mission, but then the AI could keep up just fine...

So far in two missions I've lost 3 wingmen as they simply crashed into the mountains doing attack runs. Track: https://easyupload.io/7tofdg And some tacviews: https://easyupload.io/m/fb9fp3 (track is from M05)

Still a problem. They also take forever to rejoin after takeoff.

I had the same issue. Did not do the readback right away focused on punching the waypoints coordinate, then the option disappeared and mission did not progress beyond this point even after I dropped the bomb and killed the bad guys. No F10 menu, nothing. Guess a trigger on kill would help here. As for the weapon, GBUs are so inaccurate it's better to use LGBs or swap 38s for 54s.

ATC and AI is using the opposite runway to the one briefed, so the AI does weird manoeuvres in order to land and the mission timing falls apart. Not sure if that's a problem with the mission or another bug in DCS. The wind direction seems to be ok.