GSalden

As a Ps user too I would love to see it working. Thanks in advance.

Thanks John. I have posted it too on the Prosim forum. This morning after restarting Prosim and FSUIPC several times, once as Admin and another time not as Admin, it suddenly worked. Restarting Prosim as a test and it did not work again as Admin.

Hi John, After shutting down the pc’s and later restarting them and MSFS with Prosim and SIOC again it did not work . Sometimes after shutting everything down and restarting out of a sudden ( 1 out of 9 times ) it suddenly works. All programs need to run as Admin. I found out that I have to run Prosim not as Admin to see all external lights working. When running Prosim as Admin the Taxi Light and RW TO lLights do not work in MSFS. But FSUIPC only sees the switches moving when Prosim is running as Admin ( the occasional time it suddenly works )…. Otherwise nothing on the console window … Reinstalled Prosim, FSUIPC, SIOC and the Prosim Flight Model.

Hi John, After a lot of testing and trial and error I finally have the lights working again on the Left View pc. What I did : - Uninstalled FSUIPC 7.3.11 - Reinstalled FSUIPC 7.3.19 - Downgraded Prosim from 3.25b9 to the official 3.24.2 Since a couple of weeks the external lights on the Server only worked with MSFS running as Admin but Prosim not as Admin. Before I always ran Prosim as Admin too. When enableing the Write/LUA/Lua separately Logs and looking at the Console nothing happened and the window stayed empty. After doing the above I was able to run Prosim again as Admin and have working external lights.Then I did the above test again and all data appeared on the Console window. Then I started the Left View Client and the external lights worked right away. They only react with a 5 sec delay like Sky Blue Flyer stated. Is there anything that can be tried to eliminate the delay ? Thank you again for your great help John. You pointing out to use the Console helped a lot,

Hi John, FSUIPC is used on both server as client. The server sents the lights info ( on / off ) to the client. The issue on my W11 setup exists also when WidevieW is not running. And WidevieW uses Simconnect. I will try your suggestions to see if the server is sending data from the external lights to the client and if the client is receiving any data.

The package are the files needed to get the external lights to work ( see DL link ) , like LUA scripts. I am using the same FSUIPC version on server and client pc’s. All instruments work using Wideserver/client and WidevieW also works correctly over the network. All pc’s are using the same workgroup. Sky Blue Flyer will probably post the requested files tomorrow. Thank you for your help. regards, Gerard

WidevieW is a program where an outside view client is slewed by a server so the outside views connect. The package was made to have external lights function over a network. So when I press the runway take off lights light on my Overhead I can see the light on the server and the client. The package works independently from WidevieW but they are both used. WidevieW for the outside views position and the package for the external lights on the clients aircraft. In February it all worked for all of us. Than several MSFS updates and FSUIPC updates later it stopped working. As we do not make nightlights each week it is impossible to pinpoint exactly when it stopped working. Sky Blue Flyer found out that going back from FSUIPC 7.3.19 to 7.3.11 it started working again on his W10 pc’s with current MSFS version. People with W10 have it working up to FSUIPC 7.3.11. Myself I had it working on my W11 server and W10 client with FSUIPC 7.3.11. After upgrading the client to W11 it stopped working. Wideserver / Wideclient is not needed when Prosim and MSFS are installed on the same pc. However, I do have Wideserver installed on my Server and Wideclient on my Client pc’s to have working hardware gauges with SIOC ( OpenCockpits hardware ). Imho finding out how it will work again with Sky Blue Flyers setup and a current FSUIPC is our main goal. After that why it works on W10 and not on W11. Thank you for your help.

Hi John, In addition to what Sky Blue Flyer wrote : it worked on my system with the version that he mentioned till I upgraded my Left View client to W11 (coming from W10) . My Server already was W11. Even with the Firewall disabled, Defender disabled and ports open on both pc’s, it will not work again. Doing the LVAR test on the client ( see Readme file ) shows that the external lights go On/Off. Here a link to the complete set with LUA files too incl Readme : https://wetransfer.com/downloads/d3860ea6e14e5c186fd81bc546705c6720230423081252/1b10defee308e52fb8e46bf797ab18bd20230423081330/893bef?trk=TRN_TDL_01&utm_campaign=TRN_TDL_01&utm_medium=email&utm_source=sendgrid Sky Blue Flyer can show the requested files when it is working and when not.

Goodevening, Is it possible to DL v 7.3.11 ? Several Prosim users use a WidevieW setup and with FSUIPC files ( lua , Lvar etc ) to have the external lights working over the network. Recently it did not work anymore and one of the users found out that with FSUIPC 7.3.11 it is working again and with higher version not. Thanks in advance.

Seeing the same using Prosim

Fair enough. The issue has been reported to Asobo.

Probably caused by the MSFS SU10 beta, but with Prosim in FSUIPC mode I have no toebrakes or braking from the reverse thrust. The temporary solution in to use Simconnect mode but then my Cockpitsonic motorized TQ levers start to jitter . Is this known to you ? Thanks, Gerard

Thank you John. So the C\Fsuipc folder is where the LUA files go. That I will take as a starting point.

Hello John,Pete, This is not entirely FSUIPC related but perhaps you can give me a suggestion where to start. I am trying to get the Landing Lights, Runway Turn Off Lights and Taxiway Light to work on my left view pc. The PC is client in a WidevieW setup. The server is my front view pc and the client my left view pc In P3Dv4/5 I have the lights working and now I am hoping to get them to work too in MSFS. In P3D I only had to add files to the Modules folder and it I assigned OVH switches to commands. Those commands are still assigned in Prosim. As I did not find a Modules folder I was wondering how to continue. I have some LUA files but also dll files and do not know where to put them … Any idea would be ver welcome.Thank you in advance. Here the topic I made at the Prosim forum with screenshots : https://forum.prosim-ar.com/viewtopic.php?f=142&t=23953

Hi John, Humberto from Prosim wrote me that these types of CTD are already under investigation. He stated that it is the result of doing something to an unfinished product, when the lack of documentation is the main issue. Prosim for MSFS is a kind of “preview” and any update from Asobo might even break the current status. Your suggestion to disable Live Traffic and AI Traffic might help, so for flying from A to B it is no problem. If I want AI all over the place I can switch to P3D. regards, Gerard