Pete Dowson

Ah. Sorry. I've never heard of that program. Yes, it is clear, but I think you are more likely to get a helpful reply if you post your questions in the MyTraffic support forum, not here which is for FSUIPC and my other programs. I really don't have anything to do with MyTraffic, except as a happy user! Regards Pete

Doesn't MTX just work on Vista the same as on WinXP? I can't imagine there being any need for any difference. "Using" My Traffic X? I simply installed it, and traffic appears, very nicely. What do you mean by "using" it, exactly? Really you would do a lot better posting such questions on the MyTraffic support forum, just two entries in the Forum list above this one I think. Burkhard works very hard supporting everyone in that Forum. Regards Pete

Sorry, I've no idea what your gauge is reading. Care to be more explicit about how it works -- specifically what FS variables is it reading? Maybe the gauge is not written correctly? This must be the case if the flight controls are operating correctly despite the false readings, don't you think? Not really, at least without further information. It is easy for you to check whether the gauge still works without the calibration enabled, just disable it (press the appropriate "reset" button(s) -- you can always re-enable these afterwards). If you've assigned your flight controls through FSUIPC4 then, depending on what your gauge is reading, it may not work in any case -- it could be reading the joystick value rather than the actual control surface positions. Please ALWAYS state the version of FSUIPC when asking questions here. Regards Pete

I use the complete Boeing suite -- 3 x PFC (pilot, Eicas, copilot), MCP, CDU, RCDU, pmSystems, pmSounds. I've been using PM for many years now. They are shown okay on my (only) Eicas. Not really. The display is owned by and driven by the PM "PFD.EXE" software, and that operates by reading FS values. . If PM is not working correctly for you you need to write to PM's Support. Unfortunately hey don't operate a support forum now, though you could ask other PM users over on http://www.mycockpit.org/forums/forumdi27981&f=99 Regards Pete

Why not simply reverse the axis? Both FS and FSUIPC (if you use the calibration there) have reverse options. It is actually quite normal for the throttle axis to be reversed and normally the defaults set in FS for your joystick driver would set them so -- seems the drivers for Flight Link throttles aren't setting these correctly? No matter though, it is only a check box in FSX (or in FSUIPC -- but don't check both!). Don't use both -- a double reverse is the same as no reverseobviously? If you don't mean that then please explain what you mean by "no success". Please always quote version numbers of my software when asking for help. Regards Pete

Right. Vista stops programs writing and changing files in the Program files folder -- they are apparently supposed to put them all in "AppData" folders, part of the system's "Documents and Settings" replacement. Ugh. I prefer keeping all parts of a program together -- easier to install, easier to delete. My advice, therefore, for Vista is NEVER EVER install anything in "Program Files". Regards Pete

I've just put Wideclient 6.75 on my only Vista PC, together with FSInterrogate2, and it runs okay without using "run as administrator". It connects immediately to my FS installation on another PC. I placed it into my FSInterrogate folder on the C:\ drive, not in "Program Files" anywhere. Are you sure you are not simply running into Vista's default protection of the Program Files folders? Regards Pete

Er .. I am not aware of anything WideFS does which needs any administrator privileges whatsoever. Could you explain in more detail please? I obviously cannot change things if there's nothing to change. To start with, what part of "WideFS" are you talking about, and what version? What are the symptoms of not running it as administrator? Is it possibly simply related to where you have it installed? Regards Pete

