Pete Dowson

It cannot be FSUIPC. You have to look elsewhere. Pete

Exactly as I hypothesised. Okay. Good. You need to use "Setbit" for pressing a button/switch, and "Clearbit" for releasing it, both with the same value. In your picture you've used Set value for a byte, which will affect 8 buttons, not just the one you want to change! Values are 1 for button 0, 2 for button 1, 4 for button 2 ... 128 for button 7. Pete

Yes it is. It is clearly listed as "Extinguish engine fire". All controls listed in the document, and more, are in the assignments dropdowns. They are all in alphabetic order. If you can't scroll down for yourself just press the 'E' key to get close. There's no separate pricing. Pete

Mouse trim, mouse move and mouse look options are described in the User Guide and shown on the Miscellaneous options tab. Pete

I thought about this overnight, and what I am hypothesising is wrong is that whatever software you are using to set the virtual buttons offsets is doing something like this: When a button/switch is "pressed", is is WRITING a value to offset 3360 (which corresponds to virtual joystick 72). For button 2 it writes 4, for 3 it writes 8, and so on. By writing a value rather than simply setting a bit, it effectively means only one button/switch can be seen as "pressed" at any one time. The correct way of using the virtual buttons offsets is by ORing the value into them to set "pressed" and ANDing the bit out to set "released". So each time a switch is pressed or switched on, the others are set off or released. But, additionally, it looks like the value 0, to show the button released, is not being written when the button is released. Nothing is written when a button is released! Now, this hypothesis explains all of your symptoms. (But it would be much more efficient for you to actualy tell me how it is all programmed). If the software you are using has no facilities for handling bits instead of byte values, then you can only do what you want by using only one button/switch per byte. i.e. offsets 3340, 3341, 3342 ...3363 (36 of them) all with only values 1 (on) or 0 (off). They would be seen in FSUIPC as buttons 0, 8, 16, 24, on each of joysticks 64 to 72 inclusive. Regards Pete

I still suggest you test with FSX controllers actually disabled. It's easy enough to do and loses nothing. After the test, if you wish, you can re-enable them. Okay, so this shows conclusively that FSUIPC is sending just the one control, but two events are being seen. The others are NOT from FSUIPC, so must be either from FSX or some other software. There is no way I can determine what other software they are from, but I still think the most likely source is FSX. I think this is made even more likely by the fact that the default FSX assignments ("Standard.XML") include these two: <Entry> <Index>7</Index> <Down>GEAR_TOGGLE</Down> </Entry> [/CODE] i.e. button 7 = GEAR_TOGGLE, and [CODE] <Entry> <Index>4</Index> <Down>FLAPS_INCR</Down> </Entry>[/CODE] i.e. button 4 = FLAPS_INCR. So, your "I verified that there were no assignments" was not very complete, I think! Anyway, always try disabling controllers in FSX. It's the only way to prove it one way or the other. Regards Pete

Didn't you search on the word "Fire" as I said? You would find an offset which has 4 active bits in it, one for each engine. 1 = fire, 0 = No fire. You can read and write it You said you wanted an offset. If you want to use a control, why not just assign your buttons to EXTINGUISH_ENGINE_FIRE with parameter 1 or 2 respectively? I don't understand why you just don't go ahead? Pete

