Joe Kurr

One must really hate aircraft to be able to do such a job...

I think when they start recovering them, the dig will be well-documented. They haven't started yet, so don't expect any pics soon.

The Dutch Military Aviation Museum will once again host the annual Military Flight Simulator Event. During this event, visitors can watch virtual flying demonstrations or climb into an F-16 cockpit for a virtual flying lesson. The museum is inviting everyone in the international military flightsim community to join the event. Participation is free, as is the admission to the museum. Accommodation, breakfast and lunch for the participants are provided by the Royal Netherlands Air Force. Participants can stay at military hotel "Huis ter Heide" (at the moment, they have 25 double rooms reserved for the event) If you want to join, don't hesitate too long, as places are limited to 100 participants, and accommodation is limited to 50 people (at the moment, but might be increased if need be) Timetable for this event: Friday, September 14th - 10:00 - 17:00 - Build up - 17:00 - Late - Dinner at a local restaurant and social talks at the hotel Saturday, September 15th - 08:00 - 12:00 - Build up and check rides - 12:00 - 16:30 - Museum open for public - 16:30 - 17:00 - Shutdown - 17:00 - Late - Dinner at a local restaurant and social talks at the hotel Sunday, September 16th - 08:00 - 12:00 - Build up and check rides - 12:00 - 16:30 - Museum open for public - 16:30 - 18:00 - Break up Head over to http://milsim.322squadron.com for more information and to subscribe. The website is in Dutch, try this link for an English translation via Google Translate

Another one in Google: 1. Enter the answer to life, the universe and everything 2. Click Search 3. Enjoy your new-found wisdom :D People who know Douglas Adams already know the answer ;)

1. Write in google: askew 2. Click Search 3. :D

if loadstring doesn't succeed, just return false. In that case you're comparing the orignal (working) script with an edited (non-working) script.

I wonder what would happen if everyone put links to banned websites censored content on their websites. Then they'd have to censor the entire internet, which is near impossible.

Yesterday evening we were able to fly online on several public servers for a few hours and had no problems. Although I did spot someone joining the server in all aircraft in the list, before joining as spectator again and leaving, all within one or two seconds. Don't know if it's the same issue though.

Maybe this is what you're looking for. I haven't tried it myself yet, but it should enable you to use your laptop as a second monitor. http://www.zoneos.com/zonescreen.htm

I also have the Asus Eee pad Transformer with keyboard. Big advantage is that you get a netbook and a tablet in one. It runs Android 3.2 (Honeycomb).

Watch out for oncoming traffic :) Saudi Hawks Red Arrows Turkish Stars Above pictures were taken during the Koksijde airshow in Belgium earlier this year.

Mine is me in a Hungarian MiG-29. I was visiting the airshow at Kecskemét in 2007, and couldn't let the opportunity go by to have a chat with one of the pilots and take a seat in his plane.

somewhere between 4 and 30 FPS, depending on my position in the formation, and the amount of flares around me :D It was the first time I participated in this mayhem, but definately not the last!

The E-3 was flying, the Eagle was still on the ground, maybe that makes the difference.

Made me think of this one: Although I agree that DCS AI isn't smart enough to notice and go around.

I think you're mixing me up with Wasserfall ;) You just gave me a new project to work on with your previous post. When I have the USB Extension and Master board from OpenCockpits, I'm starting work on the PPD-SP panel :)

@Maraudeur: I need a 10-bit input because the Flare Quantity selector is basically a variable resistor (like a potentiometer), with 1000 possible values. An 8-bit input only has a resolution of 256 values, so it doesn't 'see' most of the numbers I choose. A 10-bit input has a resolution of 1024 values, which as a result can detect all 1000 possible numbers. As for your SIOC code, it looks simple enough :) Are in/outputs directly coupled to your variables? (e.g. &Flaps_ind, V0999, etc) With the lua code I posted earlier, you can drop the code to calculate whether the gear and flaps should be up or down ;) The lua code gives you accurate gear and flap positions, even when lockon puts the flaps up or down automatically. My setup constantly reads the position of all switches, which enables me to put the gear-lever up while still on the runway, and have the gear retract automatically when I rotate :) This works perfectly in the Su-27 and MiG-29. With the Su-25T on the other hand, it has resulted in some embarrassing moments when the gear retracted right after I spawned on the platform...

