Pete Dowson

Is that the end of the Log? Have you had this working before okay? It sounds like it is stuck within the serial port functions in Windows. Unfortunately we don't have any VRInsight stuff to test with, but there are others here who do and I hope we hear from them. Are you using LINDA at all? That's the main add-on we had similar reports on before, but i don't know if that's now used for VRI stuff. Pete

I see you posted in the wrong place! Why in the "My Traffic" forum? This says 4.955c, not 4.975! That's the wrong version of SimConnect for your version of FSX. Try updating. Run the installers (.msi files) for the "XPack" version of SimConnect from your FSX-SE \SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK Pete

Okay. Also, according to the Logs you supplied earlier (3 messages above), the axes are all responding okay too. So can you now list exactly what isn't working for you? i'm still a bit confused about it. If you are still using your FSUIPC6.INI renamed to FSUIPC7.INI, none of your Profile files will be working as the names of the aircraft in the assorted [Profile....] section of the INI won't match any of the MSFS names. So the general assignments will apply, and there you don't have any made for the yoke, only for the rudder & brakes (not on the Cirrus), and Throttle, PItch and Mixture on the quadrant. Pete

I think John's got this working now, so I expect it will work in the next FSUIPC7-Beta release. Pete

Interesting that bit 5 comes into play. So Exit 6 (counting from 1 as the UI does) is the Cargo hold, and 4 is rear (?) catering door (starboard side). Nice to know for add-on aircraft that there may be up to 8 controlled doors. FSX and P3D were limited to 4 -- addons providing more had to invent their own controls for those (as for instance the 738 from ProSim). Of course, I'm assuming the limit would be 8, but that's just our offset size (BYTE). There may be more possible. Pete

The file you attached is empty. Can you try again please? So, this was definitely with FSUIPC7 assignments and calibrations? So this is different from what I understood. So the normal Joystick type axes are okay in P3D5 after all? It's rather strange then that they aren't seen as normal joystick axes in FSUIPC7. Another user (Thomas, in fact), told me this: The Axes can be reprogrammed via a PFC tool to be a Joystick or via Driver (PFChid) only. So it depends on what his is programmed to. Here definitely not as a Joystick controller and so I don't see it as a Joystick controller with axes and buttons but only as a HID device. I can see the axes only in FSUIPC I'm not sure I've ever encountered another user with this setting. In P3D how were the yoke axes seen? (What Joystick IDs in the Assignments tab). Don't worry remembering, just show me your FSUIPC6.INI file, please. I'm a bit concerned about the contrast between your "Most ..." and then "None of...". Can you clarify please. If "most" switches are okay, surely listing the ones which aren't wouldn't be too arduous. Trim Up and Trim Down, plus all light switches (what's that, 4?). What are the "others" please? And by not working, do you mean not seen by FSUIPC or not working in MSFS. Many of the Event controls used are broken in MSFS and we're waiting for ASOBO to fix them. With a list i can try them here. Oh, I've fixed PFChid64.dll so that it doesn't fill its log up with lines about "pfc.mcro" when you are using one! You can download it again to replace your copy. It doesn't change anything else though -- just removes the spurious logging. Pete

But Expect a release date for the patch in our August 27th update. Unfortunately all that means is that we won't know when we get the patch until August 27th, but the patch release date the then announce may well be weeks later. They're not promising fixes on the 27th. 😞 Pete

As well as needing a good FSUIPC.INI file to look at, next time you test the Cirrus with FS2020 please first change these highlit lines into your PFChid64.INI file: [Debug] Console=No LogComms=No LogData=No LogDecode=Yes LogDevices=Yes LogDeviceChanges=Yes LogToDebugger=No LogIPCwrites=Yes LogMacroNames=No LogLoopActions=No LogTxData=No LogReadCounts=No Then upload the PFChid64.log, Zipped, please. As far as I understand you, the Cirrus was working fine on P3D5 though you didn't specifically mention the use of PFChid64.DLL - you just said "I do have FSUIPC 6 working successfully in P3Dv5." Can you clarify that please? With FSUIPC7 + PFChid64 do you mean you get nothing registered from the Cirrus is FSUIPC's "Buttons & switches", nor "Axes"? Try using the FSUIPC logging facility -- log Buttons/Keys and also Axes. Then try some of the Cirrus buttons and switches, and one move each for the axes (yoke, throttle, trim). ZIP up the FSUIPC7.Log for me too -- but ONLY if you get a response ot anything in the assignments tabs. Pete

There's currently no SimConnect variable we can request for that (see the supplied spreadsheet "offsetStatus"). Interesting. It was reported as responding. I'll double-check here. Have you changed the rate? I assume there's a keypress for it, or are you writing to that offset too? Pete

