algerad3

I tried to play with the directoutput sdk too much, give me some time and I will get back to you.

Devrim, Somewhere along the line I wound up working on both ..I do need to do more work for the X52pro. I had been working on the X52pro and set up a tutorial for making scripts for the Pro. Then I needed to get the fips working as others had been waiting. Now , I need to finish getting the a-10 - p-51 gauges going and then update the x-52 pro scripts .... in the end I will have both items working in the script and the script will decide whether to run the x-52 , the fips or both . Now that I have a week to myself , I should have a lot done by next weekend. So to Devrim and everyone else .... Still a wip just sharing as I go.

More gauges Well , got some more gauges to play with here. Huey and Ka 50 in this package. Not much has changed for the Ka50 for now.. I only have a few of the Huey gauges working for now. Still a bit to work out. Gauges Scite is the gauge program to be started in scite. Exports.zip is to be opened and the lua scripts placed in user/saved games/dcs / scripts folder. the other two zip folders ar to be opened and the folders placed in C/program files/Saitek/directoutput/ folder. Not all of the gauges in the gauge folders are functioning yet. The export script will pick the correct script according to module being flown. Just be sure to start the right gauges script with scite. If Dcs world crashes when loading or during startup.... you may have forgotten to start the script. Follow the comments in the Ka50, huey gauges scripts, they are set up for an 8 fip run. You can change the update speed in the export file ( i.e saitekuh1h) look for the last line "tNext = tNext + .9" changes can be made from .1-.9. If you set tNext to low ( say .2) dcs may crash as it is not enough time to clear the output socket. A higher delay rate may help speed up fip response times. Experiment according to your rig. Any questions post here. Now on to the a-10. saitek package.zip

It was me , a quick reboot and as is well. In other words ..... Never mind!!!! work resumes

Is it me or does the new updates mess with these files ? Trying to get things going for Huey and a-10 but I am not getting export info.

Gauges You know, I think it might help if I add the gauges for the gauges pack. Sorry, forgot that part. Here are the gauges for the fips. put the folder into C:\\Program Files\\Saitek\\DirectOutput. The lua files already direct to that path. Ka 50 gauges.zip

well, my original plans are still up in the air. Had to do things a bit different. I have things working ( at least the gauges. Still need to work on the button callbacks.) Right now I am focusing on getting the gauges to display properly...math the input. here is the ka -50 set... going to do the a-10 tonight , maybe get the huey done before the end of the weekend. The lua I attached is set up for eight gauges. Take a look at the lua file and follow the tips for setting up the index and pages. when using this for Dcs World make sure you start the gauges lua before starting a mission. If Dcs world crashes while loading , you forgot to start the gauges lua. For some reason when using the lua files , dcs drops to desktop and you have to find the tile on the system bar and click to bring it back. After missions you have to restart the lua gauge files with scite. But we now have gauges , let me set up the rest of the modules and I will get the rest of the documentation done and ready. Export.lua Ka 50 gauges no buttons.lua

I think I figured it out. All this "stop and go" nonsense is making me forget where I am going after I stopped. One of those been there , done that ,solved it and forgot what , how , or why. Basically..... Never mind.

I am finding after several test that saitek.SetImage slows down the input stream during tcp transfer and gives a slow response to the gauge needles. After closing the simulation, I still have to wait for the stream to catch up and close the tcp script. Is there any way to speed up the transfer /input rate of this function?

Welcome back, I understand how all that goes. Nothing more painful than getting into this stuff and having to stop for r/l and then returning. Oh, the confusion... Made a series of gauges , not the greatest looking stuff, but some lessons have been learned. Now I just need to figure out who and why data is bottle necking with multiple fips. Add the x52 pro back in the mix and we should be good to go. Of course , real life has been slowing me down on this end quite a bit.

Which axis are you trying to map and how are you doing it? I am sure the solution is something simple.

Excuse me for sounding like I am tooting my own horn here, but have you taken a look at the Lua dll in this thread. I was trying to put something together in c++ (learning phase) and then the lua dll was created. While I am currently focusing my project using the lua dll, I was able to gleam a lot more knowledge in how it should be put to use in other programing languages. I believe in the first ten pages are some examples you can look at for a better perspective. I am pretty sure the answer you seek is in there , just can not remember details at the moment.

Sweetness, So for now all is working I take it? I found that the X-52 pro sdk ( directoutput 6.2) easier to use when I tried playing with it. It was created when only the joystick was on the market. When they created the Fips they had to create a more accomodating dll for both. ( 7.0) When you update the drivers make sure the s.s.t program version and driver version match. ( if you use the s.s.s program.) It sounds like you are on the right path, any more question feel free to ask. Algerad.

