Pete Dowson

Anything more than the maximum set in FS or FSUIPC will be set to that maximum. That's why they are called maxima! ;-) Please read the FSUIPC User Guide, the section on the visibility options. Change them if you don't like them. The user guide provides the description of the user facilities, and especially for the weather filters he can apply. Have you never looked at the documentation, or browsed the user facilities offered by FSUIPC? As explained at length in the User Guide, the "random extend METAR maxima" is a useful facility for generating visibility distances beyond 10sm or 9999 metres when the METAR explicitly specifies those figures -- many METAR reports generate those values to simply mean "at least ...". they do NOT mean "restricted to" or "is". Generally it is the automated stations which provide these fixed maxima. The option is defaulted 'on' because it is so annoying never having visibilities more than 10sm or 10km. Well you can turn off the FSUIPC options, but you cannot exceed FS's own maximum. You can also force FSUIPC to bypass all of the filter mechanisms (and so risk annoying your user! ), by using the clearly documented NW_SETEXACT command -- did you miss this one too? Regards Pete

If it can be calibrated / configured in Windows Game Controllers, and uses one of the standard Joystick Axes XYZRUV supported in the original Windows joy API, then both FSUIPC3 and FSUIPC4 will see it in their axis assignments. If however it uses one of the later DirectInput-only axes, then only FSUIPC4 will see it. Scanning the installation instructions it seems to indicate that is comes across as "Z-rotation", which I think is normally mapped to "R" in the older interface, so it should be seen by FSUIPC3, but there's no way I can possibly guarantee it. It depends on how is defines itself in its USB handshaking I think. Sorry, I'm not about to buy one to try it for you. Perhaps you can ask the suppliers. Regards Pete

Can you explain what you are talking about? Also always state FSUIPC version number. And try the latest updates. Whatever it is you are having problems with might already be resolved and it would save everyone's time. See the Announcements. Pete

Okay. That eliminates most things. What is wrong is that your Registration Key doesn't work. This can only be for one of two reasons: 1. Your PC's date setting precedes the date of your purchase of a registration, so making it look invalid, or 2. Your registration key is an illegal one, possibly made by a pirate key generator. If you believe it is neither of these, please ZIP up the FSUIPC.KEY file and send it as an attachment to me at petedowson@btconnect.com . Meanwhile I suggest you remove it from your FS Modules folder, to make your FSUIPC unregistered. Then your add-on will work. Pete

Sounds like either there's a serious bug in that program, or you have a registration problem. I could tell from the LOG. Yes, just paste it into a message. It will be quite short. You've not enabled any extra logging I hope. Don't go to the Logging TAB in FSUIPC, simply run FS as usual, get the error, close FS, show me the log. Regards Pete

That is too far out of date. I cannot support anything older than 3.85 at present. If you want more help, please update first. Then close FS before getting the Log for me to see. Regards Pete

Ah, that "Valid for FS2k only" dates from when the offset was added -- in FS2000 times. It wasn't valid before FS2000. Do you see the two columns to the right, both marked "Ok". One is for FS2002 and the other for FS2004 (the heading is on the first page of the list). It means it is "ok" for those. That's why the columns were added. Sorry, I never seem to get enough time to go through al the text. You should find FSInterrogate, supplied in the SDK, useful for determining offset validity. That's why it is provided. Or you can even use the on-screen monitoring facility in FSUIPC (right-hand side of the Logging page). Regards Pete

Why do you want another for the same data? Just use the one provided at 3D00. I don't see any point in mapping it more than once! Pete

The registration system uses the email address (or street address) plus your name merely to identify you. They are both tied irrevocably to the registration key. Two different names or two different addresses look like two different people, and registration for two different people at the same time in the same FS session is not allowed. Well, it does mention this in the FSUIPC documentation, in the section on Registration. You would then have to mention the original Email address to SimMarket when you ordered -- I expect you now have two different accounts with them, too? The quickest way to resolve it now is probably to raise a problem ticket in SimMarket, explain the problem, and they can either replace your FSUIPC key or your WideFS key, as you desire. Regards Pete

