Abburo

I would like to add just a short comment regarding of modularity of Sweedish mod. I can understand the flexibility of having every unit as its own mod mainly to save disk space, but in the same time this is having some drawbacks: - in multiplayer can generate issues if players have only specific set of units - the disk space is bigger because each unit have its own files, even some of them can be shared among all of them. - is cluttering the module list of DCS This is not a critique nor will stop me using it ... by contrary... but I just felt that will be constructive to have some feedback

Hi guys, Currently I found the Leclerc is not drivable (other frenchpack units are... ), and script to deploy units by marker is crashing DCS to desktop. Is this something only on my side or must be consider for correction? Thank you!

The vehicles are absolutely great. The lights for police, ambulance and firetruck are from another world ! Thank you !!

That's a great immersive mission. The real time menu is absolutely fantastic and first time for me seeing such development. One single issue I went to by now. While I was running the powerline EMP thingy, one of transformers explosions affected my heli. On the next mission the landing did no triggered next steps so I assumed is because the damaged I took. Also the nice menu/realtime planner disappeared. I have returned to base for repairs, but that was not possible, maybe because there were not present the required FOB vehicles for this. I don't know how it works but maybe would be good to introduce an on demand mission for repair or refuel... Thank you for your great work @Presidium !!!

Waiting for it ....

Try to disable "Speech recognition for Windows Mixed Reality"

Excellent mod... step by step these kind of mods will take over DCS assets !!! One thing is not clear for me... where are the vehicles? Are they released yet ?

I used to have such similar issue on my side for mission editor, but even worse. Look like ME filters were not working at all. My take was to delete everything from my saved games, and preserve only the aircrafts inputs... this solved my issue.

Attached you'll find a test mission created by @Apple/Applevangelist in which the MOOSE Mantis functionality is emphasized for SMA assets. Just to remind/clarify to anyone not fully aware: Moose Mantis is a function which emulates an integrated air defense system, similar to the older Skynet IADS, with pros and cons. However, the MOOSE devs (in this case Applevangelist) are very supportive and quickly integrated the Sweedish assets into their core framework ! You may read and learn more about further MANTIS configuration here: https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Functional.Mantis.html Kudos to both Moose and SMA mod teams! MTS-410_-_MANTIS_-_Automode_Zones (1).miz

Is any good reason to use this Arduino interface over the CLSim embedded vJoy functionality for Force Feedback ? Asking this because i'm using this vJoy workaround and seems fine... and not sure if Arduino can do more!

LA-7 and Yak3P were my favorites while i was playing IL2 Sturmovik 1946. Buying it day one!

Will try to make comments in script so that will be easier to understand and adapt to your needs!

i'll try to create a basic MANTIS setup for sweedis mod... @currenthill is any of the short range SAM site able to defend against HARMS?

