The LT

I cannot get ScITE to run the saitekwithfiptcp script as I get lua: saitekwith fiptcp.lua:3: module 'saitek' not found: no field package.preload['saitek'] no file '.\saitek.lua' no file 'C:\Program Files (x86)\Lua32\5.1\lua\saitek.lua' no file 'C:\Program Files (x86)\Lua32\5.1\lua\saitek\init.lua' no file 'C:\Program Files (x86)\Lua32\5.1\saitek.lua' no file 'C:\Program Files (x86)\Lua32\5.1\saitek\init.lua' no file 'C:\Program Files (x86)\Lua\5.1\lua\saitek.luac' no file '.\saitek.lua' no file 'C:\Program Files (x86)\Lua32\5.1\lua\saitek.lua' no file 'C:\Program Files (x86)\Lua32\5.1\lua\saitek\init.lua' no file 'C:\Program Files (x86)\Lua32\5.1\saitek.lua' no file 'C:\Program Files (x86)\Lua32\5.1\saitek\init.lua' no file 'C:\Program Files (x86)\Lua32\5.1\lua\saitek.luac' no file '.\saitek.dll' no file '.\saitek51.dll' no file 'C:\Program Files (x86)\Lua32\5.1\saitek.dll' no file 'C:\Program Files (x86)\Lua32\5.1\saitek51.dll' no file 'C:\Program Files (x86)\Lua32\5.1\clibs\saitek.dll' no file 'C:\Program Files (x86)\Lua32\5.1\clibs\saitek51.dll' no file 'C:\Program Files (x86)\Lua32\5.1\loadall.dll' no file 'C:\Program Files (x86)\Lua32\5.1\clibs\loadall.dll' stack traceback: [C]: in function 'require' saitekwith fiptcp.lua:3: in main chunk [C]: ? >Exit code: 1 I couldn't find any such files anywhere! Help?

A couple of Russian links for you guys: http://www.vkb-flightsimcontrols.com/ And another guy who makes nice pedal kits: http://avia-sim.ru/forum/viewtopic.php?t=682 http://avia-sim.ru/forum/viewtopic.php?t=716 Both manufacturers are somewhat pricey, but well worth the money.

Great job! Thank you, algerad3! If it is not too much to ask, could you throw together a quick howto on how to get things to work in DCS? Like, file paths and generic setup. I'd really love to try it out but there is almost no concise information on the subject and it's time consuming to read through all the forum (wish I had more time).

Great news, keep us posted!

I want 1080p display of similar size :)

Nice work on the approach plates, mate! Thanks!

There was a new version out somewhat recently, both the driver and the SST programming software: 7.0.27.13 Among the new features I've found out that rotary encoders below the MFD started to show up in the game without the Control Panel being open. On the downside, the throttle started to flicker the MFD and glitch out, causing phantom keypresses. I downgraded back to 6.2.2.4 and it has been mostly perfect since. So YMMV.

Any news on the subject? By the way, there are new drivers for the X-52 Pro, is it compatible with the DLL?

I've dug up the 6.2.2.4 driver and software and it seems that the problem went away. But I've lost the rotary encoders below the MFD which were functional on the newer driver. Any ideas how to get "the best of both worlds"?

Hi guys, Got a problem here, My X-52 Pro MFD backlight started going dim on me and I'm getting random phantom keystrokes. I've recently updated my drivers to the latest Saitek ones. It doesn't happen all the time but after some time playing. Is it a known issue?

Excellent video.

Sweet skin. Should be included into the main game

Such an awesome flight, hopefully I'll join up sometime later when there is one! :) Familiar Nov Vinson there ;)

Genius! Very nice trick! Thanks a lot, sir!

Autopilot. Автопилот in Russian.

I fly on the Pony with an X52Pro without any curves and it's fine. I think that the regular X52 isn't much worse than a Pro.

Take-off and pull re-cage when you're in level flight. Simple. The gauge accumulates errors over time though. By the way, the manual describes it all in quite adequate detail. Check out the relevant section.

Stupid question, but is there a Ka-50 equivalent of this app?

That's actually not enough, you would have to set the bombs guidance to the correct laser code in the DSMS page. The number below the GBU stations is the code they are set to. Also, you don't really HAVE to use the LSS, you can just make a quick bomb run on an area without getting the TGP on the target (if you're in a hurry).

iPad version, pretty please? I know I'll pay.

Nice sword...

The switches should be clickable just to be able to follow procedures to the letter. (immersion factor!)

It requires quite a few other tasks though. Don't think that WW1 type aircraft is simpler than a VW Beetle. They have a lot of quirks. They would also require tremendous effort to do a physics-based airframe model.

Combat simulation, you say? How about you suffer battle damage to several systems and have to use the same "startup procedure simulation" controls to get things under control? There are reasons why those systems are there in the first place, not simulating them is just unacceptable if you are aiming for a true simulation and not a "game".

After getting a firm grasp on the engine operating ranges and having followed Yo-Yo's guidelines on engine operation, I didn't have a seized engine in more than 20 hours of flight time, in the whole range of operating modes, including WEP bursts. Most of the time my rads are set to automatic, for low speed, I might open them up, but 90% of the time they are on auto. No problems. It might be worthwhile to analyze your actions and see where the fatigue builds up...