Sylosis

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.

Yea ok I can definitely say I'm intermediate at best. But there are a few things with Jester that seem like contradictory behavior. For example, he doesn't know who's friendly and who isn't but when you lock someone he will now suddenly know if it's friendly or not. Other example, he'll drop chaffs like crazy whenever any missile is shot, but there will also be occasions where he won't bother and let you die. I really just don't get Jester....

It was visible in radar and I'm fairly certain it was not a DL contact, but to be perfectly honest it's possible that for the specific instance I have in mind, it was. But I really don't remember. I was still able to lock it myself using the horizontal scanning so that makes me believe it was "lockable", but maybe these pilot radar modes are more efficient? At the end of the day, it's just very common for Jester to reply "no can do" and if it's because the radar doesn't see contacts then I guess the F-14 radar is more <profanity> than I thought? I've always read it was super powerful even by today's standards. But my experience is that I severely struggle to lock stuff (or keep locks) almost everytime

I guess I could change the title, but anyways, the fact of the matter the F-14 is one of the best module when it comes to everything except, at least for me, Jester. First, he's dropping chaffs all the time no matter who is shooting who. Can be a friendly shooting an enemy and he'll drop chaffs. Therefore, any way to ask him to only handle flares while I take care of chaffs? Still haven't figured this out. I thought I had by looking at someone on Youtube that was saying how, but it doesn't work. Also, Jester's incapacity to lock is really making it difficult to enjoy flying solo in the F-14. You can have an enemy aircraft at 15nm at 12 o'clock and 30 000 ft and he'll say "No can do" when you ask to STT lock enemy in front. What am I not getting? What am I supposed to do different?

Confirm I also suffer from this. Surprised they still create new bugs to this day.

Title says it all. Can't provide track because it is corrupted and doesn't show what really happened (I'm flying straight forever in the track). Wingman finished refueling before I did and I assumed it turned right ignoring entirely I was there also refueling. Part of a mission from Persian Lion campaign, although I doubt this is relevant

Hi, Often times, when refuelling, I can't get a "connect" even if my aim seems ok, so I then switch to the other side (suppose I was trying to refuel on the right side and it doesn't work, I switch left) and surprise, I easily get a connect even with a worse aim. Is this normal and if it is, how can I know which side to use?

To be honest I've always set it the same way, but maybe this time I did it differently. I'll double-check and test again, thank you for your help.

I'm never good at Air refueling, but I usually manage. Tonight I experience something I've never had issue with before: I am connected, I'm told "you're getting fuel" but my fuel gauge doesn't go up... It keeps slowly dropping Never had that before, what would be the issue?

Well the area my AI bombed was a lot more straight west, based on my TPOD compass at least. That being said, looking at your screenshot, I see it seems to be the case (mostly west, so west-southwest). Could be what messed me up, as I was looking a lot more south than that and found another building with 2 pipes on it. Can't say with confidence it's also at 250m.

Second target Jim asks us to attack is described as a "warehouse with 2 pipes 250m Southwest of their position". There is indeed a warehouse with 2 pipes 250m southwest of their position, but once I bombed it, nothing happened. I therefore asked Ein-stein to attack the warehouse and he bombed something at a completely different location. More like 100m west of their position. My reflex is usually to think I'm bad and don't understand something, but in this situation... I'm tempted to think something is wrong in the mission?

No it's fine. I was mostly curious to know if it was fixed like that on purpose or not. I see it is not fixed like that and that it has already been noted and discussed. I can definitely understand (and agree) why people prefer to keep it like that, it's simply more realistic. In my situation I think I couldn't have gotten more unlucky as the cloud was super big, dense, low and right where it had to be to make it nearly impossible to succeed. I'll run it again and hope it'll be not as bad! Thank you!