Hi @currenthill, I am looking forward to add the swedish SAMs into the "Mantis" function in MOOSE. Mantis is an alternative function to Skynet IADS, but is made in moose framework. It is having it's own features and drawbacks, still is a very functional and easy to use implementation of IADS. I was thinking to add the data according with the syntax required in Moose that can be seen in the table below. However, I am wondering if you would be able to compile such a list for Swedish assets better than I could do by browsing the .lua files... maybe i could miss something. "Blindspot " is a minimum firing range around the SAM site. Radar is the type name of the radar bearing unit, in case it cannot be identified otherwise. So please let me know if that is something you could do on your side, or if I should try my best guess on it . After that we can submit this to the Moose devs so that it can find it's way in the main branch . Thank you in advance MANTIS.SamData = { ["Hawk"] = { Range=44, Blindspot=0, Height=9, Type="Medium", Radar="Hawk" }, -- measures in km ["NASAMS"] = { Range=14, Blindspot=0, Height=3, Type="Short", Radar="NSAMS" }, ["Patriot"] = { Range=99, Blindspot=0, Height=9, Type="Long", Radar="Patriot" }, ["Rapier"] = { Range=6, Blindspot=0, Height=3, Type="Short", Radar="rapier" }, ["SA-2"] = { Range=40, Blindspot=7, Height=25, Type="Medium", Radar="S_75M_Volhov" }, ["SA-3"] = { Range=18, Blindspot=6, Height=18, Type="Short", Radar="5p73 s-125 ln" }, ["SA-5"] = { Range=250, Blindspot=7, Height=40, Type="Long", Radar="5N62V" }, ["SA-6"] = { Range=25, Blindspot=0, Height=8, Type="Medium", Radar="1S91" }, ["SA-10"] = { Range=119, Blindspot=0, Height=18, Type="Long" , Radar="S-300PS 4"}, ["SA-11"] = { Range=35, Blindspot=0, Height=20, Type="Medium", Radar="SA-11" }, ["Roland"] = { Range=8, Blindspot=0, Height=3, Type="Short", Radar="Roland" }, ["HQ-7"] = { Range=12, Blindspot=0, Height=3, Type="Short", Radar="HQ-7" }, ["SA-9"] = { Range=4, Blindspot=0, Height=3, Type="Short", Radar="Strela" }, ["SA-8"] = { Range=10, Blindspot=0, Height=5, Type="Short", Radar="Osa 9A33" }, ["SA-19"] = { Range=8, Blindspot=0, Height=3, Type="Short", Radar="Tunguska" }, ["SA-15"] = { Range=11, Blindspot=0, Height=6, Type="Short", Radar="Tor 9A331" }, ["SA-13"] = { Range=5, Blindspot=0, Height=3, Type="Short", Radar="Strela" }, ["Avenger"] = { Range=4, Blindspot=0, Height=3, Type="Short", Radar="Avenger" }, ["Chaparrel"] = { Range=8, Blindspot=0, Height=3, Type="Short", Radar="Chaparral" }, ["Linebacker"] = { Range=4, Blindspot=0, Height=3, Type="Short", Radar="Linebacker" }, ["Silkworm"] = { Range=90, Blindspot=1, Height=0.2, Type="Long", Radar="Silkworm" }, -- units from HDS Mod, multi launcher options is tricky ["SA-10B"] = { Range=75, Blindspot=0, Height=18, Type="Medium" , Radar="SA-10B"}, ["SA-17"] = { Range=50, Blindspot=3, Height=30, Type="Medium", Radar="SA-17" }, ["SA-20A"] = { Range=150, Blindspot=5, Height=27, Type="Long" , Radar="S-300PMU1"}, ["SA-20B"] = { Range=200, Blindspot=4, Height=27, Type="Long" , Radar="S-300PMU2"}, ["HQ-2"] = { Range=50, Blindspot=6, Height=35, Type="Medium", Radar="HQ_2_Guideline_LN" }, } --- SAM data HDS -- @type MANTIS.SamDataHDS -- @field #number Range Max firing range in km -- @field #number Blindspot no-firing range (green circle) -- @field #number Height Max firing height in km -- @field #string Type #MANTIS.SamType of SAM, i.e. SHORT, MEDIUM or LONG (range) -- @field #string Radar Radar typename on unit level (used as key) MANTIS.SamDataHDS = { -- units from HDS Mod, multi launcher options is tricky -- group name MUST contain HDS to ID launcher type correctly! ["SA-2 HDS"] = { Range=56, Blindspot=7, Height=30, Type="Medium", Radar="V759" }, ["SA-3 HDS"] = { Range=20, Blindspot=6, Height=30, Type="Short", Radar="V-601P" }, ["SA-10C HDS 2"] = { Range=90, Blindspot=5, Height=25, Type="Long" , Radar="5P85DE ln"}, -- V55RUD ["SA-10C HDS 1"] = { Range=90, Blindspot=5, Height=25, Type="Long" , Radar="5P85CE ln"}, -- V55RUD ["SA-12 HDS 2"] = { Range=100, Blindspot=10, Height=25, Type="Long" , Radar="S-300V 9A82 l"}, ["SA-12 HDS 1"] = { Range=75, Blindspot=1, Height=25, Type="Long" , Radar="S-300V 9A83 l"}, ["SA-23 HDS 2"] = { Range=200, Blindspot=5, Height=37, Type="Long", Radar="S-300VM 9A82ME" }, ["SA-23 HDS 1"] = { Range=100, Blindspot=1, Height=50, Type="Long", Radar="S-300VM 9A83ME" }, ["HQ-2 HDS"] = { Range=50, Blindspot=6, Height=35, Type="Medium", Radar="HQ_2_Guideline_LN" }, }

