algerad3

Cool, it is good to here all is working well for you. I think the new dll is the way to go as well, but I want to make sure I get input from others that have been waiting patiently for the other modules to get added. The extra button functions are nice and add more immersion.

A little update. I finally got some time to dig into the newest saitek dll and got the screen grab to work ( as shown a few post back). I ran into a couple of issues along the way and had to make changes to the dll. It was crashing during button presses. I was able to correct that without adding other issues(I think). The colors are off for the hand drawn gauges and I am/was working on correcting that issue. ( still a bit stumped). The current process for using the new dll with screen grab is promising for adding the mfds(A-10c warthog) schval-abris(blackshark) and radar -with some graphic issues(F-5e). I have got all of those to display on the Fip and interactive by button presses. I use desk space and an android tablet as a monitor so I do not have the mfds and such duplicated on my sim screen.While the display on my tablet is some times sluggish on the refresh , the fips refresh almost instantly ( they refresh well before the desk space screen). I ran into a curious situation in which I did not activate desk space and the fips did display the mfds and the buttons worked , so maybe desk space is not needed. I am still investigating. Currently I am away for a few months and can not continue for awhile, but will continue when I get back. I am still undecided as how to proceed, do I update gauges for new modules using old dll and then switching to new or do I advance the new dll (iron out issues) and adjust everything for that model. Also , I am waiting for corrections to be made to the"options.view(?) lua script , I see the need for that to work in order to switch between modules properly in the new system. That is all for now, will be at it some more in a few months.

let me know when you get back and I will walk you through the issues.

Which item are you using? Fip, X52 pro , Both. IF you lost your assignments, it sounds like you are using x52pro. If X52 pro did you install BOTH x52 and Fip drivers. The dll requires both drivers to be installed for the x52 to be captured.

Let me know how it all goes. For the most part , this thread was started to get like minded people together to get these items to work. Now that I have new options , once I get the new scripts done , I will have this thread cleaned up or start a new one and post better info.

Use the drivers posted here . the newer drivers do not work for some reason. https://forums.eagle.ru/showpost.php?p=2507414&postcount=356 The scripts are for 32 bit lua.

My mistake !!! SaitekStart is the script to click. ( it is the same as Cpias .luac, just not compiled.) I thought I updated the zip file. As soon as I finish my current script changes I will work on cleaning up this thread and all zip files as well as post a pdf manual.

Have you seen this post ? http://forums.eagle.ru/showpost.php?p=2385283&postcount=336 The first page includes the current packages and the link above explains where everything goes.

Hey Grabby: I agree the tutorial needs work ,I am still learning what all can be done and how. What is it you are having problems with ? I will walk you through it.

As stated before, I am working on displaying mfcds (radar,abris, schval etc) on the fips. You will need to export the mfcds to the monitor. Now would be a good time to peruse this post: https://forums.eagle.ru/showthread.php?t=89282&highlight=Multi+monitor . If you do not want to display items on your "gamespace" and have a tablet or smart phone, try this free app ( I am using it ) http://spacedesk.ph/ Don't worry about lag on spacedesk...Mine lags a little but the fips ( for some reason) does not lag and captures the content faster than spacedesk receives the info. Cleaning up gauge art and adding mfcds with button interactions for ka 50 and a-10. Pics above as well as video.

Anyone remember the first time the lights were strung up. Scared the crap out of me, had the volume up and thought someone was downstairs breaking things. LOl good times. This year I was mentally prepared after the first light broke.

What steps have you taken?

A big thank you and shout out to Chrilith!!!! I am on my way to seeing my biggest goal happen !!!!! A little live action demo. Got the Shkval going as well (needs to be hooked up) Camera skills suck ( I know, but I will get more practice as I proceed with this project.):poster_oops:

Back in the saddle? I decided to try something different. I am now in the process of moving this project off of the saitek dll and on to the passerelle dll. F5e gauges will be delayed. (I might release on saitek dll as it is almost done). I would rather focus on the Passerel scripting as I can do what I wanted to do in the first place (I think). The attached pics should offer a hint or two.....:music_whistling::book:

I am having an issue using clickable data input for Accelerometer reset and fast erect buttons. Using GetDevice(27):performClickableAction(3001,1) (accel reset) the button depresses but does not release. Is that intended operation? Same with Fast erect button GetDevice(16):performClickableAction(3001,1) I tried GetDevice(16):performClickableAction(3001,1) GetDevice(16):performClickableAction(3001,-1) chained together no joy. Only solution found was to assign both actions to a separate button. Not sure if bug or just me, thought I would let you guys know.

Well, it has been awhile since I posted anything. I decided to change things a little after looking at the F5E module. It seems to be a bit redundant to add all of the cockpit gauges to the scripts. I am now going to update all scripts to only contain gauges that are hard to see and/or are interactive. For example I will remove the airspeed gauge in the KA50 and keep the HSI, so that the fips will provide access to the knobs and switches. I will also add radio control functions to the fips. This will reduce the number of pages needed and reduce the needed to cram so many gauges into a small screen. I will create one package to contain all of the changed gauge set and leave the current ones up for now. (I will upload F5E gauge set I had been working on in similar fashion as before, then make the changes.) I will also include x52 pro to be interactive as best as possible.

