Pete Dowson

All three parts, not just the Registration code? If you are really sure, then I suggest you send me your SimMarket data and your KEY file and I will check it here. Send to petedowson@btconnect.com. Be sure to RENAME the KEY file and ZIP it, or it will be blocked by the email system. Also include your FSUIPC.LOG file. I won't be able to look at this till the morning now ... Pete

The FSUIPC SDK deals with offsets. But the list of offsets in your FSUIPC Documents folder should show you enough to see what those handle. And L:Vars are really the province of aircraft addon makers. There's no way of predicting what an add-on may have or what names they will be using. The only thing you know beforeghand is that they use NAMES for identifiers, not NUMBERS (like offset addresses). Pete

If the controls don't work, please show me your FSUIPC5.INI file (from the Modules folder). For the axis you said Does that mean the axis is still unreversed when you select the REV option in calibration? Don't forget you need to re-calibrate afterwards. Best to Reset then Set again. That seems to conflict with what you said before, i.e. "I've tried many many times even resorting to P3D controller settings!" Oh, the P3D Forum (and the Beta Testers Forum there) both confirm a similar problem in 4.2 to your trim one, but with rudder -- the left rudder control operates but not the right. This has been confirmed by a well-known developer, and tested with no add-ons installed I'm afraid i'm retiring now, so I'll check back in the morning. Pete

The compressor variable is an L:Var, which is only addressable by name. There is no offset equivalent to an L:Var. No, no, they don't! Local Variables (L:Vars) are known only by NAME. Offsets are memory addresses where non-local variables are stored for reading and writing -- variables supported by the underlying Sim Engine, not only by a local gauge specific to an aircraft, add-on or default. You can't. And why do you need to? You use ipc.writeLvar, as you posted, the equivalent of the ipc.readLvar for reading. The two make up a complementary pair! Pete

And does it work when you use P3D instead? This sounds like yet another matter to report to L-M, as the controls are the same. FSUIPC doesn't care what they are and doesn't treat any differently from any other. There seem to be quite a few little oddities with P3D4.2 -- take a look at the L-M support forum. Again, if you've not changed things in FSUIPC, it can't tell the difference. But in both cases, try P3D assignment just to be sure. by all means come back if that's okay and FSUIPC is not, but then we'd need to do some proper logging. Else, try just going back to 4.1 without changing the FSUIPC version. You'd only need to install the Client. Oh, one other thought. A lot of the problems folks have had with 4.2 seem to come down to only updating the Client. I think with this release you really do need to install the Content package too. Pete

I get the same here on occasion. I'm pretty sure it's due to some Windows or driver updates. It's okay on my older Win7 Client PCs (I have a 7 PC cockpit system). I have two small touch-screens either side of the cockpit, one for the Captain the other for the 2nd Officer. Sometimes it's not all black, just a few of the button rectagles appear. As you say, it is always okay when forces to repaint, e.g. by just moving the border in or out a little and returning it. I've not had reports of others seeing this before, but now you have I'll take a look and see if there's something I can do to correct it. Maybe a forced re-paint a second or so after connection. Pete

You just need to open your account at SimMarket. All keys for all programs purchased from SimMarket are accessible there. Pete

I see from your FSUIPC settings that you are not using any user facilities at all in FSUIPC. the file just shows the default settings. So I'm not sure why you've installed it. With no user settings, FSUIPC itself is most certainly not responsible for your problems. If you were running some FSUIPC-using applications then it could be doing things on their behalf, but you have not listed any. So FSUIPC is simply sitting there, reading FS data in case any application needing it is started. It won't be controlling anything nor writing anything to FS.. Those are both add-on aircraft and may do things differently. If their documentation doesn't cover this you'd need to ask their support or find their support forum, if there is one. To check that the COMM/NAV swap facility does work, test it with a default aircraft not an add-on. BTW FSUIPC version 4.974 was released earlier today. Pete

I think it's related to the keypress you assigned to access the ProATC/X menu. With GSX I think the default is F12 or F11. With ProATC/X it may be 0, 1, or some numeric, which is also a SimConnect menu selection. You could try re-assigning the ProATC-X shortcuts. Pete

It is not a problem with FSUIPC, but with P3D4.2. It is being investigated now by L-M. It seems to be that P3D4.2 (not 4.1) stores the previous keypress and takes that as the response to the menu. There are work-arounds.discussed on the Avsim P3D forum, to which you may wish to refer. Many folks have temporarily gone back to P3D4.1 because of this, as it is also a problem with GSX and other SimConnect Menu using programs. Pete

