Pete Dowson

No, you can use a different email for WideFS. Only your name must be spelled identically. And both FSUIPC and WideFS are on the same PC, the FS one. The only part which runs on the other PC is WideClient which needs no registration. Pete

No, as i just said, perhaps you misread it? "You can use FSUIPC on any PCs you own. It is licensed to the person, not the machine(s)." What else can that possibly mean? Pete

I see it uses a Lua plug-in. You do realise you can only run Lua plug-ins with a registered FSUIPC I suppose? Lua plug-in actions are easily checked and debugged using logging facilities as shown on the Logging tab of FSUIPC. You should also be using the current version of FSUIPC -- 4.852 for FSX. Pete

Assuming that program is reporting this correctly (it is code in the application program, not in FSUIPC, which does the checks), this is an extremely rare error. In fact I don't remember the last time I saw it. Somehow the data being passed across in the shared memory area is being corrupted. This can happen in a couple of ways I am aware of. One is having a multi-threaded program trying to use the connection to FSUIPC in more than one thread without taking precautions to synchronise use of the memory area, and the other is bad hardware -- failing memory chips. I'm not clear on this. What drives the gauges on the second PC? Are you using WideFS as well? No. In fact I've never heard from anyone using FSXpand at all. Reinstalling the same version of FSUIPC does nothing, because if the existing version were corrupted it would say so and not run at all. I assume you've looked at the FSUIPC4 log file -- that's always the first place to look, that is what it is for! You should of course always use the currently supported version, which is 4.852. If you are not using that already you should have upgraded before you came here. And upgrading FSUIPC merely provides a replacement DLL module and updated documentation. Yu never uninstall anything and it doesn't affect your configuration. No idea. You need to ask them. Maybe you are out of date with that? You should always use the latest, especially if you want support. I cannot support old versions. 16?!!! Phew! You could certainly try swapping out RAM chips then. Even 8 is well over what you need! Pete

If the list of PMDG controls, provided in their SDK, includes one to open the guard, then you can certainly use FSUIPC to assign to that control, by number. Regards Pete

What's "ozrunways"? Are you sure it uses FSUIPC? I don't think it can from an iPad. Pete

Either you are still making an error, or using the wrong key for the product (as Ian says), or the date on the PC is set to something BEFORE your purchase date, which would make it look invalid. If you think everything is correct, tell me the order number. I can't check by name. Don't post any other details here. Pete

You can use FSUIPC on any PCs you own. It is licensed to the person, not the machine(s). Both are "stable", but they aren't the same interface, so it depends what programs you are running -- FSUIPC clients or SimConnect clients! Pete

It isn't really FSUIPC not working -- it isn't even being loaded. It's some clash in FSX. And you'll need to ask Ask nVidia. It's very evidently their bug! Pete

Because you are testing offset 132C when you press the button. With that code I might expect that the LED lights on the 102nd GP-P8 unit of yours when you press the button to turn OFF the GPS mode, assuming it was on when the button was pressed. What is turning the light off when you toggle GPS mode off? Have you really got 102 GF-P8 units connected to your system? GF numbers the units 0 for the first, 1 for the 2nd and so on. I can't imagine a sysyem with 102 of them! Really you probably want the light controlled by an event, in a Lua which is actually preloaded and running all the time, waiting. You should program your button in FSUIPC's buttons tab not in the same Lua, it is unnecessary here. Have an event.offset on offset 132C and use the value passed to the function to set or clear the light accordingly. You can have the Lua loaded automatically using the [Auto] facility in the FSUIPC INI file. Regards Pete

Okay, that's more useful because it contains the Windows error number: You shouldn't cut bits off logs! ;-) You also said: I assume here you mean FSUIPC4.LOG? Have you not actually run FSX since running the installer? If you had there should certainly be a log! The error number means the following, according to the Web: Error 0x80092026: The cryptographic operation failed due to a local security option setting. I think this may be the error intriduced through a bad registry setting. Please see the FAQ subforum thread entitled One solution for "My signature check fails on the installed FSUIPC4.DLL. (Error 80092026)" which seems entirely appropriate, does it not? Pete

Please stop adding new posts every few minutes! It doesn't help! It the signature checks okay, then it is okay. Nothing to get running. Why is the Installer log stopping before the end? There should be more of the log in the Modules folder. Post the whole thing. Where do you get the error message? In the Installer or in FSUIPC? Is there an FSUIPC4.LOG there? If so post that too. I'm out in a short time now until tomorrow evening (Monday). Pete

You posted this THREE times, all in the wrong places. Please always use the Support Forum for support! I've moved it for you. Post the comple installation log please. It sounds very much as if you don't have some of the essential Windows services running -- like the cryptographic one which is always needed for signed modules. Right click on the DLL and select "digfital signatures", select the one listed and see if it says it is ok. Pete

Well, you can still use gfDisplay if you wished, it is just that if you don't know how to I'd rather not tell you as it is, in my opinion, too complex, too arcane. The support for GF devices has been moved to the Lua plug-in system, with the "gfd" library functions able to drive displays much more ably. Check the Lua documents in your FSUIPC Documents subfolder. Regards Pete