Thank you. I was just going to start looking at the files, but: The "FSUIPC.ini.test.txt.7z" can't be opened (even by 7zip) -- seems to be fault. Could you try again -- but make sure, please, that it is actually "FSUIPC7.INI", the one you are using. The modified name is a little worrying (same as the name change of the Log "FSUIPC7_prev test.log". Pete

Answered in this main Forum thread:

Oh, yes. Thanks Thomas. i should have asked for those, though for the HID driver probably the more important logs are the FSUIPC ones. I'll need to leave looking at them till morning anyway. Off to bed now! Pete

I've had a quick look to see if I can find the files to scan, and figure out the order to scan them. Looks like a lot of work as it's nothing like FS9, FSX or P3D, which were all so similar, just with additional bits added to the BGLs. I think it is feasible, but I also believe the data in the BGLs may have changed too, so that's a double whammy. I'll need those database files when I finally install MSFS on my cockpit -- but that needs scenery-only views and multiple views, to span my 210 degree curved screen. I'd also need ProSim to be converted. I'd need to have it done by then, but finding the time to go further at present is just not possible. And I'm not promising anything. Pete

So you can assign and calibrate in FSUIPC7, but the result has no affect in MSFS? That's stange, as all the main axes are definitely working well. Some of the more esoteric ones aren't (like aileron trim, rudder trim, and all the slew axes). I think you need to enable Axis logging in FSUIPC7, then do a test -- just with one axis, like rudder. no need to fly, just make sure MSFS is running and ready. then ZIP up both the FSUIPC7.LOG file and your FSUIPC7.INI file. Oh, also the FSUIPC7.Joyscan.csv file if there is one. Attach the ZIPs to a reply here. Pete

If all your assignments are in Profiles then, yes, that would be a good idea. Otherwise just delete the Profiles folder and all of the Profile specific sections of the INI and start off with your generic assignments. You can provide text files here very easily -- ZIP them first, then they aren't very big. Pete

Seems, then, that the Managed DLL accesses MSFS via the unmanaged DLL. Very convoluted! At least MS has now given permission for you to include both DLLs in your packaging. Pete

Sorry, I'm a little confused by this part. "all seems to be fine" but "not connecting properly". Can you elaborate for me, please? The names of aircraft in MSFS won't be the same, so if your only assignments are to specific P3d aircraft they won't be applied in MSFS. Pete

Okay. Good detective work! Please let me know what Mark suggests. Pete

Sorry, then. I can't really help diagnose bugs in FSX. I think you do need a reinstallation. Pete

Why? Why delete anything? You lose your settings and anything else that programs may have installed there. Okay, so something has gone awry with your first system. 1. If your just remove FSUIPC from the Modules folder, or rename it to, say, FSUIPC4.DLX, does the problem still happen? If so it isn't related to FSUIPC -- as I think you've proven by try your previous version again. 2. Does that "heliforce" program use or need FSUIPC? Does the problem still occur without using it? 3. If it looks like being related to FSUIPC in any way, show the FSUIPC4.LOG file after such an occurrence. Also, if FSX is crashing, the crash details from Even Viewer might help identify where the problem is. Yes, just like FSUIPC , deleting the FSX.CFG file will simply make it will make a new one with default settings. Apart from losing any settings you made it does no harm. No, not really. Generally it is quicker just to re-install FS. There may be a repair option, but a complete install is generally better in the long run. Pete

You posted in a thread about PFCcom64.dll, which is for serial port PFC devices, not USB. Are you sure you have installed the correct driver, PFChid64.dll? Does MSFS recognise the axes -- all of them, including the throttle quadrant? and all of the switches and dials? Are there displays being driven? Pete

If you used them before with FSUIPC then the same support is there with FSUIPC7 -- though untested as yet (I do not have any Goflight units). It is a Beta release and you use it on the understanding that it may or may not work and will hopefully provide feedback on your findings. If, on the other hand, you used these units with GoFlight software, then it is maybe less ikely at this stage, but you need to ask GoFlight themselves. Pete

That's a bit lower than for most folks. mostly it halves at mosst. here I measure 30+ down to 20-ish. But if I disable traffic completelt in MSFS i get it back up to 25or more. This degradation is from ANY simconnect using application, and is a change (bug) introduced in the Release version of MSFS which certainly wasn't there in the last Beta us developers had. With that last Beta there wasn't really a noticeable differences at all, even with two or three SimConnect applications running. We need to persuade MS / ASOBO that this is an important problem for quick resolution! For further discussions on performance, please use the existing thread: Pete

Yes, there's always a default place. Pete

There's nothing known in FSUIPC about devices of type "Driving". It accepts "Joystick" devices. I'm not aware of type "Driving". Perhaps you could run HidScanner for me and show us the resulting Log file. You'll find it in this thread: