Jump to content

xaoslaad

Members
  • Posts

    1171
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by xaoslaad

  1. I'll check it out. Might be the cause, thanks!
  2. Oh, great! Glad it works! Enjoy!
  3. Thanks, I'll look in a bit!
  4. 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.
  5. 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?
  6. 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.
  7. Yes, for the F/A-18C... http://forums.eagle.ru/showpost.php?p=2563925&postcount=1
  8. 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.
  9. I'll have to read the script later for that one to tell you :)
  10. 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.
  11. 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.
  12. 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 ;)
  13. 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.
  14. Intel i3770k with Intel HD 4000 works ok. It runs windowed 1280×1024 with 3d disabled fine. I do not know about 2500.
  15. Video is private. Perhaps you meant unlisted?
  16. Let me see if I can figure a way to make that work better
  17. 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
  18. 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
  19. This is a more advanced test using DCS-CTLD for lasing instead of the built-in JTAC. This way an AFAC will lase as well, which I couldn't get working otherwise, even though it should work. It's also testing a modified DCS-CTLD so I could get the AFAC to prioritize SAMS (any target I want really...) instead of blindly choosing what's closest. It's a multiplayer mission with an AI AH-64 standing by to perform as AFAC. OH-58 was causing weird and extreme lag, otherwise I would have used one of them. You could also have a friend in an A-10C do the lasing work. Nothing dynamic or crazy; just tests some possibilities. Hoover.miz
  20. Ka-50 and Su-25T do not use the same codes. You could probably fake it with an AI bird with DCS-CTLD
  21. No steering queues that I know of. I missed one of 4 the first time I made an effort because I was too off course. You will see a line come up from the bottom of the HUD to the top when you're the correct distance to drop. Not sure what's right, but center has been working for me. It'd be nice if there was a way to lock on based on coordinates fed to you and to get steered to the target, I agree.
  22. Havent tried with a human, but if it worked with AI it should work with a human!
  23. Attached a simple test mission above, should be able to see from there.
  24. OK, so now no crashes in 2.0, but GBU-12 STILL does not track when JTAC is lasing on 1688. Some magic involved besides this? Edit: Nevermind, working as expected. Had to follow the 500 JTAC prompts a little further Edit Edit: Test Mission with some mean old Tungs you can smash from 40k with relative impunity. Edit Edit Edit: And if you're still having trouble this is the process: JTAC Test.miz
  25. 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?
×
×
  • Create New...