Pete Dowson

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. See offset 3302. Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. Map the single throttle to 4 throttles, then go to the 4 throttles page and calibrate throttle 1 there with a centre idle zone and a reverse minimum, as documented. Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. First make sure al the files from FStarRC ZIP are in the same folder as your FliteStar program. Then you run FStarRC instead of FliteStar -- it loads the latter for you. For an FS PLN file you merely need to edit the FStarRC.INI file (found in the same folder as FliteStar and FStarRC to give it the folder path for the FS2004 file, and it will make a PLN file and place it there for you. No conversion is needed. Can you please explain what you found confusing in the documentation, so I can improve it? Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. If the program supports standard NMEA sentences and you can provide a serial port link between the two which works, then it should be okay. I suspect you will need to ask the Support of the program you are using. Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. Did you cut-and-paste your name and email address too? If not it is most likely you made an error in one of those. As clearly stated in the email you received, all three parts must be exactly correct. I don't make or distribute keys at all. I do programming development and technical support. SimMarket do all the rest. Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. The most likely reason for that is a bad key -- usually one made and supplied by pirates. If you email your registration details and FSUIPC.KEY file (Zipped please) to me at petedowson@btconnect.com I can check it for you. Where did you purchase it please? Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. Just check the option for the reverser assignment to only operate with jet aircraft, for which you need no mixture axis. Yes of course -- just edit the assignment in the FSUIPC.INI file before loading FS. The FS axis control numbers you need are listed in the FS controls document included in the FSUIPC Zip. Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. What version of WideFS? I can only support the latest, 6.50. If you use that and have WinXP on both PCs you don't need to add either SeverName or ServerNode details. If it is running then Wideclient won't run. WideFS links non-FS PCs to the FS server PC. Please check the documentation. Regards, Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. I'm sorry, but this is a question for PM support. All FSUIPC does is toggle or set bits according to the defined PM offsets interface. There are alternative methods for some of these things, for example, via values written to offset 04F4 (see the PM offsets list on the PM website, and/or my Advanced User's guide), so you might try those. Some things were broken in some PM releases I know, so also check latest builds. Regards Pete

Apologies for the delay in my reply -- as announced in this Forum I've been away with no Internet access from 24th September until 12th October. You get an email with your registration details within 24 hours or else fill in a problem ticket, EXACTLY as it says in the place where you ordered it. Mr. Schiratti has a website where you can download my programs, but he is nothing to do with SimMarket and will not be writing to you! Regards, Pete

You posted this twice? See my other reply please. Pete

Apologies for the delay in my reply -- as announced at the top of this Forum I've been away with no Internet access from 24th September until 12th October. "Latest" being what version number please? 3.50 is current. Many folks mean "the last version I saw" when they say "latest", and it has happened that this has been a year out of date! ;-) What "throttle quad"? The CH one, or the GoFlight one, or another? There's quite a lot of threads here about the CH quad, and some references to articles by Bob "Sticky" Church, the CH expert. Have you tried with a default aircraft? I think the PMDG aircraft are pretty unique and do their own thing. Get it sorted with a default aircraft first. I'm afraid I don't know the PMDG 747 at all, but there should be enough documentation supplied with it for you to at keast igure out keypress assignments. The correct actions for FS probably won't be the correct actions for PMDG aircraft. I suspect you will need to make keypress asignments. Regards, Pete

Hmm. Why would you think that? I don't think CH would ever supply a device that needs a third party program in order to work. No! They provide their own drivers. FSUIPC is not a device driver by any stretch of the imagination. However, that said, some folks have found they can get better use out of the quadrant using FSUIPC rather than, or sometimes together with, the CH control manager. Not having such a device myself, I really couldn't advise any further, which is why I referred you to the expert. "Erase" what values showing up where? FSUIPC does not provide any "programming" facilities for joysticks in any manner you seem to be thinking. It can, optionally, calibrate specific FS controls, internally, which may be assigned, externally, to joystick axes. That is all. In the joysticks section an axis is calibrated by FSUIPC if it displays the Min/Centre/Max values (or whatever are appropriate to the axis) and the top left button in the axis section says "Reset". If you press the "reset" button, it resets the calibration and then FSUIPC has nothing whatsoever to do with it. The button will then read "Set", meaning that you press it to set it. This is in the user documentation, which I really do recommend you peruse at some stage. Regards, Pete

If you are wanting to write a program to interface to FSUIPC then you'll find all you need in the FSUIPC SDK, available from http://www.schiratti.com/dowson. If you simply mean "assigning an axis" to perform those functions, then first of all you calibrate your joystick axes in Windows Game Controllers, then, in FS, go to Options-Controls-Assignments, assign the functions you want. Then check the Sensitivities menu to make sure they are all set to maximum sensitivity and minimum null zone. This is the proper procedure for any joystick attachment. Then test them. If you want more precise minima, maxima, and possibly some filtering or response curves applying, then (and only then) go to the Joysticks part of the FSUIPC options and follow the instructions, step-by-step, given in the user documentation. For special help with the CH throttle quadrant you may want to check out further documents written by the expert, Bob Church. There are some threads on this here somewhere -- do a search on that name. Bob has published a useful document on his website. Regards, Pete

You suspect correctly. All you get without paying is an interface for application programs to interface to FS, which is the prime function of FSUIPC and always has been. All those menu extries for tinkering with the weather, programming keys and buttons and caslibrating and mapping joysticks are additional user facilities which is what you get if you buy it. It does actually say this quite clearly in the user documentation. Read the first few pages. The rest don't apply till you register. Regards, Pete

I think the relevant gauges must light the indicators according to the current conditions which set them. I can find no sign of any specific Master Caution or Warning lights. You will probably have to check each condition which will set these and set your LEDs appropriately. FS itself doesn't really model many of the subsystems which contribute in any case -- in my 737NG cockpit I use PMsystems (from Project Magenta) to simulate most of them and also set the annunciators ("six pack" on a 737) and Master lights correctly. Regards, Pete

Yes, sounds reasonable. But I'm afraid it will have to wait now till I get back from holiday, i.e. after October 12th. No, sorry, It represents many hundreds of hours of hacking through disassembled parts of FS, and has to be repeated for each FS release -- even the 9.1 patch needed further hacking. This is really the main part of the benefits of using FSUIPC -- I do thousands of hours of such work for each release then disguise it all so each FS version looks similar but more extensive than the last. If you would enjoy such work and have the tools (a good disassembler like IDA and the NuMega Soft-Ice debugger at a minimum) then have a go and get back to me when you think you've mastered it. Then maybe we can discuss you taking over FSUIPC etc at some point in the future so I can retire properly! ;-) Sorry, not a good joke, but it is half serious. Volunteer experts in "hacking" and assembly code analysis will be sought to take over in not many years -- I am 62 now and don't want to have to do this for many years more! Regards, Pete

Odd. But Do I understand that the parameter does make your screenshots clean in instant replay mode? Regards, Pete

There are no facilities in FSUIPC for adding or removing messages. It has never been one of its functions. I really wouldn't know how to do it programmatically. I think there are only two ways to get rid of the red superimposed messages, and both affect the whole session. One is to use an edited version of the messages DLL with them all removed. However, I fear that in the case of messages containing changing numbers, as here, this won't help -- you'll still get the changing numbers. The other, I think is actually a parameter you can add to the FS9.CFG file which is said to hide all messages, so presumably does work on those too. However, although I did write it down a couple of years ago (when FS2004 came out) I can't find it at present. Sorry. Possibly if you ask the question on the FS2004 Forum someone will remember. I did look through their FAQ but it isn't listed there. Regards, Pete

Good! Wish I was always right! :-) Pete