These units mobility seems like a dream ... it simply can add a new layer of possible missions... swedish army excels on mobility and stealth capabilities !!!

@currenthillHow to deploy the RBS70 from BV410? Should i find an F10 menu command? I did not find it yet. Is it something will be available later? Or am I completely off-road ? :)) How did you managed to get them properly aligned with the target?

One more query... how can we find out the rearm timing, and how many rounds is having each unit, including infantry especially ATGM, manpads and sniper team.

@currenthillfirst of all thank you for your hard work and the excellent result !!! Secondly, I don't know if you realized when you created this mod how well could be suited for heli logistics actions. For example a Gazelle could transport and infiltrate a sniper team or an ATGM in some strategic spots... perfect for ambush or stealth actions ... Did not try it yet, however the only think I got in here that would need some work according with what I was mentioned above would be the posibility of movement for sniper team, or at least posibility to rotate ... this would be required becasue spawning from heli cannot really control where they will face to. Once again , big thumbs up!

I think the forum is loosing it's visibility as new comms ways are arise and here I need to mention especially Discord. Is not like people are not flying JF17, but more like your message is not seen. Try join various Discord Servers, including ED's official one and make your call again !

@gotit DCS standards are just not for you, but as you can see there is another player base seeking exactly what you don't like. Some brains can adapts easily than others to all those kind of things (no pun intended, just facts). The best option for you is either to play FC3 modules or change the simulation/ gaming platform to something that would suits you.. check Arma3 for example. I would also thank you for your comment because is a truly and hearty statement that could help people making their decision to onboard DCS or not !

There still are some great workarounds which can make your flying experience even more natural. I would agree some of them are not indeed applicable to everyone but at least I would like to bring them to your attention to have a look into: 1. Using VR headset (a high resolution one) - while using zoom you can focus only outside if you want... or you can focus on a specific bit for your cockpit. In VR the zoom function have two levels and will be active only as long as you are keeping the button pressed. 2. Exporting your gauges - Helios would be the best tool for this so you can have a full fledged cockpit clearly seen on a second monitor... including MFDs. There are also some Android/IOS apps for these, but Helios is the master of them all. Can be used even on a separate computer/laptop. As said in the beginning, those are kind of workarounds, and I do admit that not everything is perfect, as we are inside a simulation.... as good as it gets.

In some circumstances pilots are using binoculars. I think this can be easy understood as a RL zoom which magnifies even your avionics... @L0uiscyou are saying your computer cannot cope with the 2.7 version (because of reasons)... for same good reasons most of our computers cannot cope with the full complexity of graphics nowadays, so there are required such workarounds... And to be more precise, to render up to a visible level some very distant objects, even using LODs, will simply kill our computers.... is just a compromise. In the same manner, you cannot compare let's say a 4K 24" monitor with a 4K 46" monitor... but we all still need to enjoy this game (oops is not a game but a sim ) And don't forget, we even have labels to leverage a bit visibility issue... there are the "neutral dots" which are working pretty ok ...

VBS4 engine have an interesting mechanism. The map is procedurally generated on server side then somehow is sharing it with the clients... could be a thing for DCS as well maybe... just my thoughts!

Your updates should be posted on the main ED Discord server ... no joke ! Thank you @Charly_Owl

Much appreciated your input @Sneep !!! I wasn't aware about this feature at all !!! Your tool looks exceptional great and can cover one of the biggest misses for DCS. I am thinking at the Arma3 Launcher which is able to read what mods are required by a specific server, then it might allow the user to check if those mods are already downloaded, if the versions are correct , then update them accordingly, allowing a user to join. This would make the users experience far greater, by having various other mods installed, like VPC assets, specific livery sets, and so on. Indeed this would require some rework of repository by ED itself, but this might be doable anyhow. Did you ever considered a partnership with ED for this? Arma3 in the beginnings had also a open source launcher doing the exact same things, then they moved this entirely within Steam. For DCS case, the mods source should remain on ED site... but they would require some rework to standardize how files are presented. Some users upload the mods as OvGME ready, others not... and this is where some effort is required. If needed, and having ED support to allow such a standardization I would also be happy to work on some tedious activities as checking the mods and changing their presentation within. Also users might be able to create mods profiles by themselves and activating them according with the server they are joining.