HC_Official

If we could get the functionality I requested in this thread added, we could do some really cool stuff with dynamic fires in DCS fire fighting missions

I would like the ability to both create (which we can with trigger command) - but it does not return a reference object (which would be needed to destroy it later) or the ability to assign a name to the created object (also another way to destroy the fire/smoke object) eg: info here https://wiki.hoggitworld.com/view/DCS_func_effectSmokeBig trigger.action.effectSmokeBig(Vec3, 3, 0.75, "mysmoke") or local smoke_object = trigger.action.effectSmokeBig(Vec3, 3, 0.75, "mysmoke") And Also be able to destroy the created big fire or big smoke object at a later stage in the mission eg: Unit.getByName('mysmoke'):destroy() or smoke_object:destroy() I would also like this to work in both Single player and Multiplayer

they need to be connected to the server BEFORE the smoke triggers, if the connect after it triggers they will not see it, it has been like this for years with DCS

HI Newy, can you please confirm something for me For multiplayer game traffic DCS uses both TCP and UDP on port 10308 For Voice TCP and UDP on port 10309 the 10309 Voice port , is it hard coded at 10309? or is it derived from the main server port + 1 eg I run a server on port 10310 , then the VOIP would be 10311 ? just curious to know

Sorry about that @USSR_Rik it was an old config file that did work prefectly fine for the last couple of years hosting DCS dedicated server 2.5

1. dunno 2. server setting control this, edit your /Config/serverSettings.lua file to enable or disable these messages

Am I missing something? I do not see a link to download this on the first post ?

@USSR_Rik I just want to thank you for taking the time to help me out with this issue

Oh hang on , I deleted the options.lua file has re-created its own new one

As our online community grows and grows, we recognise that ensuring a level playing field for all has become an important matter and therefore, on popular demand we have locked the LUA files relating to weapon systems. @BIGNEWY @NineLine Can you guys link me to the thread where this popular demand was requested by DCS users please? Is not the job of online IC supposed to deal with cheating ?

I am sorry I do not understand @USSR_Rik can you show me what my options.lua should contain please ?

log dcs.log-20210422-210515.zip

this is about as close as I could get to doing fire fighting stuff within the limitations of the DCS scripting API (did this a 3 years ago)

I hope at some point ED will give use a User interface to do this type of stuff

Hi Rik, Yes here it is options = { ["graphics"] = { ["height"] = 600, ["visibRange"] = "High", ["width"] = 800, }, ["miscellaneous"] = { ["autologin"] = true, }, ["plugins"] = { }, }

more info dcs.log-20210422-192327.zip

FYI dcs.log-20210422-190541.zip

I would also love this

Yeah this would be needed as well And yes late activation statics = good thing

FYI dcs.log-20210422-185353.zip

if you do not have many modules, then copy over you Config folder to you new PC, load up DCS and import each planes config lua files one at a time

another dcs.log-20210422-184637.zip

another log to help out dcs.log-20210422-173145.zip

SOLVED - Issue was the options.lua file it was copied over from 2.5.6 dedicated server , this worked ok with 2.5.6 DCS World dedicated server but caused the DCS World 2.7 dedicated server to crash, many thanks to @USSR_Rik for helping me solve this problem I updated and started up the server, then connected to the server just using a CA game master slot , and did nothing else no other interaction with game at all, then server crashed dcs.log-20210422-164255.zip

I am also seeing this, SLMod might need updated for the new 2.7 event handlers ? (MOOSE also needed updating)