Pete Dowson

Thanks. I didn't even reallze you could select Network types per program. Where's that done? Is it by specific mention in the firewall? Pete

Found it. This is another very long-standing bug which affects not only the togglebits functions but also the setbits and clearbits functions. Basically the problem was it was changing both the memory area for "Writes" AND that for "Reads", so the part of the code detecting changes to offsets never saw any. Of course they should read the read copy and write the write copy! The earlier bug effectively masked this one! Fixed in 4.949e, now provided in Download Links. Sorry I didn't see this earlier. It was the problem of two different bugs affecting the same functions! BTW this statement from earlier also led me astray: "Since 4.949c in P3D 2.5 the offset ist toggled, but the switch in the panel doesn't move anymore." I couldn't see how it was possible to separate the two actions. It sounds like your add-on aircraft is, itself, reading the offset as well as obeying the FS control event? Pete

What do you mean by "the only designation listed there"? If the key is valid, the registration can be judged to be invalid for only one of two reasons: 1. There is an error in the Name and/or Email field. 2. The date set in the computer is earlier than your purchase date. The latter can happen if your PC is new or has been completely reset (lost its CMOS clock setting). I just select each part, separately (use the mouse, hold the left button whilst dragging over the data to be "cut and paste" (it should actually be "copy and paste" because you leave the original intact). Then, with the correct part highlighted, press Ctrl+Insert. Then, with the mouse select the field in the Registration entry field, and press Shift+Insert. Do this for each of the three fields separately. This is standard in all Windows (and mine is Win7 Pro too). Pete

Okay. Thanks. I'll check it here. Pete

No. That part is about making data arriving from that MCP, from the switches, look like normal joystick buttons. You already have normal buttons. your need is almost the exact opposite! No. FSUIPC cannot possible provide such support for every add-on out there, most of which I've never heard of. Those add-ons which do have offsets assigned mostly only have them because their authors applied for them. But that happens less and less since SimConnect provides a direct interface into FS and saves using FSUIPC. In FS9 days and before it was very different. The only FS controls you'll find are those FS provides. Whether any specific add-on takes any notice of them is up to their authors. There will always be add-ons with functions not known to FS in any case. I think you have the wrong end of the stick. From your post earlier: "To use this method, Enter values on the event lines in the format FSUIPC:0x1234567 where 1234567 is any avaialble FSUIPC offset based on the FSUIPC documentation. The G1000 expects the offset to be an integer in the range of 0 to 255. Each time the value at the specified FSUIPC offset increments, the G1000 will execute the specified function. If the value at the offset increments more than once, then the G1000 will interpret that as a request to repeat the specified function for the number of times the value changed. Once the value reaches 255, your hardware driver software should return the value to 0 and start incrementing again from there" Note the part I've highlit in red. I think that this option is really specifically designed to allow folks to write a driver -- i.e. a program. You could do that as a Lua plug-in. I think it is also only referring to the user of offsets you choose yourself from those freely available for users -- those in the range 66C0 to 66FF. However, you could try doing it purely through button assignments. It needs a value cycling from 0 to 255 and back to 0, changing each time you press a button. You can do than in button assignments by assigning to "offset ubyte incr ", with a different offset (66C0, 66C1, 66C2 .... 66FF) for each of up to 64 functions. You tell the G1000 software the way it says, eg, NAV_ID_TOGGLE=FSUIPC:0x66C0. And so on. Even the option 2 you mentioned looks okay too, and it really is even easier. The FS control numbers from 67000 or so upwards are free, providing you are not using PMDG 777X or 737NGX aircraft. This is from your earlier post: "SimConnect events for the G1000 use any hex number between and inclusive of 0x11000 to 0x11FFF. The number must be coded in the INI file with the 0x prefix in order to be recognized as a SimConnect event. The G1000 will monitor the SimConnect event stream for the specified event, and if that event appears, the G1000 will execute the action to which the event number was assigned. Formatting Example for SimConnect Events: NAV_ID_TOGGLE=0x11000" They refer to these as "SimConnect events" but in fact the FS event or control number system has been implemented for many FS versions before SimConnect was introduced in FSX -- I remember them in FS95. I call them FS "controls", but the official FS documentation calls them "key events". 0x11000 is decimal 69632, so well above those used by FS itself. You can then assign a button to that function in FSUIPC by assigning to "<Custom Control>" with value x11000 or 69632 (note, no 0 in front of the x in FSUIPC). You won't have a limit of 64 controls using this method. Pete

These hat switches, are they on the same device as the buttons and axes you are trying to access? Because if FSUIPC sees the device it will be reading the entire set -- 8 axes. 4 hats and up to 32 buttons. All of them are read together, they can't be separated. if they are not detected then they don't appear to be changing. Are you sure you haven't got some other driver or software reading these devices? That's the only cause i know of for this sort of thing. Pete

Download this updated DLL and try again. Show me the Log please. FSUIPC4949d_TEST.zip Pete

Okay. In the Log I've highlit those lines which prove that the files are being made: So, as far as ASN and FSUIPC are concerned, it is working. Those size notes are logged just before the Bitmap image is written. (There SHOULD be a message the first time the binary file, the one Prosim uses, is written But there's no entry for that, which is certainly odd). Either at least the BitMap file is there and you are just not seeing it (maybe to do with access rights -- try sending them to the same folder as your FSUIPC4.INI and LOG files), or for some reason there's a failure when FSUIPC tries to create them. Currently there's no log entry for a failure to create. Sorry about that. I hadn't anticipated there'd ever be such a problem. I'll add a log entry if this happens -- 4.949d. I'll give you a link later today. Meanwhile please re-check, and try a path you KNOW you can always access. Pete

