Pete Dowson

Run it? Run what? FSUIPC.DLL cannot be run on its own! It is a library file! It has to be installed into FS! Just downloading FSUIPC is not enough. Please extract the files from the ZIP, then find the User Guide. It will be called "User Guide", oddly enough. Read the Installation instructions. You obviously haven't installed it at all! Documentation is provided for people to actually read. The Installation instructions are very very short, consisting of only one step. Pete

with a program, yes, of course. You need really to wire your indicators to all switch off when there's no power. Use a double pole battery switch perhaps? The offsets 0BEC/0BF0/0BF4 are controlled from FS values. Even if you could override them they'd reset back to whatever FS set them to. They aren't really "LED" indficators, but "Gear Position" indicators, varying from full up to full down as the gear moves. Cockpit programming USES FSUIPC facilities, but FSUIPC is not specifically for programming cockpits, only for reading and writing FS data. The drivers for hardware add-ons normally contain whatever logic they need. Regards Pete

Advdisplay is not supported and has not been so for several years, not on FS9 nor on FSX. It most certainly won't work on FSX. It most certainly is not. It was superseded by the special display facilities built into FSUIPC many years ago. Please have a look at the FSUIPC user guide for all the details. Pete

Of course. What else? That is the current User release. It will likely be replaced by 3.82 next week, though. There are also often later, interim releases (without full documentation) available in the "Other downloads" Announcement above. In fact there's a version 3.817 there now. But you should always first get the main release, so you have up-to-date documentation. Pete

It means you are using FS9.01 (i.e. FS2004 updated with the 9.1 patch), but with a version of FSUIPC which pre-dates it -- i.e. a very very very old version of FSUIPC which doesn't recognise 9.01 and needs to run in version 9.00 (the original FS2004). Simply go download and install the current (and supported) version of FSUIPC. Pete

There are only four possibilities: 1. The version of FSUIPC you have installed is, in fact, inadequate for what Flight Tracker requires. Double-check that it is actually 3.81 or later by going into FSUIPC options and reading the version number on screen whilst FS is running. 2. You have FSUIPC registered but with an incorrect registration number. Try temporarily removing your FSUIPC.KEY file from the FS Modules folder so that it becomes unregistered. 3. Same as 2 except that the reason for the invalid registration is that your System Date (set in Windows) is before the date you purchased your registration, which would make it invalid. In this case, correct your system date in Windows. 4. The GlobalSign root certificate is not installed in your Windows, making FSUIPC's codesigning check fail. If this is the case the fact would be logged (see the FSUIPC.Log file in the FS Modules folder. The fix for this is to run the Globalsign Root program provided in the FSUIPC ZIP file. Regards Pete

Yes, the same as you showed originally. As I said then, something is messing up your SimConnect session. If the first such error occurred after 11268 seconds (over 3 hours), I assume you are saying you flew for over 3 hours with no problems at all? Were any extra add-ons added during that time or were they all running right from the start? Why have you let it run for so long? Are you only getting problems after a long session? If so it may actually be memory problems (memory leakage), or possibly hardware, related to heat. I'm not sure what you'd expect me to do with the full log in any case. I couldn't possibly read it all. Some clue is needed first. At present I'd only be interested in the first page or so, just to see how many SimConnect-using programs you have (assuming you started them all up at the start). Of course you might be able to tell me that anyway. I think you may have to use a process of elimination, doing without one of your add-ons at a time till you find which one is causing it. Did you miss my suggestion on this earlier? I'll repeat it: "You could try a process of elimination, dropping one SimConnect component at a time. Start off with whatever you have running remotely, as that will certainly be using TCP/IP." If you aren't using 4.298 (or later, when I make a later version) it probably isn't relevant. Please see the FSX Downloads announcement. Things have moved on. Regards Pete

Yes. Well, yes, for as long as anyone is using them. They are actually produced for RCV5 which is still in Beta, so there's a long term demand for them in any case. That is more difficult to guarantee as the prime (and until you) the only user of the files is Radar Contact, and for a version not released yet. Once it is released i would expect no further changes to those files at all. In the past the only changes have been for ADDITIONAL fields at the end, so if you make no assumptions on the number of parameters per line, only reading what you need, you should be okay. MakeRunways only works fully with FS2004 and FSX. There's no way I'm going to backtrack to FS2002 for the new stuff like gates, taxiways and frequencies. Sorry. MakeRunways doesn't affect any files other than the ones it makes itself. Pete

