Pete Dowson

That isn't true. If both toe brakes are exerting the same pressure the red label says "BRAKES". It only says "DIFFERENTIAL BRAKES" if you are applying different pressures on each. Do NOT mess with the "delta" value. That's for use by hardware builders and programmers. The most usual reason for this problem on CH and some other pedals is that you need to REVERSE the control. They operate backwards. If you do not select the "REV" option in calibration before doing the calibration the brakes are full on when released and full off when fully depressed! Go to your toe brake calibration tab in FSUIPC, reset whatever calibration you've made (ie press RESET), then press SET, select REV, and then do the calibration. Always press the pedals a little before setting the minimum value so that you don't accidentally brake when using the rudder. That won't occur normally with analogue brakes, but FSUIPC does it for you in all recent releases. You have to press both of them most of the way down, as in a real aircraft (to let the strongly sprung catch release). The pressure you need to apply is adjustable is an FSUIPC parameter (see documentation, Advanced User's guide). No. You don't need to do anything on "control when range entered". Why are you doing that? Regards Pete

The only time the calibration tab makes an "error beep" is when you attempt to put a lower number to the right of a higher number or vice versa. Of the two or four numbers in a calibration line, the left-most must be the lowest. It is often so low it is negative (the most negative).. The middle two, if any, should both be higher than the left most one, but in either order, and the right-most should be the maximum value, the "most positive"). This is why they are often labelled "minimum" (for lowest), "centre" (for middling) and "maximum" for highest. See? Other labels are used to give context appropriate to the control being calibrated, but the principle remains. Left-to-Right = Low to High. Any other arrangement makes no sense and would make everything go wrong, so it isn't allowed. The "beep" just means "you cannot do that!". Pete

If WideClient says "Connected" in its title bar then it sounds like a registration problem in FSUIPC. First check the Windows system date on the FS PC. Maybe you haven't set that correctly yet? If it is set to a date before your FSUIPC or WideFS purchase then the data supplied by FSUIPC will be insufficient. It will look like a bad registration. If not that, please close FS then paste here your FSUIPC, WideServer and WideClient logs. Regards Pete

The SDK provides source examples, but not ready-made projects. You need to set up your own projects and use the documentation and examples only to understand how to program to the FSUIPC interface. The source for the library file is also provided, so if the library doesn't match your version of Microsoft C you can build your own, or simply use the source directly in your program. The files do tend to date back to FS98 days because that's when FSUIPC started and the interface is compatible for all versions of FS from that time till today. Regards Pete

Ok. I'll continue to send you stuff for the FSUIPC Beta VRInsight support, though. Pete

Sorry, all that is lost on me. Can you slow down a bit and explain each of those rants one at a time please? What's the bit about bugs about? What's all that about reloading flights? I just save a flight with the Radar Contact window showing, and use that flight as the basis for all others I create. I'm not sure what the problem is that you are having with that. I've been doing it for years, starting well before I added the FS window usage, because the "AdvDisplay" window position was saved in a similar manner when we all used that instead. Well, I'll take that request on board, adding it to my list of things to look at. But I do find it a little odd that it is suddenly important after all these years. What has stopped working, or is it simply a misunderstanding? Regards Pete

Just save your FSUIPC.INI (for FSUIPC3) or FSUIPC4.INI (for FSUIPC4) file from the FS Modules folder. It contains all of the settings you make in FSUIPC except Macros. If you create any Macros, they'll be in files you gave names for and with filetype .mcro. Don't forget to save your FSUIPC KEY file too. That contains your registration. You'll need to re-enter it, but the details will be in their. Copy the files to another PC or a removable disk or USB memory stick, or even write them to a CD. Regards Pete

Just default values in FSUIPC. There are three different positions for three different Window uses. You move it and size it and save the Flight with it where you want it. The length might change to suit the data it gets, though, but the width diesn't, not position. When you reload that flight it should be in the same position next time it appears. That's what happens here. That is the way, same as the way panel positions and so on are saved to suit a flight. It was one of the benefits of using standard FS windows, that they get saved in the FLT file. Naturally the window has to be present at the time you do the save. I looked in the thread you referred to, and that's what that ended up saying too, but for the ATIS window. Regards Pete

