Jump to content
The simFlight Network Forums

GSalden

Members
  • Posts

    170
  • Joined

  • Last visited

Everything posted by GSalden

  1. 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.
  2. 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.
  3. 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,
  4. 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.
  5. 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
  6. 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.
  7. 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.
  8. 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.
  9. Fair enough. The issue has been reported to Asobo.
  10. 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
  11. Thank you John. So the C\Fsuipc folder is where the LUA files go. That I will take as a starting point.
  12. 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
  13. 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
  14. Many thanks for explaining what is going on. I also found other threads about it and will try the workaround too. Is it correct that I then do not see AI traffic on my PFD ? If that is so then it is no problem as finishing a flight is more important. Surely I will make a Zendesk ticket . Regards, Gerard Additional : Unfortunately MSFS crashed again with the workaround applied, just by standing on the tarmac , but with Prosim running. I now only see 1 error Simconnect message instead of multiple, so there is progression. 39359 Aircraft loaded: running normally now ... 39547 User Aircraft ID not supplied -- trying default 40547 Aircraft="Prosim_B738 2021a KLM" 40547 System time = 29/01/2021 07:59:23, Simulator time = 05:59:21 (06:59Z) 272750 -------------------- Starting everything now ---------------------- 272750 Starting WideServer now ... 275922 \\SERVER\Users\gsald\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 1884906 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 1888187 MSFS no longer running - exiting 1888187 === Hot key unregistered 1888187 === Stop called ... 1888203 === Closing external processes we started ...
  15. Hello John,Pete, I am having CTD’s when using MSFS with my Prosim cockpit . Flying half an hour to do some sightseeing at low altitude is no problem. Making longer flights always result in a crash. This time after 45 minutes. Prosim V3.03b13 / FSUIPC mode (otherwuse blanc speed window in CpFlight MCP Pro 1 ) First this : Windows Apps log : FlightSimulator.exe 0.0.0.0 5fda32ba FlightSimulator.exe 0.0.0.0 5fda32ba c00000fd 00000000009805de 1f10 01d6f23031ca2ce3 C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 451e640f-9a3b-46d3-91d0-23adea41d9bc Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe App Then this : Windows Apps log : FSUIPC7.exe 7.0.0.4 5ff89538 ntdll.dll 10.0.19041.662 27bfa5f0 c0000005 0000000000045f86 ec0 01d6f2306e1250b9 C:\FSUIPC7\FSUIPC7.exe C:\WINDOWS\SYSTEM32\ntdll.dll 4bc5cda9-42c6-43f7-b991-d34af7b228df Then this : FSUIPC log : 21016 MSFS version = 11.0.282174.999 21016 Initialising SimConnect data requests now 26828 \\SERVER\Users\gsald\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\prosim-b738\SimObjects\Airplanes\prosim_b738\aircraft.CFG 26875 flights\other\MainMenu.FLT 28312 Aircraft loaded: running normally now ... 29156 User Aircraft ID not supplied -- trying default 30156 System time = 24/01/2021 10:08:37, Simulator time = 08:08:34 (09:08Z) 30172 Aircraft="Prosim_B738 2021a KLM" 690406 -------------------- Starting everything now ---------------------- 690406 Starting WideServer now ... 692484 \\SERVER\Users\gsald\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 1552812 **** Restarting traffic scanning due to non-reception **** 4377344 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 4377344 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 4377437 TransmitClientEvent failed! (Event=65706, Param=-2964, nGroup=0, fSame=0 4377547 TransmitClientEvent failed! (Event=65706, Param=-2959, nGroup=0, fSame=0 4377641 TransmitClientEvent failed! (Event=65706, Param=-2954, nGroup=0, fSame=0 4377750 TransmitClientEvent failed! (Event=65706, Param=-2949, nGroup=0, fSame=0 4377844 TransmitClientEvent failed! (Event=65706, Param=-2944, nGroup=0, fSame=0 4377844 **** Too many TransmitClientEvent errors received! Re-connecting now ... **** 4378500 MSFS no longer running - exiting I have a RTX 3090 and have it running at default speeds with only a more acxtive fan profile for maxed cooling. Driver 461.09. Happened too with the driver before that one. Swapfile = automatic ( perhaps on fixed values ? ) CPU 7940X @ 4.7 Ghz since 3 years / 32 Gb 3600 / 2 Tb M2 (MSFS + P3D) + 1 Tb M2 (P3D) Displays 4K @ 30 hertz. One wide view spread over 2 displays (4096x2160). Already lowered settings so 38-50 fps is no problem to sustain. Set FPS to 30 inside MSFS. Also emptied Rolling Cache to be sure that there wasn't faulty data in it. Is this a Simconnect issue from what I see in the FSUIPC log ? Thanks and best regards, Gerard
  16. Hello Pete, John, At this moment I have both P3DV4 and V5 installed. With my Prosim setup I use WideFS too. WideFs server has been installed into v4. I bought FSUIPC 6. If I install that one will it install in both sims ? And how do I get WideFS in V5 too while it also exists in V4 ? While building up V5 I also would like to make flights with V4. Thanks and best regards, Gerard
  17. Finally I managed to get it back to work as it should: 1 deleted the p3d.cfg file 2 deleted the Saved flight Now the values go up till 16383 instead of 16381 like before. Watching the offsets values onscreen helped a lot. Many thanks Pete ! BTW : a little off topic . My 2080Ti card performs the same as my former 2x 1080Ti card. But less power consumption and no more SLI staying in Idle mode too long when entering heavy scenery....
  18. Hi Pete, Since 12 days I am having this Landing Gear issue with Prosimand it has not been solved up to know. Humberto and Martin also do not know what is going on. Since a W10 and P3Dv4.3 reinstall 6 weeks ago everything was working fine and for weeks I have made very nice flights. Then from 4th november up to now I am having a landing gear issue with my Prosim aircraft. At approach lever down , the gear extracts but I am getting 3 red lights and the warning horn. Prosim support has tried to help me : - un-and reinstall the aircraft model - un- and reinstall FSUIPC - disabled all addons  - tried earlier Prosim versions ( clean install ) The default aircraft do not have this issue. Using the FSUIPC LG offsets in the Fs Window I can see that the gear down command is being sent/received by P3D. The only thing I remarked : Gear up = 0 / Nose gear up = 0 / Left gear up = 0 / Right gear up = 0 Gear down on the ground. = all 4 offsets : 16383. But when extracting the gear while flying the Gear Down offset goes to 16383 but the nose/legt/right offsets to 16381, so not 16383. As Prosim receives the gear down command from my hardware and sents the command towards P3Dv4 and FSUIPC , Prosim support think that there is something wrong with P3Dv4. But my default planes do not have the issue. As I am running out of options do the 3x 16381 values point to an issue ?  Thanks, Gerard
  19. Many thanks for the help Pete. I will try it . regards, Gerard
  20. Hi Pete, Since 2 weeks I am having an issue with my Landing Gear : when pushing the LG lever down I am hear the gear dropping and the sound of the turbulence. However, I am only getting 3 red lights and at approach the LG warning sound. When putting ProsimPanel onscreen I also see the lever down and 3 red lights. The hardware is the CpFlight MipBoard. Humberto asked me to check what offsets are used when pushing the gear handle down and advised me to use the Fs Window to FSUIPC offsets onscreen in order to check what offset is being used with Gear Down. I have never done this so can you advise me how to do this ? Thanks and best regards, Gerard
  21. Got it working with your help : handle, error = ext.shell("C:\\DOS\\StartDCS.bat", "EXT_MIN", "EXT_CLOSE") ipc.log("ext.shell returned error = " .. error) Now it is working perfectly. Many thanks Pete for your patience. If it is Ok with you I can put the LUA-batch combo in the Users section as " Starting programs ( exe ) with a yoke button through LUA " Regards, Gerard  
  22. Hi Pete, Thank you for your great support. As I have started looking into LUA yesterday for the first time I am making errors. The only thing I want is a LUA that starts a batch file. I have made a new folder in C called DOS with the batchfile in it. Just to be sure I will not have any rights issues in the program files (x86) folder. You are right about computers . That I am finding out right now. I will try again later today.. regards, Gerard
  23. I have tried these : ext.shell("C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX\StartDCS.bat", "EXT_MIN") ext.shell("C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX\StartDCS.bat") handle, error = ext.shell("C:\\DOS\\StartDCS.bat", EXT_MIN, EXT_CLOSE) handle, error = ext.shell("C:\\DOS\\StartDCS.bat") Unfortunately none of them are working. I even tried after reinstalling DCS directly into C , so above program files (x86).. Regards, Gerard
  24. You are right that didn't work. I also tried : ext.runif("C:\Program Files9 x86)\FSPS\Dolby Cockpit Sounds FSX\StartDCS.bat", "EXT_MIN") whicg didn't work either. ********* LUA: "StartDCS" Log [from FSUIPC version 5.103e] ********* 684766 System time = 21/09/2017 14:55:17, Simulator time = 09:21:59 (07:21Z) 684766 *** LUA Error: cannot open D:\Program Files\Lockheed Martin\Prepar3D v4\Modules\ipcDebug.lua: No such file or directory 684766 LUA: beginning "D:\Program Files\Lockheed Martin\Prepar3D v4\Modules\StartDCS.lua" 684766 LUA: ...les\Lockheed Martin\Prepar3D v4\Modules\StartDCS.lua:1 684766 LUA: Global: ipcPARAM = 0 684797 >>> Thread forced exit (ipc.exit or os.exit) <<< So it should more be like : ext.shell("C:\Program Files9 x86)\FSPS\Dolby Cockpit Sounds FSX\StartDCS.bat", "EXT_MIN") .... ? Regards, Gerard
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.