Pete Dowson

You are making an error. All three parts (name, email, key) must be exactly correct. Why are you needing to re-register in any case? Reinstalling FSUIPC doesn't require its files to be deleted beforehand. Your KEY file, which you should have a backup of in any case, is all that is needed for the registered install. Pete

No, only Lua currently provides a method of reading them. The problem with providing access through an offset-based interface is that L:Vars are only identifiable by name, and need requesting via the Gauge interface into FS. Whilst writing a name as a string into an offset in order to get something done (like load or save a flight or a paln) is okay -- it's an action initiator and requires no reply -- having one which then has to await a response is not so nice. The question which would arise is how is another request, maybe from a different program, going to be handled? Who gets which reply and where? How can they tell? If there was a desperate need I might try to work something out, but I implemented Lua as a more convenient way of adding facilities to FSUIPC without such horrendous complication on top of the already pretty unwieldy interface inherited from FS6IPC long long ago. So, I'd much rather Lua be used for such things. It is better to add facilities to Lua to implement new things than try to implement them in FSUIPC proper. Regards Pete

I don't think it can be done from a separate process. I have no idea what Yahoo messenger is. Sorry. you'll need to do research on Windows programming websites. Pete

If it is not showing any text or graphics, what is it actually showing "on top of" FS2004? If it doesn't need to show anything it doesn't need to be "on top"! In any case a process running in full screen mode cannot share that screen with other processes. That's the whole point of full screen mode. What you want is called windowed mode. Pete

Sorry, but I don't understand what you mean. Are you saying everything is working now? Pete

Okay. You Server is not sending broadcasts to your Client. They are probably in different workgroups. Didn't you read any of the WideFS user guide at all? The bit you need to refer to is the bit entitled "Configure your network", the bit with the red notice saying IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! Have a go, and let me know. Pete

All controllers are basically the same. First of all, decide WHY you are wanting to use FSUIPC. What is wrong with the normal FS assignments? If you are needing to have different controls assigned for different aircraft, then FSUIPC comes into its own, but if you only have the one controller, and a simple one like the Sidewinder at that, what is it you think FSUIPC will do for you? If it's only a matter of better or more precise calibration, just refer to the Calibration chapter in the User Guide and follow the simple numbered steps. That's what they are there for. I can answer specific questions, but since everyone's use of FSUIPC is different -- it is a general toolkit after all -- there can be no such thing as a "tutorial" to suit everyone's individual and specific needs. If you purchased FSUIPC I assume you must have had a good reason? Did you not read about it first? All the documentation is available before you purchase, so it would have been easy to determine whether it was what you wanted, don't you think? As far as I can see, ASN needs no setting up. Just install it, run it, and go fly. What setting up do you want? Anyway, Active Sky's own support place is where you need to go for more on this. I can't support every one's programs! Sorry. Pete

Don't you understand this part? "If you still can't work out what you are doing wrong, send me the details, and I'll try to help by email. Do NOT post private information here. My email is petedowson@btconnect.com."? If not, then I'm sorry, but I cannot help. Pete

Are you using the latest, supported version of FSUIPC? (4.929 for FSX or P3D, 3.999z8 or 3.999z9 for FS9). Did you buy the correct version? The keys are different for FSUIPC3 and FSUIPC4. Is your computer's system date correct? If it is before the purchase date it may make the key look invalid. The process of key generation is entirely automatic, and the methods used in FSUIPC's installer have not changed for many years, so I'm sure you must be making an error. f you still can't work out what you are doing wrong, send me the details, and I'll try to help by email. Do NOT post private information here. My email is petedowson@btconnect.com. Pete

But if it doesn't see it, it wouldn't act upon it and send another control. It would simply be the same as if it didn't occur. That logging of the buttons being pressed and released is in-line with the code which acts upon those events. If the logging is enabled, you can't get one without the other. Pete

Use event.button. That makes sure the relevant joystick is scanned. The only other way would be to pre-declare the joysticks needing scanning, but either way you'd need an event driven plug-in, so why not use the purpose-made facility? Pete

I think you are making an error, then. Did you retrieve the key from your account? Are you cutting and pasting all three parts -- name, email, and key, properly? Every part must be EXACTLY correct! Pete

Hmmm. It should be looking at the "combustion flag" instead. N1 could be >0 just because of wind -- you see the blades rotating all the time at airports. To do it from a Lua plug-in you'll need to use the spoofing offset, 0024 -- see the example Lua "liar.lua" in the package included in your FSUIPC documents folder. Pete

N1 is a result of throttle setting. It's an output not an input. What are you trying to do? You set the N1 you want by an appropriate throttle value. It may be temporarily settable when you stop the simulation engine overwriting it, as in paused or maybe slew modes. Pete

Do you mean you aren't able to get a bounce, or that you do but they aren't recorded? Pete

Did you try looking in your FSUIPC Documents folder, in the FS Modules folder? The Offsets Status PDF there is fully up to date to 4.924, and there's not been any offset changes since then. The one in the SDK is updated less often -- the one installed by the FSUIPC updates are always up to date. I do get around to updating the SDK from time to time, but it is extra work and there's always more pressing matters it seems. This is why latest data in always included in the main installer, and folks are expected to keep their FSUIPC updated (at least if they want support). Pete

