Moburma

Saitek UH-1H exporter version 0.2 -- New page with info on engine related gauges -- Fixed odd altitude behaviour Haven't sorted out airspeed yet, will get to that eventually! saitekuh1h.lua

The recent Huey release has spurred me back into action! Getting the A-10 to behave drove me round the bend, but thankfully the Huey has been reasonably simple to get working with the exporter dll. As such here are two new releases - an update for my auto export loader, and an exporter for the UH1. Automatic Saitek Export Lua Script V 0.2 -- Now suppots the new UH-1H Huey module. To create your own, just call it saitekuh1h.lua Saitek UH-1H exporter version 0.1 -- Basic information on one page, airspeed, altitude and vertical speed. -- Airspeed is NOT correct at the moment, but I think I know how to fix it. At the moment it's just "ballpark" accurate. Altitude goes weird under 100 feet or so as with the P-51 exporter, but again I can fix it, just need to get round to it. -- Auto loading of joystick profiles. As ever uncomment line 10. -- Toggle LEDs represent from left to right: Master Caution Lamp, RPM Limit lamp, Fire warning Lamp. As you can see this is pretty crude, but it's a start! The Huey seems a pretty easy mod to get going, so once I've flown it a bit more (and can manage to not crash every 10 seconds) I'll try and add useful things to this. Export.lua saitekuh1h.lua

Sounds like this might be of help.