It has been a long time since I used the SST. If I remember correctly , you have to start the SST program before DCS or any other game/sim. It will cause issues otherwise. ( I might be wrong. Take a look and let me know.) Also, Dcs was known to have issues with SST programing , not sure if that was fixed.

Should be good to go. The driver most of the times installs with the sst software even though the sst software can be downloaded separately. If you can program the stick then, sst is installed.

I have not used the sst software for quite some time. The stick still works and the windows for the sst software still displays as before.

Profiles here: https://forums.eagle.ru/showpost.php?p=1016722&postcount=1 https://forums.eagle.ru/attachment.php?attachmentid=51508&d=1305586510 https://forums.eagle.ru/attachment.php?attachmentid=51504&d=1305577914 http://forums.eagle.ru/showthread.php?t=63912 https://forums.eagle.ru/showpost.php?p=1199899&postcount=1 https://forums.eagle.ru/showpost.php?p=1194563&postcount=1 https://forums.eagle.ru/showpost.php?p=971032&postcount=1 http://files.lockon.ru/en/38409/ https://forums.eagle.ru/showpost.php?p=1317548&postcount=6 https://forums.eagle.ru/showpost.php?p=991009&postcount=1 https://forums.eagle.ru/showpost.php?p=971032&postcount=1 https://forums.eagle.ru/attachment.php?attachmentid=93227&d=1390101922 Reviews and such here( my two cents are in there somewhere): https://forums.eagle.ru/showthread.php?t=60224&highlight=x65f https://forums.eagle.ru/showpost.php?p=1560216&postcount=1 https://forums.eagle.ru/showthread.php?t=103139 https://forums.eagle.ru/showthread.php?t=101958 https://forums.eagle.ru/showthread.php?t=109725 https://forums.eagle.ru/showthread.php?t=111129 https://forums.eagle.ru/showthread.php?t=116346 https://forums.eagle.ru/showthread.php?t=119094 https://forums.eagle.ru/showthread.php?t=117821 https://forums.eagle.ru/showthread.php?t=127271 https://forums.eagle.ru/showpost.php?p=1014188&postcount=1 https://forums.eagle.ru/showpost.php?p=1078919&postcount=1 https://forums.eagle.ru/showpost.php?p=1704124&postcount=1 https://forums.eagle.ru/showpost.php?p=1585512&postcount=1 https://forums.eagle.ru/showpost.php?p=1646445&postcount=1 https://forums.eagle.ru/showpost.php?p=845300&postcount=1 https://forums.eagle.ru/showpost.php?p=962418&postcount=1 https://forums.eagle.ru/showpost.php?p=1001499&postcount=1 https://forums.eagle.ru/showpost.php?p=1967520&postcount=1 https://forums.eagle.ru/showpost.php?p=2126295&postcount=1 I just used search and pasted links . might have a couple of duplicate posts.

Cool enough. If you want , I have a c++ socket to gather info if you want to try.

Ian, Your code works for me ONLY after I have a connection on the other end of the socket. Dcs world does not create the connection, the other script does and waits for DCS. ( See syntax on "socket test " script attached). Think of "c" as a bool value for the connection. True if connected , false if not. try this for your connection. Open Dcs world, open the script in scite console and press the blue arrow/triangle(run). pick module and enter mission. Once mission starts you should get values displayed on scite console screen. Your export script works as is. socket test.lua.lua

Do you have a receiving socket script on the other end ? Let me look at what you have , maybe I can help further.

Ian; Are you trying to manipulate the data Valued "c" ? If so; you need to break "c" down a bit more before you can use the data. "C" is the data stream Table. Before using the data try something like this : function Import() The function you want to use the data in(can be any function you make up) local input=c:receive() Tells the function what part of the table your data is in. if input ~= nil Then this states as long as the data is there, perform the function. If you try something like this : local input = c input will be nil . if you are using Scite try this in your receiving script: function stream() l, e = c:receive() if l ~= nil then print(l) This should display the data stream in the output panel below the coding panel. Also you will need to break down the data stream to get the individual pieces of data. Here is a widely used script for that. function StrSplit(str, delim, maxNb) if l ~= "quit" then if string.find(str, delim) == nil then return { str } elseif l =="quit" then do c:shutdown("both") clearfip() end reconnect() end end if maxNb == nil or maxNb < 1 then maxNb = 0 -- No limit-- end local result = {} local pat = "(.-)" .. delim .. "()" local nb = 0 local lastPos for part, pos in string.gfind(str, pat) do nb = nb + 1 result[nb] = part lastPos = pos if nb == maxNb then break end end -- Handle the last field if nb ~= maxNb then result[nb + 1] = string.sub(str, lastPos) end return result end And to call the data : function scriptrun() -- you can make your own function name. l, e = c:receive() data = StrSplit(l,",") print (data[number]) end -- "number" is numeric number of data table from "c". If you have 14 pieces of data in your export script, then data[] can be from data[1] to data[14]. This snippet will print the piece of data called for in data[number]. This is my basic understanding for lua sockets. There maybe some errors in my explanation of how it works and I am sure someone will educate us both further, but the examples given are what I use in my scripts.

Still around , just been super busy. I will be doing some tinkering this week end.