Purzel

Ja, das ist wohl nicht so einfach. Mit den Programmier-Sprachen kenne ich mich halt so gar nicht aus. Wo mache ich das mit dem Eventhandler im Mission Editor?

Danke für Deine Hilfe, aber das habe ich nicht gesucht, ich suche eine Abfrage, ob die Runway getroffen wurde. (Habe ich oben auch nochmal ergänzt, um keine Missverständnisse aufkommen zu lassen.) Die Wegpunkt-Funktion "runway-attack" (mit dem Dreieck auf der Runway) ist mir bekannt, es spielen aber Clients und dafür brauche ich eine Abfrage. Was die zwei Videos da oben zeigen ist für KI-Piloten... Ich möchte abfragen, ob die Runway von den Spielern getroffen wurde und dazu dann einen Trigger auslösen, dass alle flights wissen, dass die Runway auch getroffen wurde. Greetz Purzel

Hallo, gibt es eine Möglichkeit, eine Runway als Ziel für einen Runway-Strike zu definieren? Mit Gebäuden geht es ja über "assign as..." wenn man hinklickt, nur bei der Runway finde ich den Klick-Punkt für "assign as" nicht. Ich brauche eine Abfrage, ob die Startbahn wirklich getroffen wurde, damit ich einen Funkspruch an alle Spieler ausgeben kann. Ich habe auch schon mehreres probiert, wie z.B.: - Empfindliches Objekt draufstellen, das man dann halt zerbombt und der Trigger fragt das Objekt ab, ob zerstört, aber ich kriege die Dinger nicht unsichtbar, auch mit den 3 Häkchen bei "Hidden" nicht. - Mein zweiter Ansatz war eine Triggerzone mit Bedingung "Bombe in Zone", aber dann müsste ich alle (!) Bomben als Bedingung eintragen, und wenn eine Bombe 90° zur Landebahn in 50m Höhe durch die Triggerzone fliegt und abseits explodiert löst ja auch nur das Durchfliegen der Triggerzone auch aus, ob wohl die Bedingung ja nur dann auslösen soll, wenn die Bombe im Asphalt explodiert. Gibt es eine elegante sexy Lösung, die ich nicht kenne? Dann her damit! Gruß Purzel

I cannot install the CGTC 2.84.1 files. Is no more compatible to DCS 2.9xxxx I use OVGME. "Wrong Zip-format" Any tipps?

Lösung: (auf Englisch)

Solution:

Hi, most of you know the issue, that you build a mission and want to preset some values for the player, so he can focus on flying without beeing distracted by inputs while in-flight. Imagine an AAR-scenario for training-purposes, and you just don't have to set this stuff will closing in to the tanker and even your fuel-probe comes out magically... Or (if you have no life ) you could code an personalized startup-sequence or whatever. In this tutorial I conclude several posts from different users so you don't have to search yourself for all informations. This tutorial regards to the F/A-18C "Hornet", but all "keystroke-codes" are different on each aircraft, keep this in mind if you're trying to setup other aircrafts. The tutorial can be used for airbourne or ground starts, I'm not sure, if it will work in multiplayer as well. Ok, let's go: 1.) I strongly recommend "Notepad ++" for editing .lua-files. Please note, that you'll have to set it up for DCS and .-lua-files first. 2.) Be sure DCS is not running. Open your C:\Users\YOUR-NAME\Saved Games\DCS or DCS.openbeta\Config-folder. Copy the lang.cfg-file and insert it in the same folder, rename it to autoexec.cfg ( <<< fastest way to create a .cfg-file) or use this one: autoexec.cfg Open the autoexec.cfg and insert the following code and save it: input = { command_code_tooltips = true, } 3.) After saving the file, you can close the window and open DCS. 4.) In DCS go into the options-menu (the gearwheel-symbol on top) > controls, and hover your mouse over the keyboard commands and will show you the device ID and key-stroke codes: This is the step you will have to do for every specific aircraft itself. You cannot read out the codes while ingame, you'll have to go the way from the main-menu! (click to enlarge) (This is the step you will have to do for every specific aircraft itself. Codes from the AH-64D are not the same as the A-10C, as the F-16, etc.) For the F/A-18C I've uploaded a file with the most needed codes. Keycodes DCS.xls Else you'll have to note all needed keystrokes with ID, Down- and Up-values. (Note that the down value "1" is only to push a button down, it will not get back until you create a new trigger with the UP-value "1". As an example: The TCN button is listed as ID 25, Down 3001, Up 3001. Note, that UP and DOWN are the same values. Create a new trigger "ONCE - Time more than 1 sec. - X: COCKPIT PERFORM CLICKABLE ACTION" with the following Values: Cockpit Device: 25, Command: 3001, Value:1 (This is the UFC TCN-button pushed down) It works in DCS as just a push of the TCN-button, but it stays pushed in and it will not glide back out. To released the button again you'll have to copy trigger and change the value to "0": Cockpit Device: 25, Command: 3001, Value:0 (This is the UFC TCN-button released) To change your TACAN to Ch.18 X, you have to know the keystroke-sequence (X is standard, so I'll let this out here, "Option1" is the upper one of five round buttons) (TCN - Option1 - 1 - 8 - ENT - ON/OFF) , now search in controls every keystroke you would have to do with mouse and note them. 5.) After all go into the mission-editor place your unit and open the triggers. Create the triggers (Type "ONCE", Condition: "Time more") as shown in the picture: Note that every button is triggered a second time "in and out". This will all happen in a second and your aircraft is good to go. I hope someone can use this tutorial. Greets Purzel Kudos to @Rudel_chw and @Yurgon and all others, who put their informations and efforts into this forum!

yeah, it's not even working with sending a blank text message to the player with a minimum display time. In your mission, what's the second trigger for? Flag on ("999") there's no reference in the other triggers? Everything else is self-explaining, thx for your great help with that topic! Actually I'm writing a list with the most important keystroke commands. I'll publish them later with a little tutorial, So everybody can use it for his own training-missions, or whatever... Greets Purzel

THX, I did all the actions in the "ACTIONS" field one after each other, I'll try your mission later. Thx a lot! There's no possibilty to add the delay under the actions? Greetz Purzel

Nice, but it doesn't work for me... First I had not "autoexec.cfg", so I created the autoexec.cfg-file in Saved games/.../Config-folder. It's a blank file, I added nothing than input = {command_code_tooltips = true, } After that I'm able too read out the "cockpit-keystrokes". As example: the TCN button is listed as ID 25, Down 3001, Up 3001. Note, that UP and DOWN are the same values. So far so good, but if I create a new trigger "ONCE - Time more than 2 sec. - X: COCKPIT PERFORM CLICKABLE ACTION" with the following Values: Cockpit Device: 25, Command: 3001, Value:1 (This is the UFC TCN-button as listed above) it works in DCS as just a push of the TCN-button, but it stays pushed in and it will not glide back out. After I had a serie of clickable action in the triggers list for a change to TACAN Ch.18 X, you can see all pushed buttons (TCN - Option1 - 1 - 8 - ENT - ON/OFF), but they all stay pushed in. I even tried to put two "X: COCKPIT PERFORM CLICKABLE ACTION" each with the same values after each other, but the buttons stayed pushed. I took a look at "Banklers recovery-trainer" in which all of those switches are used the same way I did, but Bankler used only one action line to push and his cockpit-button went out again. And I don't understand the "Value"-value, it goes from "0", "0.1", "0.2", "0.3", ... up to "1" but I see no difference with any changes? What does that value mean? Any solutions to get it working? Greets Purzel

Is there a list with all commands? I cannot find that CODES_TO_TOOLTIP line in the MissionEditor.lua? I think they changed something...?

Hi Leute, ich möchte gerne bei einer Mission, die in der Luft beginnt, in der F/A-18C die TACAN, ICLS, ACLS, Link4 Kanäle/Frequenzen voreinstellen, dass sich der Spieler nicht mehr darum kümmern muss. TACAN und ILCS sollen im HSI auch schon geboxt sein. (Lasercodes und Bomben-Lasercodes voreinstellen wäre auch noch ein Wunsch) Wie kann ich das im Editor (ohne Moose oder so) bewerkstelligen? Geringe .lua-Grundkenntnisse sind vorhanden, mehr aber auch nicht, habe schon probiert andere Missionen zu reverse-engineeren, da werde ich aber nicht schlau draus. Mir reichen ein paar Code-Zeilen für Copy/Paste und wo man die verbaut. Danke schon mal für Eure Hilfe. Gruss Purzel

@Rapti I cannot open that .cmd-file with Notepad++, either by rightclick and "open with", nor by dragging the .cmd-file into Notepad++. How do I get this done? Cheers Purzel

### SKUNKWORKS-Installation Note > The process for updating DCS-BIOS is exactly the same as installing it. 1. Go to the [latest release][latest-release-url] 2. Download `DCS-BIOS_x.y.z.zip` 3. Extract the zip file 4. Within the extracted folder, copy the `DCS-BIOS` folder into the previously mentioned scripts folder. 5. **If your Scripts folder does not have an `Export.lua` file**, copy the `Export.lua` file over 6. **If your scripts folder _does_ have an `Export.lua` file**, add the following line to the end ```dofile(lfs.writedir() .. [[Scripts\DCS-BIOS\BIOS.lua]])``` Tip Still having trouble? Check out our [wiki][wiki-url], ask a question in [Discussions][discussions-url] or get in touch on [Discord][discord-url]. ## Usage #### Connect DCS-BIOS stream to your serial ports Both `socat` and [DCSBIOSBridge](dcsbiosbridge-url) can be used to connect to your device. This is the only part I don't understand: Which files are meant?

Hi folks, for my cockpit I've ordered an IFEI and an UFC from tekcreations a few years ago, when DCS-BIOS (the original Hub) was the real hot <profanity> back then. Now I've bought some newer stuff rom tekcreations (left and right brain-controllers, MasterArm and IRcool-panel), which requires Skunkworks BIOS and I've installed Skunkworks-BIOS step-by-step (see next post) as described by TekCreations (https://tekcreations.slab.com/public/posts/dcsbios-installation-skunkworks-byjgzhpu). Export.lua is updated and the new stuff is running. My older IFEI and UFC weren't running anymore (only, if I started the old DCS-BIOS parallel). As far as I understand Skunkworks is running in the background and does not have to be started everytime I start DCS (as the old BIOS). But I have to do everytime the following steps: Read out the COM-ports (4,5,9 and 13) and then I have open the "connect-serial-port" 4x and put in every window each of the four COM-port-numbers. Only after that I can use my hardware-panels. Randomly I've found out that the older IFEI and UFC are running under Skunkworks when I use the "connect-serial-port"-part as described above. Now my question: How can I spare this part with the four windows? Is there an automated way to go? Greetings Purzel PS: A I already asked Kieron from TekCreations, but he can't help me with that.