Pete Dowson

You purchase either FSUIPC3 (for FS or earlier) or FSUIPC4 (for FSX and P3D). You don't purchase a specific release, and in fact you are expected to keep up to date because I cannot support old versions. You only pay once for the whole life of that program, no matter how many releases are made. FSUIPC is not aware of and doesn't care about specific add-ons, so the question of compatibility doesn't really come into it. Pete

That crash information relates to an old version of FSUIPC, 4.929, which is not supported. Please go and get 4.937a from the Updated Modules subforum, and let me know if that helps. If not I need the error data for that version please. Pete

If you are using the mouse it is far easier simply to do it on screen with the mouse point and buttons. Writing a program to do ir with a single mouse wheel would first involve selecting which radio then part of which frequency you want to increment or decrement. Once you know all those things it's simply sending the appropriate control. But doing all that with a single mouse wheel is very compicated. Not sure how you'd do it without buttons etc too. If you are using a mouse, why not use it in the way MS intended, on the radio stack on screen? Pete

FSUIPC already does this, a pair of beeps at <= 300Mb left. I can be suppressed in the INI file but it is defaulted on. If you want a different sound or a different threashold you'd need to make a little Lua plug-in to monitor the offset and play the sound you want. Pete

FSUIPC is not compatible with X-Plane. It is for FS and P3D only. I do not use nor support X-Plane. I think there's a program called XPUIPC which may do what you want, or at least partially. If you want to get rid of FSX to make more space on disk, you mean? If your FSX is running smoothly why would you want to be rid of it just because you want to try X-Plane? if you want help with X-Plane you'll need to go to X-Plane forums. Well I'm over 71 years old now and not many folks are gentle with me! ;-) Pete

No need. Your words are enough. thank you. Pete

Oh, in that case you would need to change the last but one line there to lonmins = 6000*(lon - londegs) or even lonmins = math.floor(6000*(lon - londegs)) BTW Lua does not need ; at the end of each statement. They do no harm though. Pete

Answers to what? Pete

You would best handle it all in numeric form, not in string form. Then compute degrees = math.floor(value) minutes = 60*(value - degrees) Then just use the string.format features in the usual way, as in C etc. Pete

Hmm. System Error 6 is "Invalid Handle". The only handle there is the special one, 0xFFFFFFFF, which is specifically needed for a system paging file. Here's what the CreateFileMapping documentation says: "If hFile is INVALID_HANDLE_VALUE, the calling process must also specify a size for the file mapping object in the dwMaximumSizeHigh and dwMaximumSizeLow parameters. In this scenario,CreateFileMapping creates a file mapping object of a specified size that is backed by the system paging file instead of by a file in the file system." INVALID_HANDLE_VALUE is actually defined as -1. Are you trying to compile in 64-bit mode? Try -1 instead. Maybe 0xFFFFFFFF is coming out as 0x00000000FFFFFFFF instead of 0xFFFFFFFFFFFFFFFF. Pete

I need the details of the actual error report from Windows, please, plus a list of any other add-ons being loaded with FS. It looks like FSX is crashing in SimConnect when FSUIPC attempts to connect to it. For the Windows crash report, check the event viewer logs. Pete

Sorry, you only show the one line, and I don't know what your szName parameter is. A return of 0 means a failure, so use GetLastError() to get the error number to see why it failed. Pete

FSUIPC 4.937a should work okay, now up in Updated Modules. It deletes orphaned profile headers in the main INI file (so the Profile can be added as New and therefore appear in the Profiles folder), and it allows axis settings to be included in a new Profile. Pete

Okay. Try 4.937a which will be available in Download Links subforum shortly. Pete

Really? How odd. Never knew that! In any case, it doesn't stop the FSUIPC Installer from doing it's job. It just means that when it asks the user to find the correct EXE they need to press Cancel. It only cancels that part of the install, not the rest. Regards Pete

There's something else wrong then because TrackIR doesn't use FSUIPC and there's nothing significant changed in the running actions of FSUIPC between 4,934 and 4.937 other that the changing memory locations accessed for P3D. Without more information other than this unhelpful posting I can't really assist, but mostly this sort of thing indicates problems which exist in any case and which are just coming to light by slightly different memory arrangements as versions change a little in size and timing. Please don't ask for any support whilst using an older version, as I'll simply have to ask you to use the current one, whatever it may be at the time. Pete

Maybe, but it doesn't happen in Win7 and didn't in WinXP either. Microsoft is supposed to maintain DirectInput compatibility so there's somethng messed up in Win8. Pete

Moved from the FAQ subforum, which is NOT a Support Forum. Seems the uninstaller doesn't work correctly then, as the Registry evidently still points to where P3D should be! Please report this to Lockheed-Martin. Pete

I think I spot an error in FSUIPC whereby it is sending 120 times the value you provide. Very odd that it seemed to work fine in testing. I will release a correction -- 4.937a. Tomorrow. BTW you ARE using FSUIPC4, aren't you? FSUIPC3 is no longer easy to maintain. Pete

In any one of several ways, as described in the documentation. Once it is placed into the Modules folder you can assign a keypress or button to start it. Pete

If you mean the Autopilot control, you need to check the 737NGX documentation. PMDG do not use the FS Autopilot so you need to use it's own controls or assignments. I'm sure you'll get help with this at the PMDG forum. Just check the REV checkbocx (REV = Reverse) before claibrating. I think you'll find a lot for the 737NGX in the User Contributions subforum, above. Pete

Are you saying that you actually assigned "smoke off" from the drop-down list, and it is sent to the aircraft but does nothing? If so, then the "Smoke off" being logged is some sort of separate thing the aircraft is using. Sorry, I've no idea about that. But you said it was an XML gauge, so it is still quite likely that it can be operated via Local Panel Variables (L:Vars. You need to check those. If you run the Lua plug-in provided to log them, you will see a real time display on scren of L:Vars as they change (as well as getting a log of them). Once you can identify the correct L:Var you can try assigning a button to write to it. This involves making a macro file then assigning to the appropriately named macro -- you'll need to see the section on L:Vars in the Advanced User's guide. Pete

There is ALWAYS a LOG file. It is there, alongside the FSUIPC.DLL, FSUIPC.INI, FSUIPC.KEY and Install FSUIPC.LOG files and the FSUIPC Documents sub-folder. You are looking in the vwrong place if you don't see it. Maybe you have Windows hiding filetypes from you? Please see the FSUIPC user guide about turning off that annoying Explorer option. Pete

Ah, right. It assumes you wanted a "hybrid" system, i.e. some in the Profiles folder some not. It isn't would be very hard to change, because when adding say [Keys] it isn't looking at [Axes], [buttons], or [JoystickCalibrations] so must assume, since there's no INI file for it in the Fies folder such sections, if they exist, must be in the main INI. Maybe it can re-run the original conversion which at present only happens if the Profiles folder itself doesn't exist when it sees "UseProfiles=Files", but that only happens during initialisation. I can't do it during new assignments. An alternative would be to delete orphaned entries like yours altogether during initialisation. After all a Profile aircraft list with no assignments at all isn't doing anything. Then when you came to assiign you'd create a new profile. I think I might implement that latter method. It's cleaner. Pete

Actually that is simply not true. I do not and never have sold FSUIPC or WideFS myself. I do programming and support. I've been with SimMarket since the very start of going payware, in 2003, and the arrangement has been good for both my users and myself. Loyalty does garner rewards and respect, and you won't find me deserting. Regards Pete