wcdiver

From my experience: Using Head On and Pursuit mode is far superior to using automatic mode. So for targets that are far away: Head On mode, then setup the bracket at the relative distance to the target, and then setup antenna elevation to the target relative altitude. When target is close enough - switch to the Pursuit mode and check the antenna elevation (make sure that is not pointing too high / too low). Here is an example: lock achieved at 80+ km using Head On mode and correct antenna elevation.

I'm staying low and try to acquire enemy visually, then once he's on top of me I'm climbing to get on his six and shoot some R-73s or lock him with radar close combat mode to use R-27Rs. Same tactics that I've used in MIG-21. For BVR I identify my enemy first (via AWACS). If it is a modern jet like F-16 I just don't bother fighting him with this technique, because MIG-29s chances of survival are slim to none. But harassing some ground pounders or older/equivalent planes? That can be done. /edit not AWACS but GCI on multiplayer servers.

I'm so happy to see that. I've been living near airbase with them since my birth. I'm so used to seeing those beatiful planes fly over my house. My dad was working on them. Looking forward to this mod and can't wait.

I've made a video of how loading the game in multiplayer looks for me. The same is for Retribution/Liberation (so a game with many units) My specs are core i9-11900kf 32 GB RAM RTX 4070 And I have nvme disk. During loading I see the ram going 100% usage (so entire 32 gb) which is probably the cause of this thing. My pagefile is set to 32 gb. I have a standalone install. I removed my DCS.openbeta folder from the saved games and let the game create new one. I use only 3 mods: A-4 community edition, OH-6A and nin's mig-21 sound mod. There is no difference mods or without mods. I have problems only with DCS, other AAA games run completely fine. I will also attach the dcs.log file here dcs.log /edit I've turned my preload radius from 50 000 to 10 000 and it seems to have helped a lot bit. I guess that 64 GB of RAM is now mandatory for multiplayer with bigger preload radius. Still I'm a little disappointed.

Thank you for this mod. It brings me much joy.

I've got the same problem. It shows itself the most in SP, in campaigns like Retribution/Liberation (lots of units) and in multiplayer. Even the Hind sometimes takes 2 - 3 minutes to load the cockpit textures. Ram usage spikes to max (32 GB). After it loads the textures, it drops significantly.

I have encountered similar problems. There is a lot of stuttering in the single player, especially in the external view. However, multiplayer is slowly becoming unplayable at this point. Very long texture loading times, that I have to wait in cockpit for several minutes with single digit fps, then constant stuttering. God forbid i check another player by using F2, it almost freezes at this point. For now the game is utterly unplayable for me.

I've done a simple comparison with the real world counterpart and it seems to me, that the rotor spinup time (which is now a little faster with the newest update) is way too slow. Are there any plans to match the real world counterpart speed ? Here is the video I made:

Sadly, there are english subtitles.