You'll need to paste the contents of your FSUIPC4.INI and FSUIPC4.LOG files into a message. They were not attached. Also please clarify: is ASN on the same PC as P3D? It is not clear from your message. Pete

Well, let's hope that L-M can reproduce it too, then. Though I think they have worse problem areas like program crashes during flight. At least when it's only at termination you aren't badly affected. Pete

You posted this in "Download Links" subforum. I've had to move it here, to the Support Forum, so it can be answered. Just re-installing Windows does NOT destroy the one file needed for Registration, the FSUIPC.KEY or FSUIPC4.KEY file in your FS Modules folder. It sounds like you also reformatted your disk or else deleted things as well. As with anything you pay for, a back-up is always a good idea and it does recommend this in the documentation. Anyway, though you found your way to the Support Forum THEN into the Download Links subforum, you apparently did not see the FAQ subforum. "FAQ" = "Frequently Asked Questions" and is a repository of the Answers. You will find the answer there in the thread entitled READ THIS IF YOU LOSE YOUR FSUIPC or WIDEFS keys

Okay, thanks, but it should be posted on the Lockheed-Martin site where all the other NTDLL crashes on termination are reported. I don't think yours is just because of LINDA. Lots of stuff causes them. I'm pretty sure it's something in SimConnect doing it, because I can make it happen over 50% of the time by letting FSUIPC tidy up with a "Simconnect_Close" before terminating, as it does without a problem in previous versions of P3D (<3) and all FSX/FSX-SE versions. Current versions of FSUIPC4 don't do the SimConnect_Close on P3Dv3. I have reported it to L-M directly too, but they, of course, cannot reproduce it! Pete

Well, okay, think that. But MakeRunways is used on thousands of systems with no other such reports. Pete

See the FAQ subforum above. The thread entitled Some Saitek axes only provide partial movement