It just occurred to me. You said "SB4 does not allow to configure joystick button ...". But I'm pretty certain that SB4, like SB3 before it, accepts the standard Roger-Wilco broadcast messages for "PTT" and the Private PTT, or "PVT". Both of those can be assigned to Buttons in FSUIPC's assignments dropdown. There's an 'on' and 'off' for each. Not curious. It is possible, indeed, but it is by using a different method. FSUIPC intercepts normal KEYDOWN and KEYUP messages received in FS's main Window Procedure. These are asynchronous from the hardware use f keyboard and in fact may not come from the real keyboard at all. If FSINN is using the hardware indication for these then merely sending keystrokes to it from a program wouldn't work in any case. It would need a more privileged routine, like a service or debugger, hooking into the hardware keyboard testing API and thus pretending to be a keyboard in order to provide the correct codes in the correct manner. Regards Pete

As stated in the documentation, virtually none of the default FS gauges are susceptible to mouse macro programming. They are either using XML (in FSX especially), in which can you might, if you are lucky, get access via L:vars, or they simply don't abide by Microsoft's own gauge SDK. The structures simply are not there for FSUIPC to hook into. Most of the MS gauges written in C/C++ do direct calls into PANELS.DLL instead of using the standard published methods with hookable stuff in the gauge DLL themselves. This is what it means when you get no response to a mouse click in macro creation mode -- "not possible". Regards Pete

Okay. But I just checked, and there are no separate Virtual Keycodes for "left" and "right" Control keys. Programs which differentiate these two must be referring to the raw hardware codes, which FSUIPC has never used. You could try using Shift and Control keys instead (left and right would be the same). The VK code for Shift is 16 and for control is 17. Regards Pete

If you just search the offsets list document (in the FSUIPC SDK) for "message text" you'll find offset 3380 for the message (up to 127 characters plus zero terminator) and there get the reference to 32FA which is where it is controlled. It still also talks about AdvDisplay, but that is of course now replaced by FSUIPC's own FS windows. Regards Pete

Okay. Actually I only got two, both about 60+ miles away! But I found why the last one wasn't cleared. I was thinking the size of each entry was 16 bytes, but of course it is 20, so the last 24 bytes weren't being zapped. Sorry about that. But I can't see any way at present to make SimConnect return all the airport list. I've extended the logging to show the complete list I get, before I select the nearest 6, and it is never really complete. According to the documentation it is supposed to split the data packets into more than one if there are a lot, but there's only ever one packet supplied, varying in size from the 2 I got for SLCB to about 92 I got somewhere East of Gatwick. In my younger days I might have taken up the challenge and started hacking into FSX code to see what was going wrong, but I'm too old and impatient to do that sort of thing these days. It was bad enough for FS9, made be ill the lack of sleep i got over that one! If I have any bright ideas I'll let you know. The next interim update will have the invalid entries cleared, but not the problems fixed. Sorry. Regards Pete

Strange. I've been running RC 4.3 like that with FSX for over three years and have never seen an ATC.DLL crash. I think you must have some sort of corruption in your FSX installation. Either way, I know of no fixes possible to any bugs in FSX, and I do know the main one that was in FS9 is not in FSX. Maybe you aren't using a fully updated install of FSX and there was a bug in the original or SP1 versions? I never heard of one though. Of course I've been using SP2/Acceleration ever since that was in Beta, so pretty nearly for all of the three years or more. Oh, and with the ATC volume turned down I hear no ATC voices on the FSX PC at all, so that's a bit strange too. Sorry. I would refer you to Microsoft support but we know that's not going to get anywhere! :-( Regards Pete

Not as a key it recognises on the keyboard. If you mean to send when you press a joystick button, then yes, you should be able to do that by editing the assigned "virtual keycode" in the INI file for a button already assigned to send a keystroke. Pete

Okay, nothing wrong there either. As I said: "version 3.972 is currently available in the Updates and other Goodies Announcement above." You should review the Announcements from time to time. They are there for a purpose -- to Announce things. They are probably the most important part of the Support offered by this Forum! Pete

Yes, that is it and it shows everything in FSUIPC is fine. though maybe it could have shown more if you'd loaded the PMDG aircraft you say you have a problem with. As it is, it appears FS only loaded the default Cessna! Anyway, I suggest you follow Stephen's advice (see the message earlier, from "srcooke"), and replace the FSUIPC.DLL with the latest Beta -- version 3.972 is currently available in the Updates and other Goodies Announcement above. Regards Pete

