fredkura

I just wanted to report this.... Yesterday I attempted to update FSUIPC5 to 5.124 from an earlier version using the .exe installer. I received a message that "This app is not compatible with your PC. Contact software supplier for a version that is". I am using a WideView arrangement (4 computers), and this was the same message on each. I have WIN 10 version 1709 loaded on each. The issue might have to do with the most recent updates KB4088785/KB4088776 dated 27Mar. Since this is a dedicated system I am using no security software other than the native Defender. I was able to get around this by transferring the DLL from another computer other then these recently updated. Fred K

Pete - That is great news! Many thanks! And I absolutely agree with the others here that you should charge a fee for the new registration.....even to the extent that there are no "free" basic versions. You do far more than your fair share on this and should be commensurately rewarded. But sooner than later someone else is going to need to step up to the plate on this....We cannot rely on Pete forever. Ultimately FSUIPC should be integral with the P3D SDK. I have to assume it is in LM's best interests as well. LM would be smart to work a deal with Pete to do that. Fred K

Just an update..... I now see the text in the LUA window on the client OK, however there appears to be some confusion going on. When I bring up the ProATCx window for the first time it appears on both the server and the client as it should (I think) and the first few keystroke commands work as they should. However after that when a new keystroke window is brought up it appears on the server screen but does not update on the client screen, the old screen text remains.........after a few more attempts of bringing up the new screen ProATCx then crashes. Also, the status communication text (top of P3D window) appears initially on the client but then only intermitently thereafter. It does not appear on the server. So I am going to try to study the LUA script to see what can be adjusted there or simplified. For example, in my case I do not need to have menus disappear on the server screen since I never see that anyhow and I do not need to see the top status message lines on the client since I can comprehend all that through the instructions on my headphones. I only need one window on the client. Perhaps that will help? ProATCx works fine of course without the LUA running. The LUA script appears to be confusing it. My question however is whether there are any known communications issues like this within the current scheme of things. I do not want to spin the wheels here needlessly of course. Otherwise I will pursue trying to figure it all out. Thanks again, Fred

Hi Pete I found the issue with the LUA plugin. The LUA file template I was using was taken from the LUA Library Reference document. I now see there is a more comprehensive one listed in the "Example LUA Plugins" file. That one works. So sorry to have bothered you on that part. If you want me to test anything with the most recent P3Dv3.4 I can load such here and send the log file on to you. Thanks, Fred

Hi Pete Sorry for the delay in getting this to you. I made the change in the FSUIPC ini to add the extra logging instructions. Associated log files for both 4.459 and 4.462 are attached. Also attached is my LUA file installed on the client...just to be sure nothing is amiss there. Also attached is my FSUIP ini file. Again...my problem is that the LUA window is present on the client but is not populated with text when such is displayed by ProATCx on the server monitor. Fred FSUIPC4 4959.log FSUIPC4 4962.log ProATCx.lua FSUIPC4.ini

Pete Okay....I will get to this tomorrow as soon as I can and will send the info to you. Thanks, Fred

Hi Pete - Further to the above....I updated both FSUIPC (4.962) and WideClient (6.9993) to the current versions. Now FDS SimAvionics flat-out crashes P3Dv3.4 which I guess is the expectation you sort of alluded to above. Also, text still does not appear in the LUA window. So I have retreated back to FSUIPC 4.959 which does not cause a P3D crash but of course does the recurring 3400 message logging. I have queried FDS about it. Regards, Fred

"SimA" is SimAvionics....Flight Deck Solutions' avionics software suite. So there really is no way I can turn that off being that it is the guts of the system. I did peruse this forum about the 3400 logging block message and it appears that there is a least one reference to it related to FDS hardware about a year ago. It is not clear if such was resolved. I am using the latest P3Dv3.4 (as of 2 weeks ago). I will obediently update to the latest FSUIPC version. Many thanks, Fred K

