Pete Dowson

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. Please refer to the section "PTT (push to talk) for Roger Wilco, AVC and TeamSpeak" is the WideFS Technical document. There's a bit on Teamspeak which tells you exactly. Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. What FS settings do you have in fltsim for PTT? I don't think FS supports PTT!? If you mean should you delete a button assignment in FS when you assign one in FSUIPC, then the answer is yes, as it clearly says in the User Guide -- unless of course you want both FS and FSUIPC to act on the same button press. What working? PTT? There is nothing in FSUIPC which checks whether you are on the ground or in the air. You must look to whatever application you are using the PTT with. Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. Surely a new MB, unless it is identical to the previous one, means everything needs re-doing. All Windows drivers and so on have to be re-installed. You aren't trying to foll Windows into thinking nothing has changed, surely? Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. It isn't FSUIPC or WideFS which can do that, but it can certainly be a program which is using one or the other. Try terminating the other program(s) first. Please make sure you are using the latest versions as well. If you have any further questions please include the relevant log files. Regards Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. Right. It does actually say this in the Registration section of the FSUIPC user guide. Well, I think SimMarket would have dealt with it if you'd mentioned it when ordering, and still can now via a Problem Ticket, but otherwise you can Zip up your existing FSUIPC4.KEY file, from the Modules folder, and send it to me at petedowson@btconnect.com along with your registration details for WideFS7 (as received form SimMarket), and I will re-issue the FSUIPC4 key to match the WideFS7 one. Regards Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. You missed some very important lines off! Please do not edit files before posting. Because the first lines of the Log are missing, I cannot be more explicit. But: 1. The Version Mismatch error may be fixed by using the latest version of FSUIPC, but equally it may be due placing a SimConnect.dll file in places where it should not be -- it especially should not be in the Modules folder or in the FSX main folder. 2. If 1 does not fix it, you need to try a Simconnect repair as advised in the FSX Help announcement above. 3. If neither 1 nor 2, then a complete uninstall and re-install of SP1 and FSX may be needed. 4. If none of the above, you need to report it to MS Tech Support and get them to advise. Regards Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. SimConnect is not responding at all, even though it loaded FSUIPC4. I cannot solve SimConnect install problems directly, but maybe the FSX Help Announcement above will help. It says how to get a SimConnect Log (which may show what is happening), and also how to repair SimConnect. In the end a complete FSX uninstall and re-install may be needed. Regards Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. I don't think getting into FS's ATC gives you control over AI -- it's an illusion if you think that's how it works. I'm pretty sure that the AI are following their plans come what may. I think the ATC "interaction" with them is acting to match what they do. You can send FS controls to AI aircraft via FSUIPC (or direct through SimConnect in FSX). This is what Radar Contact 4.3, and more so the upcoming RC5, does to try to "make way" for the user. AI Smooth does the same. The nicest thing which I'd like to be able to do is to assign runways for takeoff and landing, so that it would affect both AI and ATC. I don't know how to do that though. Creating AI aircraft is supported via SimConnect in FSX. Regards Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. Just installing the SDK adds nothing to FSX. You actually have to edit the DLL.XML file to get those utlities you want to run. then you may get a "Tools" menu. It doesn't affect the Add-Ons menu. If there is no FSUIPC4.LOG file then FSUIPC4 is simply not being loaded at all. This can only mean one of these: 1. The DLL.XML file is wrong. Find it (in the same folder as your FSX.CFG file) and delete it, then re-install FSUIPC4. (Your FSUIPC Install Log will give you the location of the DLL.XML file, as in this example: 2. If this doesn't work, check the FSUIPC4 Install log and make sure it says: and never finds a SimConnect.XML file. If it does, delete it. 3. If both things fail, we'll need a SimConnect Log. Please see the FSX Help Announcement above to find out how to get one of those. Regards Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. Yes, you have to use the multiplayer interface to FS. There is no other way. No way I know of except in FSX, where this is specifically catered for. Well, not quite. I was made a Microsoft MVP because I try to help where I can. And in any case FSUIPC is only one of many of my own FS contributions. Unfortunately, though, multiplayer is something I know almost nothing at all about, excpet that it is designed to do exactly what you want. No, no use at all I'm afraid. Multiplayer in FS2002 and FS2004 is designed specifically for exactly what you want to do. In FSX is it via SimConnect instead. Regards Pete

