Sylosis

Ah well it's just me being bad! XD First try my Mig29 target dodged my missiles and killed me (shot 3 missiles at me, dodged 2, died with the last). Then the second time, I got too low when trying to rifle the vehicles. They shot AAA at me and they had one lucky shot. ONE bullet hit me and turned out to be a pilot headshot....

All right so I tried it two more times and everything was OK on both occasions. (and I still haven't managed to finish the mission! XD) I'm almost certain I did everything the same on every occasion, but anyway, at least it works.

More than a year late, but I have that same problem and it's the first time I try this mission. I have no mod installed and I did wait below 300 for Sting to join. Sting even confirmed they had joined Starboard, way before they had to break for IP. Got the radio message to break for IP, they replied they are breaking for IP, but stayed on my wing. Accelerated time quite a lot to make absolutely sure and they just stay there.

Sorry, R/BL, not BOL. Didn't save correctly (like it almost always does), hence why I tried to describe every step of what I did I think I wasn't doing a full lock with the A/G Radar. I wasn't pressing SSS towards the radar a second time to make a full lock.

First time I try the R/BOL mode and I must be doing something wrong. I set everything in the stores page (FLT, TERM, SEEK). Used the surface radar in SEA mode to lock a submarine. Maybe my lock was not directly spot on (difficult to get a perfect lock as the radar refreshes), but it was still almost on it. Mission I was flying needed me to report visual before attacking. So I had to get close, reported it and then flew away to around 10 nm. Turned around, made sure my radar lock was OK and shot. The Harpoon didn't fly at all towards my target. It seemed to be flying towards the waypoint I had active at the time. What did I do wrong?

Don't think the joystick went to idle and my computer didn't go to sleep either. It's something else for sure, but don't know what. Thanks for the suggestion on an app to back up the control files, I'll look into it. Probably quite useful!

Hi all, Just curious if anyone has any sort of explanation for this bug I encountered: - Played one mission in the morning (Windows 11, up-to-date open beta, multi-thread version), everything was fine. Close DCS, went to do something else, which included installing something on my computer that required me to restart it. - Logging in later in the afternoon for one more mission. As the mission starts, I realize that my Virpil throttle doesn't do anything. I open the Adjust Controls menu and all the controls mapped on my Virpil throttle are gone. There is nothing mapped, the list is empty. Everything else is mapped correctly, except the throttle. I load my control file (I back them up regularly as I'm used to having some DCS updates reset my mapping), click OK and in the mission the controls are not at all responding as they are mapped. - For example, in the "Adjust Controls" menu, I can clearly confirm everything is correct (I push every button and axis to confirm they are correctly detected and they are). But when I close the menu and go back to the mission, they don't work. The slider on my Virpil that I use to zoom in and out is now the throttle axis, but in the Adjust Controls menu it's clearly mapped on the zoom axis. - So I closed DCS, reopened via the "non multi-threaded" file and the throttle controls are, again, not mapped. I load my file once again, test it, it works. Start a mission, everything works. - Close DCS, reopen via the "multi-thread" file and everything is fine again. Through all of this I have not unplugged/plugged my controllers, I have not updated the Virpil softwares, nothing special. I've only installed something on my computer that is not at all related to DCS (and to gaming) and restarted my computer. There wasn't even a Windows update during that reboot.

Gotcha! Sorry, I assumed for some reason the update had already been pushed. My bad! As for the AI that is what I thought and maybe I should have worded it differently. It's indeed not really a bug and luckily there was only one left and I had not used my gun for the F5, so I had enough left for one boat.

I think a few of the bugs listed in this thread are still happening during Mission 3. 1- Way too soon the message "I'll take the two on the left, you take the two on the right" is triggered. I haven't even seen anyone on the radar, plus the messages from Strike, warning you that bogeys have taken off, happen much later. Not sure what triggers it, I think it's when you get close to waypoint 3. 2- My wingman doesn't engage the F5s 3- Dodge stops attacking even with one boat left. I think they run out of ammo and punch out. They were just going in circle doing nothing and I think they both said "I'm out" on the radio. Ended up using my guns to finish that last one and it triggered the end of the mission.

Thank you very much for the explanations. One thing I realize this weekend is that there is a chance I sometimes mistakenly install the E variant instead of the E2/L. And the other thing I might very much to wrong is what you mentioned. It's very likely that I forget to re-select the MAV and not realize it got unselected. But thanks a ton, your information was very detailed and clear. I think I have also experienced the problem you just described. However I can't reproduce it every time. But thanks for the tests, it's interesting to see you also encountered a few issues.

There are a few things that I struggle with on the Harrier. First point, is it designed as intended that whenever you switch your SOI (for instance, activating the TPOD), your MAV gets unselected and whatever warm up (or should I say, cooldown) was going on goes to an halt? Considering the time you have to wait for your typical IR MAV on the Harrier, I often get screwed by switching sensor to check something and not realizing my MAV has therefore been unselected. Is there anything I should be doing to prevent that and again, is this modeled accurately in DCS? The Harrier really behaved like that? Second point, how do you manage to have your SOI appear on the MFD that you want. I am often looking through my TPOD on the right MFD and when I push the IRMAV Sensor Select switch, it'll take the place of my TPOD MFD instead of appearing on the left MFD. What am I doing wrong? Third and last point, I can't get the sequence right for the LMAV. Sometimes it will work and sometimes it won't and I just can't understand why I can't use them consistently. I will do the following: - 1: At the top of my EHSD, select LMAV and wait - 2: Activate TPOD and make sure its laser is ready to lase. - 3: Find target with TPOD, then Designate it. - 4: Lase the target - 5: Uncage LMAV -6: Shoot My issue is that 50% of the time, uncaging the MAV doesn't do anything. Is it that I have to wait the same "cooldown" time in between shots as well? Could be the explanation to my problem, I am just unsure this is required. I have seen people not leaving the EHSD screen and actually selecting the LMAV from the Store page. Doing that, when they uncage it, the LMAV screen replaces the TPOD screen, but it seems the lasing is still in effect, so the tracker snaps the TPOD laser anyway. However I like having my TPOD on one MFD and the EHSD on the other, so up to now this is not a method I have been tried. Thanks for the help.

You mean that according to you it has been fixed or you mean they didn't even though clearly they should have?

I have witnessed situations like the one you describe, that is, some random laser drop, likely due to LOS. The situation however that triggered this post is consistent laser drop every time I fire. Because it happens online, I can't provide a track file. I might try to recreate in single player. That being said, I can confirm in the same evening I have tried with a friend lasing for me and everything worked fine. Pointing that maybe the predator AI is the problem

Not sure this is a bug, or really Harrier related, but I'm playing online with a friend on his own server and we're using some dynamic map he's found online. There are bunch of Predator JTACs in this map lasing targets and whenever I am able to lock their lasers using LST (for instance using a laser MAV), the Predator will drop it's laser lock 1 second after I shoot. My MAV is wasted and then 15 seconds later he'll lase the exact same target again. What's up with that?

The occasions where I have seen Jester not drop CMS is when I'm in a dogfight. My experience is that he actually rarely drops any CMS when shot at close range. Following your comment that would mean he "doesn't see" the missile but if so, that's a bit strange since you would think Jester is programmed to follow the enemy plane as much as possible. I mean I'm piloting the aircraft and I'm mostly able to keep visual and see the missiles coming to kill us.