The Device.cfg file is only used to provide FS with an initial automatic assignment, to suit the specific device (it finds the one with the name reported by the Windows joystick driver). It will only do this when you plug in a device (first, or after having disconnected it) , or if you re-enable the device in the Options-Controls-Assignments dialogue after it has been disabled. To find out whether it is actually a button operating your Gear, and if so which one it is, try enabling Button logging in the Logging page in FSUIPC options, and see what Joystick number/button number it detects. If you enable Event logging too it will show the resulting event(s). Pete

I didn't think V/S hold ever worked on its own in any version of FS. You set a target altitude for altitude hold, then adjust the V/S you require, and FS tries to hold to that V/S until acquiring the altitude. I think if you don't have an altitude set then the V/S won't hold in any case. Pete

I can't understand where your problem is either, because there isn't one described here. A difference of 0.000473 in latitude works out to around 150 feet -- much much shorter than a runway, and 0.000014 in longitude, at that latitude, to less than 4 inches! So, put yourself 150 feet further south then check again! If it is FS2004 default LTBA you are talking about, the "start" positions encoded into the BGL (those places to which FS positions you if you tell it to got to Runway X in the menu) are NOT the centre of the threshold itself, if you compute the latter based on runway length and width. Here's the output for 36R from my MakeRunways program: Start 36R: N40:58:11.7129 E028:48:34.0316 163ft Hdg: 358.5 true Computed start 36R: Lat 40.969452 Long 28.809471 You'll see that the computed ("ideal") start is different from the START location encoded in the BGL: N40:58:11.7129 = 40.9699203 E028:48:34.0316 = 28.8094532 in other words, spot on what you are reading programmatically! You know you can also check your position using Shift+Z, on screen, don't you? Or in the Map view? Pete

4.298 is available now. I've checked the default feedback settings here and so far they seem to work about as well as it did in FS2004 -- i.e. not bad for pitch and bank, a little unstable for speed and mach. And the 90% N1 limit default for jets seems to be too severe a restriction on FSX compared to FS2004. Maybe a higher default is needed? Is FSX underpowered compared to FS2004? Pete

Your request is illogical! How can I provide an update before the next update? That would be the next update! That's what "next" means! The one which comes next! I am working on fixing it now. When it is done it will be compiled and supplied as the next update! They aren't scheduled like trains, I provide them when something significant is changed. This is a change, I am working on it at the moment. Answering daft messages slows it down, of course ... I don't see how you can rely on it, however, as it won't necessarily be working 'properly' -- i.e. actually stabilly controlling the aircraft. That may need some adjustments, and for that I would need feedback. Pete

OkayI found the problem. In fact the internal table for the feedback functions got screwed up a little when I re-coded it for FSX, and of course I'd not gotten around to testing it in FSX yet. It looks like only the pitch feedback part would have had any chance of working. I'll fix the tables in the next increment -- watch out for 4.298 or later in the FSX Downloads announcement above. I can't guarantee that the facility will work well in FSX. The various parameters and timings will probably need adjusting. However, please do feedback any results you do get. Regards Pete

Have you tried using the panning controls instead of the viewing controls at all? Not being a VC user I've never really experimented with any of that stuff. However, there have been other threads here with examples, and in fact the solutions shoown below are currently published in the FSUIPC4 User Guide (and due to go into the next update for FSUIPC3's User Guide): Regards Pete

I've no idea how to do that I'm afraid. Sorry. Maybe it should be a SimConnect option in the next version of FS -- send your ideas to tell_fs@microsoft.com. Pete

