Pete Dowson

The other possible reasons I've come across before are: 1. Insufficient power to the device (i.e. needs a proper poered USB hub, not the feeble supply from the built-in USB ports. The X55 I had needed a hub rated at well over 1 amp I seem to remember. 2. Faulty wiring between device and socket. 3. Faulty USB in the PC (try a different socket -- not one of the same pair (USB ports on mobos seem to be in pairs). The ID numbers to be used should be defined in the INI file, not in the LOG. the log reflects what is found. Pete

But the log you showed does show that it was via two keypresses. I don't see a use of the control except by keypress. But there's no log showing that, only a log showing the keypress, pressed twice. Sorry, but I don't see the point of attaching a pic of Prosim assignments. Maybe you need Prosim support to look at that instead? Pete

Look in the FSX options. Move the weather change; rate slider to the extreme left! Or, to do it by program please do read the NWI readme where you will find this: This will be my last reply till at least the 16th as I am away till later that day. Pete

It does indeed. But this complete sequence is repeated: with the second: taking place 4.6 seconds later. The action appears to be instiguated by a Keypress -- 84 is the key 'T'' and it looks at if you have that keypress assigned to 1009. Is that correct? And if so, what has that got to do with ProSim, and why are you pressing that key, twice? Please note that I won't be able to respond further till the 16th as I am away for a few days, starting very soon ... Pete

Sorry, XP is a completely different program to anything derived in the Flight Simulator line. I am not about to take on new work, I am in fact trying to divest myself of much of the work I have. I am 75 this month and looking to relax more and even fly my own cockpit a little more regularly than now! You need to ask in X-Plane forums where I am sure you must find folks who are both Programmers and X-Plane enthusiasts. The work you would probably need would surely centre more around what X-Plane offers than anything specific in the way FSUIPC works and XPUIPC emulates. Pete

Yes, of course. you don't "toggle" elevator trim! What would a toggle action do? Toggle turns on and off!. That's what it means, like a light switch! You can't do that with a trim! Just assign to elev trip up and down! Pete

No, sorry. As I have said before, I am NOT aware of any such facility in FSX ort P3D. did not not read my previous post? I am out now till the 18th. I suggest you do some research yourself. What do you expect FSX to do with your RVA setting in any case. Just put some fog on the runway only? Surely the RV range is only a report, not a setting? I don't see how it could be set separately to visibility! Pete

You are making an error then. make sure your Name and Email address are EXASCTLY the same as when you purchased. Copy and paste all three parts. Pete

I really don't know what you expect FSX to do for the RVA. Isn't that just sureface visibility? As I said before, it isn't anything I've come across in relation to Flight Sims. Can you set it (independently of visibility?) in the Weather Menus of the Sim. I think all the SimConnect facilities do is let you set whatever you can set in the menu. I think all that part of the P3D SDK is the same as that of FSX. I don't think they've done much in the way of changes to the weather system. Did you try searching for "FSX SDK"? All the SDK information, including all of SimConnect's facilities, are of course in the SDK. So you need to download the SDK! Doesn't that semm the logical thing for you to try try try? After all, the P3D information is in the P3D SDK, as I told you and gave a link to! Pete

Ah, yes. Found in the P3D reference: Use one of the following two formats: RDD/VVVVFT RDD/XXXXVYYYYFT where DD = Runway ID (1-6 characters) VVVV = Visual range in feet. May have P (above maximum) or M (below minimum) prefix (following the slash). XXXX = Varying minimum range in feet. YYYY = Varying maximum range in feet. Thanks. I've never seen it before but I should have remembered from way back. I'm afraid I can't actually confirm whether it works or not in P3D. Meanwhile, here's a more direct reference to the SimConnect format for METARs: http://www.prepar3d.com/SDKv4/sdk/simconnect_api/references/world_functions.html#SimConnect_WeatherRequestInterpolatedObservation Be aware, though, that I found that, for the extensions, the format for READING the weather METARs is not the same as when WRITING it! If you enable weather logging in FSUIPC, the log will show lots of METARs being read and how I'm interpreting them. You can also see METARs you are writing -- useful if you use the NWI binary to see the METAR that FSUIPC puts together. I'm afraid that I've not developed the FSUIPC weather interface and its operation for many years now (it dates back to the early FSX versions, 2006), mainly because the third party weather programs like Active Sky have become so good directly interfacing to SimConnect themselves. I'm sure they are doing a better job that I. (You can probbly see the METARs a third party program is sending by using SimConnect logging). If FSUIPC was still the main way for applications to control P3D weather I'd probably investigate using the PDK weather API, instead of SimConnect. However, that would be a big job and not worth it given the existing applications. Pete

