Pete Dowson

I think I can answer that for John. The static library provided in the latest SDK is for native code programs. I'm afraid it cannot be used with Managed programs. Pete

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

Why? Sorry, but there's no way FSUIPC, with no settings made by you, does anything which can be related to which aircraft is loaded. I'm afraid you supply no information which can be used to help. It sounds more like you have removed or corrupted something you shouldn't have. Why, exactly, do you think this is anything to do with FSUIPC? BTW when updating ot new versions of FSUIPC there's NEVER any need whatsoever to delete anything beforehand. Pete

Good! Thanks for telling me. Pete

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

Up till now every 64-bit SimConnect application would need the DLL in the same folder. It might work okay by putting it in C:\Windows or one if the folders within. But I think this not worthwhile as things should change. The next release of FSUIPC7-Beta will not need access to the DLL as MS have now released the static library which can be compiled into our program. I expect this change to be taken up by any other 64-bit programs using SimConnect. 32-bit programs like LittleNavMap can quite happily use the old FSX SimConnect installs. Pete

Can you check in the FSUIPC menu that WideFS is enabled? There will be a WideServer.LOG in the FSUIPC7 folder, and a WideClient.LOG in the same folder as WideClient. Please show those. Make sure you have no firewall blocking access. But no network access to folders is needed. Doesn't matter -- just make sure they both have the same privilege level. Pete

As John says, for PFC devices with normal Joystick USB configurations you don't need any special software. But that's only applicable to devices recognised by Windows as joysticks. MSFS should recognise them too if so. However, I think the PFC Cirrus 2 Pro is a non-Joystick type of HID device. If so you'd need FSUIPC7.exe + PFChid64.dll. Were you using this device previously with FSX or P3D? If so then it's the same method. Pete

Don't you see an extra entry in the FSUIPC menu for PFC? I just tested again, and the menu bar shows "AddOns" when the PFCcom64.dll driver is started, and its PFC entry is within that. Pete

It might be related to the big problems caused by the release version SimConnect being extremely slow (causing stutters for many). This maybe also causing intermittent disconnects from FSUIPC which would interfere with frequently occurring events (like flight control ones) and so also giving such failures. You need to supply the Log file -- look in the same folder as FSUIPC7.EXE and find FSUIPC7.LOG. Then please ZIP it and attach it to a reply here. Unfortunately both John and i have been experiencing problems downloading the Release version of MSFS so may not be up and running again with it for a day or two, so our own testing with it may be delayed. Pete

No, it means MSFS didn't tell FSUIPC about it. Which means it isn't in the published Event list (which is pretty much the same as FSX's, give or take a few). So either they don't work like those "KEY_EVENTS", or they do but because we don't know about them we cannot ask for them to be monitored (as we do for all the others). Pete

Well, just check what works and what doesn't. Hopefully nothing doesn't work -- but not having been able to test every single SimConnect function and Event we are not sure. you can help us tick them off. Short lists of "good, works" and "bad, doesn't work" -- with notes as to in what way. Thanks. Pete

FSUIPC will have its own menu bar. It'll be in there. You can get FSUIPC to show itself via ALT+F (default assignment, can be changed). Pete

Thank you! Pete

As stated earlier, and documented in the place you download latest versions (Download Links above or on FSUIPC.com), the latest version of the PFCcom64.dll module has been updated for MSFS. The rest is dependent upon the facilities offered by MSFS SimConnect, which are still incomplete. We think much will work, but there will still be areas where the facilities in SimConnect are incomplete or simply not yet working. In order to progress this with Microsoft & ASOBO, we need feedback. So, if you intend to get MSFS 2020 at any time, don't wait. The sooner you try things and report back then sooner it'll all be fully working. Pete

As already explained just above, if you had read the thread, it is a problem with SimConnect affecting ALL SimConnect client programs. It's a bug added to MSFS since the last Beta release (where performance was excellent). Pete

Did you enable Developer mode and download the SDK installer, as instructed in that thread I linked to explaining this? You install the SDK where you like -- searching for something you haven't even installed is futile. Pete

Please try this version of WideClient. Only change is that it tries to trap the error and record where it as at the time. You can change back to Log=Errors+ so the log isn't large. WideClient716.zip I'm not expecting miracles. Most of what WideClient does is handle the network transfers and that is asynchronous (i.e. windows network functions are busy doing things whilst WideClient carries on). I suspect a bug in one of the Windows updates to the networking functions, but being asynchronous to what WideClient is doing I might never find any fix -- except possibly further Windows updates or disabling whatever recent changes they did. I say this because all of the networking parts of WideClient have remained unchanged since Windows XP days. The other parts have long been protected by trapping crashes and logging them -- only the extensive networking side was free of that. Not sure why, but that's what I've changed in the attached version. Yours is the only report of this problem at present so there's no way of narrowing it down to a "common factor". I use WideClient on an 8 PC network (I use ProSim, not SimAvionics, so WideClient usage is less, but used heavily for my other applications. Pete

I've moved your question to the proper subforum for FSUIPC7 support. Scan down a little from here and you will see a thread giving the answer!

Well, they should be able to -- the last Beta developers received was fine -- no noticeable degradation with SimConnect applications running. I don't know why they go and release a version none of the Developers or beta testers have seen beforehand! Very disappointing. 😞 Pete

Unfortunately that reveals nothing to identify anything different going on at the end compared to what is being done all the way through. Tomorrow I will look to see where I can best add more more logging (or rather alternative logging) to try to pin down an area in the program, before then trying to go into finer detail. i'm afraid this will take several iterations. I think this will still point to a bug in Windows introduced by recent updates. But maybe it will suggest a workaround until the next batch of updates fixes this bug and adds different ones. Pete

Try using ZIP! A text file will Zip up very small. 5.6Mb is nothing. Pete

I asked because those offsets aren’t in use or allocated. It is Log=DebugAll Pete

Okay. But of course none of the sceneries you may have installed via the Add-Ons XML method will feature in the generated files. Yes. Try is as intended (run as Administrator, mind) to see if fixing the Scenery.cfg glitch helped. If not i'll have to refer to Lorby-Si. AddOnOrganise is a separate program altogether, nothing to do with MakeRunways. Running it is just a test to see if whatever is affecting the utility MakeRunways uses also affected the AddOnOrganizer, which is doing the same sort of scanning. Pete

If you refer to the Updated Modules thread in the Download Links subforum you'll see that both PFCcom64 and PFChid64 have already been made compatible with FSUIPC7. Our FSUIPC.com website also lists MSFS2020 compatibility for those latest versions. Pete