Pete Dowson

Hmm. I'll try disabling WideFS, just as a test. I normally have 7 or 8 clients running. It is certainly a change brought about by the latest UT2 hotfix, though, as it was fine before.. I'm not able to test again today, but I'll try tomorrow. Okay. Thanks. Pete

I don't know which values you are wanting to change, but those two aircraft have their own autopilot -- they do not use the FS autopilot -- so you have to program controls to operate them specifically, differently. I cannot instruct you on this -- there will be plenty of help in their respective support forums. At the lowest level you should be able to program your controls to send the assigned keystrokes, according to the aircraft's documentation. There is also the possibility of using FSUIPC's "mouse macro" facilities, to allow buttons, knobs and so on to directly influence the cockpit just like the mouse. This technique is known to work particularly well with the PMDG series of aircraft. I don't know much about the LEvel D. Regards Pete

Not as such. There's an (out of date) list of FSUIPC-using applications along the right-hand side of the Schiratti download page. Many, but possibly not all, of those would work on a WideFS client. Obviously not any of the add-on aircraft, and possibly not some of the programs needing intimate access to FS's file. Best regards, Pete

I haven't checked the taxiway data provided by the AFD file, but I can do so if needed. It is quite possible that this information is neglected or incomplete for EGLC, it being really just a runway with a connected parking area. I still believe the problem with the Exclude file should be notified to Aerosoft. Regards Pete

No, sorry. Now I am confused. You cannot configure keys in FSUIPC from a client PC. The client PC has its own keyboard. You can SEND keypresses from that keyboard to the FS PC, and what you then do with them is up to you -- they might be FS keypresses, or hotkeys, or ones you want to program in FSUIPC. Perhaps it would be better if you explained what you actually want to do, then maybe I can suggest the best solution? Regards Pete

Okay .. no need to send me the file! I've checked. I have now have Aerosoft's London City installed. Here's the EGLC references according to my MakeRwys scan: (the first is the FSX default) Airport EGLC N51:30:18.9957 E000:03:18.9995 19ft City Name="London" Airport Name="London City" in file: Scenery\0601\scenery\APX48130.bgl Runway 10 /28 centre: N51:30:18.8337 E000:03:17.5879 19ft Start 10 : N51:30:20.0323 E000:02:39.8814 19ft Hdg: 92.9 true Computed start 10 : Lat 51.505573 Long 0.044037 Offset Threshold primary: 400 feet Start 28 : N51:30:17.6675 E000:03:55.2944 19ft Hdg: 272.9 true Computed start 28 : Lat 51.504887 Long 0.065734 Offset Threshold secondary: 160 feet Hdg: 92.900 true (MagVar -3.000), CONCRETE, 4930 x 98 ft Primary ILS ID = ILST Primary ILS: ILST 111.15 Hdg: 92.9 , Flags: GS DME BC "ILS/DME 10" Secondary ILS ID = ILSR Secondary ILS: ILSR 111.15 Hdg: 272.9 , Flags: GS DME BC "ILS/DME 28" *** Runway *** EGLC0100 Lat 51.505573 Long 0.044037 Alt 19 Hdg 96 Len 4930 Wid 98 ILS 111.15, Flags: GS DME BC *** Runway *** EGLC0280 Lat 51.504887 Long 0.065734 Alt 19 Hdg 276 Len 4930 Wid 98 ILS 111.15, Flags: GS DME BC ... Airport EGLC N51:30:18.9957 E000:03:18.9995 20ft City Name="London" Airport Name="London City" in file: Aerosoft\EGLC Airport\scenery\EGLC_ADE_PD.bgl Delete all taxiways! Delete all runways and starts! *** DelBth *** EGLC0100 Lat 51.505474 Long 0.045493 Alt 19 Hdg 96 Len 4402 Wid 98 ILS 111.15, Flags: GS DME BC *** DelBth *** EGLC0280 Lat 51.504864 Long 0.064867 Alt 19 Hdg 276 Len 4402 Wid 98 ILS 111.15, Flags: GS DME BC Delete all taxiways! COM: Delete all frequencies! Runway 10 /28 centre: N51:30:18.8661 E000:03:18.4473 20ft Start 10 : N51:30:19.9999 E000:02:40.3419 10ft Hdg: 92.7 true Computed start 10 : Lat 51.505558 Long 0.044234 Offset Threshold primary: 164 feet Start 28 : N51:30:17.7971 E000:03:55.3089 10ft Hdg: 272.7 true Computed start 28 : Lat 51.504925 Long 0.066015 Offset Threshold secondary: 164 feet Hdg: 92.663 true (MagVar -3.000), CONCRETE, 4948 x 98 ft Primary ILS ID = ILST Primary ILS: ILST 111.15 Hdg: 92.7 , Flags: GS DME BC "ILS/DME 10" Secondary ILS ID = ILSR Secondary ILS: ILSR 111.15 Hdg: 272.7 , Flags: GS DME BC "ILS/DME 28" *** Runway *** EGLC0100 Lat 51.505558 Long 0.044234 Alt 20 Hdg 96 Len 4948 Wid 98 ILS 111.15, Flags: GS DME BC *** Runway *** EGLC0280 Lat 51.504925 Long 0.066015 Alt 20 Hdg 276 Len 4948 Wid 98 ILS 111.15, Flags: GS DME BC etc ... Airport EGLC N51:30:18.9957 E000:03:18.9995 20ft City Name="London" Airport Name="London City" in file: Aerosoft\EGLC Airport\scenery\EGLC_exclude.bgl Delete all taxiways! Delete all runways and starts! *** DelBth *** EGLC0100 Lat 51.505558 Long 0.044234 Alt 20 Hdg 96 Len 4948 Wid 98 ILS 111.15, Flags: GS DME BC *** DelBth *** EGLC0280 Lat 51.504925 Long 0.066015 Alt 20 Hdg 276 Len 4948 Wid 98 ILS 111.15, Flags: GS DME BC Delete all taxiways! COM: Delete all frequencies! Note that the file EGLC_ADE_PD.bgl does contain all the ADF information (I've omitted all the taxiway and parking data, but it is all there. The extracts you posted earlier were, I think misleading. Too much deleted! But notice that EGLC_exclude.bgl file DELETES everything just included. The order in which the BGLs are processed in a single folder depends upon the order they exist in the folder's directory -- so it is actually pot luck. In fact, since the Alphabetic order puts EXCLUDE after ADE it is more than likely that the order is wrong. I really do not see the point of the EXCLUDE file in any case, as it is merely repeating the same instructions as at the start of the AFD file. So try disabling it -- change its .BGL ending to .BGX. I think this is an oversight or error on the part of the scenery designer. The only sure way to get scenery files processed in a specific order is to put them in separate folders and use the CFG layering. You should report the problem to Aerosoft even if you find the solution is okay. Regards Pete

