Abburo

Your behavior's description is related only and only to your scripts definition. You may PM me if you would like to let me have a look on your setup!

The heli landing is a DCS thingy. Is known fact they cannot actually land anywhere, especially if the landing zone is a slope. Try place a helipad on the landing area or rework your mission and make sure the landing area is suitable (flat area, airbase, helipad)

@currenthill the following query just stroke me ! You mentioned about the mines that they have to be set to invisible, though they still can be seen when an enemy unit is close enough. I suppose is about a parameter that will define what is the minimum visibility range. So, my query to you if above is true, can this setting be extrapolated to the snipers, eventually to any future JTAC/spotters? I don't have any idea how this works so please excuse me if I'm saying any non-sense

This is a absolutely fantastic addition CH! Thank you! This items opens a lot of scenarios. However, can you please explain a bit the " really up-close" term. What means more exactly. Is the exploding trigger embedded in the mine mod?

Are you going to be Grinch today? :)))... These are guided projectiles, not missiles .... so they are quite limited on their correction capabilities. There is also a reason setting up different skill levels for the units... right?

CH made a great effort to present his assets features best as he could ! But who to read

SAM sites IADS setup question is not for CH. He created the assets then the logic is applied from various scripts which already know the units capabilities. To answer your MANTIS question: is always a good practice to setup the SR as first unit, then there is absolutely no specific order. Having SR as first unit is more like a requirement for the Skynet IADS (mist), but definetly not hurting MANTIS. As we speak MANTIS is having an automode setup which works best of all. It requires just two lines of code, while rest of information is taken from the internal definition of sites (lorad/merad/shorad). Be carefull about SAM sites naming convention which is very clearly stated on the Mantis doc page: flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Functional.Mantis.html local BlueMantis = MANTIS:New("BlueMantis","Blue SAM","Blue EWR",nil,"blue",true) BlueMantis:Debug(true) BlueMantis.verbose = true -- watch DCS.log BlueMantis:__Start(5)

Because one of the other mods is conflicting with CH ones... you may add one by one the other mods, identify where the conflict is and choose to get rid of either of it... Neither CH, nor ED and also no other modder can keep up with this kind of conflicts... you need to assume it and work by yourself to sort out. You have to understand no one knows what's in your computer... Use multiple mods profiles in OvGME... just don't use them all at once... this is by far the worst scenario ...

No, is not ! .. check my previous answer to you, as well as the one for Timex... do what i was mentioning in there. I think CH is already super tired answering the same thing to everyone over and over....

I saw you having a lot of issues, where you should not. I suggest you the following: 1. Delete everything you have under DCS/Saved Games/mods 2. enable newest CH mods. Et voila !

That ALERT is not from CH mods... double check your mission scripts... etc

That mod seems to be quite old. I see no reason to preserve old mods, especially when you can have counterparts better done by CH. CH mods are safe to be used but are not intended to be 100% safe while using other mods.

Make a backup of your Saved Games/DCS Open Beta, then delete that folder and let DCS create a new one. You may revert the config folder for your "inputs" only after that. What you have is not related to mods!

@currenthill would ED want to give you a hand on this ? Shall we try make kind of "user" requests to them ? I'd happily sign on

Please, please... make sure it will sound VERY loud ... as it should be

@Dzsekeb the above changes are only on the scripts level and nothing else on the map itself ? Thank you!

Fix one break another 2

I've mentioned in another thread as well. Using mods hurry-scurry is by far the most unwanted way to play DCS. Use OvGME and create profiles. Use limited specific set of mods and try as much as possible to not mix to many authors into one ovgme profile...

That is so true as there are several absolutely great authors in here. My point is to try to no mix them all as @Joey_Destroyah did . Use specific sets for whatever is needed. OvGME profiler is our friend for this . And mostly the main problems come from airplane/heli mods ... ground units and statics are usually the safest mods in DCS by now.

Way too many mods, way to many different authors. Me personally I am sticked to CH mods and Massun92...

If I'm not wrong I think i saw the same behavior for the default revetments in Syria for example. Even a JTAC unit cannot spot the units behind them...

There is not such a list but you can find it easily. Using Notepad++ for example you need to create a workspace with folders of your interest (in this case CH mods). Then you need to search for "GT.DisplayName =" within that workspace. The results will look like in the picture below:

Why that, we can just imagine a submarine under water right? Can be a simple cube as it Isn't supposed to be seen anyway...

That's shame he is out of business, but we all have to thank him for his fantastic work ! I'm also on the same boat, kindly asking for ED to take this in consideration natively!

Wha'you'doin' ? :))))