Either is okay. The METAR is more direct and sets all apects at once. The binary method can just set some aspects leaving others as they are. FSUIPC's other weather interfaces just translate the binary data into P3D METAR form, reading the existing weather first to fill in any gaps. There's actually no other way then the METAR strings of setting weather via SimConnect. The METAR has extensions over the normal one you will have reference to on the Web. To make full use of the METAR facilities you'd need to refer to the SimConnect reference inthe P3D SDK http://www.prepar3d.com/SDKv4/sdk/simconnect_api/simconnect_api_overview.html#APIReference Scroll down to find the functions where a METAR is sent to set weather observations. There will be a link there to where the format and extensions are defined. FSUIPC sends acording to that spec. (Note that I seem to remember that they start with a date/time reference, before the ICAO. For global weather you set ICAO "GLOB"., but any local weather overrides that locally, so for gloabal weather you need to clear all weather first. There is a global mode you can set through FSUIPC (not via a METAR though). Oh, and I don't remember ever seeing a format like EDDF R18/P2000FT. What is that supposed to mean? Pete

The Forum is one complete entity. it doesn't matter where you enter it, you can always get to all the SubForums AND this, the main forum. The subforums are there so that we can store reference information, with the one exception of Paul's .NET DLL support subforum. The emboldened and red section is a standard text I use to try to reinforce these rules. Sorry if you take objection for some reason. It would be far easier for me to simply keep deleting posts in the wrong area, as happens in most other forums. Would you have preferred that? Pete

Ah, sorry. missed that. I'll need to update the documentation to mention that. It disables all SimConnect stuff, from all programs, just excepting Menus. There isn't really a good way I can make this into a menu, and giving a name in response isn't possible. The only other way would be coming up with a dialogue window every time, but that would be horrible. Thanks, Pete

There were never boxes around clickable parts The earlier versions (FS4, FSX and P3D1-3) used hooks into the ctual code to trap the mouse click. that's being done for me now by P3D, part of its Programmer Development Kit (PDK). Makes the code in FSUIPC much simpler and more foolproof! 😉 What "something"? Please give me a specific example, with a specific default aircraft. All the clickable switches I can try here provide the correct response. "SimConnect" I assume you mean! :-) Test it first, via TAB, as it says. Pete

You must be doing something wrong. Did you click "Creat mouse macro" and give a name for the macro file to be created? Then OKayed out of FSUIPC Options? Er, why do you think you get boxes around clickable things? The facility does nothing to the panel display. it just sits there awaiting your mouse click on such a "clickable thing." It is working perfectly, I assure you, and as documented and illustrated. Pete

MOVED FROM "USER CONTRIBUTIONS" SUBFORUM PLEASE DO NOT POST SUPPORT QUESTIONS TO REFERENCE FORUMS. THIS IS NOT A "CONTRIBUTION" One of your add-ons has a problem. It might be using FSUIPC, or it might not. "FSUIPC_Unloaded" means FSUIPC is not actually there any more -- i.e. it has terminated. Maybe something else you are using it trying to interface with it too late. Try stopping all add-ons then re-enabling them one by one till you find it. BTW the currently supported version of FSUIPC5 is 5.14. Pete