It's rather inefficient and it may not work predictably. Every time offset 9420 or 940B changes the thread has to be re-entered 2 times for 9420 and FIVE (!) times for 940B. Since it isn't re-entered when already just reentered (as it will be), the results will be rather unpredictable. You should have just one event per different offset. So, try it rewritten this way: gfd.SetBright(GFWP6, 0, 15) light = false function Warnings(offset, value) if logic.And(value,0x0001) ~=0 then gfd.SetColour(GFWP6,0, 0, 2) gfd.SetLight(GFWP6,0,0) else gfd.ClearLight(GFWP6,0,0) end if logic.And(value,0x0002) ~=0 then gfd.SetColour(GFWP6,0, 1, 6) gfd.SetLight(GFWP6,0,1) else gfd.ClearLight(GFWP6,0,1) end end event.offset(0x9420, "UB", "Warnings") function FLASH() if light then gfd.ClearLight(GFWP6, 0, 3) light = false else gfd.SetLight(GFWP6, 0, 3) light = true end end function APIndicators(offset, value) if logic.And(value,0x0008) ~=0 then gfd.SetColour(GFWP6,0, 2, 6) gfd.SetLight(GFWP6,0,2) elseif logic.And(value,0x0010) ~=0 then gfd.SetColour(GFWP6,0, 2, 2) gfd.SetLight(GFWP6,0,2) else gfd.ClearLight(GFWP6,0,2) end if logic.And(value,0x0020) ~=0 then gfd.SetColour(GFWP6,0, 3, 6) gfd.SetLight(GFWP6,0,3) else gfd.ClearLight(GFWP6,0,3) elseif logic.And(value,0x0010) ~=0 then gfd.SetColour(GFWP6,0, 3, 2) gfd.SetLight(GFWP6,0,3) light = true event.timer(500, "FLASH") else event.cancel("FLASH") gfd.ClearLight(GFWP6,0,3) light = false end if logic.And(value,0x0040) ~=0 then gfd.SetColour(GFWP6,0, 4, 6) gfd.SetLight(GFWP6,0,4) else gfd.ClearLight(GFWP6,0,4) end end event.offset("940B", "UB", "APIndicators") function SPEEDBRAKEARM(offset, value) if logic.And(value,0x0004) ~=0 then gfd.SetColour(GFWP6,0, 5, 3) gfd.SetLight(GFWP6,0,5) else gfd.ClearLight(GFWP6,0,5) end end event.offset("9414", "UB", "SPEEDBRAKEARM") [/CODE] Regards Pete

Did you disable controllers in FSX? If not try that and re-test. FSX has a habit of automatically re-assigning things if it thinks the connection is new for any reason. If you still have double assignments with controllers disabled in FSX, and you aren't running Saitek's own software (which I believe can also make assignments?), then you'll need to show me your FSUIPC4 ini file -- at least all of the [buttons] sections, and also tell me which buttons have the problem (joystick and button numbers). You could also check things for yourself by using the FSUIPC4 logging facilities -- try both the Button and the Event (non-axis) logging options. Regards Pete

Sorry, I don't quite understand what you are saying. If you know it "installs" how can you tell if it "disappears" straight away? What do you actually see on screen? If it installs then there will be an Install log in the same folder, the FS Modules folder. I'll need to see that if you believe there's a problem. Regards Pete

So, i repeat my question: ... did you try putting in the client ServerIPAddr and Protocol parameters, as suggested in the little "must read" part of the User Guide? That shows that the Client simply doesn't know where ther server is. It is not receiving the Broadcasts, so either the two PCs are on in the same WorkGroup, or there is a block. If you would please try to do as suggested, telling the client the server address and protocol to use, then we will know. Pete

Is that a default FSX aircraft? If not it may not obey FSX default methods. Did you check the Offsets list installed in your FSUIPC documents folder? Just search for "fire". There's an offset which flags fires in each of up to 4 engines. You can set the flags to start a fire or clear them to extinguish one. Pete

Where did you find 69997? That sounds like a PMDG 737NGX control. What is its description? [LATER] Okay, 69997 is 69632 + 365, so according to the PMDG document it is So, if a parameter of 1 increases it by 1, didn't you try the obvious, a parameter of -1? Sorry, but i do not have the NGX installed and cannot solve all PMDG questions. You have to work it out yourself or ask at the PMDG forum. Regards Pete