Are you calibrating your controls through FSUIPC? Have you set some of the A/P options in the "miscellaneous" page which the LDS767 doesn't like? Sorry, not heard of either of those, and there won't be a conflict with FSUIPC. couldn't say about the LDS767. All that would have done is lose all your FSUIPC calibrations and buttons setting, and other options, resetting everything to defaultwhich basically makes it do practically nothing at all. FSUIPC.INI is named FSUIPC.INI. What text doc? You mean the FSUIPC.LOG file? You don't (didn't) need to delete anything anyway. Both the INI and LOG files are text -- you can read them in Notepad and paste them here. INI type files are standard Windows configuration settings files, whilst Log files are output=only files containing records of what happens. There are Logging options in the Logging page. See the documentation (which is NOT a "text" file but a DOC or PDF). If you are getting confused you probably have Windows hiding the proper filenames -- an option which seems to be of no use whatsoever ot me except to confuse folks. Best to turn it off. Pete

The ZIP by that name contains the tools and an example for writing programs to interface to FSUIPC, in the C (or C++) language. There are little packages for each language. I did the C one, other folks have kindly added the others. I attach my latest FSI, but to use this you may need to download the updated FSInterrogate2 program from the FSX Downloads announcement above, as it now contains stuff for FSX too and the version you have will probably not recognise FSX. Regards Pete FSUIPC FSI.zip

Did you run FSX "as administrator", as instructed in the documentation? You cannot register otherwise. Pete

Do you mean there is no Add-Ons menu entry? If so, please let me see both the Install FSUIPC4 log and the FSUIPC4 log files from your FS Modules folder. If not, please explain a little more. Regards Pete

I'm surprised you can do any of them -- what happens to the real value, coming from FS, then? Or is this without engines running? Is this with FS9 or FSX? You mean is FSInterrogate written in C? No, I think Pelle used Delphi. Regards Pete

Control N1? N1 is a result, not a control. You control the engine with the throttle levers, the simulation computes the resulting N1, N2 and EGT figures. Even if FS allowed you to overwrite the computed value it would be changed again immediately on the next simulation cycle. Sorry, you've lost me. I've never used this "see also" tab. What do you think it will do? Surely it is only a documentary aid. It won't actually do anything in the sim. It is a note for you, the reader. The PM glass cockpit program will be reading the Sim's N1 value, not yours. If you want it to display your value (why? Don't you want to know the real value?) you'd have to get Enrico to write you a special version of his program. I really don't understand what you are trying to do. Are not not happy with the Sim's computation of N1? Surely the correct way to fix it, if so, is to work on the FS aircraft model, either via the Aircraft.CFG file or the .Air file? The FSI file has nothing to do with Flight simulator at all, as I already explained. It is merely the data file for FSInterrogate, so it can show you in an easier explanatory fashion what you are looking at. FSInterrogate is a useful program for folks wishing to write FSUIPC application programs as it enables them to experiment and see what is happening, and also debug their programs. But it has nothing whatsoever to do with how Microsoft's simulators perform their simulation! Regards Pete

It can be used for both reading and writing offsets. There are several ways provided to write data as well as read. The documentation is quite comprehensive I think, too. FSInterrogate is an external program and can be run from any folder of your choice. Nothing "happens" automatically no matter where you put it. The FSI file will only be read when you run the program. Nothing else uses it. What "new offset" are you adding? Have I missed one out? I thought I'd already added most -- maybe I've not yet added some of the very recent ones. If you need a full up-to-date copy I can send you one. Or are you simply adding details for third-party applications using FSUIPC offsets, like Project Magenta? Regards Pete

OK, good. That's a better note to end the thread with. Regards Pete

Yes, exactly as documented. There is no reverser axis in FS. I repeat THERE IS NO REVERSER AXIS IN FS! In order to support a reverser axis I have to "steal" another axis that IS in FS. The aircraft which will have reverser levers do not also have mixture levers, therefore it was and remains a good choice! In other words, it is precisely because "those two controls seem not to go together in any way" that they make good alternatives. If i had stolen a control which was useful in an aircraft which could use a reverser it would have been very awkward. No, not at all. From where I sit you seem to be deliberately persisting in not understanding what I say for no good reason. Let's end this here and now. It isn't going anywhere at all. Pete

Sorry, I don't understand where "Enter" comes in -- is that in combination with the other 4, or separated, afterwards? Certainly combinations like ALT+CTRL+SHFT+'1' are possible, though there is always the danger that the ALT part will invoke FS's menu system. Ahprobably not with FSUIPC button assignments, as it only sends the key-presses to FS. Possibly your KVM software will intercept these, but it seems unlikely. I think these usually intercept keypress combinations at a much lower level, which would mean either a real keyboard or something which could emulate it at the right level. Regards Pete

FS9 should have got itself installed as a "non-Vista aware" program. Vista does strange things with such programs to ensure that they can even write to their own folders, like mimicking the actual folder elsewhere. This can certainly confuse programs quite a lot. I know it confuses me. Personally I think Vista is rather a disaster in its current state and I am not using it for anything serious until it looks better. Maybe after the promised SP1 update? Regards Pete

Right, as I said. If it is being used as mixture then it will certainly cut the engines when pulled right back! It is NOT a throttle! Oh dear, you still misunderstand what I've been saying, and what the documentation tells you? How? :-( The mixture IS the mixture!!! You *can* use it as a reverser, via FSUIPC, but only if you tell FSUIPC to so do. It is one option available to you! In order to use it as a reverser you "Set" it (i.e. press the "Set" button top left in the Reverser section), and calibrate it as a reverser. Then it is no longer a mixture control at all and will instead act as a reverser instead. Please please do take some time to read the user guide. Regards Pete

Something very wrong there then. Are you sure that's a throttle and not a mixture? If you lean the mixture completely that will kill the relevant engine for sure (or all engines for the non-specific mixture control) -- in both a prop and a jet. In a jet the mixture is used in FS as the idle/cutoff lever. I think you have definitely got it assigned as a mixture lever, not a throttle. It is the only explanation. depends on the aircraft. Jet airliners tend to have reversing levers which can only be operated after pulling the throttles back to idle. Pete

Well, it is optionally set to the mixture, yes. It is configurable of course (and INI file option -- you can use any otherwise unused FS axis control)). And it isn't actually set unless you set it in the calibration screen. Of course you can do it that way if you wish. The choice is entirely yours. On a full throttle quadrant the reversing levers, although attached to the throttle levers, are separate "axes", but if you are short of levers you do it whichever way suits you. The addition of separate reverser calibration in FSUIPC (both the single one and the 4 separate ones for up to 4 engines) were later additions. Up until then everyone calibrated a reverse section of the main throttle levers, with idle as a sort of "centre". You don't seem to understand. There's nothing "tied" to mixture, that only happens if you set it. Just do not "Set" the reverser (press "Reset" if you have already) and it is the mixture again!!! And engines don't "cut off" if you reduce the thrust to idle, they simply idle. Where have you read that sort of stuff? If you want to calibrate throttles with a reverse section, just follow the detailed instructions provided. I am not about to reproduce sections of the User Guide here. Please do refer to it! Pete

You never need to run it as administrator EXCEPT to register FSUIPC. This is because the registration enters some small things in the Registry. FSUIPC doesn't touch anything else in the system in normal execution. Pete

The controls are FS controls. Whether they were actually listed in FS's own assignments I've no idea without loading old versions of FS up and looking. Sorry. How weird. I've honestly not seen any difference here. Maybe it's to do with the "defaults" for the specific joystick connected. There are files which define which buttons, by default, do what when FS detects a specific joystick. Maybe they have changed. Maybe. Sorry, I don't know how you did it in FS9 or before. Why not load FS9 up and take a look? Equally, if you had made assignments in FSUIPC3 then you'd only need to copy over your old FSUIPC.INI and rename it FSUIPC4.INI to get the same assignments. Good. Regards Pete

There's no such change that I know of. The controls are as they were -- there are Gear toggle, Gear Up and Gear Down controls just as before. The 'G' key is the default assignment for Gear Toggle and that is the one normally assignable in FS assignments. It must have been assigned to do Gear Up one way and Gear down the other. I doubt whether that was by default, however, as the separate controls are not usually assignable via the FS settings. That sounds more like how I would expect the default assignment to be. Just do the assignments yourself. The gear up and down controls are accessible through FSUIPC's buttons and switches page. Regards Pete