I meant anything at all either added to FSX apart from the FSX SP1/SP2 or Acceleration updates, or anything running on the same PC which works with or into FSX. All such things apart from what Microsoft provides are termed "add-ons". FSUIPC4 is one, but I know you have that! ;-) Anyway, it isn't the 310A throttle inhibitor acting. Three small last tests before I have a long think about what extra code to add to log the path through for the throttle. Can you try changing the throttle assignment in FSUIPC4's axis assignments to (a) The FSUIPC plain "Throttle", the one without the slew action included, but still "direct to FSUIPC calibration. See if that is any different. (b) Select the FS control option instead and assign the "Axis Throttle Set" control. Does that work? © Same but assign the "Throttle Set" control. Depending on what happens to those, I will try to work out a way of narrowing the main problem down more. It might mean running some special test versions of FSUIPC4. Regards Pete

Yes. Very colourful! ;-) Pete

Well, this has got me truly puzzled. The throttle is not treated, inside FSUIPC, any different than any of those other axes. It is just a different number being sent to FS. The code path is the same, Everything else is the same. The values are just interchangeable. Furthermore, with exactly the same settings as you I get good results, so there's nothing hidden in the parameters you have which is doing this. There's just one other facility which can stop FSUIPC sending the results of an axis to FS -- a facility which can be operated by an FSUIPC client application to disconnect the axis. It is used for third party Airbus-style fly-by-wire and auto-throttle actions, for instance So, do you have any other add-ons running or installed? Can you list them, please? Go to FSUIPC's "Logging" page, and on the Right-Hand side, in the Offset column top row enter 310A, and select U16 as the type and check the "Hex" option. Below, check "Normal Log". OK out of there. Then I think it best to close down FSX and start it again, so I can see the log from the beginning. Just run it as far as you can see no throttle response. Close FSX, show me the resulting Log. Thanks, Pete

What sort of setting are you after? If you merely want to assign two (or more) yokes in FSUIPC, just do it. Or maybe I'm not understanding your question correctly? If you assign them with the option set to send the values "Direct to FSUIPC calibration", then calibrate in FSUIPC as well, it will arbitrate between the two yokes for you, giving priority to the one with the largest deviation. Regards Pete

Well, you have named both the Server PC and the Client PC "camtech"!!! Each PC must have a unique NAME! How else can they be identified? You've now told WideClient to connect to a WideServer on the same PC as itself: All PCs you want to work together should normally be in the same workgroup. But EVERY PC needs a unique name! Looks again at where you set the name. There's a workgroup name too. See it? Change that to be the same, change your PC names to be unique! Pete

