pet333r

Maybe your router assigned different IP addresses to devices? Did you check?

Let us understand each other well. You have the script installed in: C:\user\SRPC\Saved Games\DCS\Scripts ?? because it must be installed there

Yes! All scripts must be installed in this location (C:\user\SRPC\Saved Games\DCS) not to the folder where DCS World is installed

The image is not yet displayed on the MFCD. So far, it's a better alternative to the Thrustmaster Cougar (with the right amount of buttons for the JF-17)

You mean UFCP in landscape mode on the side with indicators? I think I could add it, you just have to think that it makes sense (so that the panel is not too small and you can click the button on smaller devices) MFCD the first time you have to click in the middle and select from the context menu which panel you want to use

The files that are on the main page of the script (not in the zip file) are files directly linked to my DCS. In such a situation, when after a few minutes you stop receiving data, some software installed on the PC must cause this (was Windows Firewall / Bitdefender turned off for a certain period of time? After which it started?). If the script receives data, it will receive it, but if it cannot send it over the network, the device will have nothing to receive. Test it with: https://www.dropbox.com/s/xowl6rv0528ucif/DCS_ScriptTester.zip?dl=0 - In Config.lua change one of your IP (example: 192.168.1.4 to 127.0.0.1) - run DCS, some mission in F-14 / F-16 / FA-18 - run DCS_ScriptTester.exe from downloaded zip - select 1 and Enter will display data from DCS to you, you should receive data even if it does not reach Android (this will mean that some software is blocking their forwarding)

25070 UDP, for incoming connections to the PC

This is what Export.lua looks good. The port is 25070 UDP. Windows firewall can block incoming connections. Turn off all the software you have for a while and check if it's ok. Are the data on the LCD displays displayed in the application?

Just a few more things to add, tests and the panel will be ready????

Didn't you change anything in the main Export.lua file after reinstallation? Check your computer's IP address, maybe after reinstalling Windows it has been assigned a different IP (compare with the one given in the DCS UFC settings). If this is ok check the firewall (in Windows) that it is not blocking ports

New version 1.0.2020.730 avaible - F-14 ACMP: added Wing Sweep and engine fire indicators - F/A-18C: added HUD panel & ALR-67 buttons - F/A-18C UFC: chaged graphics and knobs - JF-17: changed UFCP font - A-10C CDU: increased size of some buttons and lot of layout performance improvement - A-10C UFC: fixed Master Caution button and lot of layout performance improvement - AV8BNA: improved layout ... and IMPORTANT ... Update the script, the problem with the lack of some data on the displays of some users has been eliminated :-) Tested by several users and works properly for everyone:thumbup:

First, the CK-47 and the waypoints. I didn't think about what to add later, I think Master Mode panel as well. What useful else can I add?

I did quite a bit of modification a few minutes ago

Sure, more additions are planned, not only for Viper:smilewink: EHSI is Viewport the same as MFD (and that's more complicated) ... but ... I managed to "extract" some data from EHSI (and it would be even better), but I still have to "figure out" the rest

I found a bug that could cause this, download the file itself to Hornet and replace it in the script. https://github.com/pet333r/pw-dev_script/blob/master/Modules/FA-18C_hornet.lua Let me know if it helped

The problem will probably be somewhere on the device side, check the wifi, restart, once again make sure that the IP address is correct on the device. Probably some crap, it happens. Not that long ago I used to look for a solution at home why the device won't connect (2 hours of searching for a problem, it was enough to turn on the wifi:doh: )

A few more things to improve and the update will be ready. It includes a wing sweep indicator for Tomcat, a HUD panel for Hornet and ALR-67 Then I take on Viggen:smilewink:

Update folder Modules to the latest version

Why do you have 192.168.1.104/105/106/108 set in the Config.lua file when the router configuration shows the IP address .4 / .5 / .6 / .8 ??

Give something more info, what devices, what is connected to what etc. Have to read more about such networks, whether devices in them are visible "directly" or not. What the configuration looks like, maybe devices are connecting to a router other than the PC.

ExportXSD - this is an option that looks a bit ahead because thanks to this you can "separate" the data required only by DCS UFC and my other applications (currently it allows to display G / AoA value / Mach in DCS AoA Indexer). It will also be required to receive data in SimFDR http://pw-developer.com/soft_simfdr.html But for it to work, ExportScript.Config.ExportSelfData = true must be set so for your configuration: device 7 (Phone_S4-AoA) Export7SD should be true for the rest of devices with DCS UFC set to false (unnecessary data for this application will not be sent -> less data sent over the network -> less application has to process -> the device responds faster and works longer on the battery) Important: if ExportSelfData = false, then setting any of ExportXSD will have no effect (no matter if it's false or true), this data will not be sent from DCS to any device anyway. I use "device 4" to test the script and all the changes I make to see if everything is received from DCS as it should be. You can safely change its settings for any device

Some news that will be in next update: Wing Sweep indicator on ACMP panel new font specially prepared for JF-17

RWR is the same Viewport as MFD, VDI or all the rest, if I manage it, everything will work Heh, thanks:-) Update the script, I think I found a fix for the problem. It started working for me again:-)

At the moment it is an alternative to the Thrustmaster Cougar

The file for Hornet is correct, but I saw that you added a fifth device, but for this to work, you still need to change some code in another file and add the ability to send data to this device. Maybe this is why your data is not transmitted. On the other hand, you still have 127.0.0.1 on the 4th device (I'm testing the script and data transfer on this group), you can safely change this address to 192.168.0.11 It is best to download and install the entire script again and enter the IP of your devices in groups 1-4 as for ExportDisplays* you don't need to change to false for some modules if you don't have them. This is an option for people who, for example: they fly F-16 and use only ICP in landscape mode (no DED display), then DED data will not be sent from DCS (because there is no need to even display it) -> less data from DCS / less data sent via network / Android it receives and processes less data (this will make older and slower devices respond faster)