sunski34

Salut, j'espère qu'ATME t'apportera ce que tu attends. Son principal objectif est d'offrir une base logicielle pour les missions multijoueurs et monojoueurs. Les deux types de missions sont alors compatibles en terme de scripting. Par ailleurs, ATME se base sur une approche modulaire, un module pouvant être générique et donc réutilisé dans plusieurs missions ou dédié à une mission. Comme l'a dit snow,les exemples te montreront les bases et la doc est essentielle pour comprendre le concept (même s'il reste encore quelques coquilles !) Je travaille actuellement sur la V1.2.1 qui amènera son lot de corrections de bug et d'améliorations : Ajout d'une gestion de tags pour les noms ou chaines de caractères. Ceci permet d'avoir par exemple des noms de groupes ou d'unité formattés genre "M2000C GBU #001" et de récupérer ou comparer chaque tag ici "M2000C", "GBU" et "#001". Il est ainsi aisé d'ajouter un avion de nom "M2000C GBU #002" qui aura le même traitement que l'avion #001. Ajout du verrouillage d'une fréquence radio pour éviter la superposition d'émission radio. La fréquence est verrouillée pour une durée donnée par une unité. Amélioration de la gestion du spot laser et IR avec une gestion de la perte de visée, la possibilité de cibler à partir d'un drône, un choix des priorités et une possibilité d'ignorer une cible proposée. De nouveaux événements core ont été créés pour celà. Ajout d'une possibilité de tracking à partir des senseurs réels d'une unité. Exemple : pour un radar, il est possible de suivre les targets détectées. De nouveaux événements core ont été implémentés pour ce faire. et d'autres fonctions à suivre. Par ailleurs certaines fonctions existantes ont été renommées afin d'être plus cohérent : ATME.rotateH (un peu bizarre en V1.2.0) est renommée en coordLocalToDCS et corrigée. Sa fonction inverse a été créée. Les fonctions liées aux spots débutent par spot donc par exemple activateLaserSpot et activateIRSpot de la classe ATME.C_AIUnit ont été renommées en spotActivate. La fonction startAircrafts de la classe ATME.C_Group a été renommée en start avec la possibilité de démarrer des véhicules, dans ce cas, l'AI est activée et si le groupe de véhicules dispose d'une route avec des waypoints alors il débutera son parcours. Voici quelques éléments à venir, une liste plus complète sera donnée ultérieurement. J'espère pouvoir publier cette version d'ici fin octobre. A bientot Sunski

Très bien, j'ai appris deux trois trucs. Par contre sur le RWR c'est 29 car le radar du SU33 et du mig 29 sont les mêmes, celui du 33 étant plus puissants de mémoire. Il ne peut donc pas y avoir de différence. Il me semble aussi que sur le RWR c'est comme celui du A10, plus la menace est forte (signal du radar fort), plus c'est au centre, donc menace grave. Pour le canon AA, les traits sont de mémoire à 300m et 600m à confirmer. Excellent travail cependant ;)

Here's the F5 mission for DCS 2.... with a script. It works because freq > 1Mhz testADF.miz

Humm yes and no... I want to update an old mission rescue with Mi-8 and Huey, in MP but in that case (frequency < 1MHz) that doesn't work :mad:

In ME I don't know because I didn't use it directly. With scripting functions no, that was ok beginning of 2017 with all frequencies. actually, ok only with frequencies upper than 1MHz. I will post a mission with F5 this night that's good in MP.

Hi, here is the thread : https://forums.eagle.ru/showthread.php?t=193885 Bug on 1.5.7 and 2.1.1 last updates Sunski

Basic mission example with no script 2 Frequencies : 430kHz (speach) and 450kHz (SOS morse) test ADF.miz

Hi, There's a bug in both 1.5 or 2.1.1 last updates, multiplayer mode. Radio frequency is set to a value less than 1MHz like in Huey or Mi-8, When using trigger "Radio Transmission" in ME (where now frequency setting is in MHz but decimal values seem to work in single player mode. In older DCS version that was in kHz), or when using scripting function trigger.action.radioTransmission, or when using command type "TransmitMessage" with controller:setCommand, then remote clients don't have any sound, any message (if using command) or any HSI ADF informations. It's ok for hosting client. When radio frequency is set to a value upper than 1MHz, like in F5 it's ok both hosting and remote clients have good sound, message (if using command) and HSI informations. Sunski

thank you Zeus Of course ... And that is perfectly understandable ;) Thank you again for your return, I appreciate :thumbup:

I can understand that of course... Planned delays can shift because of problems or other "havoc" as you said. Bugs and update shifts are cumulative little problems, and finally, that creates a big "problem" from customer's point of view. So, in that case, can you give us new delays for major updates like avionic or irritating bug fix ?