Mentioning Battlefield 3 is interesting - although totally an apples and oranges comparision, one thing I found annoying when first getting into DCS World was the lack of detail in ground textures. Although the flight model in BF3 is of course completely unrealistic, the high level of graphical fidelity actually does have "realism" benefits over DCS - I would frequently rely on the detail in the BF3 textures to instinctively know how close I was to the ground when flying helicopters etc. This threw me for six when getting in to DCS world ( I hadn't played a hardcore sim for a good decade before!) as the level of fidelity was so much poorer on that front - information you'd have both in real life and in graphics heavy games like BF3 was missing. Having said this, in BF3 the edges of the maps (where only aircraft can go) have deliberately low res textures and transition between the two would knock my sense for six all the time as again my internal sense of altitude would have to be recalibrated crossing that line. I remember reading an interview with real pilots in the mid ninties talking about this as being one of the major failings of flight simulators then (and although crude the military grade ones were way beyond home sims like F-15 Strike Eagle etc), so I think it is one area where graphical "fluff" has a real benefit.

Let the speculation begin! Maybe a Vietnam map to go with the huey? Afghanistan? Korea?

I personally assumed the 64-bit statement was totally seperate from the 1.2.4 details due to the fact it is was in bold and further down the page to highlight the very fact this was only something they will do in the future, but are starting to consider seriously. It obviously won't be 1.2.4, but for me it can't come soon enough as it means more potential for a better looking game, not to mention the loss of the dead weight that is 32 bit support meaning the game can be better optimised for 64 bit performance.

I'd never seen that Commanche information before, very interesting stuff. I'm another Gunship/Gunship 2000 veteran, and those games got me obsessed with attack helicopters during my teens. For that reason alone I was sorry to see the Commanche cancelled although I can see exactly why they did.

A tiny update seeing as the thread has all but died. I tried investigating the crash behaviour, and it seems to be something to do with the bitwise operations. I don't know if it's the game receiving values it doesn't expect, or simply too much data is being pumped into the process, but even I remove any end processes, simply calculating how the dial has been moved consistently crashes the game. I've even tried it with a simplified of code to B and and this doesn't make any difference to stabilty compared to the code Algerad3 was using. It's annoying as I just don't know where to begin to fix the problem. It's a shame, as essentially getting a new free control on your joystick would be one of the very best features of this script. Despite all this I might release an A-10 script soon. I might just take all my dial code out of it as it just seems to cause crashes and none of the dials behave properly anyway, but I'll think of useful stuff to add in and you'll have the usual features such as auto profile loading and landing gear lights on the LEDS etc.

Haha, don't worry, i'm not going to give up, just take a break for a while. I might even try messing about with the SU-25, I've not even tried to fly that yet, so maybe making an exporter for it would be one way to learn how it works. The most annoying rotary problem I had was dials not increasing by the amount I expected. I had the same bug with the first ILS dial as this guy where it doesn't behave in a logical way. I also had problems with all the other dials not going increasing their values other than two or so different extreme settings that is almost certainly just bad code on my part. I also had a weird thing where it seems the second ILS dial outputs null values when set higher than 0 that causes the x52 page its on to completely die, really weird.

Another post before bed.. I spend some time over the weekend working on my own A-10C exporter. I got a lot of stuff working, but have been largely stumped by the damned radio controls (I can see why algerad3 was having so much trouble now!). I've got the ILS, and AM and FM VHF radios reporting their information to the screen, and also fully controlling them from the rotary dial. Sounds great, but "working" really needs to be in inverted commas - none of them behave as I expected. I'm in over my head on the rotary stuff, and I really need to sit down and work out the theory behind how the bitwise operations work (never done this kind of mathematical stuff before). I actually managed to successfully replace the bitwise AND code (the only operation used by algerad3's Ka-50 code I cribbed off so heavily!) with a shorter supposedly faster one someone had written, but it doesn't seem to have made any difference to performance or stability. Stability is also a big problem. I don't know if it's the bitwise operations code not being quite right, or the dll file or a combination of both ( crash logs seem about 50/50 that I can make out), but as with the Ka-50 exporter the rotaries cause guaranteed crashes. It's hard to test stuff out as I'll often get a crash just moving the dial twice five seconds into a mission. I really wanted to get this kind of "hard" stuff working good first as I think some really interesting things can be done with the A-10C's controls, and really add to the game, but for now I have to admit temporary defeat!

A new release for a new home! I added a new feature to the KA-50 exporter. At the moment we have lots of pages with information that is readily available on the normal HUD/instrument panel, so I tried to think of something that would really ease the normal workload of flying the chopper. I realised one of the most annoying things was quickly checking the autopilot states. I'd often get in situations were I'd accidentally leave auto turn on target on, or embarrassing times when I'd forget to turn on the autopilot assists on a cold start and even with my freetrack I'd have to take my eyes off the "road" as it were to check and change them. As such this release has some skill-o ascii art representations of the autopilot lights on the MFD! I'm quite pleased how this came out and think it makes a genuinely useful addition to the game (I'm aware that so far a lot of the stuff on the MFD is a little gimmicky - it's often simpler just to look at the relevant gauge etc in the game). Here's a picture of it running: In this picture I've got Auto turn to target and Moving ground target lights on the left panel, and bank, pitch and heading hold on the right panel. The top right can also show the Flight Director light, marked with a D when on. Saitek Ka-50 Exporter 0.3 New Features - Auto Joystick Profile loading. This is commented out in the release file. To enable it, remove the "--" comment marks from the start of line 10. The path shown should be the default for the SST software on a standard Windows 7 installation, so you should be able to just change the filename specified at the end to the filename of the profile you are actually using for your Ka-50. - New page showing autopilot light status as above. Shows the status both for weaponry assist modes and also for the actual autopilot. Installation If you're using my autoloader export.lua from (download here - highly recommended), then just save this file as-is into your Saved Games\DCS\Scripts\ folder and it will automatically be loaded every time you fly a Ka-50 mission. If not, rename it to export.lua and put it in there. saitekka50.lua

I just tried out a cool idea this evening that I think is quite exciting. With Chrilith's dll it is possible to not only add pages to the MFD screen, but also remove them. This might sound pretty banal and obvious, but you can also set a screen as "active" when it is created. This makes it show up instantly on the screen. I've used this in my export files so far to make one screen the "default" one that comes on when the mission is loaded, but I realise now you can do stuff that is MUCH more interesting than that. Basically you can make one off messages flash up on the screen depending on what is happening in the game, and then have them be removed again and not be part of the "regular" set of pages. You could for example, emulate the Ka-50's Ecran this way to report e.g. system failures on the MFD. What I did was set up a new page text string wise, but then didn't declare it in the normal way using addpage. Instead I hid it behind an if statement. In this case I just triggered the conditions to be when the red landing light in the P-51 was on to display a message via saitek.AddPage with the activate "true" argument, and then when the red light was off send a saitek.RemovePage command if the light was off. Pretty basic and arbitrary stuff, but I realise now you could make everything from automatic warning messages to menu systems using this feature set.

One more post before bed! I played around with the P-51 exporter some more, and got some cool stuff going. As such, here is a new release. Saitek P-51D exporter version 0.2 New Features: -- New page featuring levels of all fuel tanks on board. No more looking under the seat! I'm not sure if the maths here are quite right, but I think it's close (exactly how much fuel CAN the P-51D hold?). Levels measured are Left tank, Right tank, Fuselage tank (empty in most missions), and combined Total in gallons. -- Landing gear indicators are now mirrored on the left and middle joystick toggle lights. The right hand toggle will still be default colour. Should I switch this off or leave it as-is? -- Auto Joystick Profile loading. This is commented out in the release file. To enable it, remove the "--" bit from the start of line 10. The path shown should be the default for the SST software on a standard Windows 7 installation, so you should be able to just change the filename specified at the end to the filename of the profile you are actually using for your P-51. If you set this up then the game will make your joystick automatically load the correct stick profile every time you fly the P-51. Cool huh? If you set it up and the stick defaults to No Profile then you've typed something incorrect. Installation If you're using my autoloader export.lua from my last post (highly recommended), then just save this file as-is into your scripts folder. If not, rename it to export.lua and put it in there. I got an Su-25T profile working as well, but it's very boring at the moment (airspeed, alt, etc). I need to look up how (if?) you can get the indicator lights status from these old Lock On planes. saitekp51.lua

I'm pretty new to modding DCS World so I didn't realise it was that new a development. I saw the code at the end of the lua from this thread, and nicked the directory finding code from the instructions for Tacview. Of course you can't inspect devices that aren't present in the current aircraft in a lua, so this seemed like the obvious way around it. As far as I know there aren't any shortcomings to it, and have been playing KA-50 missions all evening with no problems. I can happily load up a KA-50 mission, quit, and then load up a P-51 mission and get my the X-52 exported screens working perfectly and automatically! I've got my joystick profile set to autoload in the KA-50 export now and it's awesome to just load up the game and have everything good to go straight away. I deliberately didn't do any work on an A-10 exporter as I know you were working on one (with cool stuff I don't dare touch yet like radios), but I might try and start an SU-25T one (haven't really flown that plane yet though), and will probably add some cool stuff to the P-51 exporter such as landing gear lights and fuel status etc. I know this is hardly the most popular thread/development, but do people have any requests for data they'd like to see for particular aircraft?

I've been working on a new framework for these export lua files. At the moment you of course have to rename the lua file for whatever plane you want to fly to export.lua, and it won't work correctly if you then decide to fly a different plane without manually changing the files around. As such I've made an automatic launcher that will detect what aircraft is currently being flown and load the appropriate saitek export lua file. If you want to use this system you will need to rename your export.lua files to fit the scheme I'll lay out below. You can actually use this export.lua to launch any other lua files you want and not just these saitek ones, so feel free to edit it and use this for other projects. Automatic Saitek Export Lua Script Instructions Attached to this post you will find a file called export.lua. Download and save this file in your Saved Games\DCS\Scripts\ directory. If you already have an export.lua in there then back it up first, then overwrite it. Once you've done this, you need to name your old saitek export.lua file in the Scripts directory to one of the following filenames for the game to automatically load it and start outputting the X-52 or FIP screens: [table]DCS Module|Filename A-10C|saiteka10c.lua Ka-50|saitekka50.lua Su-25T|saiteksu25.lua P-51D|saitekp51.lua Other|saitekother.lua [/table]So, to use e.g. the lua attached to my previous post for the Ka-50 (MoburmaExport0.2.lua), simply download it and then rename it to saitekka50.lua and put it in the Saved Games\DCS\Scripts\ directory. This system will also work perfectly with the export.luas created by Kucha and algerad3. With this script you can therefore have a separate exporter lua for each DCS supported aircraft, and even better it will be loaded up automatically for you on mission start! I've also included support for new aircraft. If you're somehow lucky enough to have access to a non-public DCS mod, the script should fall back to saitekother.lua so that file could be used to create a new MFD script for your mod. As a bonus I've included my early exporter for the P-51D Mustang. It doesn't do anything that exciting yet, just two pages showing you altitude and airspeed, and another showing you engine information (altitude goes a bit screwey under 100ft at the moment, I think I can fix that with some maths), but you can use it in conjunction with the existing KA-50 export files to test my script framework. The P-51 exporter is already named correctly to work with the autoload framework. If you don't want to use the framework, just rename saitekp51.lua to export.lua With this system and Chrillith's dll file it is actually possible to have the X-52 automatically load the profile for the aircraft into the joystick itself. I might include this in the next version of my exports, but it will be left commented out as obviously you will need to be using the exact same profile as me for the script to work. The brave can of course edit this to have their favourite profile automatically loaded along with everything else. Enjoy! Export.lua saitekp51.lua

Here's a fixed version of my export.lua I posted above. This is pretty much the same as the last one, only I coded the landing light behaviour differently to stop the flickering that would happen if the lights were off such as from a cold start or when the gears were retracting (was due to bad code on my part). I also set this version to automatically switch to the APU page as soon as the mission starts now. algerad3 - thanks for the stopwatch info. I guessed it was the case you can't control it, but you never know. Shame they seem to have put so much effort into this thing and then just abandoned it. MoburmaExport0.2.lua

I got a very basic export.lua for the P-51 working now. It's nothing exciting, just a single page with airspeed and altitude etc on it. Does anyone know what the device ID is for the radio on the P-51? I'll add that if anyone can give me a clue.

Ok, I've been playing with this today and made my own version of the export.lua. This is 99% based on algerad3 and Kurcha's amazing work. In his words I'm just a copy/paste programmer, I'm relying on much smarter guys like him to do the heavy lifting. The file I've attached below does two main things, it merges Kurcha's really great fixes to the flight values so what is reported on the MFCD is now correct (I hope he doesn't mind this), and also includes his tidied up labels (so e.g. the radios are now reported as VHF1 etc). The new changes I've made myself are just fun stuff with the LEDS on the stick. With this version the stick's main FIRE button LED now reflects the Weapon Arm indicator in the KA-50. It will illuminate when that switch is turned on, and will be off when weapons are not armed. I've also added some changes to the landing gear LEDS so that they now work across ALL pages, and should reflect the correct landing gear state if you switch back and forth between pages (previously they'd all go amber due to both LEDS being on). Due to the way I coded this the lights will flicker slightly in a neutral state (i.e. gear moving and neither completely up or down yet), and I think the effect will be broken if you've changed the default LED colour (i.e. not green) in the X52 joystick control panel, but I think it's good enough. Keep in mind that LED effects do NOT work on the default MFCD information page (i.e. the one that tells you which profile you have loaded). I'm not sure how to do this yet or if it's even possible (I tried setting the page to '0' but that didn't make any different, is there a special number for this page, or is it just impossible to change?). The changes I've made will however now mean that landing gear colours will still be correct after you switch from this page to one of the new exported pages unlike in algerad3's original LUA. To install, just rename to Export.lua (I only renamed it to distinguish from algerad3 and Kurcha's releases) and place in the Saved Games\DCS\Scripts\ directory. Feel free to use my crappy code in your own versions! Oh yeah, and I guess this is more of a question for Chrillith, but is it possible to assign the START/STOP and RESET buttons to controls, or are these hardwired to only work using the useless built in stopwatch functions? I didn't see them in the readme for his dll, so I guess you can't use them. Also, is it possible to change the clock area to show information? By the nature of the LCD here you can't do much with it, but I thought it might be cool to be able to show the current local time in the game rather than just the real world time (for e.g. missions that require you to wait at a location until a certain time has passed). MoburmaExport0.1.lua

Got it working! impressive stuff, only used it for five minutes just now, but your latest export.lua worked perfectly, no flicker on my screen. The reason why it didn't work was a combination of two things; me being an idiot and not reading the example lua file from one of your old archives and renaming the .dll file to "saitek.dll" (duh), and two not using the lua5.1.dll file from Chrillith's original archive. Using just the 64 bit executables from your archive/the official 64bit Lua distribution would NOT work for me, is the saitek.dll hardcoded to use lua5.1.dll? I found this whole process quite confusing, so if you don't mind I'll lay out a little "for dummies" tutorial for anyone who is interested to join the party based on what I found: How to install 1) Download and install the drivers for your X52 Pro joystick (you've almost certainly done this already, but this is for dummies!) 2) Download and install the drivers for the Saitek Pro Flight Instrumentation Panel from here (YES you NEED this even if you're not using a FIP and only the X52 Pro). 3) Download the installer package for LUA for Windows from here. Install it to the default location. 4) Download the 64 bit LUA executables (the ones we installed above were only 32 bit, and DCS World is 64 bit). Get them from here. 5) Go to the C:\Program Files (x86)\Lua\5.1 directory where LUA was installed. Delete all the files in the directory after the 7zip.exe (assuming you have usual Windows sorting. DO NOT delete any foldiers). Replace the executables in here with the ones in the 64 bit lua zip file above (e.g. lua52.dll etc). I'm actually not 100% sure if this step is necessary, but algerad3's original instructions included it so so am I! 6) If you want to use a 32bit based lua editor you need the 32 bit environment installed as well, so reinstall the file you downloaded in 3) again. This time install it to C:\Program Files (x86)\Lua32\ NOT the default installation directory or you will overwrite the changes we just made! 7) Download Chrillith's Saitek DLL package from his site. You can find the download link here. 8) Extract the files to a temporary directory somewhere - we only want some of them. 9) Open the Install\Saitek\64-bit directory in the files you just extracted. There are two more directories after this, and we need to move the files inside them to different places. Open the "dll" directory, and copy lua5.1.dll to the C:\Program Files (x86)\Lua\5.1 directory where we stuck the files in step 5). 10) Go back and open the other directory that you would have seen in step 9) called "lua". Copy the saitek.dll file inside here to the "bin" folder inside your main DCS world directory. You can now delete all the other files you extracted from the archive to clean up. 11) Download the "Export.lua" file from algerad3's post here. Copy this to your Saved Games\DCS\Scripts directory. To get to this directory, you need to open the start menu in Windows 7, and click on your username on the right hand side of the menu. You should see "saved games" listed in the window that will open. Once inside the DCS folder you won't actually have a "scripts" directory by default, so you will have to make it by hand if not. 12) Load up the game and start a KA-50 mission. If everything worked then you should be able to use the left dial on the X52 throttle MFCD to bring up info. If not then check the DCS.log file in your Saved Games\DCS\Logs folder, and towards the end there will hopefully be error messages to do with "saitek" in there to give you a clue as to what went wrong. Usage Info Algerad3's currently released Export.lua only functions with the KA-50 module for DCS World. Algerad3's export.lua will create new "pages" on your X52 Pro MFD screen. The MFD will default to the usual screen that shows the current profile that is loaded. To get to the new pages that show you information on radio frequencies, engine RPMs, etc, roll the left dial below the screen (marked with Pg ^ etc). While on the page with the APU information, the LEDS on the joystick itself will reflect the current state of the KA-50s' landing gear (Green for down, Red for up, as on the instrument panel of the aircraft). This does not work while on other pages of the display. The right rotary dial changes the first dial of the VHF1 radio in the aircraft, adjusting the frequency up and down as the real control would. To toggle to the second rotary for this control, PUSH in the right rotary dial. Push it in again to change back. Note that this control is very buggy at the moment, and WILL crash the game if you use it a lot or change frequencies quickly. -- This is really cool, and now I've got it working I might see what I can do myself. I'm not much of a programmer but I've done some modding work on other games and I think I have a very basic grasp of how the lua file works. A-10 stuff sounds very exciting!

