asdfg1111

Agreed, there seems to be some kind of inconsistency which ends up making CCIP/CCRP inaccurate sometimes. I've had some instances where the marker seems to be showing the correct impact point, but then it gets messed up when flying over mountains/hills. Then, when going back to flat terrain, it is still messed up as if it won't revert back to the correct impact point. When spawning mid-air in Mission Editor with bombs, I can consistently drop them on target and the CCIP marker is accurate. But when I try that in multiplayer, by the time I get to the target, it usually seems the CCIP is inaccurate by that point. So any weapon that uses the bomb drop CCIP/CCRP marker seems to be affected. Rockets and gun seem to work well for me consistently.

While I do like the damage modeling, I would agree that the new Mig-29 gear seems too weak. Even just taxiing through grass/dirt for a very short distance the gear is likely to collapse compared to other modules.

I tested it again and maybe accuracy is the wrong word, but it does seem like there's some difference in how it's working between singleplayer and multiplayer. I've attached my track file from singleplayer. In singleplayer, I'm able to drop bombs during a low pass and despite being very low altitude, the CCIP still shows the correct impact point throughout the pass. When I try in multiplayer, the CCIP marker is responsive until I go below a certain altitude which it then reverts to it's default position and is no longer accurate until I regain altitude which makes sense. Just wondering which way is correct, and what may be causing that difference between single/multi? It seems there's no 'too low' altitude limit for the CCIP in singleplayer while there is in multiplayer. 1.trk

Have tried this a few times now and it seems pretty consistent. In mission editor I can hit targets nearly dead on accurate using CCIP with bombs and the CCIP marker is visibly responsive as expected. However, when I try the same thing in a multiplayer server, the CCIP symbology seems a lot less responsive to aircraft movements and the bombs are way off from where the marker is. Pre-designation doesn't seem to make a big difference. Guns and rockets seem to work as expected in both. In the Mission Editor gameplay, I start with the plane in the air. In Multiplayer, I've started both cold and hot starts but seem to have no accuracy with the bombs. Am I doing something wrong or is this a bug?

Ok, I think I found the cause. I just tried launching it again and when it hung up in the usual spot I did open BitDefender and disabled some of the active protection options. As soon as I did that the game launched. I guess there was some other way it was blocking it besides the Firewall. I think it's working fine now. Thanks for the help!

I do see the file, but not seeing any access violation error. Should I share the file here?

No mods currently

I do see a dcs.txt file in the Logs folder which is dated 7/1/2025 (yesterday when the issue had occurred). Is that the correct file? I don't see any recent 'CRASH' filetype files.

Thanks for the reply, I checked my antivirus firewall settings and I do see DCS is allowed access

Hello, I've been having an annoying issue lately with DCS. The launcher opens fine (using MT launcher with VR). However, at least once a week if not more, the game will refuse to launch and the DCS World pre-launch window just stays there as if it's trying to load. I've found that if I run the full repair, it fixes it and I can then launch the game, but the full repair takes some time and the issue returns weekly it seems. Then needing another repair to launch. Should I just try to re-install the entire game or has anyone run into this issue and solved it? My PC has no issues running DCS, so I don't think it's related to hardware or hardware limitations. It's a relatively newer issue that started within the last month or two. Thanks

Thanks, it turned out my issue was that I was leaving the INS selector on the GND mode after startup and takeoff. Needed to turn it to NAV or IFA for it to work. (Not exactly sure what IFA means though)

Followed the video but it just doesn't work for me. Has this changed since the video was made? I can load the targets fine and see them in the recall. I then click Use and 'T01' appears on the scratchpad immediately instead of the '0' yours shows. If I hit enter on T1 or click 1 and hit enter, the EHSD doesn't move at all. it just sits at Waypoint 1. Do you know how I can get the EHSD to stop focusing on waypoints and focus on the target points?