Pete Dowson

No no no! You still haven't looked at the documentation! There's no "=yes", just a comma!!! Why not actually look at what it says? Pete

There is no "Close1=yes"..." parameter supported in FSUIPC. You are evidently not looking up the format of the facilities you want. Please refer to page 45 in the FSUIPC4 Advanced Users document, where you will see the defined formats and options available. You have similar problems in your Wideclient.INI. There is no format matching the last line. It is just Close1=Yes Why not refer to the documentation provided, rather than make it up yourself? Pete

What commands and what aircraft? I really cannot help without specifics. What is this "menu" which shows a change? The FS "menu" is the strip along the top, the one which has "Add-Ons" in it which you select to choose FSUIPC. Pete

Please just specify the correct IP address to WideClient. Please read the section in the WideFS User Guide entitled Quote Pete

It's 3367 not 3362. No, they should be identical in this area. The aicraft model interprets the control, though. Are you checking on the same aircraft? If you log "Events" in FSUIPC, you will see that when you write to 3367, fSUIPC simply does what you are doing -- sends the same controls as Shift+E+n does. Compare the two logs from FSX and P3D. Maybe on P3D there's some control getting in between? FSUIPC uses a "macro begin/Macro end" facility provided by SimConnect to ensure the controls stay together. Prepar3D 1.4 is now very old, and if there is a SimConnect problem with it it isn't going to get fixed. Have you considered move onto P3Dv2? It is far superior to 1.4 in every way. Pete

As clearly stated in the FSUIPC User Guide, Mouse macros only work on those very few gauges which are written in strict accordance with the original Microsoft C/C++ Gauge SDK. Fewer and fewer are these days. If, in Mouse Macro making mode you don't get the overlay appearing when clicking on a gauge button it simply means it can't be done. Pete

You either need to make the WorkGroup name the same on both PCs, or add parameters to the WideClient.INI file to tell it the Server name or IP address. Please read the section in the WideFS User Guide entitled Pete

What "adjustments" don't change which "functions"? You need to be rather more explicit I'm afraid. Pete

No, the Delta value is in the Assignment parameter, its part of assigning not calibration. The "/n" part of the calibration entries refer to options selected on the calibrations pages, like filter, reverse, no reverse zone. I don't recall which one 8 is but a reference to the calibration tab for it will show. Pete

Sorry, you need to stay in thread. I've no idea what this is about and really I have too much to do to search for old threads. Pete

Does the aircraft provide any ways to do that? Is there any documentation? If not, have you asked Carenado support? What says "Key not programmed -- passed on to FS."? FSUIPC? Where? If you have turned some logging on for some reason, and it is the log entry you are talking about, it means exactly what it says -- that you pressed a key (or at least FSUIPC detected a key press) which has not been assigned in FSUIPC, so, naturally, it lets it go through to FS. If you want to program keys you do it in the FSUIPC Options -- please see the user guide. So what are those keys "not programmed -- passed on to FS"? You are confusing me! Maybe Carenado haven't provided any keypresses to drive their G1000? Maybe they'll respond to Mouse Macros or L:Var settings, but that will take some research. Unfortunately many aircraft makers do not abide by any existing rules or provided alternative methods when creating their aircraft. Maybe they thought the existing FS controls were insufficient or incorrect. Pete

I think the PMDG aircraft all need to intercept the throttle inputs themselves, so you CANNOT calibrate them in FSUIPC. Just assign them to the regular Axis_throttleN_set controls (sending to FS, not direct to calibration), and don't calibrate in FSUIPC. You are actually adding to a thread in which this answer was clearly provided by myself in the second entry. Did you not read the thread before adding to it? That is not similar in any way whatsoever! You evidently have incorrect or conflicting assignments! Pete

