Pete Dowson

Except for one thing I omitted to mention -- the solution with sending two different controls alternately only works if you have the acceleration fix option selected in FSUIPC's Technical page. Regards, Pete

I'm here now, but I confess I am not sure what you find awful about the views you posted. If you could capture a picture with at least the horzon in it and maybe some scenery, and explain what you think is wrong, then it might make more sense to me, but those just look like views straight up of an early morning or evening sky. In any case, I'm afraid I am no expert in any of the graphics of FS. You may have better luck in the main FS2004 forum. Sorry, Regards, Pete

Two points: 1. In offset 3367 at present only bit 0 is used for doors (in FS2004). In case other indications are added in future you should check for bit 0 only ( and logically AND with 1). 2. The bit is set to 1 if the doors are Open, so you are interpreting it in reverse. What is a "Variant"? The value is a simple byte or character. You could read it into an integer, but set that to zero first to avoid confusion in the parts not read into. 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. Provided all your PCs are running WinXP, then since WideFS 6.50 there is virtually nothing to do except install the programs. You don't even have to provide Server Names and stuff now. None at all if you aren't unloading some external programs from the FS PC. And even then it depends on what processor you are using on that PC. For instance a hyperthreading P4 will run FS and several external programs with virtually no degradation in any of them. The prime purpose of WideFS isn't really to gain performance, though it can help, but to support more applications on more screens. 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. Possibly, but how do I find such details? Maybe RealityXP know how to do these things, but I'm afraid I don't. I will be asking MS to provide some interface for this in future versions of FS, but i won't be holding my breath! Regards Pete

Please contact PMDG support about this. If there is a bug there it needs to be fixed. I cannot support any old versions of FSUIPC, and in fact some later PMDG products will be dependent upon later versions of FSUIPC. This is not at all related to FSUIPC. I am using the 737-800 with no problems at all. And merely replacing the FSUIPC.DLL corrupts nothing whatsoever. 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. Not if you don't want them, no. Yes, this is a built-in action of FS. It is automatic is two identical controls arrive within something like 400 mSecs of each other. You can only avoid it by pressing more slowly, or making sure there's an intervening control which is different. I see you have "repeat whilst held" checked. If you want to press it repeatedly yourself you need to uncheck that. Alternatively, reduce your "32" increment value to compensate for the acceleration. The only ways are as I just described. Sorry. If reducing the increment to compensate isn't suitable, you could add another line in the FSUIPC.INI file to program a different action on the same button -- another non-axis FS control with no effect, or an innocuous one. Then when you are holding down the button both controls will be sent alternately and this will defeat FS's acceleration. 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. Try using the Logging provided in FSUIPC. If you enable IPC read logging you will probably see that your VB code actually tries to read offset &FFFFE004 (masked to 1FE004 probably). The stupid VB compiler sign-extends everything with a top bit set. Even stating &0000E004 doesn't appear to work. I think you have to postpend another & to stop this, i.e. &E004&. Please always use the latest version -- 3.47 is well out of date. 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. 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