Hi, I'm agree with you. The best way is to have a On command and a Off command to have maximum flexibility of settings. In that case : Master Arm : Same command but well initialized when started. So no real problem. Warthog throttle switches can be used without problem with a down and a up config For FBW Limiter : Same command but bad initialized when started, so when you start with the swich in the bad position you have to click one on the virtual one to come back to the good synchronization. For Gun, no problem the command has two states (0 and 1), so it's work for Warthog throttle switches For Warthog throttle switches you just have to set a up command like I did in my example in another thread and for Gun example : {down = 3463, up = 3463, cockpit_device_id = 16, value_down = 1, value_up = 0, name = _('Gun ON else OFF'), category = _('Add on switch')}, For Warthog stick, of course, if you want a pulse on push button, with one command per push button, you can do the same but in that case 2 lines (one with state 1 and one with state 0) for gun switch as you've done.

Hi Zeus, no problem.... But clearly, when you announced 3 weeks in June for avionics update, a lot of people (like me) wait for it (same for the FM) ! But weeks passed and nothing was released ! That's why some of us are disappointed ! So, now, I hope it's just a question of weeks ;)

Hi, As I can see in other threads, Zeus is back but he works on .... Harrier ... RAZBAM priority is still Harrier So I didn't expect any bug fix or avionic update soon... Perhaps for RAZBAM, a week is equal to a month ... Wait until September 12th (3 month instead of 3 weeks) !!!! I hope I'm wrong,.. I hope :mad:

No mirror bug for me, no FPS drop when activated. Hud is visible, Clearly better than before ! Thanks

Hi, here is a link on a mod I made a few months ago : https://forums.eagle.ru/showpost.php?p=2880171&postcount=1 I think it's still working with later version ;) Regards Sunski

Ok thanks.

Hi, the only problem is iCommandPlaneCobra (for G limiter roll when heavy) which must be set manually if the corresponding switch is set initially. For your question about jettison cover, yes you can because the two positions declared in the initial default file like this : {down = 3248, up = 3248, cockpit_device_id = 6, value_down = 1, name = _('Selective Jettison Safety Cover OPEN'), category = _('Weapons Management')}, {down = 3248, up = 3248, cockpit_device_id = 6, value_down = 0, name = _('Selective Jettison Safety Cover CLOSED'), category = _('Weapons Management')}, So you can create a new command line in the same section (-- ADD section) : {down = 3248, up = 3248, cockpit_device_id = 6, value_down = 1, value_up = 0, name = _('Selective Jettison Safety Cover Open ELSE Close'), category = _('Add on swicth')}, As you can see, I just add value_up in good place with the good value. You can do the same for gun arm Hope that help. Sunski.

Hi, here is the mod (to use with JSGME) and the file (be careful, I suppressed all default buttons assignations). In the joigned image, the modification to modify manually in disk:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\M-2000C\Input\M-2000C\joystick Sunski M2000C Input.zip default.lua

Very interesting ;) If it is a real manual, I saw that a BRM push button is used for weapons and the joystick trigger is only used for cannon A/A and A/G modes (actually trigger is used for all weapons).

I will send you my mod asap.

Hi, see here : https://forums.eagle.ru/showpost.php?p=3189588&postcount=1 here is an extract : {down = 3193, up = 3193, cockpit_device_id = 7, value_down = 0, value_up = 0.5, name = _('Air Refuel Transfer Switch OFF ELSE ON day'), category = _('Add on switch')}, {down = 3193, up = 3193, cockpit_device_id = 7, value_down = 1, value_up = 0.5, name = _('Air Refuel Transfer Switch ON night ELSE ON day'), category = _('Add on switch')}, you just have to add those lines in the default lua joystick file. Hope that help. Sunski

Just a word ... EXCELLENT ... Thank you for those informations. Sunski

Ok... More tests ... I'm in W10 and in my case (1080 GTX), when full screen is set in DCS 1.5.7 then I have the problem. If ths option isn't set, it's ok. The problem seems to be random because of Alt+Tab key use (which desactivates this option in DCS).

Strange ... it's not a permanent problem... If I restart DCS then it's good. I will test again.

Hi, It dépends on what you call "fly".... Personnaly I started with A10C but M2000C didn't exist. Mirage is a FBW plane so for normal fly, M2000C is not very difficult compare to a spit for example or a L39. Those planes don't have electric or electronic systems to avoid (as possible) pilot errors. As a delta plane, the problem is AOA when landing for example or the loss of speed when turning at limits. A/A missiles are Fox 1 and Fox 2 so if bandit has Fox 3 (fire and forget radar missiles) or long range fox 2 that may be hard for you and you need a lot of practice to win ... Because of its unfinished doc, it's difficult to have all informations to learn correctly. This is actually a real problem for a beginner. As Jojo said, A10C is more complex (weapon and sensors) very interesting for A/G but not for A/A. M2000C offers the 2, even if A/G is less powerful (no pod for targetting) because M2000C is an interceptor first ;)