Sorry for the delay in replying -- as mentioned in the Announcements above, my wife and I were off touring Argentina & Chile (by steam trains where possible) immediately after I returned to the UK from the AVSIM FanCon in Seattle. Assuming that you are calibrating multiple throttles on page 3 of the FSUIPC Joystick Calibrations tab, all you need to do is to make sure you have a wide enough idle zone calibrated to be sure that you can select idle easily. The steps for calibration in the user guid do explain the need to have two definitely separate positions to mark the top and bottom of the idle zone. Pete

Oh, yes. A lot of folks have mentioned that. In fact I added a special facility to ignore transient button presses especially to get over those spurious ones (see the Dowsnloads announcements above). Yes, it certainly can. Maybe best, though, for add-on aircraft, is to assign normal flight controls and throttles through FS. Flaps and extra reverser axes can be assigned direct in FSUIPC, giving you more options. you can assign everything in FSUIPC, with the main controls and throttles going via FS and the flaps and reversers, or even just the reversers (which aren't provided directly in FS) direct to FSUIPC. Certainly for force feedback I think you need to assign the main axes in FS. Because of the way FS "picks up" controller axes, it may be best to keep all axes on each controller either through FS or through FSUIPC, not mixing them. If FS does start contorlling axes which FSUIPC is also controlling then things will go pretty horrible, many jerks and changes as each does its own thing. Ah, okay. That should make things a lot simpler, then. Regards Pete

The "next days" means December 4th earliest for me, as after this message I'm away till then. Is that it? No more lines? If so, it is not loading any DLLs or any EXE programs at all. You either have a screwed up DLL.XML file, or none at all. However, the FSUIPC4 install log does show this okay: You are running FSX under logon name "GreatGameKiller", aren't you? Have you installed other add-ons? Have you edited the DLL.XML file? That is the file which tells SimConnect what DLLs to load. FSUIPC4 is not being loaded, so it cannot do anything. Regards Pete

Well, let's stop there for a moment. If you want to CALIBRATE in FSUIPC, why unassign things in FS? FSUIPC will easily calibrate anything assigned in FS. You only need to unassign things in FS if you want to ASSIGN things in FSUIPC, and why would you want to do that? If you want force-feedback you most certainly CANNOT use FSUIPC for assignments. Delete your FSUIPC.INI file and start again. Just use FSUIPC for calibration, as originally intended. The axis assignments facility is an advanced option for folks using multiple controls who want automatic changing when they swap aircraft, or need axes to do other things like press buttons or send keystrokes. FSUIPC assignment can be more efficient than FS assignment, but it certainly doesn't support force feedback, and since it bypasses FS fror most everything (that's why it is more efficient) it will also fool some of the more elaborate add-on aircraft. From what I've heard, the Level D aircraft does its own thing with the axis controls from FS. Even if you assign axes in FSUIPC you have to assign them to FS controls, not direct to FSUIPC, otherwise it won't see them. You can, of course, make such assignments aircraft specific. Maybe because you wanted to use its facilities? Why DID you buy it if everything was "working like a charm"? I cannot read your mind, I don't know what you wanted to do. Sorry. So, why ASSIGN in FSUIPC? What did you want to accomplish that way? What is wrong with using the more precise calibration, long the mainstay of FSUIPC facilities, without using the relatively new and rather specialist facilities of FSUIPC assignment? Even so, since it was all working like a charm beforehand, why try to mess it up? Why not just continue as you were before? I don't understand. Regards Pete

2A70 only works for the Canopy on those aircraft which have such. Door control is by using the FS control, "Toggle aircraft exit". This is the one which the Ctrl+E (or is it Shift+E?) key does. You follow that by Select 1Select 4 according to which door(s) you want to operate, or leave it for the main door. You can send any controls via offset 3110. The Toggle aircraft exit control has number 66389, and the select controls are 65538 to 65541. There are lists provided on the download page. 3367 provides an indication of door state. On FSUIPC4, for FSX, I do deal with writes to that as well as reads, but in FS9 this is a straight-through mapping and is only a read-out, and for the main door only. Regards Pete

You should not use the same method as you use for the latitude. That is the point. It will, indeed, look like a huge number if you do that, because floating point format is completely different to fixed point. You need to read floating point values directly into floating point variables (easy in C or C++), or at least copy them over in a way which doesn't convert them -- unlike your method for the latitude. I'm afraid I cannot help further with your language. If you don't know how to use its floating point variables perhaps someone else will be able to help. Regards Pete

I have seen this in the windows API, so I guess I have to see if it is available in directinput / directx. I'm sure it would be there somewhere! What are you expecting to see in these interfaces? They simply tell you if the button is PRESSED or NOT PRESSED. Surely your program reads the fact that they are pressed or not, so you know when the button changes from one state to the other!? So you have deliberately programmed it to only act on button state, and not to only act when the state changes! No wonder it repeats! Just store the complete button state (all zero initially), then Exclusive Or that previous state with the new state on each cycle, and act on the changes. 0 -> 1 = press, 1 -> 0 is release. It isn't complicated, but any processing of buttons surely needs to detect user action, not static state! Buttons are for user actions, after all! Pete

Sorry, I have no idea what is wrong with your installation then. I'm not sure why you are asking here, in that case, nor why you refer to FSUIPC4 in the subject heading. Sounds like your FS installation is screwed up. Best to uninstall FS completely, including all add-ons. Install it afresh and re-check. Then take care to install only one thing at a time, checking after each. Pete

Do you mean a brakes button, or analogue toe brakes? How are you assigning them in FSX? Are you talking about the simple trim up / trime down button actions, or an analogue trim axis? How are you assigning those? What "fsx people" told you that? The brakes on the keyboard are '.' and the trim are the Numpad 7 and 1 keys. They all work in FSX the same as they did in FS9. Pete

In that case one of three things is happening: 1. The DLL.XML file is incorrect and preventing SimConnect loading FSUIPC. Re-installing FSUIPC4 should fix that, but if not you might need to find it (it is in C:\Users\GreatGameKiller\AppData\Roaming\Microsoft\FSX\FSX.CFG) and delete it, then re-run the Installer. 2. SimConnect is broken. See the FSX Help announcement and get a SimConnect log, see if that tells us why. 3. There is a Simconnect.dll file in the modules folder or with some other add-on you have enabled. The only Simconnect.DLL files in use should be those in the WinSxS folders in Windows. Regards Pete

I think you are reading that the wrong way around. It's the new edition of FSUIPC you need because the one you have only works with FS 9.00.30612. Your add-on is very very old and has installed an ancient version of FSUIPC which is no good even for FS2004 updated to 9.1. Just go to http://www.schiratti.com/dowson and download the current version. Copy the updated FSUIPC.DLL into the FS Modules folder. Pete

I seem to recall someone saying you had to postpend a '&' too to stop thati.e. &HC0FC&. But maybe I'm mis-remembering? Regards Pete

A lot of folks seem to be having problems with the new Saitek stuff. Have you tried their support? A conflict with what? Get everything working properly inb FS itself first, before even thinking about using FSUIPC. If it doesn't work in FSX it won't work in FSUIPC either. Regards Pete

It would help more if you could be specific. What is the message, what version of FSUIPC4 are you installing, and where is the Install Log which the documentation explains and asks you to show if you have any problem? It sounds to me as if you are not using the current supported version of FSUIPC4 -- version 4.20. If not, go download that first and try again. Regards Pete

To have a joystick button repeating surely necessitates EXTRA code? You notice the change from "not pressed" to "pressed", which happens only once -- then, later you get the "pressed" to "unpressed" change. To get repeats in-between would mean extra code with a timer, to see if it is still pressed. Merely by-pass that to avoid repeats! If your hardware is sending repeats and mis-representing the "press" and "released" states of the buttons, you have a hardware problem. If you can't make it work correctly I am not sure what you can do, other than ignore presses which occur too close to previous ones. But that can be quite limiting in the button usefulness. Regards Pete