I am only guessing here , but it looks like you have the old sdk reference sheet and examples. The Hello world and output test examples only work on the old sdk....( the one for X-52pro alone). Currently you seem to be working with the X52 pro and fip sdk. The functions have been changed to allow for multiple devices ( mostly more than one Fip). Either one will do and if you plan on getting an fip or two down the road creating gauges then I would recommend sticking with the dll you have installed. The reference for that should be in C:\Program Files\saitek \DirectOutput. Also, the reference in C:\Program Files(x86)\Saitek \Directoutput\sdk. should not be there, only \gauges. If you have the examples "hello World " and "Output Test" but , the dll has the callback "DirectOutput_RegisterDeviceCallback". Then your Directoutput files are messed up. Uninstall all, Reinstall X-52 drivers and Directoputput, Then install new Fip/x52 drivers( if you want to get fips later , if not don't). That should sort it out. If you only install the x52 pro sdk then you will find the saitek stuff in C:\Program files(x86) folder only. Also, You have to install the x52 pro first before the Fip drivers to register things properly. Also save the old reference sheet and then compare the new with the old. They changed the enumeration process in the new one. Hard for me to explain in writing but, feel free to ask if you have anymore questions/ confusions.

No worries.

Sorry to create confusion. I meant the first link in my reply. We are using a lua dll for the saitek gear.( X52 pro and Fips.)

Update... A-10 gauges pretty much done , still need to figure out how to draw a few things. Will get p-51 done then , sort out the lag time. After that will put out individual module gauge set. Once that is out will work on making a package gauge set that will work with all modules. Of course the wiki still needs more input. will do when I have better understanding of getting things to play nice together. X-52 pro readouts will be included. Just busy and this is a bit more tedious than I thought it would be. Slow and steady and I should be caught up before they release the next module.

Soyo, Welcome to the club. We have a section on the X52 pro and the Fips here http://forums.eagle.ru/showthread.php?t=94174. whis should help you get started. As far as the different sdk one is for the x52 pro only and the second is for both the x52 pro and the fips. More info on the fips here http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CDsQjBAwAg&url=http%3A%2F%2Fwww.saitek.com%2Fuk%2Fprod%2Ffip.html&ei=31MuUpvCKuH8iwLw5oHQAw&usg=AFQjCNGsw9bWPRET-I_Dan3KFgnMnppxZg&bvm=bv.51773540,d.cGE&cad=rja . You will find information about the sdk in C:\Program Files(x86)\Saitek or in C:\Program Files\saitek depending on which sdk you install. Hope this helps.. If any question post up in the How to forums and I will respond.

Just an update: Drawing A-10 Gauges..After that P-51. Pretty much have Huey and Ka -50 drawn. Still a learning process so,not exactly glamorous stuff , but working. Need to "wire" the gauges and work on script. I think I know why the FIPS are acting sluggish when more than one and will revise script. So hopefully soon we will have gauges for all DCS aircraft working for the saitek gear with corresponding buttons and knobs functional. Saw another post that reminded me of another feature of the sdk and that may allow me to get the mfds,Schval, abris and other screens to the Fip. Will investigate after the above issues are completed. Hang in there getting closer by minute.

Cool , Will check it out .. Thanks Gremlin

AH, Liking the concept..Will keep an eye out for this.

yes , currently the KA-50 gauge pack ( wip) Uses buttons and knobs for page two( abris, no visuals) the hsi and the other gauges in the sim with buttons and knobs will be matched. I plan to do this for all of the gauges, and maybe add radio functions to the fip similar as with the X52pro. Drawing the gauges is a slow process for me , faster than the scripting but still tedious effort and I am still learning how to do that. It will be a bit but it will be...

I'ma afraid that I can't export graphics with lua... Gd only works with everything but bmp files. I have to draw my own gauges. I understand what you say about lua...driving me bonkers but, I have to admit I am at the learners stage of programming ... Would you care to share your c# set up , I would like to see how to do it at that level , was trying to create an interface with C++ but they changed the callbacks on one of the functions and it kept me quite confused.

Hey gremlin, welcome to the club. Yes I would be interested in the tool. My attempts are finally coming together but , I am pretty much learning the ins and outs of lua..( I know , you are using C#) Take a look at this.....http://forums.eagle.ru/showthread.php?t=94174 A few lua scripts in there to get the X52 pro and fips going .

Try this link http://forums.eagle.ru/showthread.php?t=94174. A lot to read but at the end you will find that they now work.. some work still needs to be done. Oh and about the x65... The fips mount on them nicely, I have two mounted there and 6 others sitting on desktop. All kinds of knobs and buttons to play with .