You can set the time, but I don't think you can just do general settings such as !Day, Night, Dawn, Disk" For weather, the only safe way is to set the complete META in pretty much standard format. You can try using the other interfaces FSUIPC provides, but the results are not always guaranteed. And you'd need to set global Weather mode and set the weather change slider to zero to prevent the weather you set from being changed. Why is it doing that? Are you pausing the simulator? Just setting the position etc doesn't pause the sim. Are you using P3D4? Text messages on screen can be inhibited via the user options. Or you can change them in the main sim CFG file. Really what you want to do can be done more efficiently using the SimConnect interface directly. FSUIPC was only ever intended to provide compatibility with previously written programs before SimConnect was designed (with my cooperation i should add) back in 2005. As a layer on top of Simconnect, It is still used a lot for relativel;y trivial things, and to read inforation from the sim, but your application sounds rather more ambitious. Pete

Go to FSUIPC options, under "AddOns" menu, click the Key Presses tab. On the right to can go through all your normal FSUIPC keypress assignments, uning "Next" and "Previous" buttons, and "Delete this entry" for ones you don't want. Also have a look at the "Hot Keys"tab. Check you've not got any hotkeys you don't want assigned. You can change of clear them. Pete

Yes, it is possible. you can actually manipulate the data received from an axis before it goes to calibration. Take a look in the Advanced User's guide. The section entitled Axis Assignments startng on page 41 gives details in the subsection "Additional parameters to scale input axis values" on page 42. you will have to edit the assignment line in the FSUIPC5.INI file. In this case, if the input value is going from -16380 or so to +16380 or so, you would just need to multiply the value by -1, so find the relevant assignment in the Axis section of the file, and add ,*-1 at the end. If the input range is "lopsided" (i.e not the same at the negative end as the positive) then it is more complicated -- you'd need adjustments -- but it is still possible. Just let me know if that looks to be the case. (Example: I have some PFC devices which only provide positive inputs. Didn't ACE stuff used to be made for them by PFC?) Pete

You are missing the A and B GUID lines. Copy the 0 and 1GUID lines and change the 0 and 1 to A and B respectively. I

WideFS is only for accessing FSUIPC from a networked PC instead of the sim PC. Of course you don't need to buy it if you don't need to do that. And WideServer is built into FSUIPC4 and FSUIPC5. The separate WideServer.DLL only applies to FS3 and before (i.e. FS2004 and earlier). Pete

Good. Now please remember two things: 1. Find and read the documentation 2. Title any further questions here with words which explain the real subject, so you attract the right help. Next time I see a post from you, I will first ask "have you read the documentation yet". If you still say no or you can't find it, I shall not respond further. Pete

Thanks Paul! I hoped someone who's actually got the 737NGX would chip in. That's why I changed the thread title! Pete

As I said twice now, and I'll say again These are listed in a file in the SDK folder of your PMDG aircraft, at the end of the one with filetype ".h" (sorry, I don't remember the name itself -- I don't use PMDG aircraft). Go find that file first! Then look at it in an editor. There's a long list of data then, at the end, a long list of controls. Find the one with the name matching what you want to do. I'm sorry, but I do not have the aircraft installed. I cannot give you explicit instructions -- you should really go to the PMDG forum for that, it is their aircraft and their SDK and file, after all! Once you have the number, then you assign it by selecting <custom control> in the dtop down. There will then be a place for the number. Why bother? When the dropdown appears just start typing what you want. For instance if you type x the list will move to the start of the x's. This is normal Windows behaviour for ordered lists like that. Works in Windows explorer too if you sort by filename by clicking the top of that column. And anyway, why so many A's. Wouldn't just one or two do, max? If you read more carefully I'm trying to guide you to the rihght places. I cannot tell you more exactly what to do for an aircraft I don't have! Oh dear. You were telling me how you were assigning to the mouse macro you created, but then you said you selected a switch by the name APU ... which isn't a macro name and is not supported by the PMDG aircraft in any case! I didn't say you are not going to make macro assignments! Stop putting words in my mouth which I am not using. I have been try to help you do things. I am NOT telling you to do anythig. You please yourself. I am only trying to give advice which you then ignore whilst denying that you are ignoring it. You are talking about this, but that function doesn’t actually refer to anything, and that is my made mouse macro that doesn’t work. What are you talking about? The function refers to a macro in the macro file aaaaaa.mcro, the one which I suggested be edited to make it work! you can't have anything in the list that doesn't refer to anything! That's nonsense! You didn't even read the Installation and Registration guide which was included in the ZIP for for the install package? That clearly tells you where the documentation is! Sorry, I am not replying to you again until you have at least referred to the appropriate parts of the documentation. I would recommend reading it all once, then just using it for reference. This forum is NOT a substitute for the supplied documentation! Pete

I understand all right, but I need the actual detail -- especially the NAMES of the controls you are assigning to! That's the most important thing of all! That is what should be activating. Last time you said " where it says “apu-start” or something like that" which is imprecise and useless, and it is even missing the macro file name! I see you've been more precise later on and I'll get to that. Why on Earth call it by such a weird name? Does your A key stick, like apparently you mouse button? First, why are you using Profiles? Are you planning on having several aircraft each with different assignments and calibrations. If so, that's fine -- but why not a sensible name, like "737NGX"? That is NOT a control leading to a macro file! Haven't you referred to the documentation before ploughing ahead and trying to use macros? Macro assignments nee the macro file name then a : then the name of the macro inside that file. For example, these are your weird macro filenames: So, you have two usefully named ones (b738 and test), 4 silly named ones, two using your sticky A key. If the b738.mcro file (which you didn't show me even though I asked you to show the the macro file you are using) contains, say, a "taxi" macro, then the assignment dropdown list would contain "b738:taxi", and that is what you'd assign to! Please do refer to the documentation provided! Moving on to the assignments you have actually made for your AAAAAAAAAAAA ... profile (!) Only one of those is related to any macro file, -- Q to "aaaaaa:taxiliht'. The others are all default FSX-SE controls, which probably don't work at all on the PMDG aircraft (an exception being FREQUENCY SWAP which may do as I think PMDG use the default radios). So I would need to see the macro file aaaaaa.mcro. If it contains a part "RX3f000*Xffcc,23" then I suggest trying it with the ,23 deleted. Mostly that part should be omitted -- your sticky mousse button probably stopped that. But as the documentation states, you do sometimes have to experiment with that parameter. If you look at the macros in that User Contributions thread you'll see most are without that parameter, but some have 31. I think those switches are actually dials, and one variety turns them one way, and the other the other way -- maybe left and right mouse buttons? Earlier you said: "I tried the pmdg controls, no success either. If I for example set the letter q to taxi light (pre made by pmdg), when I go into my cockpit and press q, nothing happens" Oh, yes: what do you mean by "pre made by pmdg'? Apart from that odd part, the PMDG controls are "custom controls". You can't assign by name, but by number. You obviously didn't read my advice there at all -- I said: You should know that, whilst many folks have successfully used Mouse Macros on PMDG aircraft, the Boeing range does have a full set of assignable "custom controls". These are listed in a file in the SDK folder of your PMDG aircraft, at the end of the one with filetype ".h" (sorry, I don't remember the name itself -- I don't use PMDG aircraft). then, later: AND more reliably using the controls supplied by PMDG themselves, as just mentioned. Note that to use their controls you need to compute a control number (just adding two values, in fact). Then you can assign in the FSUIPC drop-down assignments list to <custom control> and enter that number, and any parameter it may need. and later again: I really would recommend using the PMDG contorls rather than mouse Macros, as they are much more reliable and easier to program once you work out how to get the numbers. I can help with that. But all to no avainl. Youappear to have skipped over all this and NOT taken my advice. 😞 And did you even bother to go and read that thread in the User Contributions, which I found for you? You only had to click the link. You keep saying you are taking advice, you are giving details, but as you can see, you simply aren't paying attention. I feel I'm really wasting my time trying to help.:-( Pete