I am only frustrated because i don't have all the information. I've no idea how you are setting these offsets from your buttons/switches. For it to register as joystick 72 you must have somehow assigned it to operate a virtual buttons offset. How and why? I think this is more the area where your mistakes must be. As I have said several times before and which you have apparently ignored or missed, this is because it doesn't see a button release when you release it. If it doesn't see a button release is will not be able to register another press! It makes no difference whether you use the offsets method we were discussing before or the controls method suggested afterwards. If the button/switch appears to stay on forever after you operate it, at least till you press another, then it will do EXACTLY what you have described. I don't understand why you don't believe me when i explained this to you! :sad: Why ignore so much of my replies??? :-( :-( :-( You keep repeating tihs, the exact same thing, and I keep answering you with the reason. Why can't you actually read what I write? And then you are surprised that I am getting frustrated with you? The log would recerd EVERY single change in the switch, but there is NO change -- once you've pressed it it remains looking pressed until you've pressed another, different switch. How many more ways can I explain this simple fact to you? The problem obviously lies in how you've programmed the switches in whatever program you are using which is writing to the virtual button offsets. That is where to look, and where I have no informatation whatsoever from you!!! Pete

Sorry, I don't know what offset 940B is nor what you see when you run this. What is using offst 940B in any case? I think that belongs to "iFlyToFsuipc". Can you describe what you see wrong? Have you tried using the Debug/Trace option to see what happens? Pete

Yes. Pete

All things to do with FSUIPC are in the FS Modules folder alongside FSUIPC! All things to do with WideClient on the Client are in the folder you placed WideClient into! (It really isn't hard!). You'll be best just pasting them into a message here. Don't try uuploading the files themselves. Pete

In order to purchase from SimMarket you DO open an account! It is in the name of your email address and user name. In order to ask SimMarket anything you have to log into your account and raise a Problem Ticket. I think you are completely misunderstanding what you have done and how to proceed. Yet you MUST have provided an email address and user name to SimMarket to have placed the order in the first place! There's no way to have paid in any other way. And your registration will be in your logged on name and email address. You MUST open your account in order to retrieve your registrations. That's the only way I know! Pete

I'm afraid there is no way I can help without information. After a problem session you need to close FSX and WideClient, and show me the FSUIPC Log, the WideServer log and the WideClient log. Pete

Yes, all that happens because when you release the switch there's nothing seen in FS. It must be something to do with whatever is BETWEEN those 4 terminals + ground and the USB port or whatever it is you've connected it to! How does a switch send an offset? You must have some hardware and software in between! Getting information from you in order to help is very very difficult! One little tidbit for every 5 or 6 exchanges. Why can't you explain everytihng in one go? There's so much you appear to want to keep secret! Pete

Well i don't know how they'd program it in a real Lear, but if it is doing what it appears to be doing, and you cannot tell when it is released, then holding it in one position is not going to be the way to trim. Maybe it needs to be wired up differently to the way you've done it, or connected to your PC differently. I'm guessing it isn't plugged directly into a USB port because a Lear35 seems unlikely to be controlled by a PC with USB ports. Pete

How do you run it? From a shortcut on the desktop? Right click on that and select Properties, and read the path it uses. That path MUST have a Modules subfolder in it, and the path: C:\Program Files (x86)\Microsoft Games\Modules does not exist, which means that one and only FS9.EXE you found cannot possibly be the one you are running from! The correct folder has many essential subfolders in,, not just Modules. -- Aircraft, Sound, Scenery, Texture, Gauges, etc etc. On Microsoft's website I assume. Try Google otherwise. It's many many years since I last installed it. I'm amazed you are still on the original FS9 release! Regards Pete

Okay. So now we have the answer. The button you are using is acting exactly like a toggle switch -- one press and it is on, another press and it is off. Like those buttons on table lamps. You are not going to be able to use it as you had hoped. The best you could do is program both "press" and "release" to do the same thing, without "repeat whilst held" checked, and just keep pressing it over and over for repeated trim adjustments. There is not going to be any other way to get anywhere near a proper trim control with such buttons. Reading back a little too, even that might not be possible. You said once pressed further presses had no effect -- until when? Something must allow you to press it again! Maybe these buttons remain pressed until another button is pressed, like a sort of reset? You should be able to see what is going on -- either in FSUIPC or in the Windows game controllers applet in Control Panel. To be honest, I'm amazed you have a device which does such a thing. I know the VRInsight serial port devices are like that -- you can't tell if the button is pressed or released, each press/release gives one message only. Looking back you said " I'm trying to program my yoke top hatch switch". What is a "hatch" switch, and what sort of yoke has one? Regards Pete

Right. so this is where you pointed the Registry Repair program to when it wanted to find FS9. Right? That seems most odd, as usually, if you let FS install itself into its default location it would be in a subfolder below "Microsoft Games", specific to Flight Simulator not all Microsoft Games. And it is 9.0? You've not applied the essential FS9.1 update which fixes a multitude of bugs? This definitely means the place you pointed the Registry Repair tool to is incorrect, because it does not contain a Modules subfolder. Since 99% of the FS9 code resides in that folder, FS9 couldn't possibly load and run without it. It looks to me as if you have pointed to some rogue or extra copy of FS9.EXE which is NOT the one you actually ever use. Maybe you should look at the Properties of the shortcut you use to run FS9 to find out where it really is? Well, it would work, but if you are able to run FS9 as it is, it shouldn't be necessary. You should get the correct path instated. If there is a rogue FS9.EXE in the folder you pointed the repair tool to, rename or delete it, and re-run the repair to point to the correct FS9.EXE, the one you actually use. Pete

Sorry, that isn't my installer. That is someone else's program which just repirs the registry pointer to FS9, and it sounds like it did exactly that, successfully. Why are you confused by it? It says it worked. What more would you expect it to do? Pete