What is loaded is 4.958. And yes...I am also curious about that repeating "Log Options" message. What exactly is that? After some investigation here I can very confidently say it is induced by SimA. With SimA "on" the message keeps repeating....turn SimA "off" and the message recurrence stops. That is with no other add-ons running. ): So that is a second item that I need to find a resolution for ): I have SimA running remotely on a client. Previously I had SimA running via UDP, but with the latest SimA release (1.70) I had to switch to TCP due to network communication problems with UDP. So maybe it has to do with something there. I have had no problems with P3D crashing, but it is a little disconcerting that all that is going....it cannot be good for things. Any ideas on that? I am going to touch base with Mark on it of course. In the meanwhile I am still scratching my head on the menu issue. I tried without SimA running and it still did not work, so it would appear that they are unrelated issues. Thanks, Fred K

Hi Pete Thanks for the speedy response... "InterceptTextMenu" was not in the General section of the FSUIPC ini so I had originally added and enabled it. Checking today however I see that entry has disappeared. So I re-added it....and it disappeared again. I do notice that there is an entry "NewInterceptTextMenu" that was either there originally and I had not noticed it or was created when I added "InterceptTextMenu". In any event it was disabled, so I enabled it "NewInterceptTextMenu=yes". But I still do not see any text in the WideClient lua message window. So I am thinking that maybe it has something to do with SimConnect. I have tried adding SimConnect 61259 and 61242 in that regard but problem is still not resolved. The FSUIPC log shows the SimConnect menu intercept as installed and shows SimConnect running in the native P3D version..... 1453 LogOptions=00000000 00000001 1453 ------------------------------------------------------------------- 1453 ------ Setting the hooks and direct calls into the simulator ------ 1453 --- CONTROLS timer memory location obtained ok 1453 --- SIM1 Frictions access gained 1453 --- FS Controls Table located ok 1453 --- Installed Mouse Macro hooks ok. 1453 --- Wind smoothing fix is installed 1453 --- SimConnect intercept for texts and menus installed ok 1453 --- All links okay (except older global weather setting method) 1453 ------------------------------------------------------------------- 1453 SimConnect_Open succeeded: waiting to check version okay 1453 Trying to use SimConnect Prepar3D 1453 Opened separate AI Traffic client okay 218812 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0) 218812 Initialising SimConnect data requests now 218812 FSUIPC Menu entry added 218937 \\DESKTOP-NQMQ5K4\Prepar3D v3 Files\KRIC B9.fxml 218937 \\DESKTOP-NQMQ5K4\P3D\SimObjects\Airplanes\Sim-Avionics 737-800 Winglets\B737-800.air 219984 Weather Mode now = Global 219984 Weather Mode now = Custom 270953 User Aircraft ID 2 supplied, now being used 271687 System time = 09/02/2017 11:49:29, Simulator time = 11:48:38 (16:48Z) 271687 Aircraft="Sim-Avionics 737-800" 272672 Starting everything now ... 273859 Advanced Weather Interface Enabled 288297 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 288547 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 288875 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 289109 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 289422 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 289750 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 290047 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 290484 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 290719 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 291062 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 291359 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 291594 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 292000 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 292234 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 292469 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 292922 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 293047 ### Blocked: attempt made to change LogOptions via 3400, data 0x0000 293359 ### Blocked: attempt made

I have a cockpit setup where my main P3D monitor sits outside the cockpit. I would like to get the text menu display for ProATCx communications to appear on a WideClient display located within the cockpit. I have setup the "TextMenu.lua" example for Radar Contact provided in the FSUIPC pdf. The good news is that the text window does appear on the WideClient monitor and is populated with text if I run RC. However when I run ProATCx the window remains empty. So...is there something I need to do specifically to reference access to the ProATCx text? I am under the impression that the offset defined in the example Lua is for the P3D text window which should be universal for any app add-on I would think, but perhaps I am wrong on that. Or could this be an issue with SimConnect? Or something else? Thanks, Fred K