Pete Dowson

There's no other components that I know of which will cause these crashes -- maybe it's your WEATHER.DLL which is actually corpt, so you could try repairing that. You can stop FSUIPC reading or writing any weather. Of course any applications you may be using which relies on FSUIPC weather information won't then get it, but if you want to resort to such methods instead of getting FSX working correctly the way to do this is to set the WeatherReadFactor value in FSUIPC4.INI to zero. Pete

Assuming you mean the FS controls, Aileron trim left and right do a fixed increment left or right, whilst aileron trim set, like all "set" controls, take a parameter between -16384 and +16383 and use that to set a specific trim value. Similar to aileron left, aileron right and airleron set for the ailerons themselves, and, in fact, all the other control surfaces. Pete

Except for the GPSout facility in the Registered install, which sends standard NMEA sentences out on a serial port, FSUIPC does not "send out data" (it's up to interfacing applications to read it across a defined interface). And there is no networking code at all in FSUIPC itself, only in the WideFS purchasable option, which in any case only talks to the WideClient program on Networked PCs, not to iPads and the like. You mention a Lua script. I'm not sure whose or what that is, and I have never heard of "AVplan" so I don't know what it uses, but Lua plug-ins for FSUIPC only work with a Registered install in any case. So, sorry, I cannot advise you. Best to seek help from AVplan's author's or support. [LATER] I googled AVplan and FSX and found out what it is you needed. I think you just need to purchase and register FSUIPC, because the Lua script from Jason Beringer does the rest. You just need to edit the FSUIPC INI file to get the main Lua plug-in loaded, eg, from an [Auto] section. AVPlan looks interesting, but am I right in guessing that it doesn't really provide much for those not flying in North America? Pete

There is no such message in FSUIPC. You've got something else doing that. And autosaves are based on a timer, not on when you crash. Look in the Documents Flight Simulator X Files folder for FSUIPC autosaves, if in fact you've even enabled them. Pete

As Ian says, there's a "Cancel" or "Not now" button which you can press (depending on version of installer. Didn't you see this? Perhaps you ought to consider reading the Installation document which is enclosed in the ZIP which explains your options amongst other useful things? Pete

No, it is certainly not an "FSUIPC problem". You either have a corrupted wxstationlist.bin file, or the WX file being loaded with your default flight is corrupted. The only reason it only crashes with FSUIPC running is that FSUIPC is probably the only application on your system which is reading FSX weather via SimConnect. It starts doing that immediately after the last line you see in its log. The files I mentioned are binary, not text, and are read by FSX without adequate checking. Best to just delete them. If you are using a weather program such as ASN you don't need the saved weather files (.WX) in your documents "Flight Simulator X Files" folder in any case. The wxstationlist file in in the same folder as your FSX.CFG file. If gets updated by FSX fairly often and can get corrupted just like any other file being written. If you delete it a default one will be copied there from the FSX Weather folder. Regards Pete

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