Search the Community
Showing results for tags 'event'.
-
We are the Take Flight training group! Come fly with us during our next event. Details and sign-ups are on the Take Flight Discord. https://discord.gg/takeflightdcs
-
Hello DCS pilots! Recently we've added events system to VIRPIL Controls Servers and we'll be running some events (currently duel events) on regular basis. You can check the upcoming events for the duel server here. Feel free to register for any event that you might like (the sign up required) or just do some ranked duels if there is no event active (sign up is not mandatory in this case). If you have any questions on how the server works you can refer to the briefing, duel server faq or feel free to ask me - I'll be glad to answer! If you have any feedback or suggestions or willing to host your own themed event also please feel free to reach me out. Have fun!
- 10 replies
-
- 1
-
-
- multiplayer
- duel
-
(and 2 more)
Tagged with:
-
DCS YOM KIPPUR 2 [FICTIONAL] EVENT TO: DCS Pilots SUBJECT: Multi-Asset Competitive Operation – Sinai AO REFERENCE: Operation Yom Kippur 2 [Fictional] SITUATION: A fictional 1975 scenario set in the Sinai Peninsula. Two opposing forces (REDFOR and BLUFOR) will engage in a coordinated, combined-arms air conflict. Fixed wing and rotary assets will operate in direct support of ground objectives. This is a competitive, score-based event. First team to 100 points secures operational success. MISSION SCHEDULE: Event I – Saturday, 3 May 2025 Time: 1500–1800 UTC Pre-Mission Briefing: 1430 UTC Event II – Saturday, 10 May 2025 Time: 1700–2000 UTC Pre-Mission Briefing: 1630 UTC Area of Operations: DCS Sinai Map COMMUNICATION: Staging and Coordination: ACME Discord Registration Required: SIGN-UP ROSTER All command coordination will take place through the ACME Discord server. For further intelligence, mission structure, and discussion: OPERATIONAL BRIEFING – FORUM LINK Questions? @JG1_Flyboy
-
Dopo svariati mesi di confilitti nella zona sud-ovest della Siria tra Beirut e Damascus, c'è un emergenza nell'emergenza. Le popolazioni locali sono ormai allo stremo, manca Acqua, Cibo e beni di prima necessità. Nei giorni scorsi sono iniziati ad arrivare i primi aiuti, ma con loro sono arrivati anche i problemi di ordine pubblico e sicurezza. Mappa: SYRIA Mods: Hercules / SAM SITE ASSET PACK Epoca: MODERN ISCRIVETEVI NEL CANALE => ATO-PVE-MISSION DISCORD: https://discord.gg/M4BVrRswp7
-
Hello, I wanted to report an issue with the external cargo and event handler that I discovered while working on a game mode and some related lua code. This error occurs when a piece of external cargo is lifted and then destroyed, by either being dropped or damaged mid-air. When this situation occurs, and an instance of the event handler has been called in the mission, the following error is prompted: [string "..."]:10: attempt to call method 'getName' (a nil value) stack traceback: [C]: in function 'getName' [string "..."]:10: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11> null null I have also seen this error in the forementioned game mode be prompted with a getPosition or getPlayerName call; but always occurred when the external cargo was picked up and then destroyed. I have slimed the conditions of the error down to its most basic state, involving an external-cargo capable helicopter (in this case a CH-47), a piece of external cargo (in this case a small ISO container), and a 'Do Script' trigger calling the event handler, in the attached mission file. I have also attached my DCS log for the instance and a video of the error occurring with this mission: https://youtu.be/Jlano9twZQ0 (Please excuse the delay in hooking the cargo, it's more stressful when recording ) Lastly, here is the event handler code I used in the mission. For simplicity's sake, it is a slightly modified version of the event handler code found on the DCS hoggitworld wiki here: DCS func addEventHandler - DCS World Wiki - Hoggitworld.com Code: local e = {} function e:onEvent(event) local m = {} m[#m+1] = "Event ID: " m[#m+1] = event.id if event.initiator then m[#m+1] = "\nInitiator : " m[#m+1] = event.initiator:getName() end if event.weapon then m[#m+1] = "\nWeapon : " m[#m+1] = event.weapon :getTypeName() end if event.target then m[#m+1] = "\nTarget : " m[#m+1] = event.target :getName() end if event.id == 30 then m[#m+1] = "idx " m[#m+1] = event.idx end trigger.action.outText(table.concat(m), 10) end world.addEventHandler(e) As a closing remark, I am quite new to Lua coding. As such, when this error began occurring, I did believe it to be a mistake from myself; especially given the complexity of my game modes code. However, after doing an extensive amount of testing, I became more confident in the idea this may be an actual bug. I look forward to learning more about the issue and hearing other's thoughts. Thanks! EventCrash.miz dcs.log
-
- cargo
- helicopter
-
(and 8 more)
Tagged with:
-
Night Owls DCS 1v1 Tournament Join us on October 5th at 9 PM CST for our latest DCS 1v1 tournament, featuring Fox Two missiles. We’ll be using the AIM-9M Sidewinder and its counterparts from other nations. We can’t wait to see how you use these to your advantage to climb the ranks and steal the win! Event Details: Date & Time: October 5th, 9 PM CST Location: Caucasus winter with clear skies and zero wind Aircraft Setup: Balanced fuel state (5 minutes of afterburner), two Fox Two missiles, visibility aids (dot labels) disabled Match Rules: Opponents must merge before engaging/shooting. G limits (such as paddling or flaps) are encouraged. Head-on fights are allowed and encouraged. Mid-air collisions will call for a rematch. Competitors can only use their chosen aircraft. Abusing software/cheats is not allowed. Contenders get 2 chances to successfully merge. First to crash/die loses, and the winner moves forward. Important Dates: October 4th: Sign-ups close October 5th: Event begins at 9 PM CST Brackets: The brackets will be available to view the day before the event in the -bracket section (Discord). There will be a loser’s bracket, giving contenders a second chance if they lose a round. The brackets will be updated throughout the event. Awards: The winner will have the opportunity to choose one reward consisting of a DCS module, map, or mission! Sign Up: Please fill out this Google form to compete in the event. - YOU MUST JOIN OUR DISCORD SERVER TO COMPETE - https://discord.gg/xAZbAZduWZ Special Thanks: A big thank you to Skyward Flight Media for the continued use of their servers. Without them, none of this would be possible. We greatly encourage you to check them out for any and all virtual aviation-related news: Skyward Flight Media. https://www.skywardfm.com/ Best regards, Night Owls team
-
- prize
- tournament
- (and 4 more)
-
10 Days War - Operation Desert Fury by DCS Indonesia
EagleEye.DCS posted an event in Community Calendar
untilDear Everyone, We are proud to invite you all to join our upcoming event in the next ten days to commemorate Aerospace Day and celebrate the 78th anniversary of the Indonesian Air Force. The event is "10 DAYS WAR - Operation Desert Fury" and you can find the guidelines here Guide Here There are 2 Official DCS Modules awaiting you, featuring the best PVP and Ground Attack categories. These parameters will be calculated using the DCS Bot. Let's invite your friends along and make this event a memorable one! Sincerely! Forum Discussion- 2 comments
-
It's long been known that this trigger is unreliable or dysfunctional for most applications. There has been comments made that this maybe be a placeholder or has some 'unknown' workings. However, it's exposed in the DCS Scripting Engine API. Therefore it SHOULD be documented and fully working. As it's the ONLY possible event trigger relating to units/groups ENTERING or LEAVING a trigger zone, this is a truly crucial and valuable event to hook into. Kindly, like the 'menuItemsForUnits' and the broken ' S_EVENT_PLAYER_ENTER_UNIT for MP Dedicated servers, consider this an urgent fix that would enable a huge amount of efficiency and power to the scripting engine and functionality for all mission designers.
-
Phoenix Task Force presents to you ACES 22-2 ACES 22-2 will allow participating Squads to compete against each other in a much broader spectrum of what DCS has to offer! Rules of Engagement & Missions/Air Tasking Orders: https://drive.google.com/file/d/13JwnDNf4mPn0suEdFnKu9hh2ZgPmMsBc/view?usp=sharing Discord Dedicated Discord server with every recent detail of the event. Join now! https://discord.gg/jnDs3aNkEN Sign Up The Sign Up will close on 20th August 2022 Sign Up Format Sign Up preferably in following format: Squad Name: Phoenix Task Force Squad Lead: [PTF]Ghori Time Zone: UTC+5 Do you as Squad Lead volunteer for AirBoss role? Yes/No
-
About the event (more info and tickets on website linked at the bottom) You have been transported back in time to the attack against Perl Harbour. Your mission is to spawn at the supplied Airfield and carrier nearby and intercept the incoming fleet. whoever has the most amount of points at the end of the mission timeframe wins. Points are as follows: +25 points per Aircraft killed +100 points per Ship killed - 100 points per death - 200 points per intentional teamkill (intentional defined as having an intent to kill that person and not an accidentall crash into someone else, if they are attributed with a death, that death will be taken away but the person at fault will keep that death) https://www.aussiegamesserver.com/event-details-registration/the-final-countdown-take-2
-
Interactive mission creation is crippled by the inability in Multiplayer missions to know when a player aircraft has tuned to a specific radio frequency correctly (or at all). A world.event generated whenever ANY player in the mission tunes a radio, or switches to a radio that provides not only the unitName, but also the radio unit AND the freq it's tuned to would be tremendously helpful. Yes, if they were tuning from say 120.0 to 127.50 then it would fire an event for every frequency in between, but it's not hard to capture the last one and compare to the next event. Or, perhaps this can only fire when the tuning has stopped (i.e. waiting for a time > 'a specified delay' = final freq). Either way, knowing when a MP aircraft has tuned to the correct frequency allows the mission creator to be able to play specific audio/send specific text to that unit and update that Group's (better if it was UNIT level) F10 Radio Menu with options based upon what they're now hearing/reading.
- 2 replies
-
- world.event
- event
-
(and 4 more)
Tagged with:
-
Hi everyone, While waiting for functional TCTS training pod in DCS, to perform Kill Removal Procedures our idea is to shoot live ordonance against each others by setting up all aircrafts in Invicible, the last thing we need is a message declaring which person has been killed. To do that we would like to use the "Unit Hits" Trigger : -> [Once] -> [Unit Hits] -> [Message to ...] Unfortunatly we are facing a problem with this condition (Unit Hits), it looks like there is a problem with it in a specific Dedicated multiplayer server environement. An important thing to note is that the trigger "Unit hits" is working perfectly in any condition as soon as your a playing in SinglePlayer or in a Local Multiplayer Server. When playing on a Dedicated Multiplayer Server, that's only here where we are facing the problem bellow. In multiplater dedicated server (not local server) 1- Player shooter | AI Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message NOT received. 2- Player shooter | AI Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. 3- Player shooter | Player Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message NOT received. 4- Player shooter | Player Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. 5- AI shooter | AI Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message received. 6- AI shooter | AI Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. 7- AI shooter | Player Target "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message received. 8- AI shooter | Player Target "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message received. Conclusion : "Unit Hits" trigger is not detected and is not registered in the logs only when : + Mission is hosted on multiplater dedicated server. +"Unit hits" trigger is used when a PLAYER is shooting against an immortal AI or an immortal PLAYER. According to the values ahead, it looks like that the event "Unit hits" is not published/broadcasted in DCS code on a dedicated server when a player shoot against an immortal units (AI / Player). Because the "Unit hits" trigger registers well in SinglePlayer or in a Local Multiplayer Server, I don't think the problem comes from the DCS code but from the Dedicated Multiplayer Server that doesn't register all data. You will find linked to this message a test mission .miz that i have made to test every possible situation. (mission is made according to the values in the table above) _________________________________________________________________________________________________________________________________ Bellow you will find not the problem listed above but an improvement idea to the "Unit Hits" Trigger. Aditional Improvement Idea : Get the ability on the ME to get an other "Unit hits" trigger without specific number of hits on dedicated target, by the way, using a "Switched condition" Trigger, at each a time a unit has been hit by something we can have the trigger activated. (not only once) -> [Switched Condition] -> [Unit Hits] -> [Message to ...] (exemple : an information message is displayed everytime a specific immortal aircraft has been hit by something) _________________________________________________________________________________________________________________________________ Best Regards Wolf4Pm and Gemini from the JTFF. This message follows the three previous topics on this subject : Unit Hit - MP Trigger Test.miz
-
For those newbies and experienced pilots looking for people to fly with, we welcome anyone each Sunday at the time ( 1900 UTC, 2:00 pm CDT ) posted in the title. We are not really a squadron but just a small group of people that enjoy flying missions together each Sunday. If your brand new or have been around for a long time, be sure and join us on Sunday afternoons. Flight Sim Break Discord - Just celebrated our 6 year anniversary! https://discord.com/invite/fCV62Ka2QZ Meet us in the Group Flights voice Channel. You will be given the Name & Password to the server we fly on for that week. in2tech
-
1v1 DOGFIGHT TOURNAMENT [86] Night Owls MARCH 30TH 2024, SATURDAY @ 9PM CST Sighups close March 25TH Night Owls, a new DCS community, invites you to join our 1v1 BFM competition! Compete head-to-head in intense dogfights and prove your skills as a fighter pilot. Whether you're a newbie or a seasoned pro, our tournament promises fun for all BFM’ers alike, with opportunities to make friends and learn from fellow aviators. Big thanks to Skyward Flight Media for granting us the opportunity to go forward with this event! Go check out their website @ https://www.skywardfm.com/ HOW TO COMPETE To enter the event you must join the Discord @ https://discord.gg/kFbA3mnrNw Signup through the Google form: https://forms.gle/4Hf5nE6LbN2TWb8g8 That's it! If you need to withdraw after signing up, contact pickle.fbx on Discord. DATES & TIMES Saturday, March 30th, 2024: Event Day. @ 9PM CST Wednesday, March 25th, 2024: Signups Close. AWARDS The winner will receive the opportunity to choose an award of their choice, which consist of: a DCS module, map, or mission! BRACKETS Complete brackets will be available through our Discord 5 days before the event starts. RULES · Opponents must merge before engaging/shooting. · G limits, (such as paddling, or flaps) are encouraged to be used. · Head-on fights are allowed and encouraged. · Mid-air collisions will call for a rematch. · Competitors can only use their chosen aircraft. · Abusing software/cheats is not allowed. · Contenders get 2 chances to successfully merge. · First to crash/die losses and the winner moves forward. · Spawn when the horn sets off.
-
- night owls
- dogfight
-
(and 6 more)
Tagged with: