Pete Dowson

Okay, but I needed to know thattrying to reproduce something which so far hasn't happened here, I need every clue. I'll see if I can repro it with all the information you've now given me. Thanks. Pete

Ah! The reason is staring you in the face! Even doing the Reset as you are isn't really fixing anything, but temporarily masking it. See the word "direct" against each brake? That means you have assigned the brakes so some axis or other in FSUIPC's Axis Assignments -- and not only that, but you assigned them to go direct to FSUIPC calibration (not the default method at all)! No wonder FSUIPC re-enables the calibration -- you cannot have FSUIPC scanning an axis for you and sending it to the calibration routines with them doing nothing. Even with your temporarily cancelling the calibration, you are still making FSUIPC scan two axes 20 or more times per second for no reason at all other than tyo add to the load on your PC. Maybe the two axes you have directly assigned to the brakes are not the same ones you are trying to use through FS -- hence the "going wild". Two different axes trying to do the same things! If you don't understand anything in FSUIPC it is best not to use anything in FSUIPC. (Or at least read the manual! ;-) ) Since you apparently don't know what you've done, that would be my advice, yes. Then don't mess again unless you know what you want to do. ;-) Alternatively, if this reply does jog your memory into something you forgot you did, just go and undo it. Regards Pete

Well, they would, wouldn't they. I'm afraid I don't know FS commander, but I do know a lot of folks use it quite happily over a WideFS link. Are you sure it is FSUIPC it says it cannot connect to? I think it needs directory access to FS as well, and may be having the same problem if it is using the computer name not the IP address. Have you shared the folders it needs on the FS PC, and can you access those okay on the client PC using Windows Explorer? All I can do is look at your logs (FSUIPC4.LOG, WideServer.LOG and WideClient.LOG) and tell you whether FSUIPC and WideFS are working okay. If they are, he problem is either with FSC or your network, still. I suspect the latter, because all you've done so far is worked around a problem you should never have had in the first place if the network was okay. Regards Pete

The values are totally irrelevant if the top left button in the relevant calibration section reads "Set", as that means that no calibration is being performed. Full Stop. If the section were active it would read "Reset". Values should always be present in the boxes as the defaults would be there until you calibrate. If you have a problem I think you must be seriously misinterpreting something and this is confusing you more. In the same folder as FSUIPC, the FS Modules folder. Everything to do with FSUIPC is always in the FS Modules folder. Regards Pete

Maybe a bad joystick driver -- dinput is short for "Direct Input", and is part of Windows. You could try reinstalling DirectX (update to the latest DX9 (or DX10 for Vista) release maybe? Or try uninstalling and reinstalling joysticks. Dinput can also be used for keyboard and mouse input, but i don't think FS uses it for those. Regards Pete

Having only a min and max is no good. You need a centre zone as well -- that's why there are 4 values being set, min, low centre, high centre and max. you need to follow ALL the calibration steps, not just pick out one or two. That's the whole point. Defining the centre as a zone ensures you can ALWAYS centre controls no matter how variable of "off-centre" they may be. If you don't use that feature then it's a complete waste of time using FSUIPC for calibration. Oh, you mean pages? The rudder and all the main controls are on page 1. Regards Pete

Well, (2) is easy -- it is the "on ground" flag at offset 0366. For (1) you'd need to use the Latitude and Longitude and find the airport using a database of all airports. Ah, if you've loaded a flight plan into FS9, then you may be able to read the origin ICAO, before takeoff, in offset 6081. However, I'm not sure any of those GPS offsets work proprtly -- the list was provided by someone else. None of those are available in FSX. Alternatively, and more reliably, you could find the current plan (if it has been saved and referenced by the current flight) by reading the FLT file (identified with path in the offsets) and getting the PLN filename, then reading that. That should work with FSX too. But it does depend on having the plan AND flight saved, then loaded. Regards Pete

But the trim has an effect on that too -- if the aircraft is out of trim the force should be greater , no? Why not read both aileron and trim and use the combination -- especially if the A/P is engaged, as that, as you say, is operating the trim. Yes, so, in autopilot mode, use the trim read-out instead. Right? Regards Pete

when you say you have not CHANGED the calibration in FSUIPC, do you mean that you set FSUIPC calibrating before and then never changed it? That's not good. If you are happy with CH's calibration,then disable the FSUIPC settings, or perform the calibration properly. What's "the step 2 of the calibration tab", please? There are no steps in the dialogue. Are you referring to the documentation, perhaps? And what entries change to 0 when you press "Reset"? If changes made aren't being recorded in your FSUIPC INI file, it must be protected or corrupted. Please check that it isn't marked read-only. Alternatively, just delete it. If you need more help, please state FS version number, FSUIPC version number, and Windows version. Regards Pete

Is SquawkBox4 a gauge, then? The FSUIPC mouse macros only work on gauges written to FS's C/C++ SDK rules. I thought SquawkBox was a separate program? Are you saying that SB4 does not provide any keyboard shortcuts, or any other way to operate the facilities it provides, without clicking with a mouse? doesn't the sound in FSX stop when you do so? I really cannot believe they've made no provisions for folks wanting to fly FSX on-line in a cockpit. I've certainly got no access to keyboard or mouse within my cockpit, and since I'm exclusively flying FSX these days it seems I'll not be able to do so on-line, at least with SB4. I really think you need to get this clarified with the SB4 people. Regards Pete

ErI really don't know any way FSUIPC could possibly do this, but please clarify a few things for me: 1. Method of assignment. Are you assigning axes in FS, or in FSUIPC? If in FSUIPC, are you using "direct to FSUIPC calibration" or the default FS axis controls? 2. Are you saying this happens whilst you are actually flying, or when loading new aircraft/flights, or only on different sessions of FS? Or on different boots of XP? Ah, that's suspicious. "joystick re-enabled in options" sounds like FS is not remembering the assignments, and you are assigning in FS. FS should certainly not have to have its joystck option re-enabled each time. So, are you really sure FSUIPC is doing anything at all here, that it isn't FS not correctly recording the joysticks on each session? So, it most certainly sounds like you have so INI file set up wrongly. That has to be the only possibly answer. But before we continue, could you at least move onto a supported version of FSUIPC, please? 3.82 was released way back in July, and there's an interim release called 3.829 available above. Regards Pete

I need to be able to repro this here in order to fix it. So far (before my holiday) I could not. I'll try again when I've caught up with everything. I've never actually tried unassigning, rebooting and reassigning before. Never seemed a logical thing to do, but maybe it's a clue. Comparing those two I also note that in the interim you also made several changes in the [Axes] assignments. What is the default aircraft being loaded (is it one you have specific settings for), and did you change aircraft before making the de-assignment/assignment changes? Regards Pete

Well, the reply in that thread said clearly "SB4 for FSX doesn't use FSUIPC", so there's no way you can do it via FSUIPC, except possibly by assigning buttons to send the appropriate keystrokes? Do you know if you can do the transponder and ident operations with the keyboard whilst FSX has the focus? How would folks do it in any case? I assume they do? Regards Pete

Short of writing your own autopilot (or at least the Vertical parts), you can't. But I'm not sure what the problem is for "force feedback". Can you explain what sort of "force feedback" you are attempting and why it is impossible? Regards Pete

Sorry, can you elaborate on what "click" means here? I cannot visualise how a mouse click shows you anything? Can you please just run the FSUIPC 4.30 installer (the EXE program inside the current FSUIPC4.ZIP file), then show me the Install log -- you'll find it in the FSX Modules folder. Regards Pete

Not that I know of, sorry. Regards Pete

We didn't get any facilities to read anything about viewpoints. Sorry. The "hope" expressed in my documentation was reasonable in the days when Microsoft were hinting at regular SimConnect updates. Ahem. FSXI? ESP2? Regards Pete

I think you need support from this SIOC or OC companies, as their implementation will be specific to them. It isn't anything directly supported by FSUIPC, they are merely using FSUIPC as the vehicle. Some comments though: Except for 0330, which is the QNH and is in the FSUIPC documentation, these are all Project Magenta offsets and are documented in the Project Magenta website. These are nothing whatsoever to do with the EFIS you have, but was the term used by Microsoft for its heads-up guidance system for ILSs using hoops or boxes in the sky. Those offsets haven't been supported for a long time. There are no built-in facilities for operating the default EFIS features in FS at all. There are ways of operating the EFIS in Project Magenta, and also PMDG and LevelD and some other add-ons -- but they all do their own thing. there's no standard. The FSUIPC mouse macros don't work on many of the default FS gauges due to the non-standard way they've implemented them. I believe i do explain this in the manual. If the "TEST" facility (press TAB) doesn't work for it, then it cannot happen. You should never have created them without testing them to be sure. Please do follow the instructions more precisely. I'm afraid there is no way you can do anything with the default EFIS gauges in FSUIPC. you might get it sorted using Luciano Napolitano's "Key2Mouse", as it was designed for these cases. Best to delete the Macro section from your INI file for now. Regards Pete

Both FSUIPC4 and WideFS7 are registered via the Installer, and this has been the case for many releases now. It is done specifically to avoid Administrative rights problems when trying to do it in FSX. Run the installer. When it has done its job you will get the option to register either or both or FSUIPC4 and WideFS, or remove registrations, or simply check them. When and where was that? Regards Pete

Please first update to a supported version -- 4.30 from the Schiratti site, then, optionally, the latest increment from "FSX Downloads" above. Then if it still happens show me the Install and FSUIPC4 LOG files from the FSX Modules folder. Regards Pete

Not seen that one before. Looks like it doesn't know how to convert "PILLY-PC" into a TCP/IP address. Is your network actually working? Can you see PILLY-PC via other programs, like Windows Explorer? It could be a network installation problem. Here's help I found elsewhere: "An 11004 error means that the name you provided for a server in the client connection cannot be resolved to an IP address because DNS entries for that host name cannot be found or connection cannot be resolved to an IP address because DNS entries for that host name are misconfigured (for example a CNAME record without an appropriate A record). Try using the appropriate (internal or external) IP address for the server in the client connection string instead of the name." So you could try deleting the ServerName= parameter and using the ServerIPAddr= parameter instead, with the IP address. Incidentally: Why did you add these lines? If both PCs are running XP or Vista, and they are both in the same WorkGroup then WideFs should link aytromatically, without you specifying a Server name or IP address. Furthermore, the "ProtocolPreferred" parameter is only relevant to the SERVER INI, not the Client - I don't know how you got this mixed up. If you specify a Server name or IP address, as you have, you should also specify the protocol e.g. "Protocol=TCP". Regards Pete

No, it was invented for FS2000 and carried forward as compatibly as possible. but thanks for mentioning you are not talking about FSX. So, are you talking about FS9 or before? FS9.1? Please also tell me the specific version number of FSUIPC. If it isn't the latest increment (available in the "Other Downloads" above), please try that first. Then I can check it out here with the same version. I must admit it isn't something I've noticed -- WideFS and other ancillary programs all wait upon those values. Regards Pete

I've no idea what "VAFS" is -- is that related to FSInn or Squawkbox or something else? Either way, with FSX not running, find the FSUIPC4.LOG file in the FSX Modules folder and paste it here. Regards Pete

I'm aware there was a compatibility problem between FSCopilot and FSUIPC at one time, but I'm pretty sure it was fixed in a later version of FSCopilot. There was also a problem with a Kensington Mouse driver, but i've not encountered that recently. Regards Pete

They are assigned by Windows. Presumably Widows used to see a #3 and that USB port hasn't been used again. I'm not really sure how it assigns the numbers in the first place, but they are the only IDs I have for the joy API. You cannot because they are not assigned by FSUIPC. I suspect you need to be sure yo always use the same USB connections, assuming this is how Windows really does assign them (which it certainly appears to -- same as how it assigns COM nmbers when you connect a serial device as USB). Well of course you can edit the FSUIPC INI file, changing the numbers there. If this was a more general problem I would consider adding a facility for "aliassing" one number to another, but quite honestly this has only ever arisen once before that I can remember, and that's in over 10 years. I attach a program called "joyview" which uses the same API as FSUIPC so you can clearly see what is where. Regards Pete joyview.zip