The codes for dwError are all named "FSUIPC_ERR_ ...",. FS6IPC_MESSAGE_SUCCESS will be referring not the the error code returned in dwError but the return from the function itself. You only look at the dwError code if the return says FAILURE (i.e returns FALSE). Aren't you getting the files from the FSUIPC SDK? Adam wrote FSUIPC's version-specific predecessor, FS6IPC, for FS98 (and FS5IPC before that for FS95). Pete Pete

"Offsets" for the NGX are read only. They cannot be written to. I think you are referring to the custom controls instead, for which you need to compute the numberical value from the list in the .h file. For the MCP don't the MCP specific controls work? i.e. #define EVT_MCP_COURSE_SELECTOR_L (THIRD_PARTY_EVENT_ID_MIN + 376) #define EVT_MCP_SPEED_SELECTOR (THIRD_PARTY_EVENT_ID_MIN + 384) #define EVT_MCP_HEADING_SELECTOR (THIRD_PARTY_EVENT_ID_MIN + 390) #define EVT_MCP_ALTITUDE_SELECTOR (THIRD_PARTY_EVENT_ID_MIN + 400) #define EVT_MCP_COURSE_SELECTOR_R (THIRD_PARTY_EVENT_ID_MIN + 409) You probably need a parameter, one of the Mouse codes, click left or click right I should think. The MOUSE FLAGS are also defined in the .h file. As I have stated innumerbale times, the FSUIPC mouse macro facilty can only operate on Gauges written to the standard Microsoft C/C++ Gauge SDK. Very few are these days. Even Microsoft didn't stick to the rules it laid down. Also, any time you update your airecraft you must discard all the old mouse macros and make them again, because the code they address directly has probably moved. Yes, if you are choosing your own letters you certainly don't want them auto-assigned! Additionally, somewhere in your settings, you probably still have assignments to A, B and C -- maybe automatically assigned originally. You've not shown the complete INI file so I cannot help further on that. Aren't you even using profiles? Pete

Why not do as I did and look up Windows error 740? I just Googled it and found: "Create Process Failed code 740 The requested operation requires elevation" In other words you are either running FS in elevated administrator mode ("... as administrator"), or the programs which failed are set to run in that mode. A process at one privilege level cannot create one in a different level. Looks like AISmooth.exe was the only exception. Just set everything to run at the same privilege level. Unless you have allowed FS to install in "Program Files" then there should never be any need to run anything "as administrator", except for Installers, but they usually manage to acquire that level in any case. [EDIT] Ah, I see Reinhard gave the answer more succinctly already! ;-) Pete

Just in case what I suggested in my last message proves to be the case, please download this updated version of the Installer, and try it. Install_FSUIPC4939w2_TEST.zip Let me know please. Pete

What do you mean by "activate"? The word doesn't apply to any of my software. Also please clarify which version 4.939 you are using. If it isn't at least 4.939u (the current official version) please update. Pete

A question. Maybe there's a faster way for me to make the Installer work, but I need more information please. In Windows START edit fieeld, type Regedit and press Return. This will ruun the Registry Editor. Find the entry Computer\HKEY_LOCAL_MACHINE\Wow6432Node (or just Computer\HKEY_LOCAL_MACHINE if you aren't using a 64-bit version of Windows) and see if there's an entry "DovetailGames". If so, see if it contains 'FSX' and open that entry. On the right, is there an "Install_Path" entry with the correct path? If you could check quickly I might be able to make a revised installer tonight for you to use, before I disappear for two weeks. Pete

