Joe Kurr

It should be in the ["d3011pnilunilcd5vd0vpnilvunil"] part. My guess is that it should be something like this: d = down p = pressed u = up cd = cockpit_device vd = value_down vp = value_pressed vu = value_up The ["added"] block contains all key definitions for this particular function, with an index always starting at [1]. I'm still figuring out how this works though, and when I find out I'll try and redo the application I started working on earlier in this thread.

Visited the RNLAF Open Days at Gilze-Rijen airbase last weekend. Two pictures for now, have to sort through 4500 of them... 1. Polish Air Force MiG-29UB on static 2. Belgian Air Force F-16AM pulling a high-G turn

If you can place the focus over your main screen, I don't think this will affect alignment much.

You don't need a projector to make a HUD. All you need is a small monitor, a mirror, a piece of glass and a lens. A projector is way to bright for this, you may blind yourself. Here you can find some info about how to build one: DIY Head up displays

During our regular flights I only have the incoherent babble of my fellow pilots to listen to :) When doing my Su-27 solo display I play Klein Mandelbrot by Blue Man Group.

I haven't had time to work on it lately, but I expect to continue work this week. When finished, I will post it here.

Can't make it to this show unfortunately :( I'm hoping for another chance at Legends...

You need to press and hold S to do sharp turns in the F-15C.

Chicks in tow :) Formation flying (Beerhunter and me)

Drain out the fluids I guess :)

Good post, Artman_NL. Several things you mention are already being looked into for next year. The aim of the event has always been to have aces and beginners fly together and learn from eachother. Maybe this isn't clear at the moment on the current website. I remember from a past event where several participants in the Lockon section received a crash course on SEAD using the Su-25T. For people who think they aren't good enough to join a competion, don't think, just join, learn and have a good time. If you still don't think you're up to it, just join the freeflight section and still have a good time :)

Not pointing at anyone in particular (at least not my intention), but it's frustrating that after a year of preparation and asking what people want, the only response is none at all. Especially when comments then pop up that things have been too complicated all that time, it's hard to stay polite (although I'm trying to, believe me...).

It's a bit late to complain about the site / subscription system being complicated now. You've had plenty of time to ask for directions when subscriptions were open.

Subscription is now closed. We have a total of 26 participants, with a staggering 2 for the DCS section.

After the MLM (Dutch Military Aviation Museum), Hangar 23 at Tobit was the best. It was dark, had an aircraft hanging off the ceiling, and was spacious enough for the entire event. With only two participants currently signed up, it will stop us from having a good time.

Incorporated the script in our training mission yesterday, and it works like a charm! Thanks, now we can continue practicing AAR even if someone kills the tanker out of frustration :)

With so many Dutch people around here, it would be cool to meet somewhere, have some drinks and fly missions. I heard there is some kind of event going on in Enschede early April (hint hint)

If you want to reference scripts in your C:\Users\username\Saved Games\DCS\Scripts folder, use lfs.writedir: dofile(lfs.writedir().."/Scripts/yourscript.lua"); Took me quite some time to find it, so I post it here for easy reference :)

It would be cool indeed to have a TacView-like export to Google Earth, although a possible drawback could be that the DCS terrain doesn't quite correspond to Google Earth's terrain, so units might go under ground at times. I'm now experimenting with animated tracks, and have found that the time in Google earth is way too fast to have any real use other than showing the complete track in 10 seconds. I haven't found a way yet to replay my flights in real time in Google. Here is a screenshot of my latest test, showing two flights:

In its current form it has no real use, other than that it's fun to see the track you have flown in the real world. But this script can be extended and improved to be more useful. Currently, it only generates a kml file which can be opened in Google Earth afterwards. I'm working on a realtime version, but that is a bigger challenge. I think I need to take out my old TCP Listener script for that.

This evening I did some testing with exporting flight data from DCS World to a kml file and opening it in Google Earth. I already experimented with this a couple of years ago in FC2, and decided to try again in DCS, with quite satisfying results :) It looks like the coordinate system exported from DCS matches Google Earth better than FC2, but I haven't done a comparison flight yet. I'll post the lua code tomorrow, when I have a better (more readable) script.

Small addition to the above, here is some documentation I found while writing my cross-country airrace script: Pragmatic LUA basics in 30 minutes Pragmatic Lua - Error Handling, OOP, Closure and Coroutine

Very nice start indeed! Here are some additions that might come in handy :) It is possible to write object-oriented code in Lua-script. In fact, if you're scripting for DCS, you're already using objects. Let's go through some basics. To define a 'class', or object template, you can do this. First, we need to create a table (all objects in lua are tables), with the properties of our class and their default values. MyClass = { Property1 = "Hello World", -- a string Property2 = 15, -- a number Property3 = {} -- a table } Now we need to define a constructor, so we can use this as a proper class: function MyClass:New(p1, p2, p3) local obj = { Property1 = p1, Property2 = p2, Property3 = p3 } setmetatable(obj, { __index = MyClass }) return obj end To use this class, we can define some variables, and assign new instances of our class to them: MyObject1 = MyClass:New("First object", 1, { "one", "two", "three" }) MyObject2 = MyClass:New("Second object", 2, { 4, 5, 6 }) env.info(MyObject1.Property1) -- Writes "First object" to dcs.log env.info(MyObject2.Property1) -- Writes "Second object" to dcs.log The real use of these objects starts when we add some functions to them. Let's add a function to increment Property2 by a given number. function MyClass:IncrementP2(value) self.Property2 = self.Property2 + value end Notice the use of the keyword self here. It is a hidden parameter that automatically gets passed a reference to the object if you call the function using a colon: MyObject1:IncrementP2(5) This is the same as: MyObject1.IncrementP2(MyObject1, 5) Consequently, our IncrementP2 function can also be written like this: function MyClass.IncrementP2(self, value) self.Property2 = self.Property2 + value end This is a major pitfall in developing lua scripts, as calling MyObject1.IncrementP2(5) or MyObject1:IncrementP2(MyObject1, 5)won't throw an error, it simply does nothing (at best) or something unexpected. If you're using objects from DCS and your code doesn't work, check this first. It will save you a lot of debugging time!

You're welcome. Have a look here, it's a working airrace script I made, inspired by your script. Maybe you can use it to improve yours as well :)

Inspired by BB.'s race script, I created this cross-country version. The course doesn't have to be a lap, but can run from one place to another. The script keeps track of anyone flying inside the course, and also checks for missed gates, flying the wrong way, etc. The course is set up using a series of large trigger zones to create a corridor in which players are detected as race participants, and a series of small trigger zones to make up the gates. All gates must be inside the corridor, otherwise the script can't keep time correctly. To use the script, you will need to define three triggers in your mission: 1. At mission start, (no condition), do script --> enter parameters 2. Once, Time more than 1, do script file "mist_4_3_73.lua" 3. Once, Time more than 2, do script file "CrossCountryRace.lua" See the attached screenshots for details. Current features: - Keep time for all individual aircraft in course - Show intermediate times for all individual aircraft in course - Show player with fastest time - Compare intermediate and total time to fastest time - Top-10 of fastest players Planned features (wishlist): - Maximum course altitude - Maximum altitude per gate - Distinguish between clients and AI (currently AI is also registered as airrace participant) Please let me know if you find any bugs or other problems with this script. [edit] Finally had time to update the script, it is now compatible with DCS World 1.5.4 and uses mist 4.3.73. I updated the script and the test mission in the attachments. CrossCountryRace.lua Race Test.miz