Edded

AI manpad. It doesn't even fire at all even though LoS is good.

Hi, I just ran into this as i'm having trouble having manpad to shoot at target below their own altitude. It seems the problem is still there. ManpadAlt.miz

Thanks for the help. I couldn't get this to work. But I did not check to see why already. I've also figured that there are units like SA8 or SA9 with 'AAA' in the group name. Couldn't figure if it matter or not tho...

Hello, I'm looking for a way to apply a specific option (Altitude restriction max for AAA) to all AAA units on a map. There is around 100 / 120 AAA groups without this option, and i'd like to apply a script/trigger that set this option with a specific altitude at mission start, without editing each group individualy. I've used the same name prefix in group name for all the groups if that is of any use (REDAAA for red and BLUEAAA for blue).

Thank you for your answers. I don't have any antivirus installed other than default protection from Windows so i checked the events log. I couldn't spot anything unusual. I restarted my pc without doing any thing else than what i described in my earlier post. Since the reboot DCS is working smoothly again.

hello guys, I am running latest DCS World open beta version, using ED launcher (not steam). I updated the game to the 2.5.6.54046 on the 27th august and the game worked fine. The 29th august i had a launcher update and since then i'm having 4 errors that appear whenever i launch the game and that stop the game from running : My system is in french but it says for each "The procedure entry point XXXX could not be located in the dynamic link library XXXX". I've tried several things but i still have the errors afterward. 1- delete manually the .dll affected + repairing the game afterward. 2- run the windows cmd as administrator and run "sfc/scannow" in the dcs install directory. 3- Rollback to an older open beta version. 4- uninstall + reinstall the game in the same location. 5- uninstall + reinstall in an other location (changed the disk where the install is). at this point i don't have any idea about what to do... So if any of you have a clue :helpsmilie: Anyway, thanks

It has been a long time since this post hasn't been active, but since i didn't find anywhere else to post and since this bug is still bothering my game experience. I have seen this bug since 2.5.5, (when i bought the f-14), and it's still happening in 2.5.6. I'm using TM Warthog stick and throttle and TM Rudder pedals. I've found that to me the conflict is happening whenever there is only 1 throttle axis mapped ingame. Then my Rudder axis goes red. So as i wanted to have the axis "Throttle Both", i just mapped Z axis of the TM Warthog throttle in it, and mapped RZ axis to the "Throttle left" then tuned this last axis to have 0 saturation. In this way there is no conflict anymore, and i don't need to change game files.