Search the Community

I have no idea why I can't save tracks, that feature somehow got broken and it copies the same track over and over again. I am unable to save tracks, it just saves an old one each time, no idea why. Will try to fix it. So maybe someone can record a track for this. I think I found out that if you boresight your mavericks flying south to north, then boresighting the mavericks will have a slight error along the length axis, so it will deviate a bit before or aft of the target (little bit to the south, little bit to the north). If you now attack from east to west, the error will be to the side (still a bit north or a bit south, instead of long or short of the target), and maverick handoff will fail, because the error now matters, and you will land a significant distance away from your target. The error needs to be a angular one, not meters to the north / south / east / west something. Steps to reproduce: - Align your mavericks in the air, flying south to north. Check if they return to the target with TMS down, they will. - Now fly around that target, and attack the same target with a 90 degree offset (west to east). You will see that your mavericks are now shifted left or right. - Attack from the south, and alignment will be better again, because the error doesn't matter as much now (as you are a bit in front of or aft of the target, but the seeker will still point right at it) Maybe someone can test that and record a track... Because my track feature broke. Attached a mission file to test, there is a single target a bit south of the others. Boresight your mavs and that target, fly out east and notice the direction and visible amount of the error. Let me know if you see the same or not. Sounds weird, I know... So thanks for taking a look. Hope my description was understandable. Tested with the ATP but I'm pretty sure it's the same with the Litening. Mav_test_boresight.miz

Hi, I'm playing the Outpost campaign, mission 1. This worked prior to the last update. I hit the trigger point where the pilot tells the co pilot to fence in. When I use the George AI my weapons say systems not ready. I did an auto start on the chopper. I armed the weapons, then clicked on George and no weapons. I switched seats and clicked on George for piloting and no George. I saved a track file. thoughts? no systems ready with George .trk

@BIGNEWY, et al: Here is an example of GeorgeAI lasing a target beyond 8km then not lasing afterwards. He designated the target approx 2 times from 9999+ meters. The range decreased down to ~8,400m then no more lasing. I flew up close until landing next to the target. All the while, he would not lase. I purposely did not change any settings because I wanted to see if he would lase the target. This is EXACTLY what I talked about in my previous thread here: George AI and AGM-114L Lasing and Fail to Fire Problems. See my track and MIZ file. 2025-07-31 GeorgeAI-No Lase.trk AH-64 GeorgeAI Test.miz

When you start a mission cold and dark the laser isn't working despite the aircraft being armed. This is in DCS 2.9.18.12722

I'm not a great F16 expert and I recently purchased the Gambler campaign (no mods, integrity check done). The first mission uses a laser bomb, which I used yesterday without too much difficulty. Targets hit. Today, a new mission, still with GBU12, and I never hit the target: 2 bombs per mission, 4(!) missions attempted. The shot always misses the target. I've watched a lot of tutorials in case I'm getting rusty (I already finished First in Weasel a while ago), but now I'm starting to suspect there might be a bug. Thanks for the support. LastMissionTrack.trk

Hello, there is some rudder trim problem during ground taxing when then tail wheel unlock is selected. I know when tail wheel unlcok selected, apache will be very sensitive in yaw even on ground, that's why it need to be immediately trimmed to prevent oversteer And with the increase in collective to 30%rpm(as instructed in the tutorial), the increased torque will twist the aircraft to left or right. It was at the moment that the rudder trim overreacted. Here is my file rudder trim taxi 3.miz rudder trim.miz taxi rudder trim .miz

During takeoff, when speed exceeds 100 knots, tail plane is set to full up and aircraft nose goes up causing a stall and crash. Pushing the stick forward does not have enough authority to counteract to noseup attitude. This does not happen on any other aircraft in my hanger.

Regularly, the TGP will enter temporarily INR track mode while slewing, then the recent track mode is recommanded once slewing stops. Occasionally, the TGP enters a continuous INR AREA or INR POINT track. This will reliably happen when the TGP is masked. I noticed that during this state, actuating an exit out of AREA or POINT and then CZ is impossible to achieve by the usual 2x TMS aft. Pressing the CZ OSB will reliably return the TGP to the steerpoint, which often is a quick way to exit unintended masking while surveying the area. Only the TMS aft won't do in this case. While in a continuous state of INR AREA or INR POINT, TMS LEFT, FWD and RIGHT will still work normally, so it is still possible to switch TV/WHOT/BHOT and cycle between INR POINT and INR AREA. Only TMS aft is ignored. In the track we see me heading towards steerpoint 1 which is ahead of us. I then switch to steerpoint 2 which is behind us. The TGP following to the new steerpoint is ending up masked and INR AREA or INR POINT are displayed continuously. After applying a bit of slew, I then press all the TMS directions, all do work, only TMS aft is ignored. CZ by OSB does clear the CZ. When in regular POINT, AREA or INR, TMS aft behaves normally and applies CZ/ returns to INR and then applies CZ with 2nd press. 65 seconds track attached. no TMS aft to INR.trk