There's no change to WideFS for Windows 7, so it must be your configuration. Are both PCs in the same workgroup? What do the WideServer and WideClient logs show? Paste them here. Regards Pete

If there is no FSUIPC log file then FSUIPC is certainly not installed and is therefore not running. That would be your problem. You need to run the installer. Then, after re-running FS, there will be two log files - the Installer creates one and so does FSUIPC. Regards Pete

By "Server" do you really mean "Client"? WideFS's server is the FS PC. Really, what you run on the client PCs and on the FS PC depend upon their needs as well as yours. I run weather programs (Active Sky), ATC and voice programs (Radar Contact and Its Your Plane), moving maps, traffic watchers, Flight Keeper, etc all on clients, but AI traffic injectors like Ultimate Traffic 2 really do have to be on the FS PC, and most of them only run inside FS in any case (being effectively scenery type files read by FS). Regards Pete

Sorry, I think it's a bug in SimConnect. I've debugged it all the way through. I've tried flying away for and back to and over EGKK, but it is never listed as an airport in what SimConnect supplies. I get details of airports up to 120 nm away, with over 90 airports being listed, but NEVER "EGKK". Weird. For example, with extra debugging I've put in, here's the full list of airports I get from simConnect when at EGKK: 81437 ***** All Airports ***** 81437 Airport001=EGBO, Lat=52.517500, Lon=-02.259445, Dist=112.832023 81453 Airport002=EGWC, Lat=52.640000, Lon=-02.305500, Dist=119.336083 81453 Airport003=EGBW, Lat=52.192222, Lon=-01.614444, Dist=82.439545 81453 Airport004=EGBE, Lat=52.369722, Lon=-01.479722, Dist=87.845247 81453 Airport005=EG74, Lat=52.486944, Lon=-01.130667, Dist=87.733954 81453 Airport006=EGBB, Lat=52.453855, Lon=-01.748028, Dist=97.692262 81453 Airport007=EGBG, Lat=52.607778, Lon=-01.031945, Dist=93.067142 81453 Airport008=EGBT, Lat=52.040834, Lon=-01.095555, Dist=63.586215 81453 Airport009=UK03, Lat=51.930000, Lon=-01.430000, Dist=66.328483 81453 Airport010=EGLJ, Lat=51.674444, Lon=-01.085278, Dist=46.501770 81468 Airport011=EGVA, Lat=51.682167, Lon=-01.790028, Dist=68.527038 81468 Airport012=EGVN, Lat=51.749964, Lon=-01.583617, Dist=63.953379 81468 Airport013=EGTK, Lat=51.836944, Lon=-01.320000, Dist=59.522661 81468 Airport014=EGUB, Lat=51.616389, Lon=-01.095833, Dist=44.548564 81468 Airport015=EGTB, Lat=51.611667, Lon=-00.808333, Dist=36.568936 81468 Airport016=EGGW, Lat=51.874722, Lon=-00.368333, Dist=44.051823 81468 Airport017=EGWU, Lat=51.553000, Lon=-00.418231, Dist=25.862171 81468 Airport018=EGTF, Lat=51.348055, Lon=-00.558889, Dist=18.823578 81468 Airport019=EGLM, Lat=51.500833, Lon=-00.774444, Dist=30.920015 81468 Airport020=EGTH, Lat=51.765549, Lon=-00.252949, Dist=37.000437 81484 Airport021=EGTI, Lat=51.691868, Lon=-00.416197, Dist=33.740563 81484 Airport022=EGWN, Lat=51.792500, Lon=-00.736833, Dist=43.952029 81484 Airport023=EGTR, Lat=51.655833, Lon=-00.325833, Dist=30.848821 81484 Airport024=EGLG, Lat=51.802500, Lon=-00.158055, Dist=39.085359 81484 Airport025=EGWE, Lat=52.017778, Lon=-00.302222, Dist=52.237888 81484 Airport026=EGLD, Lat=51.588333, Lon=-00.513056, Dist=29.232277 81484 Airport027=EGLL, Lat=51.477500, Lon=-00.461389, Dist=22.449036 81484 Airport028=EGSL, Lat=51.895000, Lon=000.449167, Dist=50.242072 81484 Airport029=EGSG, Lat=51.652500, Lon=000.155833, Dist=32.443759 81500 Airport030=EGKB, Lat=51.330833, Lon=000.032500, Dist=13.168604 81500 Airport031=EGSR, Lat=51.914444, Lon=000.682500, Dist=55.741472 81500 Airport032=EGSS, Lat=51.885000, Lon=000.235000, Dist=46.542111 81500 Airport033=EGLC, Lat=51.505278, Lon=000.055278, Dist=22.849283 81500 Airport034=EGTO, Lat=51.351944, Lon=000.503334, Dist=27.967897 81500 Airport035=EGMC, Lat=51.571389, Lon=000.695555, Dist=41.040969 81500 Airport036=EGSX, Lat=51.721667, Lon=000.154167, Dist=36.301267 81500 Airport037=EGHN, Lat=50.653056, Lon=-01.182222, Dist=48.618229 81500 Airport038=EGDM, Lat=51.152189, Lon=-01.747414, Dist=59.415488 81500 Airport039=EGDN, Lat=51.247178, Lon=-01.754250, Dist=59.889319 81515 Airport040=EGHF, Lat=50.815278, Lon=-01.206944, Dist=44.090497 81515 Airport041=EGVP, Lat=51.142805, Lon=-01.567556, Dist=52.653857 81515 Airport042=EGHP, Lat=51.195795, Lon=-01.238013, Dist=40.313509 81515 Airport043=EGHH, Lat=50.780000, Lon=-01.842500, Dist=67.053301 81515 Airport044=EGHI, Lat=50.950573, Lon=-01.356126, Dist=46.374453 81515 Airport045=EGLS, Lat=51.098889, Lon=-01.784167, Dist=60.914474 81515 Airport046=EGHO, Lat=51.210556, Lon=-01.600000, Dist=53.951172 81515 Airport047=EGVO, Lat=51.234139, Lon=-00.942825, Dist=29.530866 81515 Airport048=EGHL, Lat=51.186667, Lon=-01.031945, Dist=32.545504 81531 Airport049=EGHJ, Lat=50.678056, Lon=-01.109444, Dist=45.519343 81531 Airport050=EGKH, Lat=51.156944, Lon=000.641667, Dist=30.500480 I've checked everything thoroughly. I'm afraid the facility I'm using for this is just plain unreliable. I'd still like to try that place where you only got three, because I can't see how that can happen. But meanwhile I think I should either withdraw the facilty altogether, or just relabel is as "6 nearby airports, possibly not including the nearest". Ugh! :-( Regards Pete

I too get odd results at EGKK. Not the same as you, but not correct. So I'll investigate that. It should list those three. But something else is odd there too, because I checked. The offsets for all 6 slots are always cleared to zero before any are filled in. So I cannot see how there can be three then two zeroed then another. That looks impossible. So, can you tell me where to "Go To" to reproduce the oddity with only 3 please? I need to reproduce it here. No, to log your accesses you use IPC read or write logging. Yes. It is a bit-oriented set of 28 flags, so setting some gets hard in decimal, so it is normally used in hexadecimal (so you can set bit 27 for instance by x8000000). You must know hex 20 is the same as decimal 32? Regards Pete

You've bought the wrong programs. FSX panels cannot run outside of FSX. You have to have two complete installations of FSX, linked by something like WidevieW (not one of my programs). If you would be just as happy with other instrumentation, there are quite a few programs which will give you different types of instrumentation on other PCs on a Network. The payware ones which I know of are: Project Magenta Sim-Avionics Flight Deck Software FSXpand There's also a freeware one which I've lost the reference to. Do a Google search. Regards Pete

If there were only three within the "reality bubble", then the others should all be zero. I'll need to check that too -- can you include that in the test with the logging, please? Would you have expected more than 3 within 80 nm (I think that's the range, but I'm not sure)? Regards Pete

Strange. Can you please add this to the [General] section of your FSUIPC4.INI file: Debug=Please LogExtras=32 (Replace that line if there already). Then reproduce the problems you find and paste the resulting FSUIPC4.LOG contents here, please. Well, it's a documented SimConnect facility, but possibly it's buggy. I would have thought it used the same mechanism as the GPS gauge. I can check it here, but I'm really busy at present so specific examples, like that one, with Logs please, will help. Can I assume you are using a fully updated FSX, or ESP? Regards Pete