pet333r

I understand that your Android's IP address is 192.168.1.245, the configuration you have now will also work, only in group 1 you have set to send "yourself" and there is no need example: if you use one Android device then: you enter the Android IP address in the device 1 "group", in others you can change the property ExportScript.Config.Export2 / Export3 / Export4 from "true" to "false" then the script will send data only to the first one how it works: you are starting DCS you run DCS UFC and select the panel of the machine you are currently in that's all:smilewink:

You enter the IP address (192.168.1.177) of your computer in the DCS UFC settings, in config.lua set Your Android device IP

I sent you an email, not all files were updated. Also check your tablet's IP address because you recently had 192.168.1.65 and you said it has not changed and in the Config.lua file you have 192.168.1.66 Check the tablet's IP address and change it if it is different

It's best to send me the entire Scripts folder from DCS, I will check if you have everything there. Always before every update I check if everything is ok, receive data, etc. Check device IP and network Where did you see it, can you send a link? edit: I tested all modules and every button, everything is ok

New version avaible 1.0.2020.522 - F-14: added Displays panel - A-10C: fixed some graphics - fixed some small bugs - code optimization Update the modules folder in script to make everything work properly:smilewink: https://github.com/pet333r/pw-dev_script

In Your DCS on c drive in Saved Games folder

here you have ready the whole zip file with the script as it should look on the disk: https://github.com/pet333r/pw-dev_script/releases if you do not use other scripts, just unpack to the right place and change the IP addresses in the config.lua file:smilewink: you're right, I need to smooth it out a bit:thumbup:

The fact that 88 is displayed in F/A-18 is just to see how it will look, from the rest of the panels such temporary text is removed. So it doesn't matter. As for the JF-17 there is a problem here, because for some people everything is ok and for others it doesn't work. I tested it together with another user probably in all ways, on the same script (exactly the same files) for some users works, for others not. In the application, everything is ok, while data from DCS for some reason are not received (despite using the same approach as in F/A-18, Ka-50 or M2000). We even compared the files in JF-17 and they are identical. It seems to me that the problem lies somewhere in DCS because using exactly the same script files, the same application file and identical files in JF-17, it works on one system and not on another I also wrote to Deka Ironwork, but I haven't received an answer yet

F-16 or other machines too? Is it on the same device or different? Have you recently updated the entire script? Have you added any new script recently?

In F-16? If warning lights work on one device, while data are not displayed on the other device, your router has probably changed the IP address of the other device. Each device has its own IP address given in the config.lua file, if you do not have them assigned permanently in the router, this one can change the address of one device, and the rest can be ok. If you have something like this on your only device, download the lua files for the given module from github again (e.g. F-16C.lua) Maybe something with the file happened. Have you recently updated the entire script? Have you recently added any other script to DCS? The last version is 513 and since then nothing has changed in the application.

image display from DCS to MFD is not implemented, it's a bit longer topic and needs more time

F-14 DISPLAYS panel ready now Mirage 2000 with INS & PCA

Strange, I need to review the DCS files again

Try to download packed ZIP from this: https://github.com/pet333r/pw-dev_script/releases And change the script from this ZIP file to copy new files without replacing. Have you updated the Config.lua file?

Something must be wrong because you are the second person who does not work. I tested an hour ago on several devices, just to be sure on exactly the same application file and same script files. It's weird because I doubt there are different versions of Jf-17

I checked the email you recently sent me, the IP address of your tablet was 192.168.1.65 at the time And you must enter the same address in the Config.lua file, find it: ExportScript.Config.Host = "192.168.1.3" And change 192.168.1.3 to 192.168.1.65 And that's it

The upgrade script does not update the Config.lua file so that you do not have to change the IP addresses it contains every time, download the Config.lua file manually and change the IP addresses to those you had In the Config.lua file you must provide the IP address of your Android device

News continued;-)

I want to change it, I was also thinking about buttons left / right to change channels

You have all "update" files?, there should be 3. As for this 8, I did not change in this update because I was working on a completely new look of the panels, example in the previous post[emoji3]

The panels look refreshed at the final stage:smilewink:

No problem, I'm glad I could help[emoji3]

Script sends data from DCS on port 5160 (default) and receive from Android on 25070 (default). In Config.lua you provide the IP address of the device / tablet to which the data is sent. However, in the application on the tablet you provide the PC address to which all clicks will be sent, etc. Also check these default ports in the config.lua file and in the application settings

In Hornet nothing has been changed lately, and the only thing that could cause such behavior is the wrong tablet IP address set in Config.lua because I doubt your firewall will block outgoing connections. Have you updated another script recently? Deactivate the others and check

Reorganize entries in Export.lua, give an entry to my script higher than Tacview and SRS, on github in readme below is an example of how it should look The application receives / sends data on separate ports