Recently I started flying on a server that forces cold starts and I noticed that GBU-38 & 54's won't ever align. If I fly on my normal groups servers and do a cold start same issue, but if I do a hot start they are aligned as soon as I spawn. Attached are 2 tracks one cold w/o alignment and one hot with immediate alignment. NEVADA DAYS TRAINING MAP 1.8-20250625-155858.trk NEVADA DAYS TRAINING MAP 1.8-20250625-154354.trk

Hi there, I got a slight problem I haven't encountered before in about 2 1/2 Years of flying the hornet. On the last 3 cold starts on the carrier I wasn't able to clear a WPNS DEGD advise on the bit page, no matter what I did. On top of that when I wanted to use the radar in A/G or A/A mode I got a flashing X on the hud and radar screen and I suspect both are connected. At first I thought the culprit could be a faulty ins alignment, but it happened 3 times no matter if I used stored hdg or not, and it also didn't matter if I selected ifa or nav after an ok alighnment. After choosing nfa it also showed a different text with rdr at the end on the hsi under the aircraft symbol with a timer counting up. I also never noticed that before. I did the cold starts on Syria and Caucasus Has something changed in the startup procedure that I missed and is it a new feature or just a bug? I attached a picture of the X on the screens and a track file. Weapons degd.trk

guys, if i press icp 4 stpt page, then SEQ, it should display mgrs after 3 sec but nothing happens. conversely if i select on icp, list 1 dest, enter mgrs and convert it function ok and then i have stpt in lat/long on stpt page any clue? thanks

In the attached track, both SLAM and SLAM-R are set to PP to destroy a T90 at the following coords. N43 46 00.55 E41 51 02.79 alt 4057 Both are set to fly a high profile. (cruise at 35k feet) Both are released within range The slam tops out at 22K feet . The slam-r at 15 k. Both are well below the high cruise profile. The slam-r hits the target. The slam falls short Any idea what i did wrong? (I dont know why the replay makes it look like my head is having a seizure. I use track ir and i really wasnt looking around that much) SLAMM.trk

Hey guys, I think this has been reported already, but just in case it hasn't I wanted to get the word out there. Whenever I use HARMs it changes the steerpoint but it never resets. I was on the South Atlantic map in the 4YA server and noticed it's changing SPT 12, 13, 14, 15, 16. I'll try to include pics to show I have a track file, but it's too large to add here. Thanks you in advance! Have a great day!

This is on the Shadow Reaper Syria Modern PvE server. They have pre-uploaded the waypoints for the missions. My waypoint was 108. My INS would bug out after about the 50ish waypoint. This happened with both a cold start or hot start, with or without stores. I attached a trackfile. If this is a bug, do we have a work around? I usually use the waypoints to begin search with TGP. If not, what am I doing wrong? Thanks SRDCModernSyria-20250114-093211.trk

Hello, easy to reproduce because it’s occur all time when you editing mission. When you add WP in flight plan on ME, if you add more than 14 waypoint, point 15, 16, etc don’t appear when you select seq1 on HSI. thanks

After 6 Minutes or so, I marked the SAM. I also placed a steer point right above the SAM, but I can't align the TGP weather to the mark point 26 nor to the steer point. This issue occurs several times to me. I've tried to push the CN button in TGP and HSD but it will not work... Not sure if it's a BUG or if I'm doing something wrong. tgp_defect.trk

Using the AGM-88C PB codes; entering the code for the EWR-1L13: Code 101, the code is crossed out, Will fire, but does not track to target. Is there any fix for this coming soon? I have also seen that code 102 for the EWR-55G6 is also blocked out with a X in the MFD. sorry if this has been mentioned, but i didn't see this directly mentioned. Aaron aka squatchy

So few days ago I reported a bug that in multiplayer cold start fighter to fighter datalink doesn't work: turns out it is not the case. It was two tankers with 6Y and 7Y tacan channels interfering with F18's TNDL. After a night of debugging deleting units one by one I narrowed it down to channel 4,5,6,7Y, but I didn't test with other channels. Attached are two tracks, one with tacan 7Y, notice I have no tacan bearing/range as well as any PPLI. When I switched to 3Y, PPLI returns. I didn't record 4,5,6Y's operation but these 4 channels are what I found out that jams datalink so far. I want you guys to know this is by no means a priority, mission makers can easily avoid these channels. Take your time to fix it and test it. 3YMIDS.trk 7Y_NOMIDS.trk