Marroux

Hi, I think it is included in the AV-8B module.

Aloha, There is the cubanace 's Su 57 Felon (https://forums.eagle.ru/topic/242354-su-57-felonefmasm-standalone/)... https://fr.wikipedia.org/wiki/Soukhoï_Su-57

Aloha, Personally, I would like to see some changes in the ability to give instructions to ships. Indeed, placing navigation points (via F10 during the game) is the only possibility (except script). An instruction system allowing to manage take-offs for example would be welcome (like in Fleet Command, for the less young among us).

Hello, I can't manage to position several AI helicopter spots on the majestic, I still only have one position. Has anyone succeeded?

Bonjour, Merci à toi rato65 J'ai essayé avec plusieurs mods de navires (Mistral, CVN-73 George Washington, HMSA Melbourne, Tarawa…) et le comportement est toujours le même, uniquement pour le Dauphin. La modification que j'ai apportée à dauphin.lua permet au Dauphin de décoller sans problème. C'est seulement le déploiement du train d'atterrissage qui est problématique au début (30 secondes avant qu'il se déploie). ******************************** Hello, Thanks to you rato65 I tried with several ship mods (Mistral, CVN-73 George Washington, HMSA Melbourne, Tarawa...) and the behavior is always the same, only for the Dolphin. The modification I made to dolphin.lua allows the Dolphin to take off without any problem. It is only the landing gear deployment that is problematic at the beginning (30 seconds before it deploys).

Bonjour Damien, Ton pack est superbe. Comme Pappy2 je rencontre 2 problèmes avec le Dauphin lorsque je le place en AI sur un navire : - - Le rotor tourne, le train d'atterrissage est replié au départ et l'hélicoptère flotte nettement au-dessus du pont. Après une trentaine de secondes, le train se déploie - - Le Dauphin se déplace ensuite vers l'avant, puis stoppe. Il ne décolle pas et fini par se mettre en arrêt (rotor coupé et porte ouverte) Rien à faire pour le premier problème mais il me semble avoir résolu le second en modifiant le fichier lua : ******************************************************************** Hi Damien, Your pack is superb. Like Pappy2 I have 2 problems with the Dolphin when I put it in AI on a ship: - The rotor spins, the landing gear is folded at the start and the helicopter floats clearly above the deck. After about 30 seconds, the landing gear deploys - The Dauphin then moves forward, then stops. It does not take off and eventually stops (rotor cut off and door open) Nothing to do for the first problem but I seem to have solved the second one by modifying the lua file : ...et il vole....

Hello, I am discovering your work and I think you are the right person for my request. There are more and more ship mods available for DCS. It is possible (subject to having combined arms it seems to me) to interact in a restricted way with these ships (setting a route for example). Do you think it is possible to have an application to "take control" of ships?

Hello, Try local deck_level_f = 11.755 local deck_level_r = deck_level_f + 0.3 in USS San Antonio LPD-17.lua this is the best (but not perfect) setting I have found.

Hello, Merci pour ce mod.... Il ne manque plus qu'une FREMM...Espérons que prochainement un modeur aura le temps de nous en proposer une ... The only thing missing is a FREMM... Let's hope that soon a developer will have the time to propose us one...

Hi, The desdemicabina-simulation team has been using this type of diffusion since their first work. I have never encountered the slightest problem with their installer. However, it is a pity not to have an OvGME format. The ships are superb. Thanks to the team.

aircraft... il ne manque plus qu'une FREMM et un soum français pour avoir ue groupe aéronal complet....

Thank you for your answer. Is there any documentation that describes the variables that appear in this type of file?

Hello, It is sometimes necessary to modify the lua file corresponding to an object. For example, for the USS San Antonio LPD-17 naval mod, the USS San Antonio LPD-17.lua file located at the root of the Mod. This type of file contains a series of parameters, some of which are quite explicit (GT.mass or GT.Length for example), but others rather obscure (GT.X_tail or GT.distFindObstacles). Is there a description of these variables, a lexicon or instructions for use somewhere? Thank you for your help. Marroux

Superbe ! La frégate Lafayette manquait à DCS.... Merci...

Hello, Une question peut-être idiote : tu as visionné les tracks pour être sûr de la position de l'avion au moment du contact ?

Bonjour, Il est quelquefois nécessaire d'aller modifier le fichier lua correspondant à un objet. Par exemple pour le mod naval USS San Antonio LPD-17 le fichier USS San Antonio LPD-17.lua situé à la racine du Mod. Ce type de fichier contient toute une série de paramètres dont quelques-uns sont assez explicites (GT.mass ou GT.Length par exemple), mais d'autres plutôt obscurs (GT.X_tail ou GT.distFindObstacles). Existe-t-il un descriptif de ces variables, un lexique ou un mode d'emploi quelque part ? Merci de votre aide. Marroux

Hi, Thank you for this Arleigh Burke expanded series. I'm having trouble with the helicopter deck. By adjusting the settings I managed to get the IA helicopters to work properly: GT.Landing_Point = {-62.0, 4.9, 0.0} instead of GT.Landing_Point = {-62.0, 3.215, 0.0} But nothing to do with the flyable (which fall under water) or even with the static objects (which are embedded in the deck).

Hello, Where can I find the meaning of the variables used in the lua files? For example in the file TYPE-054A_HANDAN.lua, the meaning of GT.mass or GT.shipLength is clear. For others (GT.X_tail, GT.Om,...) it is more obscure. Is there a lexicon?

Hi, The hook does not work. It is better to use the su-33 with the adapted livery : the J-15 skin: https://www.digitalcombatsimulator.com/en/files/1709315/ Thanks to Jet for the idea.

Hi FS Voodoo, Is your project still in progress?

Problème résolu : activation de l'ICLS par le mauvais menu :

Mystery solved I activated the ICLS in the wrong place: in the "action activated" tab (3rd) and not through the "advanced (waypoint actions)" button.

I've tried leaving the default designations proposed by the ME: same