Joe Kurr

Is it feasible to have a mission file running for let's say 48 hours or more non-stop? I have an idea for a very big scenario, but for this to work it's vital the server can run this long with players connecting and disconnecting several times.

Fixed :)

We're hard at work to set up the DCS World section for the LLTM 2014. In order to make this event even better than previous ones, we'd like to know what you want. What kind of event would make you decide to come to Enschede? What type of missions would you like to see in the competition? What would you like to see besides a competition? Please respond, so we can tailor the event to your needs to make the LLTM 2014 the best one ever. For more information about the LLTM, please visit http://www.lowlandtigermeet.com

Got the same message when installing DCS World. I chose Yes, and the installation continued. So if you get this message, you just 'S', whatever it may mean :)

There is also a small town called "America" in the Netherlands. It has 2130 inhabitants.

During our last flight we noticed some strange behaviour with the Russian smoke generators. (haven't tested this with the Western ones yet). The smoke leaves the smoke generator at the front, instead of the back. This issue was introduced after the update to 1.2.5. See the attached image.

The biggest advantage is that this will work for every controller, not just the Warthog. Another advantage is that you can make a separate setup for each aircraft, which will load as soon as you select that aircraft. You don't need to alt-tab out of the game to change your profile. One drawback I noticed by editing the controller settings directly in the lua scripts is that the DCS controller options screen screws everything up when you view the settings and click OK. Hence the idea to make a profiler instead of editing the lua files time and again. It also prevents errors caused by typos :)

In order to make editing these lua files easier, I decided to build a DCS profiler. With this tool it will be possible to assign functions to your controller like described in this topic. Note: this is very much Work in Progress.

In case someone needs data from FC3 containing gear, flap and airbrake status, here's how to do it: if LoGetMechInfo() then local RawGearStatus = LoGetMechInfo().gear.value local RawFlapStatus = LoGetMechInfo().flaps.value local RawBrakeStatus = LoGetMechInfo().speedbrakes.value --[[ Raw[Gear|Flap|Brake]Status == 1 --> Gear / Flaps / Airbrake Extended Raw[Gear|Flap|Brake]Status == 0 --> Gear / Flaps / Airbrake Retracted Raw[Gear|Flap|Brake]Status > 0 < 1 --> Gear / Flaps / Airbrake Retracting / Extending --]] local GearWarning = (RawGearStatus > 0 and RawGearStatus < 1) and 1 or 0 local GearStatus = (RawGearStatus > 0.5 and GearWarning == 0) and 1 or 0 local FlapStatus = (RawFlapStatus > 0.5) and 1 or 0 local BrakeStatus = (RawBrakeStatus > 0.5) and 1 or 0 local FodStatus = ((LoGetMechInfo().gear.main.left.rod + LoGetMechInfo().gear.main.right.rod) / 2 > 0) and 1 or 0 local MasterWarning = LoGetMCPState().MasterWarning and 1 or 0 local returnString = string.format("leds %d%d%d%d%d%d%d%d\n", 0, 0, MasterWarning, GearWarning, BrakeStatus, FodStatus, FlapStatus, GearStatus) if connection then socket.try(connection:send(returnString)) end end FodStatus is used here to indicate the position of the FOD screens inside the intakes, but since 1.2.4 this isn't indicated in the cockpit anymore. The indicators which were used for this are now used for the leading edge flaps instead.

See my answer on your exact same question here: http://forums.eagle.ru/showthread.php?t=109105

Here's how I do it (using a C# application for IO): 1. In my application I created a TCP listener, which runs on port 10309. This will be used for handling the requests you send from your export.lua. 2. In your export.lua, start by opening the connection to your application in function LuaExportStart(), like so: function LuaExportStart() package.path = package.path .. ";.\\LuaSocket\\?.lua" package.cpath = package.cpath .. ";.\\LuaSocket\\?.dll" socket = require("socket") host = "localhost" port = 10309 connection = socket.try(socket.connect(host, port)) connection:setoption("tcp-nodelay", true) socket.try(connection:send("start")) end Then you can use this socket to send/receive data. I use the LuaExportBeforeNextFrame and LuaExportAfterNextFrame to respectively read switch states and set LED states. For example, in my LuaExportBeforeNextFrame, I do this: function LuaExportBeforeNextFrame() if connection then connection:send("switches\n") line, status, partial = connection:receive("*l") local GearSwitch = string.sub(line, 4, 4) if GearSwitch == "1" then LoSetCommand(430) -- Gear Up else LoSetCommand(431) -- Gear Down end end end To set the MasterWarning LED, you can do the following: function LuaExportAfterNextFrame() local Failures = LoGetMCPState() if Falures then local MasterWarning = Failures.MasterWarning and 1 or 0 local returnString = string.format("leds %d%d%d%d%d%d%d%d\n", MasterWarning, StallSignal, CanopyOpen, 1, 0, 1, 0, 1) if connection then socket.try(connection:send(returnString)) end end end The communication exists of simple strings going back and forth. For the switches, the lua script sends "switches" to the socket, and then receives "11001" back (I have 5 switches). For the LEDs, the lua script sends a string containing 8 digits, e.g. "00101000", where 1 = LED on, and 0 = LED off. The script currently expects no answer from the application. The lua functions I call (LoSetCommand, LoGetMCPState) are for Flaming Cliffs, you'd have to do some research yourself to find the functions you need for the Huey (Can't help you there, since I don't have that module) Finally, we close the connection when the mission is over: function LuaExportStop() if connection then socket.try(connection:send("--\n")) connection:close() end end The application closes the connection when it receives "--".

Here is a small selection out of the 2000 pictures I made at the show. I'm only half-way editing them, so there will be more, featuring amongst others: Ramex Delta, Frecce Tricolori, Patrouille Suisse, Patrouille de France, etc. 1. The Viggen, raw power! 2. The Danish C-130J disposes of some flares 3. Two Polish Su22 Fitters gave a stunning role demo 4. The Red Arrows Synchro Pair 5. Nice low take-off by the 'Duke of Brabant Air Force' 6. The B-25 Mitchell headon 7. Fire-breathing Apache :) 8. Gear up! 9. Take-off for the airpower demo 10. The Reds depart for Cosford, taking the Blues with them 11. Airpower!

A few from this evening, trying out our new livery in DCS World 1.2.4 together with Wasserfall (board number 03).

Another way to get more attention is to attend live events like we did last weekend. Most people only know FSX, and are quite surprised when you tell them there are other flightsims around, with better physics and graphics. Several visitors wanted to know where they could get DCS, and what it would cost. It's too bad ED doesn't go to these events, as they could really use the exposure. So ED, if you're reading this, the next big event will be the International Flightsim Weekend in the Aviodrome museum at Lelystad Airport. With over 300 participants and 2500 visitors, this is an event not to be missed!

I'm shocked to read this. First Dee, now Jim, the community has lost two most valued people in a short time... It was always a pleasure to meet them, they will be missed. My thoughts are with their family and friends. RIP Jim :'(

Let's hope so. The response on these forums hasn't been all that encouraging. The success of an event like this totally depends on the support of the community. If no-one cares to subscribe, the LLTM will die, no matter what we do. It's true that we opened subscription too late, mainly because the website got hacked and took longer than anticipated to get it back up and running. I will open a new topic shortly where you can post your wishes and comments about the LLTM, so we know what you want from an event like this. As for the stability and module availability of DCS, that is an issue for us as well, but I'm sure it will be overcome.

Due to the woefully low turnout (only three subscriptions for DCS) we have to cancel the LLTM 2013. People who already booked will get a refund.

Thanks for the replies, I'll try the Group msg when I get home.

I'm building several multiplayer missions for the LLTM. In several missions I want to send a message to a single client when he enters or leaves a trigger zone. In the ME I can set trigger actions to Message to All, Coalition and Country. Is there a way to do a Message to Client, so that only the one client who is triggering the action gets the message?

If you have any questions regarding subscription, post them in the forum linked below: http://www.falcon5.nl/forum/phpBB2/viewtopic.php?f=159&t=12141

The website was hacked a while ago. Ice is still working to get everything online again. Please be patient, an official way to sign up should be there shortly.

You need to sign up if you want to participate (but then you'll need to bring your own gear). If you're just visiting, you don't need to sign up, but you can't join the competitions.

A public DCS server is not planned ATM. But we're open to everyone, so both aces and starters are more than welcome. So if you're able, just pack up and head for Enschede! :)

I've forwarded this to Ice, the main organizer of this event. Maybe it is possible to only bring your PC and HOTAS, and get a monitor, keyboard and mouse from Wzzrd. But no promises, we'll have to wait for an answer from Wzzrd...

There should be internet available, so this will be one event where DCS multiplayer shouldn't be a problem :)