PB0_Grizzlie

Hello everyone, Here is the latest version of DCS-Raygun.lua made by us including a new logic to turn on the UFC light. This allows the switching on and off of the master caution and master warning light to work correctly in certain aircraft. example: AV8B, M2000C,.... Installation: Stable version: Just replace the file "DCS-raygun" in Savegame / DCS / Scripts Openbeta version: Just replace the file "DCS-raygun" in Savegame / DCS.openbeta / Scripts have fun DCS-raygun.lua

This is the name of my personal F-14 V2.0 profile. The base name is F-14_v2.0b.hpf. Have a good day :thumbup:

I found: https://forums.eagle.ru/forum/english/dcs-world-topics/input-and-output/7154049-f-14-v2-0-helios-profile-captzeen-compatible-with-f-14a-135-gr

I found: https://forums.eagle.ru/forum/english/dcs-world-topics/input-and-output/7154049-f-14-v2-0-helios-profile-captzeen-compatible-with-f-14a-135-gr

Hello, I finally found it !!! Here is the procedure to follow so that your "Capt Zeen" helios F-14B profile V2.0 can be compatible with the F-14A-135-GR. You will need to modify 3 files: Open your F14B profile file (of type ".hpf") from CaptZeen with Notepad ++ and modify the line indicated in attachment 1. Then open with Notepad ++ the Lua file "Helios_F14" (located in "Saved Game \ DCS.openbeta \ Scripts \ Helios \ Mods") and modify the line as indicated in attachment 2. Finally, opened in Notepad ++ the lua file "HeliosExport16" (located in "Saved Game \ DCS.openbeta \ Scripts \ Helios") modify the line as indicated in attachment 3. Have fun Helios_F14.lua HeliosExport16.lua

hello, Is there an F-14A profile because the F-14B profile is not compatible even modified? Thanks

hello, Is there an F-14A profile because the F-14B profile is not compatible even modified? Thanks

Hello, I finally found out how to put the correct order on the appearance of the Flags on the "wing sweep instrument". See this link: https://forums.eagle.ru/forum/englis...flag-positions Have fun!!! :thumbup:

Hello, For those using the Helios profile of Capt Zeen's F-14, I finally found out how to put the correct order on the appearance of the Flags on the "wing sweep instrument". I inform you of the procedure to follow :smilewink:: First select the "wing sweep instrument" in the drop-down menu of the profile explorer ("Sweep inst" named in Helios editor). Then in the right part of the profile editor we find all the "Layers" of the "Sweep inst". We therefore find all the "Flag" of the "Sweep inst" (over, emr, man, auto, off). By clicking on one of these "Layers", we have the bindings window which corresponds to our selected "flag". The part of the Bindings to modify is in the "output" tab and is called "set value Translation X" in the Bindings column. This one is already configured with the wrong "arguments" (instrument link between DCS and Helios). Unroll the "set value Translation X" to find the "bindings" already written and delete it by the small cross on its left ("to trigger value when Network Values ​​NetWorkValue _... on DCS Generic changes"). :director: Important!!!!! ==> The Flag "OVER" is configured in "Y" base !!! This is why we never see it !!! Remember to remove your basic bind it so that there is nothing in "set value Translation Y". Once done, on the left column called "Actions", look for the path: "Interfaces \ DCS Generic \ Network Values". This contains all the "argument" links related to the lua "Helios_F14" file to export the aircraft instrument information. Find the value concerning your Flag to select (list at the end of this message), click on it and drag it to the right in "set value Translation X). Now, your flag configured correctly. I put a video link that a friend made to show you the procedure to follow in case of understanding concerns: Have fun!!! :thumbup: Here is the list of bindings to configure in "set value Translation X" for each of the "Sweep inst" flags: over = NetWorkValue_32 changed emr = NetWorkValue_31 changed man = NetWorkValue_169 changed auto = NetWorkValue_168 changed off = NetWorkValue_167 changed

Hello, I use helios with dcs-raygun without any problem. My export file available on page 25 of this post. Just download it and replace yours with this one. I hope this will correct your problem. :thumbup:

hello, I would like to understand how to set a time on a key assignment because I can't. Every time I right click to choose the time to press the key i get an error message that says "the object reference is not defined to an instance of an object" and my touch then comes back to the time of 32millisec. Thank you in advance for your help...

Hello, We are pleased to announce that we have added new module on this version, namely: - A-4E-C This new version now includes the following modules in total: - A10C - F18C - F14B / F14B RIO - M2000C - AV8BNA - F5E-3 - KA-50 - UH-1H - AJS37 - F-16C - MIG21Bis - MB-339PAN - F-15C - L-39C / L-39ZA - JF-17 Thunder - A-4E-C Installation: Stable version: Just replace the file "DCS-raygun" in C: Savegame / DCS / Scripts Openbeta version: Just replace the file "DCS-raygun" in C: Savegame / DCS.openbeta / Scripts Have Fun :thumbup: DCS-raygun.lua

Hello, We are pleased to announce that we have added new module on this version, namely: - JF-17 Thunder This new version now includes the following modules in total: - A10C - F18C - F14B / F14B RIO - M2000C - AV8BNA - F5E-3 - KA-50 - UH-1H - AJS37 - F-16C - MIG21Bis - MB-339PAN - F-15C - L-39C / L-39ZA - JF-17 Thunder Installation: Stable version: Just replace the file "DCS-raygun" in C: Savegame / DCS / Scripts Openbeta version: Just replace the file "DCS-raygun" in C: Savegame / DCS.openbeta / Scripts Have Fun :thumbup: "latest version on page 26"

Hello, We are pleased to announce that we have added new modules on this version, namely: - L-39C / L-39ZA - F-15C This new version now includes the following modules in total: - A10C - F18C - F14B / F14B RIO - M2000C - AV8BNA - F5E-3 - KA-50 - UH-1H - AJS37 - F-16C - MIG21Bis - MB-339PAN - F-15C - L-39C / L-39ZA The code of the F-15C required a little more work for my friend Miguel21 because it has nothing to do with the other modules in terms of coding since it is a Flaming Cliffs 3 plane. Installation: Stable version: Just replace the file "DCS-raygun" in C: Savegame / DCS / Scripts Openbeta version: Just replace the file "DCS-raygun" in C: Savegame / DCS.openbeta / Scripts Have fun :thumbup: "latest version on page 26"

Hello, I'm attaching my export.lua file to avoid any export error between DCS-raygun and DCSflightpanels. This export file works with these 2 DCS export software. Installation: Stable version: Just replace the file "Export.lua" in C: Savegame / DCS / Scripts Openbeta version: Just replace the file "Export.lua" in C: Savegame / DCS.openbeta / Scripts Have fun Export.lua