No, not without writing a driver to interface to WideFS. I wouldn't really advise that in any case unless you really want some latency in the control (caused by the delay in transmitting across a network). When flying (or driving or anything like that really) you are reacting to visual feedback far faster than you would think, and even an extra 20 mSecs (about the best you could hope for on a Network on average) would tend to lead to you overcontrolling. It would be akin to trying to control an aircraft with a frame rate of less than 10 fps. Better just to get an extension lead if you want the yoke further away. ;-) Regards Pete

If you mean an FS panel, then you'll need to find a gauge for one -- all the default gauges only appear to have ADF1, but maybe there's a freeware one out there someplace. Then, as well as adding the gauge to your panel (a matter of adding it to the PANEL.CFG file) you would need to add it in the [Radios] section of your Aircraft.CFG file. If you take a look at that section you'll see how to do it, it's only one line. This is not really my subject at all, but that is how I understand it. You may get some more detailed suggestions in the FS2004 Forum or an aircraft/panel Forum if there is one.

Okay, I've now had a look, and as far as I can see FS does not support standby frequencies for the ADFs. There are none that I can find, and therefore there are no facilities to swap them over. In my implementation of ADF radios on PFC radio stacks I did the standby frequency displays from memory internal to the driver (PFC.DLL) then "swapping" was just a matter of reading the only current frequency known to FS and swapping that for the one I was storing for the standby. I think you will have to do the same for your cockpit. If you are not actually writing drivers for this, then you could probably do it in pmSystems. Regards, Pete

Sounds like the sensitivities are set to zero. FS2004 has a nasty habit of defaulting new axes to zero sensitivity. Go to Options-Controls-Sensitivites and check. Ideally, if you want to do fine calibrations in FSUIPC, you want maximum sensitivity and minimum null or dead zone in FS. Regards, Pete

Well, I think can add those as an extra bit. Though I cannot see an FS control for this -- the others are implemented simply by driving the FS controls. Odd that there are none specific for the ADFs. Possibly the anonymous "Frequency swap" control would do it, but it may need directing to the ADF in the first place. If it is easy I will see if I can fit it in this week, but otherwise it won't be for a few weeks as I am disappearing on holiday from this weekend till October 12th. I will put it on my list either way. Check the Beta versions list at the top of the Forum at the end of the week. Meanwhile, you could experiment with FS controls. If you find out what works you could then send them via offset 3110. [LATER] Please see my next message here! Regards Pete