xaoslaad

Oh, great! Glad it works! Enjoy!

Thanks, I'll look in a bit!

Do you mind sharing the mission? Also, I will double check that what I copied is complete/correct... using git on Linux and the game on Windows... copying/pasting code here and there; possible I screwed something up, which would be the best scenario.

Hey EasyEB, this is exactly what I would have expected with two JTAC following all targets: https://youtu.be/jPDYa1un4uE I get similar results with two vehicle, two troop, etc. That script in the video needs minor correction as well: ctld.JTACAutoLase("AFAC", 1688, false, "all") ctld.JTACAutoLase("AFAC1", 1688, false, "all") I had the last two options flipped, which I figured out quick when doing troop and vehicle; no harm doing 'all' in that case). Are you seeing something different?

I'll check. I had one troop and one vehicle jtac and they were each following their targets. I cant imagine why two vehicle or two troop or two all would break, but I'll try.

Yes, for the F/A-18C... http://forums.eagle.ru/showpost.php?p=2563925&postcount=1

EasyEB try this one on for size. https://github.com/jmontleon/DCS-CTLD/blob/improved-priority/CTLD.lua https://raw.githubusercontent.com/jmontleon/DCS-CTLD/improved-priority/CTLD.lua Just use nothing, "vehicle", or "troop" as it was before I made any changes. Priority system is always in effect. use hpriority for your high priority targets, priority for your medium priority targets and everything else will be low priority. I think that's a pretty good range of possibilities. I tried different JTAC's lasing only vehicles, troops, or all, and squishing targets at various ranges in the expected order. Seems to work. Also, not sure it will work. Try ctld.clearupJTAC("groupname") and see what happens, if he stops for good. If that doesn't work I'll see how one might go about doing that later.

I'll have to read the script later for that one to tell you :)

I've been pondering these things as well and how to iterate the possibilities in a sane way. Logic makes my head hurt a bit. Probably a sane way to do it. Need to think on it more and stare at the loops a bit more.

I haven't looked at the ctld code for notifyCoalition but I'd imagine it's calling a DCS function to message the coalition. In the mission editor in the trigger menu you'd see you can message all, coalition, or even a group. What you want should be possible, but you'd probably want to add a group notification function that closely mimicks the coalition notification function. The other alternative might be to do something like make an option to specify a group for jtacautolase, make the notification just a tad more generic and if a group is specified send it to a group, otherwise send it to the entire coalition. I could probably do that given a bit. I also thought for my change it might make sense to make a function to call to see if a target is visible, within range, and not already targeted, since there are now two very similar loops, but haven't gotten there yet. Progress though.

Near the bottom edit ctld.notifyCoalition(_message, 10, _side) Change 10 to however many seconds you want it to display. There are lots of items at the top to edit. This could be made a parameter at the top to maybe make it a little easier to find as well, but regardless still easy to edit. No number will ever make everyone happy, but you can use the F10 menu to call for dtatus if you miss it too ;)

Try the updated version: https://github.com/ciribob/DCS-CTLD/pull/11/files https://raw.githubusercontent.com/jmontleon/DCS-CTLD/priority-system/CTLD.lua I think this fixes it. I had 1 priority target, both on priority system. started with one active and he targeted the priority target. Activated a second one next to him and he picked up the closest non-priority target. I left out a bit of ciribob's logic for the loop that is in retrospect important.

Intel i3770k with Intel HD 4000 works ok. It runs windowed 1280×1024 with 3d disabled fine. I do not know about 2500.

Let me see if I can figure a way to make that work better

Attached on the post linked below. Make sure you're setting the unit name, not the group name. It's usually something like Unit #001, etc. In my example you'll see 4 Tunguskas in individual groups. The group names are something like SAM1, SAM2, SAM3, SAM4. But if you look at them the unit names are priority 1, priority 2, priority 3, priority 4. This way of course you could have a mixed group and still prioritize whatever you want within it. Even though I didn't do it like that the Tunguskas could have been all in one group or even mixed in with the armor groups. It's also preferable this way because a group can be spread out and part obscurred and part not and the logic to know if there is a priority target within view would get sketchy fast, so it's based off of Ciribob's code to find the closest target which works similarly. Anyway, in this you should see the AFAC lase the Tunguskas, despite being further in range than most the other targets and then he'll start lasing the others once the Tungaskas are destroyed. Now, if you were to put a 'priority' Tunguska on the other side of the map it'd be ignored as he cannot see it. He still does JTAC for what he can see. That much I tested. Should the priority target come into view he will acquire that next. http://forums.eagle.ru/showpost.php?p=2671232&postcount=50

I did this so I can optionally make them concentrate on certain targets first. This way I was able to prioritize SAMs ahead of other targets. Other variations are certainly possible. Maybe like a "permitted" option or something that will only allow targets if they have "permitted" in the name if you want them to lase only a bunker or something special. Logic would be similar. https://github.com/ciribob/DCS-CTLD/pull/11

I have multiple occasions now where my pilots vision has blurred and ears start ringing or straight blackouts while in a relatively stable flight path. No hard turning, etc. Am I doing something to incur this behavior or is there a bug?

Speak for yourself. If you want those badly you can easily and non-destructively add a few to your warthog; as many or as few as you want. And the ministick works quite fine with a little practice; the only other ministick I've ever used is on the X-52 and it was a bleeding PoS... when it worked it was ok, but it did a bunch of maddening nonsense I've never seen the warthog do...

Looks like trackhat plus... $40 seems good... I'd be curious what shipping to the US is as a comparison. I think the Trackhat clip plus was $80 when all was said and done... My only complaint is the circuit board was hot glued to the battery and came undone... I had to open it up and gorilla glue it so I could plug in the usb cable again... for $80 I expexcted a lot better, but it otherwise works fine.

Examples Here's a couple similar examples. The flak is very light; mostly for scenery/feel. You can definitely make it MUCH more brutal. Train Station Defense.miz Train Station Attack.miz

If you're in a hover it's not hard to steady the laser on a target. You can't lock, but you can still rain death. It's actually a lot of fun if you have an OA-10 designating targets with the IR pointer so you can find them more easily. Did that in a pick-up group of 3 or 4 Ka-50's and an A-10C online once. One of the more memorably fun online experiences methodically taking down AAA defenses.

Doesn't seem so. I tried with A-10 and JTAC with no luck.

You should call valve and tell them the news...

That's a bad assumption. GR9 never had brimstones outside of some testing, possibly.

Esxi is a vmware product. /facepalm