Groan! :( :( :( 337D was added in version 3.22 of FSUIPC, in May 2004, as you would see if you reviewed the History document supplied with FSUIPC. I've no idea what "IOCARD MANUAL" is, but I cannot possibly support you unless you are using my latest tools. The latest SDK with the reference materials is ALWAYS provided at www.schiratti.com/dowson, as pointed to in all my documents, with sometimes interim updates available in the Announcements above. Please please PLEASE always review the Announcements, especially the one about "supported versions", before asking for support! Pete

The difference between the two is simply that you have no updated your FSUIPC3 version to the same level as your FSUIPC4 version, as the feedback facilities were added as general FSUIPC-added controls to both recently, as you would notice if you read the release notes. No idea at all I'm afraid. These were experimental untested facilities which i only released generally because i was told they worked. Please refer to the reports earlier in this thread. Unfortunately, even after I "fixed" the problem reported earlier I've had no feedback at all from "737nut". You will note that I said "You'll need to test it out in FSUIPC4 as I doubt it has ever been used." I've actually never been in a position to even look at them in FSX. To verify that it isn't something in your code, can you try the FSUIPC controls instead? Regards Pete

Refer to the User documentation, in the section entitled "Visibility (Optional)". Documentation is provided for users to refer to. It does work out a bit quicker and even easier, usually, than posting questions for support, honest! Pete

What has "programming" got to do with it? There's no programming involved for asuch things, only assignment of buttons to controls. If you check FS's own help you would find that the jet fuel idle/cut off levers are controlled by the Ctr;+Shift+F4 and Ctrl+Shift+F1 short-cuts, which in fact are the "Mixture Rich" and "Mixture Lean" controls --- FS actually controls the fuel flow valves using the mixture controls (which makes sense when you think about it). So, for separate engine start levers simply assign a lever each to "Mixture1 rich", "Mixture2 rich" etc when "On" (or "Pressed"), and "Mixture1 lean", "Mixture2 lean" etc when "off" (or "Released"). Please use FSUIPC's event logging (on the Logging page) when wanting to find out what control does what. With that enabled, when you operate the control in the cockpit, whether by mouse or keyboard, or button, it will be logged in the FSUIPC log and you can read its name there. Pete

I don't know of any message like that. Can you be more specific, please? Exactly what program or add-on is producing the message? What does it look like, and what exactly does it say? When FS is ready to fly, is there a Modules menu with FSUIPC options listed? If so, what does the first tab, the About page say? Can you find the FSUIPC.Log file in the Modules folder? Does that show anything? Pete

Good. It isn't supported in any case. ;-) There is no difference in that facility, none whatsoever, and exactly the same HotKey assignment works fine. See the Hot Keys tab. Pete

Use Search, it is much faster and less liable to error! It is called "structural de-ice" in FS, offset 337D. The default FS aircraft have EFIS options only controllable by Mouse. there are no internal controls nor keystrokes nor any other way of dealing with those. If you are serious about building a cockpit you won't be using default aircraft in any case, surely? Please read the documentation supplied, and note the "ignore" button. Your R and Z axes are jittering so much that the changes on them are seen before you have a chance to move the others. Either try and park them in a spot where they don't jitter (usually one end or the other), or use the facilities provided in FSUIPC to deal with this situation -- as exactly described in the documentation (find the paragraph starting "If the displayed axis is not the one you want to set ..."). Pete

Well, joystick button programmed to send a keypress in FSUIPC. The only touch screens I have are in my 737NG cockpit, used to select options for RC and other programs, things that don't "fit" in a "real cockpit". They are little 7" affairs screwed to the sides, below the side windows, handy for pilot or copilot. They are both connected to the same PC and do identical jobs. If you look in the WideFS documentation you will see the details of the facilities WideClient offers for them. For all other cockpit operations I prefer the real switches. ;-) Regards Pete

I assumed so. I've heard of VoiceBuddy. Not sure what "touchbuddy" is for. Ah, for a touch-sensitive screen? I see. No, not at all. You can read the keyboard at key level, at Windows KEY message level, and at Windows CHAR message level. Also there's a Windows HotKey facility which can undermine most of the others. Yes, but i don't think that helps really. If the thing you want to send them to doesn't see them then it doesn't matter how many other things do, does it? So, maybe you should ask them to change their programming? No, because it is a facility for programmers, though it is also used in WideClinet -- in fact Wideclient implements a touch-screen button array, something I added specifically to support the two 7" touch screens I added to my cockpit. As I said in my last message, if you want to proceed down this route I will explain. But before you start you should really check that FSUIPC's keypresses are recognised by the LevelD autopilot. If not you will be wasting your time. To do this without much trouble you need a joystick button to program. Try programming one to send your letter "A" for instance, see if it selects the left A/P. What? I shouldn't even be talking to you if you are using an unsupported version! What's the point of sticking to such old outdated and unsupported versions? I really don't understand why folks don't keep up to date -- especially when coming here requesting support. Please read the Announcements at the top of the Forum! The documentation contains examples already. Please use a supported version of FSUIPC before you come back. Regards Pete