PB0_Grizzlie
-
Posts
24 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by PB0_Grizzlie
-
-
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:
-
1
-
-
-
-
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
-
2
-
1
-
-
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
-
Has anyone got this to work with Helios?
Helios needs to be first in the export.lua; but so allegedly does ray gun... I can’t get it to work.
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:
-
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" -
Does the new raygun file interfere with DCSFlightpanels as it did before? Have the UFC but never installed the software because of my DCSFP's.
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
-
a few missing ones:
MB-339PAN Arg# 209
MiG-21Bis Arg# 542
f-14 has a second one Arg# 2200 (RIO)
Naming is right!
And thank you for this!! waiting sooooo long to get it to work with other planes
Hello,
As requested above, we have added in this new version the "master caution" of the:
- F-14B RIO
- MIG21Bis
- MB-339PAN
have fun
"latest version on page 26" -
Your new script works perfectly!!! I think I did have a writing error in my original attempts and then things got worse as I kept testing.
This is AWESOME!!! THANK YOU BOTH SO MUCH!!! :-)
Do you plan to announce this in any other communities? I think a lot of people would like to use this and probably don't follow this thread. The Hoggit reddit page would probably reach out to a lot of people. If you don't plan to announce it, do you care if I do?
hello,
I posted a comment on the discord server of Eagle dynamics to inform the community but nothing prevents this information from being relayed on other forum or server.
You have our green light.
Have a good day
-
By "offline" do you mean single player?
This isn't working for me in the F18 or Huey. It works in the A-10 though. I even tried "hard coding" of the of airplane ID's but that didn't work either. I think it might be something with my config.
You must have made a writing error in your script.
Try this new version.
-
Hello,
That's it we got there !!!
Again thank you to my friend Miguel21 who played the code relentlessly ^^.
We found the code which allows the export to the lamp of the "master caution" on all online servers.
The first version that we had released worked on certain servers which authorized exports.
Now no problem even with a server blocking exports.
Thank you also for giving us the information to add the F-16 and the Viggen which are
added in this new version of DCS-raygun.
The installation process remains the same as for the previous version.
Just replace the DCS-raygun file with this new version.
Have fun
"latest version on page 26" -
Works excellent mate! Any chance you can add support for an F-16 and AJS-37 Viggen as well?
For information this version of raygun only works offline for now.
We are working on a code to make it work online.
As for the missing modules, I just don't have those modules. If you can send me the exact name of the aircraft in code and its argument number for its "master caution" then I could add them.
example for the F18C:
aircraft.Name == "FA-18C_hornet" then
gArguments = {[13] = "%. 1f"}
bye
-
Hello,
I have the honor to announce that after hard work for a few days we have managed to make the "master caution" work with other modules "
- A10C
- F18C
- F14B
- M2000C
- AV8BNA
- F5E-3
- KA-50
- UH-1H
I particularly want to thank my friend "Miguel21" who without him no code would have been possible.
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!!! :smilewink:
:detective: "latest version on page 26"
-
Is it possible to modify the DCS-raygun.lua file to use the MASTER CAUTION light for other planes? I see in that file the following line:
gArguments = {[404]="%.1f"}
404 being the DCS Master light ID from "DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts\mainpanel_init.lua"
Is it possible to use the ID's for other planes?
I tried to add other argument IDs but nothing happens ...
master caution,:
F18c: [14]="%1f"
Ka50: [44]="%.1f"
Buddy-Fox A-10C UFC
in PC Hardware and Related Software
Posted
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
Openbeta version: Just replace the file "DCS-raygun" in
Savegame / DCS.openbeta / Scripts
have funDCS-raygun.lua