737-SimGuy Posted August 19, 2020 Report Share Posted August 19, 2020 Hi John, From what I can tell so far apps will not connect to FSUIPC when run on the same machine as FSUIPC7. They do connect fine to WideFS on remote computers.I tried running WideClient on the MFS machine but of course it says "The same program or class is already running [FS98MAIN]", as expected. This is a critical feature for me as my control loading software depends on it and I have no way to fly without it... James Link to comment Share on other sites More sharing options...
John Dowson Posted August 19, 2020 Report Share Posted August 19, 2020 Hi James, What apps? Do these apps report any error? Maybe they need updating for the new version? I can't really help without further information. You should also talk to the app developer to see if they have an update planned. John Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 Hi John, I am the developer in this case, but my BFF control loading software does not connect either. I am using Pauls FSUIPC_Client DLL and have changed nothing. It connects via wide client no problem. Is there something specific that needs to be changed here? I don't recall anything in the release notes about this. James Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 This from Ian at BFF: "If I recall correctly my software looks first for "UIPCMAIN" with a FindWindowEx call as this is what usually exists with a local FSUIPC active. If it doesn't find it it then looks for "FS98MAIN" which is what is present when WideFS is active" It is returning 0x0 James Link to comment Share on other sites More sharing options...
John Dowson Posted August 19, 2020 Report Share Posted August 19, 2020 I found this under MSFS topic in Paul's forum: I need to tell the DLL about MSFS2020. I'll have a new version out later today. It seems Paul's client needs updating to recognize the new FS version in offset 0x3308 (which is 13) or 0x3124 (now 110). John Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 Ahhh, ok. Thank you. I'll keep an eye out... James Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 John, BFF doesn't use the client DLL, has the window name changed? James Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 19, 2020 Report Share Posted August 19, 2020 8 minutes ago, 737-SimGuy said: BFF doesn't use the client DLL, has the window name changed? FSUIPC provides client window class-names FS98MAIN and UIPCMAIN. The class-name for MSFS itself is different. All existing FSUIPC applications should be able to connect in exactly the same way as before, at least when MSFS is up and running. I don't think FSUIPC is really active util then, though you can make assignments and do some calibration beforehand. If not, John would need full details. Pete Link to comment Share on other sites More sharing options...
John Dowson Posted August 19, 2020 Report Share Posted August 19, 2020 12 minutes ago, 737-SimGuy said: has the window name changed? The main window in FSUIPC7 is now FS98MAIN, and, as Pete says, it also creates UIPCMAIN (and UIPCINTERNAL) for messages. The window/class name for MSFS is now AceApp (in P3D/FSX was FS98MAIN). John Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 15 minutes ago, Pete Dowson said: FSUIPC provides client window class-names FS98MAIN and UIPCMAIN. The class-name for MSFS itself is different. All existing FSUIPC applications should be able to connect in exactly the same way as before. If not, John would need full details. Pete Well, that is the issue, these programs have NOT been changed, but they do not find FSUIPC7 when run on the same machine. So I am not sure what details you would need. My apps use Paul's FSUIPC Client DLL and the BFF control loader uses FindWindowEx unchanged from his previous working versions. James Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 9 minutes ago, John Dowson said: The main window in FSUIPC7 is now FS98MAIN, and, as Pete says, it also creates UIPCMAIN (and UIPCINTERNAL) for messages. The window/class name for MSFS is now AceApp (in P3D/FSX was FS98MAIN). John Ok, so it HAS changed. I will forward this on... Thank you, James Link to comment Share on other sites More sharing options...
John Dowson Posted August 19, 2020 Report Share Posted August 19, 2020 1 minute ago, 737-SimGuy said: My apps use Paul's FSUIPC Client DLL As I said previously, this needs to be updated to support FSUIPC7. Are you sure that isn't the issue? 1 minute ago, 737-SimGuy said: BFF control loader uses FindWindowEx unchanged from his previous working versions. Are you running both at the same privilege level? If not, please try that. Otherwise I don't understand why it can't find the FS98MAIN window - its there! John Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 Just now, John Dowson said: As I said previously, this needs to be updated to support FSUIPC7. Are you sure that isn't the issue? Are you running both at the same privilege level? If not, please try that. Otherwise I don't understand why it can't find the FS98MAIN window - its there! John Ok thank you, working on it... James Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 9 minutes ago, John Dowson said: Are you running both at the same privilege level? If not, please try that. Otherwise I don't understand why it can't find the FS98MAIN window - its there! John Yes, both as Admin. Am I the only one who runs anything requiring FSUIPC on the MSFS machine?? "All existing FSUIPC applications should be able to connect in exactly the same way as before. Pete" This is not the case, sorry to say. I have forwarded the info to BFF folks and I will await Pauls new DLL for my applications... James Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 Ok, more to the story. When I checked that all applications were run at the same Admin level I only checked using the BFF application and it didn't fix the issue, however when I just did that with MY applications that use FSUIPC Client DLL it worked! So John and Pete you were of course both correct and it is a separate issue with the BFF loader application! Any application using FSUIPC7 on the MSFS computer require the same privileges, confirmed! Apologies for the distraction. I did not troubleshoot effectively. James Link to comment Share on other sites More sharing options...
John Dowson Posted August 19, 2020 Report Share Posted August 19, 2020 Ok, glad that's now cleared-up. Thanks for reporting back. John Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 19, 2020 Report Share Posted August 19, 2020 2 hours ago, 737-SimGuy said: Ok, so it HAS changed. I will forward this on... No, not changed, except that previously the name FS98MAIN belonged to FS/P3D. FSUIPC just hooked into it. That's not done from an external EXE, and with the name FS98MAIN being critical, FSUIPC creates it instead. Seen from outside, by an FSUIPC application, there's no change at all. Pete Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 19, 2020 Author Report Share Posted August 19, 2020 1 minute ago, Pete Dowson said: No, not changed, except that previously the name FS98MAIN belonged to FS/P3D. FSUIPC just hooked into it. That's not done from an external EXE, and with the name FS98MAIN being critical, FSUIPC creates it instead. Seen from outside, by an FSUIPC application, there's no change at all. Pete Right yes. It appears the issue with the BFF application is that he is using the presence of FS98MAIN as indication of FS running, and some other way to determine FSUIPC was running. He has all the info now and at some point I hope to hear back from him. Thank you, James Link to comment Share on other sites More sharing options...
GHD Posted August 20, 2020 Report Share Posted August 20, 2020 It works fine with my simple legacy programs 😀 1 Link to comment Share on other sites More sharing options...
737-SimGuy Posted August 20, 2020 Author Report Share Posted August 20, 2020 John and Pete, Just an update: Ian at BFF has re-factored his connection technique and now his control loader application is connecting without issue. Thank you for the info needed to correct this. James Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now