I was wondering if I'm just unlucky or if the mission design has some control over the clouds. At the portion where you have to shoot infantry on the roof east of a compound, which is north of Kerman, I've had a major huge freaking cloud over that entire area. To top it, the cloud is roughly 3000 ft above the ground. So I have absolutely no vision to try and find them with the pod... I had to resort to the red tags showing enemies and dive with the gun. But then again, I barely had time to aim. I was wondering if this is on purpose or if I was just unlucky and if I try it again, that cloud might not be there? (cause yes I failed that objective so I quit the mission).

Thanks for the suggestion, I'll look into it!

Awesome, thank you!

Wow.... And I made sure I didn't time accelerate during my flight, as I know this screws up tracks..... This is so annoying

I could be wrong, but I think mission 6 has the same issue as mission 3 which I think you just recently fixed. That is, we are given a grid, but no elevation. As such, when trying to designate with the TPOD, it doesn't. And any waypoint O/S that is created using provided grid will also not allow proper "Designate" when using the pod. Again, maybe I missed something, but it did feel like the same issue as mission 3.

Having run multiple tests lately, there is essentially just one mode that works for the MK-20. I do not think it's normal, probably poorly programmed by Razbam and/or ED. You essentially MUST drop them using CCIP. I tried CCRP with different methods (higher altitude, lower altitude, etc.) and even created a post on the Bugs and Problems for the Harrier, and others have confirmed CCRP doesn't really work. Meaning there are nearly useless if you're engaging an area that has some kind of air defense close by.

Hi, Might not be only Harrier related, but I'm flying the Harrier lately and this has happened on at least 3 occasions, one of which made me crash. If I dive for a gun run, it sometimes happened that I suffer from sudden extreme stutters that'll last maybe 1 second or 2, which is enough for possibly crashing. I can't attach a track because the only one I have is too big. It was at towards the end of a relatively long mission. I don't think I can edit/cut a track to keep just the relevant part, right? Also, this has happened on both the Multi-Thread and single thread version of the open beta. Every time it was in the Persian Gulf map, during day time. Every time, it was a dive for a gun run, just as I want to pull up. I don't know if the track will be easily watchable, since I did sped up time during my mission. From what I know, there is still that problem that tracks get "broken" whenever they are tracks from a mission that was accelerated. I have a decent computer and usually don't experience stutters, even when close to the ground. I don't even think my game settings are maxed out. Computer description: AMD 5800x, 32Gb DDR4, 3080Ti, Windows 11, 2560 x 1140 resolution, dedicated SSD for DCS.

Thanks for that. I also made some tests and might have similar conclusions. Did an Instant Action, but forgot to choose Persian Gulf which is the map where I was encountering issues, but I still think although I wasn't able to perfectly reproduce the same thing that bothers me, it's close enough. Attached is my track. First of all, I suck at landing and I'm probably doing multiple things wrong. So bare with me please. You can fast forward as I have to land to re-arm for MK20s. After that, I made the following tests: - High CCRP release - Dive CCIP release - Low pass 2 bombs CCRP release - Dive CCIP 2 bombs Both CCRP tests didn't do great. They completely missed the target, but I can't say I'm surprised. CCRP isn't a precise delivery mode and I'm probably not good enough for it. The first attempt at diving was interesting because I felt the bomb fell quite directly on a simple truck, yet it didn't do much damage. I'm no military expert, but that didn't look like a heavily armoured vehicle.... so why just 16% damage? Last dive is also interesting, because although it did kill the tank I aimed at (using 2 bombs in the release), it looked like the canister didn't deploy. I simply mean the animation felt wrong. But considering the truck got killed, I have to assume everything deployed correctly. Could you guys please comment on the 2 CCIP dives? The one that did very little damage, and the other one where it feels like the canister animation doesn't make it look like it deployed?(but probably did) Harrier Mk20 Test.trk

Well maybe I should have put this somewhere else but I thought of it as a "problem" and not a bug, so I felt it was ok to write this here? I kept searching after writing this post and I think my MK20 are simply not deploying. Meaning the canisters hit the ground directly without deploying bomblets and register very little damage. Is it possible that dropping them in CCRP at relatively high altitude (more than 8000 ft AGL) is causing this? I'll run tests later today.