In this case they must presumably not have bothered to create their own runways, taxiways, parking spaces and so on -- all this is in an AFD file. note that AFD data does not have to be in a spearate file. No,no. you misunderstand. it scans ALL of the enabled scenery, in the priority order dictated by the SCENERY.CFG file, obeying every instruction relating to the date the files include. It is NOT scanning EGLC twice. The first EGLC file will always be the FS default one. The EGLC add-on is deleting that data by explicit instruction. It MUST replace it with its own, else there is absolutely no point in it being deleted. It still looks like there's a file missing or an error. I respectfully suggest you raise this with Aerosoft support. It really must be going wrong in FS itself too, because FS and M akeRunways processes these things in the same way. That'll be the default. If the extract you posted here was complete for file EGLC_ADE_BR then there's no runway data there! Maybe the bits of the file you posted were incomplete? If you'd like to ZIP the file and send it to me at petedowson@btconnect.com I'll check further. Possibly the data you are giving me is very misleading due to extreme editing? [LATER] One check you can make: In the FS "Go to airport" menu, can you select runways and parking spaces for EGLC? Regards Pete

To do what? I'm sure you can assign your keypresses to buttons in FSUIPCEVERYONE, and I do mean EVERYONE, can do that. I cannot explain more here than is shown in the documentation, and in any case it is all evident on screen. If you've not even tried, then go do so. No one is going to do ALL of your work for you. If you are intelligent enough to fly an aircraft then you are certainly more than intelligent enough to do simple things like make buttons send keypresses. Well if you are happy using the GF software, what is the problem? If you cannot even assign keypresses in FSUIPC, then I would not even try to use GFdisplay. It will be too much for you. Sorry. But why worry about the LEDs? Regards Pete

Oh, the pass-through for FS controls, the same as assigning controls to a button. If an add-on invents new switches and doesn't re-use FS controls to drive them, then naturally FS controls aren't involved and have no effect. So they are not specific aircraft controls and certainly not something implemented in FS itself? That's why there are no FS controls for them. You'd need to see if the Mouse Macro facilities in FSUIPC will operate them. If not, if they will only respond to real mouse clciks, I'm afraid you'd need something like the Key2Mouse program. Regards Pete

I'm sure there's an example for VB6 in the SDK. Did you look? Regards Pete

The Add-Ons tab is a menu item in the Menu bar in FSX, when you are flying. According to the log, that is most certainly there. Pete

Perhaps VAFS doesn't like FSX? Have you asked their support? You have something wrong, somehow, in any case: You installed 4.52, yet: You are running FSUIPC 4.50. How do you do that? Otherwise FSUIPC4 is fine. you must ask the VAFS folks. Regards Pete

I don't know of any program fussy about versions. what do VAFS support say? Pete

When calibrating the brakes in FSUIPC, be sure to press them a little (to get the values well off the "feet off" value) before pressing the minimum 'Set' button. And press the maximum set without pressing the brakes fully to make sure you can always reach maximum braking. This process applies to all axes, and it is actually described in the steps for calibration in the seldom-read FSUIPC User guide. ;-). Regards Pete

