Pete Dowson

This sounds like the (thankfully rare) SimConnect bug. Please see the FAQ subforum thread FSX fails to run after FSUIPC4 first installed Pete

I could have a look at mapping the 777 offsets, assuming PMDG have implemented a similar mechanism, but i don't really want to purchase the 777. I wonder if PMDG can be persuaded to let me just have the SDK portion. I'd then need someone with the 777 to test the results of course. Pete

I seem to have just read exactly the same question is a different thread! :sad: In that one I said I didn't know PMDG had implemented a similar data export facility for the 777. I don't have the aircraft and therefore not the SDK either, so at present I am unable to implement anything similar I'm afraid. No one has mentioned this before either. Pete

Is a log produced? I'd need to see that too, please. And please try again with the very latest test version, Install FSUIPC4939b_TEST so that any crash data you get will match my current code. Pete

Thanks Thomas. I've just installed the second hotfix (taking P3D2.5 to build 12944, and it seems okay. All the important hooks work fine still. I'll be checking everything more thoroughly over the weekend and update the installer when I've done. Pete

That looks exactly like the crash you get when you have a corrupted .WX file (weather file), or WXStationList.bin. Try deleting the latter one first -- you'll find it in the same folder as your FSX.CFG file. If that doesn't work, you'll need to delete the .WX files associated with the flights which cause the crash on loading. These files are binary files and are not properly checked by SimConnect when it is being asked to supply weather information by FSUIPC. Sorry, but FSUIPC did not crash. It closed normally as you can clearly see from the Log. FSUIPC closes normally when you close FS, which you did. Pete

WideFS6 is for FS9 and before. You purchased the wrong product! Pete

Aren't both of your messages asking the same question? FSUIPC doesn't care or know about the make of a joystick type device. If it is recognised by Windows as a joystick, you can assign in FSUIPC or FS. If not, you need its driver. Pete

1. What's "all sorted"? There are no previous messages in this thread!! 2. That link doesn't seem to work in any case! Pete

There's absolutely no difference. You are therefore making a mistake. All three parts of the Registration must be exactly correct. If you still have your FSX installation you can use the FSUIPC4.KEY file from its Modules folder. Pete

I never understood why this might be the case, because FSUIPC reads the joystick devices in exactly the same way as FS. Hmm. Sounds like the sorts of problem many folks complain about with Windows 8. Maybe Win10 will fix it. I'm sticking with Win 7 for sure! Sorry, I can't help really. As I said, I don't even understand how using FSUIPC can help with such problems in the first place. Pete

Sorry, there's really no way that is possible. Please read up about the FSX-SE Terrain crash problem which is by now pretty well known, and by all reports may well actually be partially solved by the latest FSUIPC's "G3D crash" fix. Pete

DO NOT mix range options with axis assignments! You'll just get a mess! FSUIPC's calibration will handle the OFF/ARM settings if you assign to spoilers. If you really do want to use the ranges instead then do NOT assign to the axis on the left as well. But it's a complicated way of doing something made easy by calibration. Pete

No idea at all, I'm afraid. But all the answers will be in the FSUIPC4 Install log, which is why it is produced. You'll find it is the P3D Modules folder. Please paste it complete into a message here. You can use the <> button above the edit area to enclose it neatly. Pete

This information is already exported in the Runways.XML file. Please use that. Pete

Something very fishy there: FSUIPC4 version 0.0.0.0, and "unloaded"? And the offset 5a0ca070 is impossible too -- that says the error occurred at byte 1,510,776,944 from the start of the FSUIPC module! Is there an FSUIPC4.LOG file at all? Maybe that will help. And when you say "started getting ..." do you mean it's been okay then something changed? Pete

I didn't know PMDG had implemented a similar data export facility for the 777. I don't have the aircraft and therefore not the SDK either, so at present I am unable to implement anything similar I'm afraid. No one has mentioned this before either. Pete

Well, it might be possible with a lot more hacking into FS code (which I did try in the past, but gave up), but in my opinion it is simply not worth it because the default ATC is so dreadful, especially for us non-North American fliers. Pete

Yes. You can assign both axes to Rudder, but manipulate the values being received to get 0 to -16383 on one an 0 to +16383 on the other. You do that by first assigning as usual in FSUIPC, but then edit the entries for the assignment, in the FSUIPC4.INI file, as described in the section "Additional parameters to scale input axis values", on page 44 of the FSUIPC4 Advanced User's guide. Pete

Version 3.999z8 dates back to September 2013, over 16 months ago! Aren't you updating a bit late? Updating versions by simply running the installer never changes any of your settings, which are all retained in the FSUIPC.INI file in the FS Modules folder. There's a limit of 127 macros which can be listed in the dropdown. You cannot assign to any beyond that. Check the list in the INI file. That sounds like a matter for iFly support. Pete

The changes seen from the rotary cannot be made faster other than by turning the rotary faster. Increasing the poll rate will merely make the program look for changes more often. If your rotary can provide more than 50 changes every second I would be very surprised indeed -- 50 is your current poll rate. But by all means experiment. Whether the turn rate is regarded as "fast" or "slow" depends only on the "FastTimeLimit". If you set that to 10 as you suggest then you would have to turn it fast enough to get 100 pulses every second to get the fast indication, otherwise it would only be slow (> 10 miliseconds). If you want a slower speed (a possible speed!) you need to increase the time not decrease it! I think maybe you are thinking this program is for something completely different from what it is intended to do? Pete

I can't tell from such a partial log! Please always paste in the oomplete log! Pete

Sorry, I don't understand "reading to DEL", and there's no INN file associated with FSUIPC. The configuration settings file is an INI file. Please post new questions to the main support forum, to add to a different thread in a subforum. Thanks. Pete

Oh, right. I would never have thought of that! I shall try to remember it! Pete

No. I don't know anything thast can read and interpret the default ATC. I don't think anyone would want to go to the trouble in any case as it is very unrealistic. There are better options. Check out Radar Contact, Proflight Emulator (PFE), VoxATC, and ProATC-X. Pete