Pete Dowson

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

Strange!, because I cannot reproduce this here. When I create a new profile whilst UseProfiles=Files, it creates a [Profile.<name] section in the main INI file, listing the aircraft name (this part is needed so FSUIPC knows there is a profile for this aircraft), but the settings are then saved as <name>.INI in the Profiles folder. If this is not happening for you, perhaps you could please tell me step by step what you do -- maybe there's a path through the assorted options which does have such a problem. Pete

But I've read just as many reports that say it doesn't help. I really don't see any reason why it may help as it uses pretty much the same Windows options as FSX. Sorry, I really don't know. It just uses the standard DirecInput interface to Windows, and there's really never been problems with Win7 or XP. There seems to be many problems with Win 8 and Saitek devices especially. Have you tried using their software? Perhaps there'll be more help on the Saitek Forum? Personally I'm steering well clear of Windows 8 (and Saitek, for that matter). Pete

No, not in FSUIPC. But you can specify that they should not be run until you are ready to fly -- put "READY" in as well. For more ambitious schemes you could use the Lua plug-in library ext which handles running of external programs. Pete

Unless this action is simulated in the specific add=on aircraft, it isn't anything supported internally in FS. If the switch on the panel does work, and the aircraft maker has not supplied a key press shortcut for it, then there may be one of two possible solutions, but it isn't guaranteed: 1. FSUIPC mouse macro. This where where FSUIPC traps your use of the mouse to activate the switch, and then provides a way of doing it directly. This method only works with panels designed in C/C++ with the Microsoft SDK. Look up mouse macros in the FSUIPC documentation. 2. Local panel variables, or "L:Vars". If you can find an internal variable used for the switch you might be able to program a button to write to it You can use the added FS control to log L:Vars, or use the Lua plug-in provided to monitor them as they change. Pete

OKAY. Please download the Install FSUIPC4937 package again from Download Links. I've made the Installer bypass the SimConnect check for P3DV2 (only). Before your report I hadn't realised P3Dv2 installed without any separate SimConnect DLLs at all. I knew it was capable of supporting SimConnect without those in the WinSXS system, and has been so since version 1.4, but the older P3D installers did actually install the ESP version of the DLL in the WinSxS folder. Odd that we've reached the 5th version of P3Dv2 and you are the first to discover the problem. Thanks for reporting it and sorry for the delay. Regards Pete

Okay. From the look of it the Server broadcasts simply are not being received on the Client. That maybe because the FS PC and Client PC are on different workgroups -- you can change one to match the other, or simply put the ServerName and Protocol parameters into the WideClient.INI file on the Client, as described in the part of the WideFS documentation which has the RED instruction urging you to read at least some of it -- i.e. configuring the network. By having the server name and protocol defined in the INI file the Client doesn't need to wait for any broadcasts from the Server, so it can be more efficient too. The broadcast method was only added to make it simpler most of the time. Pete