Jump to content

flywaldair (Skynet dev.)

Members
  • Posts

    199
  • Joined

  • Last visited

Everything posted by flywaldair (Skynet dev.)

  1. Ok, the compiled script now features a remark in the first line with the build time: -- BUILD Timestamp: 03.03.2020 21:35:37.55 Please check you are using the most current versions, by checking this line on GitHub.
  2. Yep, its time to give the scripts a version. It seems you are not using the most resent Version: https://github.com/walder/Skynet-IADS/blob/master/demo-missions/skynet-iads-compiled.lua In Commit: 82a5a91 is the most current one as of 03.03.2020. Oh and the unit test mission is intended for IADS development, not mission building. The unit test mission does not runwith the compiled script but all the single class files in the source folder.
  3. Added unit tests, should result in less bugs: :thumbup: https://github.com/walder/Skynet-IADS/tree/master/unit-tests
  4. Hi Guys, While working on my Skynet IADS Script, I came to the point where I wanted unit tests to make sure I did not break parts of my existing code while adding new features. I adapted LuaUnit to work with DCS, you can view the code and a demo mission here: https://github.com/walder/Skynet-IADS/tree/master/unit-tests I did not write a unit test for my changes :helpsmilie:. basically I rewrote the terminal output to env.info() It writes the output to the dcs.log file located at: \Users\Your Home Directory\Saved Games\DCS\Logs\dcs.log You can use a simple log viewer like https://www.baremetalsoft.com/baretail/ to inspect the output. Learn more about LuaUnit: https://luaunit.readthedocs.io/en/latest/ https://github.com/bluebird75/luaunit
  5. I just checked, setting Hidden on Map hides the unit in the hornet's SA page. FYI: I'm on the last 2.5.5 build not the 2.5.6 beta.
  6. Hmm I added a few more iterations over the sam sites but nothing too crazy. Let me know if it is due to the script. Did you ad something in large quantities? Like 1k Sam Sites or 500 aircraft?
  7. In regards to the threat ring: Try setting the unit to hidden on map in the mission editor. (see screen shot) As far I remember should do the trick. Tutorial is on the list :). I may need a few weeks until everything is finished. In the mean time you can drop me a message and I will try and help you as best I can.
  8. Hallo Zusammen, Vielleicht habt ihr es schon im englischen Forum gesehen, ich arbeite zurzeit an einem IADS Script: https://forums.eagle.ru/showthread.php?p=4221918 Last mich wissen was ihr davon denkt.
  9. Totally, agree! I also read about this function, I will look in to it once I am done with features for the IADS.
  10. Thanks, I will look in to it. It's time I add some unit tests to make sure I don't break anything with an update. In the spirit of DCS: this script is currently in early access :thumbup:
  11. Thanks I have read about this function in the docs. I curently like the idea that a mission builder can decide if a SAM is part of the IADS or not. However I could ad a simple setup mode with these descriptors. The don't by any way include range? Grimes build a database due to the fact that he could not access range etc. But that was back in 2013.
  12. Have you looked at the documentation? https://github.com/walder/Skynet-IADS I will look in to a YouTube tutorial once the features are more complete. Or maybe one of the DCS youTubers will be interested in doing one? :smilewink:
  13. Thanks, for the feedback, I just updated the repo with a new compiled script, I re wrote that part. Let me know if you can use the new compiled script.
  14. That's worth thinking about. I would have to test the script how well it handles edge cases and garbage groups ;-)
  15. SAM Sites will now act as EW radars, if you give them the corresponding parameter, see: https://github.com/walder/Skynet-IADS#sam-ew This function is not yet in the compiled script. You can use it in the test mission: https://github.com/walder/Skynet-IADS/blob/master/demo-missions/in%20development%20dont%20use/skynet-test-persian-gulf-iads-developer.miz
  16. That sounds cool. I reworked the internal data structure of the SAM site yesterday, see: https://github.com/walder/Skynet-IADS/tree/master/skynet-iads-source I am planing on a fire distance option, e.g. 100%, 90%, 80% of the zone in which a SAM can fire. With the new structure I can add that at one place with 2-3 Lines of code. HARM Defence will be bad ;-). I calculate the impact point of the missile or bomb, if it's within 100 m of the SAM it will go dark. I think this will be more realistic than just an if (HARM) do.. The IADS stores a global track file per contact, that gets updated with the last time seen. You could also store the route a contact took. Maybe you can use that for an ingress / egress calculation?
  17. Currently I have no plans for GCI, bu who knows. I will try and put together a new build on the weekend. Fixed a few bugs, and Harm defence is almost finished. I'm looking forward to your feedback!
  18. could it be that you only added the short range sa10 radar?
  19. Until the in game IADS arrives check out my IADS script for DCS: https://forums.eagle.ru/showthread.php?t=264586 https://github.com/walder/Skynet-IADS
  20. Feel free to join the development ;-). In case you haven't seen it the single class source files are located here: https://github.com/walder/Skynet-IADS/tree/master/skynet-iads-source This mission contains a build of the single class files: https://github.com/walder/Skynet-IADS/blob/master/demo-missions/in%20development%20dont%20use/skynet-test-persian-gulf-iads-developer.miz Could it bee that you were notching in redards to the EW radar? Or that you where in a valley? I nocticed that the EW radars can't see you in such situations, so they can't inform the SAM site. You can add debug information on what contacts the EW radar sees: https://github.com/walder/Skynet-IADS#debug-information In general the SAM site will become live when a target is within firing range. I fixed the log error, thanks for letting me know.
  21. @pmiceli: Thanks, these are the areas I need to improve in the code. The IADS shouldn't try to create a Sam instance from a unit that is not a sam. Will update that in the next few days.
  22. Interesting I will look in to it. Did you try: StaticObject.getByName('03949944') -> where the number is the number presented in the context menu of the mission editor? If you can access an Object this way, you can just pass it to the IADS then it should work.
  23. Well I'm standing on the shoulders of giants :). Your SAM DB has been a really good basis.
  24. Thanks' :smilewink: Put it on the bug list, will fix it: https://github.com/walder/Skynet-IADS/issues/3
  25. At the moment no, since they would get no information about targets in their area. I will most likely add an option for a SAM site to always be on, so it can act as an EW radar and SAM site at the same time. I believe the S-300 is used that way. I also have visual spotting on my list, so if a sam site would visually spot a target it would go live. There's also a fallback mode when SAM sites loose connection to the IADS, see: https://github.com/walder/Skynet-IADS#the-autonomous-mode-options-are
×
×
  • Create New...