Ah. "Alpha" and "Beta" versions aren't released in any case, only supplied to those who requested any new option or reported a bug which is fixed. Once that change is verified it is released. If the change justifies an Installer build (like something significant, or an FSX-SE or P3D update) then an Install package is released -- 4.949 is the most recent of those. Smaller updates with less general usage needs are supplied as replacement DLLs only. So 4.949c is a release, but without an installer. I call them "interim" versions. Ah, I see. But you said "I don't want Ctrl-F2 be hold for a long time so I didn't use the other option in FSUIPC", but the repeat action would only occur whilst you held the button down. Are you saying you don't want to press it for 2-3 seconds? No, I expect it is something as simple as the DECRement amount being so tiny you don't even notice on the graphic. If at normal repeat rate of 15-20 per sec it takes 2-3 seconds the difference between the axis values for "idle" and "fuel off" is about 50-70 such decrement values. Most such values in FS are 256, which out of a range of 32768 is 128 decrements from "max" to "min". I suspect the "idle" is at 0 and "off" is at -16383, giving your 64 decrements. This is why, for an immediate off setting, you'd be better just using one of the other controls I mentioned. Strange that "lo" does the opposite of what it should do -- sounds like an odd implementation. And no, none of those take a parameter (it is ignored). I forgot to mention the other control which does set a value: Axis propeller set. Try that or Prop pitch set with a parameter of -16384. Pete

Which version? 4.949c? It is there, in the Download Links subforum, and has been for a while. The main installer is still 4.949, 4.949a/b/c were minor updates which didn't justify a new installer build, that's all. Pete

Well, that's a lot to take in. But option 1, assigning keystrokes, is not related to FSUIPC so if you are using that and having problems you do need their support, not mine. Sorry Pete

I asked Enrico to support this long ago, when I first added the WX radar support for ASN to FSUIPC. I even offered to do some of the work if he would only give me formatting information for the ND files. But alas nothing happened. He said he would get to it ...? I have switched to ProSim as of 15 moths ago. Pete

Where was this button? What program? Certainly! Always best to make a thread complete. Please add the results here when you try. BTW you cannot mess anything up -- what's in FSUIPC stays in FSUIPC. It doesn't touch anything external to itself. Pete

You already posted this with a different thread title. Your new title is a lot better (as it shows that you need Oz Runways support, not FSUIPC support), but please anyway see the reply to the original which I already posted. Pete

If the panel is selection by Shift+1-9 on the keyboard, then you can assign a button tto one of the "Panel 1-9" controls in FSUIPC. Otherwise you need the ID of the panel. you'll find this in the aircraft's Panel.cfg file. Then just assign a button to one of the Panel ID controls -- Panel ID toggle, Panel ID open, Panel ID close. Pete

I have never heard of such a problem before, and if it occurs at a different place each time I can only suggest that you have a disk or memory problem in your hardware. Pete

I am sorry, but I have never heard of AST or iCFG. Those are not part of either FSUIPC or WideFS. I think you must be in the wrong place. So, I can't really help. Do you actually have any problem at all with FSUIPC or WideFS? Pete

Sounds like the device doesn't have an assigned Windows ID. That seems to happen a lot in Win8 and Win10. I've managed to program around it in FSUIPC4 for FSX etc, but it isn't possible for FSUIPC 3 (and not just because development for that is discontinued after 12 years). See the FAQ subforum thread entitled Fixing joystick connections not seen by FSUIPC Pete

"Latest stable version"? Huh? Which versions are "unstable"? I do not support anything earlier than 4.949, so please make sure you are not using anything earlier. What "other option in FSUIPC"? Ctrl+F2 is a keypress which has a default assignment in FS to a control ("Prop pitch decr"). If you have to keep it pressed for 2-3 seconds then the action occurring is that the control is repeatedly sent at your standard keyboard repeat rate (20/sec?) for that time. Why on Earth do the aircraft need something like 60 decrements? Perhaps you need to instead consider sending "Prop pitch set" with a value or either 0 as parameter, or perhaps -16383. Alternatively try the "Prop pitch lo" control. That might actually do the same. Pete