Already posted in the "Post your setup" topic, but it also fits in here. This is my mechanical systems indicator prototype, together with some inputs. Note that the LEDs are all controlled from Lockon via export.lua, and don't necessarily reflect the position of the gear and flaps switches. (for this picture Lockon wasn't running, I used my test-application to control the LEDs) The Flare Quantity selector isn't working yet, because I need a 10-bit analog input for that, which I don't have (although I do have two 8-bit inputs) If someone has an idea whether two 8-bit inputs can be combined in a clever way to 'emulate' one input, please let me know.

Here's my current setup: The Flare Quantity selector isn't working yet, still working on that one.

You can also put the connetion code inside your include file. Just remember to give it a unique name. So you could use a variable named SiocConnection for one, and LovpConnection for the other for example. (using "connection" in both will overwrite one with the other)

Someone from ED correct me if I'm wrong, but if I'm correct, the rod values indicate spring pressure, not hydraulics pressure. You can test this by logging the gear.nose.rod and apply full throttle while holding the brakes. You will see that it is ~0.5 at rest, and increases as the nose is pushed down. Currently I do not work with IOC hardware, but I'm very interested, because I want to replace my current interface board (velleman K8055) with IOC boards in the near future.

I haven't worked with two TCP clients yet, but I think it should be easily possible. This is what I use to connect to my interface application: socket = require("socket") host = "localhost" port = 10309 connection = socket.try(socket.connect(host, port)) connection:setoption("tcp-nodelay", true) socket.try(connection:send("start")) I see no reason why something like this would not work: socket = require("socket") host1 = "localhost" port1 = 10309 host2 = "localhost" port2 = 10310 connection1 = socket.try(socket.connect(host1, port1)) connection1:setoption("tcp-nodelay", true) connection2 = socket.try(socket.connect(host2, port2)) connection2:setoption("tcp-nodelay", true) socket.try(connection1:send("start")) socket.try(connection2:send("start"))

I haven't tried the canopy position yet, but this is what I use for the mechanical systems indicator: function ExportCockpitData() if LoGetMechInfo() then local RawGearStatus = LoGetMechInfo().gear.value local RawFlapStatus = LoGetMechInfo().flaps.value local RawBrakeStatus = LoGetMechInfo().speedbrakes.value --[[ RawGearStatus == 1 --> Gear Down RawGearStatus == 0 --> Gear Up RawGearStatus > 0 < 1 --> Gear 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 -- io.write(returnString) end end As you can see, everything is exported as a value between 0 and 1, where 1 = extended and 0 = retracted. When parts are moving (e.g. raising or lowering flaps), you get decimal values indicating the current position of the parts, all the way from fully raised to fully lowered. In the code above I also use gear.main.left.rod and gear.main.right.rod. These values indicate the pressure on each wheel (both main landing gear in this case), which I use to determine whether the FOD shields should be up or down. In the next version, I will also incorporate blinking leds for the airbrake and flaps, but for that I have to change my interface software a bit.

I also came across this interface, and it looks very interesting. Please let us know if it works (provided your 'Boss' agrees ;) )

It has been a while since I last posted in this topic, but in the meantime I have been working on a mechanical system indicator. At the moment it shows the state for flaps, gear, FOD shields and airbrake, all read from lockon! No cheating necessary, just plain lua. Here is how you do it: In the export.lua, there is a function LoGetMechInfo(), which gives you loads of interesting data. For the above indicator, I use the following: - LoGetMechInfo().gear.value - LoGetMechInfo().flaps.value - LoGetMechInfo().speedbrakes.value These will give you anything between 0 and 1, so if you're only interested in the up or down position, you can do this: local gearState = LoGetMechInfo().gear.value and 1 or 0 I plan on updating our DFDT Wiki with the complete code to make this work.