Please go to the Download Links subforum above, and download the replacement FSUIPC 5.123e. The ZIP just contains the DLL for copying into the P3D4 Modules folder. This is a temporary measure pending a full update early next week. Best to simply disable controllers instead. No need to delete assignments, and in any case they often seem to get automatically re-assigned. Ouch! FSUIPC works best with no Saitek drivers at all. Best to uninstall those. That could be the main reason for any problems. Something strange there. The X-56 is the only device FSUIPC knows about, and that is device 0. Yet there is an assinment to a device 1 axis: 3=1X,256,D,4,0,0,0 -{ DIRECT: Throttle }- Additionally, although you say there's no FSUIPC response to buttons, there is a button assignment to the X-56 device: 1=P0,4,C65752,0 -{PARKING_BRAKES}- Could these be left over from some other device? Note that I think the X-56 may have more than 32 buttons (I don't recall). FSUIPC will only see the first 32 (numbers 0-31 for FSUIPC or 1-32 in Windows Game Controller terms. Pete

Best to download 5.123e from the Download Links subforum, and copy the FSUIPC5.DLL from that ZIP into your P3D4 modules folder. A revised full install package will be released soon. Just a few other things to tidy up and test beforehand. Pete

You need to state the VERSIONs, please: P3Dv1,2,3or4? And which specific version of FSUIPC? If you are using P3Dv4 you need at least version 4.1, and you need to install FSUIPC 5.123 then overwrite the FSUIPC5.DLL file in the Modules folder by version 5.123e, available in the Download Links sub-forum above. For P3D3 you need FSUIPC 4.973. If you are up to date and still get problems, I need to see the FSUIPC Log file, from the Modules folder. Also, for PMDG aircraft, check that you have all the updates. The original releases did have problems in P3D. Pete

Using the mouse on the screen button? Or only using an assigned control, in FSX or FSUIPC? Well, FSUIPC won't do anything unless asked, whether by settings in your INI file or by an application (add-on aircraft or xternal program), or a plug-in. If you show me your FSUIPC4.INI file (from the FSX Modules folder) I can check some of this, but you'll also need to list the add-ons you are using, and which aircraft this applies to. You can paste the contents of the INI file here -- use the <> button above the edit area to open a bx to paste into. Or you can ZIP the INI file and attach it. Pete

The "Event" logging in FSUIPC includes all non-axis events (a separate logging option) passed to the sim no matter where they originate. For some aircraft, operating something with the mouse does also result in such an event. PMDG's Boeings support the use of "custom controls", using the same system but with numbers for events beyond those provided by the Sim. L:Vars ("Local Variables") are used a lot by other add-ons, but some of those will just indicate a setting, not control it. Even some of those which will control a switch function don't always result in the on-screen switch position moving, even though the aircraft respects the value you write. I'm afraid some functions on an aircraft panel (even for default aircraft) do not have any means of access from either keyboard or button, with no L:Var either to use. In FSX and P3D1-3, the FSUIPC "mouse Macro" facilities might be usable, though more and more aircraft are written in ways which don't support this. Mouse macros aren't available in the P3d4 version of FSUIPC, though I am hoping to be able to implement these with the help of new facilities provided by L-M. Pete

This symptom, and the log, both suggest a weather file corruption. The reason the crash occurs only with FSUIPC running is that when it starts running properly, it is reading weather data through SimConnect. These files are binary data and are completely unchecked by SimConnect when it reads them, so any corruption can crash the sim (and sometimes only when flying in the area subject to such corruption). The file which is corrupt could be a .WX file in your P3D4 Documents folder (you can delete those if you are using a weather program and don't need saved weather), or it might be the wxstationlist.bin file in your AppData\Roaming P3D files. That can be deleted as it will be re-generated by P3D. Pete

The ProSim problem merely caused the FSUIPC Options not to appear. It was a combination of two bugs, one in ProSim sending masses of offset changes for the same thing, on one in FSUIPC which has always been there -- just a terminal condition on a table (> should have been >=). The only thing i found in experimentation to find this latter bug is that there appears to be no real need to ask SimConnect to put the Sim into "dialogMode" before opening the Options dialogue. In fact it is better without -- a little faster, AND it doesn't then blank the Sim view. Try that in the 'e' version if you like. Add UseDialogMode=No to the INI file [General] section. I was thinking of making that the default mode, but I thought it might be a drastic move and I was worried about side effects. I'm not now sure why the DialogMode system exists. It might date back to FSX and P3Dv1 and their true "full screen" mode, where possibly the dialogue would not appear, or would appear on the "windows" screen behind the sim-owned full screen. I'll have to ask L-M about that. Pete

I think this has been reported in the L-M support forums already. It is not related to FSUIPC. Pete

The current FSUIPC4.ZIP and the Install_FSUIPC4973 both contain 4.973's installer dated 21st January, and they install the 4.973 DLL which most certainly says it is 4.973 in the log, on screen, and in its Properties. So it seems you've either not downloaded the correct file (try clearing your cache) or the Install failed -- check the Install log again. (Did the Installer not say it was installing 4.973?) Like Thomas said, though, the main change is in the Installer. There's a minor correction to a very very old bug too, though. Pete

An unregistered version of FSUIPC is doing almost nothing. A registered one does much more more too! Which is the "version of today"? Do you mean the current version, 5.123e? Pete

Sorry, but it cannot be FSUIPC related. The FSUIPC open and closing is exactly as it used to be. The problem with the Options sometimes not appearing was related to programs (like ProSim) which was sending many controls very quickly via offsets and a list building up in FSUIPC overflowed by 1 (bad limit check), corrupting a MenuItem saving value which made FSUIPC think the menu was already open. So it didn't re-open. This is an error which has been in all versions of FSUIPC4 and 5 till now. FSUIPC cannot affect whether mice moving over things causes them to do something. It is purely passive. Please try a series of eliminations on all you active add-ons. Pete

What does this mean? Not running at all? Where are the logs? Did it not install? Pete

Version 5.123e, now available, fixes another possible reason for the Options dialog not opening. Pete

Most FSUIPC clients don't need the paid version of FSUIPC. The purchase is mainly for the user facilities -- assignments, calibrations, plug-ins. Pete

No, sorry. There was an introductory discount earlier, but that's long gone. Did you get P3D4 at a discount because you had a previous version? Pete