Draken35

Place an invisible FARP and the Harrier in it

Had something very similar yesterday after a motherboard bios update... After some hair pulling, I was out of ideas and opened the Oculus software and clicked on devices....To my surprise, I saw a recommendation to connect my link cable to an USB 3.0 port (which is were it is connected to!). So, I ran the port/cable test and it all went to normal. Just an idea of something to check if you haven't already. Good luck!

this: works very well.

Not sure if it is working properly in 2.7 ... I remember testing it in 2.5.6 and it did work, if your were able to find flat terrain long enough. Of course, the AI cannot use it.

Excellent Luiz! Glad to hear... In this time and age, with the pandemic, is hard to tell ! And yes, Due to work too, I cannot "fly" much during the week and get to the weekend experiencing withdrawal symptoms too

It was mentioned in their Discord that the TOO issue was fixed in their internal build and was waiting for ED to push it. That was before 6/23. Unfortunately ED did not pushed 3rd party fixes in the last patch

Thanks! Good to know that it is just normal life

It has been a couple of months without updates on Github or the team posting here.... Hope everything is ok with them....

or just create the TP's in the EHSD Data.... Either way we need to type coordinates... The beauty of using the TOO is, that the target can come directly from the sensors, which is, I assume, what OP intends ... For sure, is something I want

I was referring to the context of your initial post about " multiple JDAMs in one strike without switching to multiple TGT" ... In order to do this, you need to select the TP you want to attack in the JDAM configuration by "colonizing" the corresponding TP's as you know... Well, the bug is that we cannot "colonize" the TP if it was created from a TOO. We need to wait until ED push out the next 3rd party update to get the fix.

Nope, not "fine" ... TOO can indeed create a TGP now but the created TGT cannot be used for JDAMs as of now. Next update is supposed to fix that

Most likely you cannot hear Betty or the Sidewinders either... I think your are missing this guy here (highlighted):

Syria is also my got to map... I was in the market for a "flight by the seat of your pants" aircraft and tried a couple of the warbirds but this thread made me evaluate the Tiger... I now, own it Thank you!

+1 And give the boots laser designators and comms so we can have dismounted JTACs (with laser designation capabilities)

I haven't flown at night since the last patch... During the day, in Syria at least, the changes (see above) to Display_StrokeDefs.lua still wok while combined with decreasing the gain a lot and some contrast adjustments. It is the only way that I can use the moving map.

Much appreciated!

Yes sir, I went back to the LUA changes I posted before .. It seems the the excessive gain is no longer an issue (I've only tested so far in Syria and PG). The main problem, IMHO, is the black outline... I suspect RAZBAM is using it to fix the lack of contrast of the fonts and symbols,,, Or, perhaps, it is the lack of enough symbiology brightness... The effect that the outline produces in my EHSD when the moving map is on, is a vibrating feeling that makes the symbiology unreadable and causes dizziness if stared at it too long.

Or not.... Just downloaded the update and jumped in in the cockpit to check... With the moving map on, font seems to "vibrate"... Basically EHSD looks unusable with the map on, regardless of chosen color. Looks barely okay and useable with the map off. I tested on the Syria map and need to check the others (since the map used to behave differently in the other maps). As a control, quickly changed slots in the same mission to the Hornet, Viper and Hog and I see no changes in the quality of their displays... VR Quest 2 at max res.

Apparently the fix for this is waiting for ED to push the 3rd party patch...

It appears to be... A few months back, I got one stopped working on me and I doublechecked in Tacview that I was not hit (Nobody ever shoot at me in that sortie) and "random systems failures" was off. After that, I'm careful with turning it off after weapon impact. Anyway is a very simple test

The other AFAC tasks work when the Harrier spawns unarmed and is rearmed so... Of course, cannot say if this is a Harrier bug or an ED one... Don't have any other airplane that does not have built-in guns to test this...

Well... I kinda feel like an idiot for not thinking on this before... Still not sure if it is "as intended" but here is what I found: On these kind of missions I usually leave the aircraft unarmed and at 50% fuel.... Well, one thing that the A10, F16 & F18 have that the Harrier doesn't is a cannon... So, I went ahead a put a gun pod in the Harrier, in the mission editor, and voila! It can communicate with the AFAC using the FAC Start Enroute Task as expected. Note, the aircraft needs to be armed in the mission editor at least (I have not tried with the mission planner) because if it spawns in the mission unarmed it will not work, not even if you rearm it.

I'm not using mist for that yet.... Getting my feet wet with the ME ... If you own the A-10C or A-10CII and Syria map, I'll be willing to share it with you in its current state

@Recluse That mission uses the FAC-Engage group ... Which is different task and that task works for me, in different missions, but defeats the purpose of randomness - unless, of course, you are willing to add multiple tasks - one per each of the possible random groups (50+ in the case of the mission that made me discover this issue). I truly appreciate your answer, don't get me wrong! But I am not looking to an alternative way to do it, since I know the workaround already... Just pointing something that works for other modules but not for the Harrier. And, yes, I just saw the new update.... I'll test and report back later.

DCS 2.7.1.7029 .7139 Open Beta Started working on a randomized targets JTAC mission for multiple modules and when added the Harrier, I noticed, after much troubleshooting, that the FAC Start Enroute Task is not working (not sure since which version). Attached are a simplified mission and a track running it showing the issue. You will notices that the JTAC menu does not appears in the Harrier while it does in the A-10C II, F-16C and F-18C . Not show in the track but I've tested changing radio frequencies to match everywhere and still doesn't work. It is worth noting that the "real" mission, with the randomized targets and JTACs is a lot more complex and involves delay starts of multiple objects and works like a charm for the ED modules mentioned above. Edit to add: What is used as a FAC/JTAC does not matter... Tried with other airplanes and ground units and the behavior is the same. AV8B FAC Issue.trk TEST-JTAC.miz