The GFdisplay program can do anything you like with the LEDs, provided the state needed can be determined from FSUIPC offset values. Unfortunately, except for Door Open, none of your assign commands are releated to anything in FS itself, only some add-on program, so there's no way FSUIPC can provide the inforation which GFdisply would need. It is possible to do what you want, but not easy for that reason. You would need not only to assign key keypresses you want to each button, but also an FSUIPC control called "Offset byte togglebits", which will change the value in an offset which GFdisplay could test. Try this: Assign the Press of your button to the keypress you want. Assign the Release of your button to "Offset byte togglebits", with the Offset entry set to x66C0 and the parameter set to 1 (then 2, 4, 8 etc for other buttons). In the GFdisplay file you'd then set the LEDs by [GFP8.0] L0.1=X66C0 U16 M0001 L1.1=X66C0 U16 M0002 L2.1=X66C0 U16 M0004 L3.1=X66C0 U16 M0008 etc Regards Pete

You can assign several actions to a button, but only via editing the INI file -- you cannot do this in the on-line assignments. You might find it better to use a macro and then assign to the macro in FSUIPC. Hmmm. Sorry, I've no idea about that. If you write to 88C directly instead, how how does it take to change back to 4000? No. If you are writing to 089A, then you don't want to disconnect the axis, because the whole point of 089A instead of 088C is to allow it to be disconnected liker an axis!! This is clearly mentioned in the document. If you are controlling via 088C or via 089A, only, then you should vertainly have no aix assigned to that throttle in either FSUIPC or FS -- that will be overriding you otherwise (though if it keeps overriding there must be some jitter, as both FSUIPC and FS only act on changes). Regards Pete

The methods for assigning and calibrating throttles, or any other axes for that matter, are the same in FSUIPC3 and FSUIPC4. It sounds like you simply are not actually calibrating -- please follow the steps in the documentation. If you are happy with your FSUIPC3 settings you could even use the FSUIPC.INI file from FSUIPC3, renaming it to FSUIPC4.INI. Note, though, that if you are using FSUIPC axis assignment, some of the axis numbers may be different. Regards Pete

What do the up, down and primary buttons actually do? The term EFIS is a rather general term for lots of controls relating to display options, I've no idea what yours does unless you explain. They certainly won't be listed under "up, down and primary". Mostly they will be local to the gauges which they relate to, with no access in FS proper. There's an offset which controls most of FS functions? Really? All in one place? Where? Sorry, more information certainly needed. Have you tried using FSUIPC's Event logging to see if those buttons send any FS controls? Regards Pete

If it causes MakeRunways a problem, it would also cause FSX a problem, as both a scanning in the same order and obeying the same instructions. If these entries are all there are, i.e. all deletes but no new runway details, then MakeRunways is correct in not including the runways, as they've been correctly deleted. I cannot get MakeRunways to add runways without any information about them! I think you have an AFD file missing! Please show me the folder listing for the Scenery folder of the installed EGLC. I'll compare it with mine. Without an AFD (airport facilities data) BGL (also known as an AFCAD), then there's no information which MakeRunways can possibly include! Regards Pete

Are you using the very latest update to FSUIPC3, from the Updates announcement above? If not, please do so. Regards Pete

I don't know what program is after Internet access, but it certainly isn't FSUIPC or anything else of mine! Regards Pete

I think uninstalling FSX or any parts of it nearly always causes problems. It is likely that the SP1 version of SimConnect was not uninstalled when you removed SP1. So the FSUIPC installer is quite happy with what it installed. No, it is nothing to do with Firewalls. The FSUIPC4.LOG file would be useful for confirmation of what i think, but basically you have a messed-up SimConnect. You could try deleting SimConnect, as described in the FSX Help announcement above, then repairing your installation from the FSX DVD. But I would strongly recommend reinstalling SP1 and then also get and install FSX SP2. This last fixes many problems. you should really not be still using the bug-ridden original release of FSX. Regards Pete

A correct guess. The other one isn't provided at present, but I can easily add it if needed. The main priority for FSUIPC4 was to provided at least what was provided by FSUIPC3. Most of the rest is added on request. I originally assumed that new programs for FSX would tend to be using SimConnect directly. If you need it, let me know and I'll add it in an interim update. Regards Pete

I don't know if I can access mission stuff through SimConnect. I'll have a quick look now ... ... No, nothing listed at all for SimConnect access. Do you program missions? If so, maybe there's something you can do when it completes which will be readable from SimConnect, like switch a light on or off or some other sort of similar signal? Regards Pete

So, you want to send a Key Press to a program on the Client PC, from the FS PC. Right? Yes, it is possible, and the instructions are in the WideFS documentation. You assign a button or keypress in FSUIPC to a special control in the list called "KeySend". You can have up to 255 of these, distinguished by a parameter value of 1-255. Then, in the WideClient.INI file (in the same folder as the WideClient program) you tell WideClient what it should do upon receiving the KeySend. This is explained, along with some examples, and the list of key codes, in the WideFS documentation. Every one starts of as a beginner, and beginners need to look at the documentation and follow the examples. That is why documentation is provided. By all means, when you've looked and tried, if you then still have a problem, ask specific questions. Regards Pete