Ah, that's one of the more usual errors when writing to offsets -- using the wrong size (DWORD is 4 bytes, WORD is 2 bytes). I might have suggested checking the sizes if I'd realised you were actually programming the offsets. I thought that was handled by that "ifly2fsuipc" program. Regards Pete

No! "as poiunds per gallon * 256" means it is provided already times 256 (i.e. it is in 1/256ths). So you need to DIVIDE by 256 to get pounds! And why multiply by 3.7854118? Do you think there are that many kilos in every pound? I thought it was only 2.2 something. I'd re-check that if I were you! Pete

What is making the left door continually open and close? Are you holding the Shift+E down? Don't! Press Shift+E, release, and THEN press 2. It is defaulted "on" in the Registered install of FSUIPC, but you can adjust the time within which the number key should be pressed. Refer please to the Miscellaneous chapter in the User Guide. You'll see the option mentioned on the right-hand side of the picture, and described below under "Time allowed for Engine/Door select: ". Pete

Sorry, no, no clue at all without more information, like: Why do you think it is FSUIPC hanging? Are you sure it is hanging and not crashing. You have no error message, and have to terminate via the Task Manager? What exactly happens -- where does it "hang" (i.e. what stage -- on load with splash screen, when you fly, or some other time? If it's a crash, what message do you get? Find the Windows error log entry and provide the details. What version of FSUIPC? If not 4.852, try that first. That is the currently supported version. Have you tried using the FSUIPC4 loader as suggested in the installation document? Is there an FSUIPC4 log file? If so, please paste it into your message. If there is no Log produced, it is a SimConnect problem. If you are using nVidia surround mode you need to change video drivers. Pete

As far as I know, you don't "receive the key" -- after purchase you retrieve it from your product details on your account. At least that's how it works with everything I've ever purchased from SimMarket. I've never received any emailed keys! Please check the User guide which explains what you get and what you don't get. Pete

FSUIPC4 doesn't care what the email address is, provided only that it plus your name identifies you uniquely. That's all it is used for. It is never used actually as an email address. So you can purchase that using whichever account you can access. I'm afraid I can't really help with accounts themselves, I am but a lowly forum moderator and programmer, here to offer tech support for my programs. The only way I know of to resolve account problems is by raising a Problem Ticket. BTW I've no idea what POC is. And email updates seem pretty infrequent in any case. You can periodically check the status of your products using whatever account you have available to you. Regards Pete

Yes, exactly thev way I explained and showed code for. Er, you are confusing me now. The limit of 10 is on the number of range assignments on the right-hand side of the axis assignments tab. You should instead assign to the luavalue control on the left. That passes the axis value onto the Lua plug-in. I gave these instructions already, how come you are thinking in terms of 10 ranges? I must have failed dismally in my previous reply as you appear to have misunderstood everything. Why not simply try the code I provided? But your tersting of the value was in ranges of 51!!! But loading and compiling another Lua is wasteful in time and energy, and all you are saving is a little memory space. Just cut and paste the code directly into the new plug-in. It's not necessary to work it all out again! I actually coded it for you. All you had to do was try it! I don't understand your confusion!? :sad: Pete

Just assign your buttons to the keystrokes on the left hand side of the Buttons tab in FSUIPC options. You should find it completely intuitive, but the documentation is there to help too. Regards Pete

I don't follow your logic there. Button programming in in FS or in FSUIPC. Wires have nothing much to do with it. By programmed I mean software, not hardware. And should they? Sorry, I don't have enough information. I was assuming you knew which offsets should be changing and what they did. I don't know anythng about iFly or iFly2FSUIPC Probably not if the iFly aircraft doesn't use any FS controls, no. But I don't know what it uses. I was only suggesting the tools you might use in FSUIPC, as you asked. This is what makes me think it is programmed twice. Don't forget the Bodnar boards are recognised in both FSUIPC and in FS as joystick devices. FS makes automatic assignments for newly connected joystick devices, unless you've disabled controllers in it. Or it may simply be that you've left one of the buttons programmed in fSUIPC -- maybe from a previous joystick attachment and this Bodnar board is taking the same ID number. Maybe the FDS card isn't recognised as a joystick device? I don't know those. It would have a different iD number if it is, in any case. Pete

I moved this from the FAQ subforum to the Support forum, which is where Support is provided. That's out of date. Current is 4.852. Sounds like either you've programmed it twice or there's a problem with "ifly2fsuipc". If you know the offsets then just monitor them using the Monitor facility on the Logging tab. Though it won't be able to tell you why. Enable event logging too. Pete

Well, of course any of the flaps positions offsets will give you that, but in different ways, so it still depends what you want to use it for. You have to decide which is more suitable! 0BE0 and 0BE4 give them as a flap lever position between 0 and 16383 with the increment normally as that given in 3BGFA 0BFC (FSX only) gives it as the lever detente nmber (0- how ever many, see offset 3BF8 for number) 30E0-30EE gives more detailed ingformation for the separate flap components. 30F0-30FE is the same but with flaps angles rather than positions Pete