The FSX-SE install hasn't worked correctly. There should be registry entries identifying it's installation correctly. Try running the repair option in the Steam application. If that doesn't work you could try using one of the Registry fixing programs for FSX, for instance the one at: http://www.softpedia.com/get/Tweak/Registry-Tweak/FSX-Registry-Utility.shtml. I think it should work for FSX-SE installed alone as it will look like FSX in any case. Failing any of that I can only suggest you visit DoveTail's support. BTW, as a way of explanation why the Install couldn't recover: The idea of the prompt for you to find the EXE depends on first actually identifying that there should actually be a supported sim installed. When it occurred for you, as a last desperate attempt, it was in the final (Prepar3D install) part of the sequence, which won't work even though you identified an FSX.EXE not a Prepar3D.EXE (many folks use a migration tool which can rename things like this, so the name can't always be trusted). This is the first time I've seen any example of any version of FS installed with no install path placed in the Registry. Having seen it happen, I will look at ways of making the Installer cope. When you identified the EXE it could read the version details and decide which sim it was then. I'll look at doing this, but, alas for you, I am away from this evening until 22nd July. I've made a note to do this, though, too late to help you I suspect. Pete

The PMDG offsets are read-only. It has controls for making things happen. I don't have a list of those -- they are listed in the .h file supplied in the installed NGX SDK folder. Best, and easiest, if you can assign keypresses in PMDG, would be to just assign all the keypresses you need to the same button. To do that you'll need to edit the FSUIPC4.INI file. Assign one of the keypresses then look in the INI file for it (it'll be in a [buttons...] section, presumably in the Profile one for your 737NGX ). Then add the other 3 lines in the same format but with different Keycodes (those are listed for you in the FSUIPC Advanced User's Guide). Remember, each line needs a different line number (the bit before the =). They will all be executed when you press the button, in the order of line number. Pete

I don't know vb, but surely it has arithmetic? Try using multiplication and division? Pete

Sorry, I don't deal with sales at all, just development and support. Please raise a problem ticket on your SimMarket account. Pete

Sorry, I don't want to have to try to work out what you've done from pix. Please just paste the contents of the FSUIPC4.INI file into a message here. There's never any point in pictures, the data is TEXT and can be placed in messages. Since after this evening I'm away till 22nd July, I made an exception this time and looked at the pix. They both define the same assignment, and on the one button you assigned "open doors" to press and "close doors" to release. Are you going to be holding the button down pressed for all the time you need the doors open? If you are just pressing and releasing I don't think there's time for them all to open and close! And please ALWAYS test on a default aircraft. I have no idea whether the PMDG aircraft follows standard FS controls for doors or not! Do you know? Have you tried the keys Shift+E then 2, 3 or 4 to select the other doors? If the PMDG aircraft needs different controls, or perhaps keystrokes, instead, then you have to program the button differently. The offset 3367 is related only to FS controls. Oh dear. NEVER assign in both places. And deleting entries in FSX is never permanent, it has a habit of automatically reassigning axes and buttons according the the devices it recognises. You should always disable controllers, not simply delete assignments --- unless you are prepared to re-check and re-delete on each fresh load of FS. If you must use FSX assignments at all do NOT try to use FSUIPC as well. It will inevitably lead to conflicts and confusion at some time. If you want to use the POV for Pan view why not simply assign it to Pan view in the Axis assignments in FSUIPC? Well that's never going to work as the button will be sending the "toggle door" controls at least twice even on a Push, let alone the extra one you programmed for the release! Pete

Yes, the interface is 100% compatible right back to FS98 days. 0 = no error. So how is it failing? FSUIPC produces a Log, in the FS Modules folder. Have you checked? There are logging facilities to record application reads and writes. Have you tried checking that way? If you don't understand any of the logging or other data, paste it here and I'll have a look. But an error code od 0 is not helpful. Pete

How many throttle levers are on the G940? If there are 4 and only 2 are seen, then the unit must be faulty, surely? Sorry, I don't understand that. It makes so sense to me. Maybe it's lost in translation? If you only have two throttle levers then, yes, assign them to engines 1 and 2 so that they work correctly for 2 engined aircraft. for 3 and 4 engined aircraft you simply use the "Map" options shown in the Calibration tabs. You can map 1->12 and 2->3 for 3 engines and 1->12, 2->34 for 4 engines. It isn't a problem -- that facility has been included in FSUIPC for many years. Alternatively, when assigning in FSUIPC, you can assign any axis to up to 4 controls, so you could assign there to multiple engines. Your choice, whichever suits you or you find easier. Pete