But the log from FSUIPC shows no other "spurious" button press at all. If it isn't seeing one it won't be sending the additional control. That additional control is certainly being sent by something else, most likely FS itself, through assignments there. I really don't see how. The log showed only the correct button being seen by FSUIPC, yet two controls being issued. Therefore the other was from a different source. When you fail to disable controllers in FS, as I assume you have (else why no axis assignments in FSUIPC?), FS will sometimes make automatic assignments to those buttons it knows are available on the devices according to its list of device types. This is why you have to be very careful. Generally it is best to either do all assignments in FS and none in FSUIPC, or vice versa. Pete

The FSUIPC and Server logs you supplied show everything is good at the FS PC end, with the Server ready and waiting. Where's the WideClient log? I can't help with only one half of the story. Pete

It "works" in that it provides the interface into FS. That part of FSUIPC has always been free for end users, just normally subject to agreement for the application publishers -- in this case Aerosoft I assume. I simply advised you to install the current version, if you want my continued support. I also now suggest that after you install it you read some of the User manual before you decide whether you want to buy it. There's no point in buying it before you know whether you want to use the facilities that would provide! Installation is easy, and there's a document included which explains both installation and registration. There is no "older" version available -- FSUIPC version 4 was certainly first published for FSX, which was released in 2006. FSUIPC itself (version 1) was first published in 1999 -- for FS98 and FS2000, so really it is 15 years old! But it has been updated continuously since then and, as you have found, the latest version of the full Installation is 4.929. The link on SimMarket's purchase page is EXACTLY the same as the one on the Schiratti page. Both always get the current version. There's no point in downloading it again. If you have looked at the documentation and have decided you want to Register, just do so. You are NOT purchasing a downloadable file, just a key to unlock the user facilities in the version you have! There is also a subforum here called "Download Links" where interim updates are provided as well as lots of other useful things. There's even another link there to the full install. At present the latest interim update is 4.929c, released yesterday (12th March). Interim updates are simply replacement DLLs to be copied directly into the FS Modules folder. No installer. Pete

You make the 4th person unable to paste. I assume you are using Internet Explorer? Somehow some recent update from MS has really clobbered things. Please see this thread where I believe the answer was found: http://forum.simflight.com/topic/76255-wide-fs-connection-fsx/?hl=%2Bcut+%2Band+%2Bpaste#entry464896 Pete

If you want a private exchange use petedowson@btconnect.com. Pete

If you want to make a habit of stopping them then, if they are looping have them test a flag and use LuaSet to set the flag, upon which they exit tidily, or, for all Lua's with one notification, have them test an offset or button instead. You can use the user offsets 66C0-66FF. If they are event driven (which is a better design in any case), then, again, you can have an event based on an offset change, which leads them to exit. Ah, well 16-30 isn't as many as I thought you meant! ;-) Not so bad. It might be a good idea to start them all from within an [Auto] Lua in any case. I actually use ipcReady.lua, to save even having an [Auto] section. (ipcReady.lua is automatically started in any case and is actually intended for just this purpose, starting a batch of Luas). Pete

Why do you have so many in the first place? You realise each one takes a thread and is running in your FS PC? You can kill all Lua plug-ins using the LuaKillAll control. To start them all again you'd have to write another plug-in which uses RunLua to start them all, or program a button with them all assigned to it -- an INI file editing job. Of course if any of them are aircraft or profile specific (i.e. [Auto.<name>] loaded), all you need to do is change aircraft back and forth. Note that killing Lua plug-ins can be hazardous. Regards Pete

Well, you have no Keys assigned in FSUIPC, so I don't understand your earlier reference to assignment of Ctrl+. in FSUIPC. Your button assignments are pretty simple: [buttons] ButtonRepeat=20,10 1=P0,8,C66241,0 master battery 2=U0,8,C66241,0 master battery 3=P1,5,C65752,0 parking brakes 5=P1,4,C65752,0 parking brakes 6=P1,6,C65759,0 flaps decr 7=P1,7,C65758,0 flaps incr 8=R1,11,C65607,0 elev trim down 9=R1,10,C65615,0 elev trim up In this sequence:from the log: 307510 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR 307556 Button changed: bRef=0, Joy=1, Btn=5, Pressed 307556 [buttons] 3=P1,5,C65752,0 307556 FS Control Sent: Ctrl=65752, Param=0 307556 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES 308149 Button changed: bRef=0, Joy=1, Btn=5, Released that first FLAPS INCR command has occurred with no button pressed at all -- at least in the 4 seconds since you enabled the button and event logging, so I don't know where that comes from. But when you pressed button 4, here: 311519 Button changed: bRef=0, Joy=1, Btn=4, Pressed 311519 [buttons] 5=P1,4,C65752,0 311519 FS Control Sent: Ctrl=65752, Param=0 311519 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES 311519 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR 311940 Button changed: bRef=0, Joy=1, Btn=4, Released although FSUIPC only sent the one control, the FLAPS DECR control is sent as well. Not by FSUIPC -- so I believe that button is also assigned in FSX. I notice you have no axes assigned in FSUIPC, even though you are using a yoke, pedals and a throttle quadrant. So either those are assigned in FS or being sent by some other control program. That is where you will find your duplicate assignments. Pete

Most likely poorly calibrated controls. But check that your aileron trim is centred too. If that's off-centre you might get such a result because you are trying to find an off-centre centre on the aileron to compensate. Also check rudder and rudder trim. In that case, if it isn't due a very bad aircraft model, or the trim being off centre, you either have a faulty potentiometer, or it is a logarithmic one not a linear one. A log pot will have rapidly changing values towards one end. Apart from the above, test with a default aircraft. After all it may be just that model. Pete