Sorry, a few more details: I actually had installed the FIP drivers, and did so after my joystick drivers (which I installed ages ago). I'm trying to get the X52 Pro screens working. I'm using DCS World with the Black Shark 2 upgrade version, and put the .dll in DCS World\Mods\aircrafts\Ka-50\bin is that correct? The export.lua I was using was just the one you posted on post 68 of this thread. I haven't tried to do anything "clever" with it yet, I just wanted to see it working first! Is that export.lua ok to use as is, or have I goofed? I'm somewhat new to DCS world and haven't used the export.lua functions before. Someone had basically the same problem here (posted by "Dorian in the comments there) with in this case FSX looking for the same non-existant .lua files instead of calling .dll functions. Clearly I'm doing something wrong but I'm not sure what. I guess I should delete everything and start again. I stuck the export.lua in the my Saved Games\DCS\Scripts directory, I take it you don't need the config.lua file anymore now? Don't worry too much about if if you're not sure, I know from experience how annoying it can be to use time you could spend developing stuff to helping someone who's done something dumb and not read the instructions properly!

Hey Algerad3, I've been watching this thread with interest for some time now so decided to dive in. I've tried to follow your guides to the letter, but I've been getting a problem where it seems the .dll file isn't being recognised, so I must have done something wrong. The output from dcs.log is as follows: I've got the .dll in the bin folder for the Ka-50, have LUA for windows installed, replaced the executables with the ones from your achive and then reinstalled it again for the 32 bit version in the lua32 directory, and have tried various export.luas from this thread, but I always get the same message. I noticed someone on chrilith's forums had the same problem, but he just reinstalled everything? Anyone got any insights into what I've done wrong?