Some of the items are now sold or reserved. The following are still available: Cirrus 2 Console + choice of one throttle quadrant .... £ 600 (GBP) (This is not the "Pro" version). Assorted other quadrants£ 50 (GBP) each (I have one of each type) Avionics stack + RIC£ 450 (GBP) (Connects to the Cirrus 2, or can be used alone) Throttle quadrant system (TCS) + choice of one throttle quadrant£ 150 (GBP) Cirrus rudder pedals, digital (not proportional) toe brakes£ 150 (GBP) (Wired for connection to Cirrus 2, TCS or Jetliner console, but could possibly be converted for Game Port use -- not USB though) MCP complete with pilot and copilot EFIS units and 6-packs£ 500 (GBP) (This is easily the most professional-looking and feeling full MCP that you could (once) get. It is the same one incorporated into the PFC 737NG (see "AATS" on the website)). Freestanding 737 style full size FMC incorporating mini PC and green mono screen£ 250 (GBP) (This needs Project Magenta CDU software running actually on that mini PC, and it connects as another PC on your network. There's a slight fault with it (which has been there ever since I got it) in that the switch on sometimes doesn't boot the PC. There's a consistent way around this, however). Questions? Offers? Privately to petedowson@btconnect.com. Regards Pete Dowson

Ah, I misread your post -- I thought you were using one of the PFC console axes as a steering tiller. Regards Pete

It's Dowson, actually, but most call me Pete. Your client isn't receiving broadcasts from your Server. That could be because they are in different Workgroups -- that's the usual reason. If you don't want to make the workgroup names the same you must use the ServerName= and Protocol= parameters in the WideClient.INI file to tell WideClient where to connect. Please see the documentation supplied. Regards Pete

I'm using the Citation example in an additional section for the FSUIPC User Guide, in the next full release. This is what it looks like, hope it helps: Variations for Mouse activated switches which might be made to work by editing the Macro file From experimentation, it seems that some switches operate not only from the mouse button being pressed, but also (or instead) when it is released. Because of the way I’ve tried to semi-automate the creation of macros, it is not possible for FSUIPC to detect these—especially when the action of the button pressed is to hold a spring-loaded switch in order to operate a starter, for example. The only way to deal with these is to make the macro, as described above, and follow it through to completion but ignoring, for now, the failure of the “TAB test”. End the macro making session via the options, then load the macro file into a text editor, such as Notepad. The file will be named “xxxx.mcro”, where “xxxx” is the name you gave it. The file will look something like this (from a real example: [Macros] Module="XXXXXXXX.GAU" 1=APU Start=RX70280*X8bcc 2=APU Normal=RX70280*X8bcc 3=APU Off=RX70310*X8bcc 4=L Eng Start=RX4a470*X8bcc 5=R eng Start=RX4a4f0*X8bcc 6=XTIE=RX66560*X8bcc These just happen to be the only awkward switches and buttons on a popular add-on aircraft. Here, the APU Start and APU Off macros merely get the switch stuck in those positions – it doesn’t spring back to centre. The Engine start and XTIE switches just make a click and do nothing else. The problem with the APU starter is that the macro generated for the “Off” position is actually the same as that for the Start one – it could have been the same as the “Off” one if the macros had been created in a different order. What is happening here is that the gauge is detecting the release of the mouse button, and the FSUIPC macro isn’t reproducing that. The macro facility is actually equipped to indicate variations on the mouse action, and this is achieved by appending another number. The numbers relevant here are 11 meaning “leave” and 17 meaning “release” It isn’t possible to know in advance which of these, if either, are needed. It might even be both. Experimentation is needed. Before we start experimenting, prepare the file for multiple-line macros, as follows: [Macros] Module="XXXXXXXX.GAU" 1=APU Start=RX70280*X8bcc 2=APU Normal= 2.1=RX70280*X8bcc 3=APU Off=RX70310*X8bcc 4=L Eng Start 4.1=RX4a470*X8bcc 5=R eng Start 5.1=RX4a4f0*X8bcc 6=XTIE 6.1=RX66560*X8bcc All I’ve done here is changed the lines we know don’t work by leaving the name on its own line, and inserting the extra .1 lines with the mouse action assigned. The file is actually identical in its effect to the original, but now we can add more actions. With the “APU Normal” switch, we want it to return to the normal position on button “leave” or “release” from either “Start” or “Off”. So the first thing to do is extend its part with the Off code as well, so it does both: 2=APU Normal= 2.1=RX70280*X8bcc 2.2=RX70310*X8bcc By experimentation, the solution for this is the “leave” code, 11: 2=APU Normal= 2.1=RX70280*X8bcc,11 2.2=RX70310*X8bcc,11 This works! But it turned out that the other three needed ,17: 4=L Eng Start 4.1=RX4a470*X8bcc 4.2=RX4a470*X8bcc,17 5=R eng Start 5.1=RX4a4f0*X8bcc 5.2=RX4a4f0*X8bcc,17 6=XTIE 6.1=RX66560*X8bcc 6.2=RX66560*X8bcc,17 There, all done. When you are trying things and testing the results, remember that you can edit the MCRO file then go into FSUIPC’s Buttons or Keys tab and tell it to reload the settings. It will re-process your MCRO files including any changes. You don’t have to keep reloading FS.

Updates are merely replacement DLL modules. They don't change you INI file, which is where all your settings are. If you are worried about losing stuff, make backups, but you won't lose anything simply replacing the DLL module. Regards Pete

They also need another line, it seems, but not the ",11" flag but the ",17" one -- the one I thought would have been needed in the first place, meaning "button up". It seems they only make a "click" on "button down", then another click and the action on "button up". Odd sort of programming, but I suppose they have reasons. The way to do these is to set about making a macro as before, then edit the MCRO file. Change the n==XXXXXXX*XXXXX line to n= and move the rest to a new line below it: n.1=XXXXXXX*XXXXX That's step one. The action is identical, but now you can add more lines for the same macro. So add: n.2=XXXXXXX*XXXXX with the same details, and append either ,11 or ,17 -- that's the experimental part. You can't know without trying which the gauge actually needs. Take a look at the solution for the APU switch. You'll get the idea. Regards Pete

Version 2.xx is unbelievably old, and was designed for FS2002. Are you sure you don't mean 3.75 and 3.85? The flaps discrepancy was fixed in the Updated versions many weeks ago. Please see the Updates announcement above! If you stick with any old versions, please never come back here for support as I cannot support them. Pete

It is really perplexing then. Did you try, as I asked, using one of the other axes as a throttle, just to eliminate some sort of odd behaviour with that one axis. In other words, one of the axes which work with the mixture or prop pitch control? Also, can you move the throttle via other means -- dragging with the mouse on the throttle quadrant, or using the 9 & 3 keys on the number pad? I notice you always have the Cessna loading as default then change over to the Extra for the test. Could you test with the default loaded Cessna please? 20625 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR <<<<<<<<================ 294125 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Extra300\Extra300S.AIR I'm trying to simplify things down to the least possibly variation. The log also shows only the Prop axis being moved from one extreme to the other and back. Did you move it, or were you moving what you thought was the throttle? If you are testing the Prop Axis here, why, and why not also the Mixture axis? Finally, I think you should delete this aircraft-specific section from the INI as it is doing nothing different from the generic one and will only complicate the issue: [Axes.Extra 300S Paint1] 0=0X,256,D,45,0,0,0 1=0Y,256,D,46,0,0,0 2=0Z,260,D,5,0,0,0 3=0U,256,D,6,0,0,0 4=0V,256,D,48,0,0,0 5=1X,256,D,7,0,0,0 6=1Y,256,D,8,0,0,0 7=1R,256,D,47,0,0,0 Regards Pete

Sorry, what impression? Please don't keep attaching large useless pictures. You can find the version numbers of any of my programs simply by right-clicking on the module, and selecting Properties-Version. For FSUIPC the version number is shown on screen, and it the Log file. Theres never any need to do things like take pictures of folders on your disk. The error is a very commonly used part of Windows and really shows nothing useful related to anything else other than that you were running FSX at the time. A high proportion of crashes from any program would give the same sort of details. This thread was almost entirely about the interaction between FSUIPC4's attempted wind smoothing and the behaviour of the PMDG aircraft. The crashes were specific to one person and related to scenery I think. Either way they were resolved a year ago. You need to determine what is causing the error specifically on your system. Use a process of elimination. Try not running one thing at a time. If you have plenty of add-ons it could be any one of them, or just a combination. Perhaps it is associated with something you are doing? Perhaps it is simply a corrupt file. But you say nothing, you describe nothing of what you are doing, nor how long you have to fly before it happens, nor whether it happens all the time or just once a week. You just append some rather less than useful pictures to the end of a 12-month old thread which appears to be completely irrelevant, referring to 4.232 and wind smoothing on the PMDG aircraft as it does. If you have a problem and think it is anything to do with any of my programs then start a new thread with a more appropriate title and explain clearly WHAT is happening, WHAT you are doing at the time, and what you have installed. Also please explain why you think it might possibly have anything whatsoever to do with anything of mine. And try the latest update for FSUIPC4 (in the Updates announcement above) before this, in any case. Regards Pete

I don't handle registrations. As it clearly says in the Announcements just above, you need to go to SimMarket and retrieve your keys from your account. Please be sure to make a backup of the KEY file next time, as advised in the documentation. Pete

It sounds exactly as if you have dual assignments. Have you disabled the joystick(s) in FS? Yes. Why on Earth are you using FSUIPC's assignments for such things when you can use the PFC driver I provide for everything on the Jetliner console, as I do? If you do use FSUIPC, you MUST disable the PFC driver's actions for the same axes, otherwise its assignments will also be operating! Pete