Pete Dowson

Have you entirely missed the section in the User Guide entitled USER CONFIGURED QUADRANTS or it there something in that section which isn't clear? Such a question hasn't arisen before in the two and a half years since the facilities were provided, so naturally I thought it was described well. Please tell me what isn't clear. Regards, Pete

No backup, no hard copy? Tut tut:roll: I am not at all involved in the issue of keys. All that is handled entirely by the retailers. If you purchased it from SimMarket I think that, if you go to http://www.simmarket.com and open your account there, you can retrieve your key directly. Regards, Pete

Ah, yes, sorry, I think was getting mixed up with the VOR/ADF selection on the RMI. Things got a bit weird around here earlier today and messages have been lost all over the show, so I was getting a bit rushed and apprehensive. Let me see ... There are FS controls. Have you tried the Toggle DME control? There are some other DME controls too -- DME, DME1 Toggle and DME2 toggle. Not sure what they all do. Have you tried any of them? I don't know if they are also assignable in FS's own assignments. There's also an offset (0378) but I don't know if that works -- it used to in FS98 and FS2000 but it looks like no one's ever tried it in FS2002 or FS2004. Yes. Sorry if this wasn't clear from the documentation. It is sometimes hard to know how to pitch things, especially those things really intended for more advanced users. Regards, Pete

It looks like the panel includes some FSUIPC user which isn't accredited. In fact in cannot be as it is written to the wrong interface: 118110 Client Application: "fs9" (Id=2332) 118110 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe 118110 Product="Microsoft Flight Simulator 2004 - A Century of Flight" 118110 Company="Microsoft Corporation" 118110 Illegal read attempt: offset 0B80, size 4 118110Program or module not accredited for use with this unregistered FSUIPC These are the tell tales of a gauge or module accessing FSUIPC incorrectly. Unfortunately, because of that, it cannot even be identified. You will need to work out which gauge it is, and get an update, or purchase a user registration for FSUIPC. It doesn't look like it's the TCAS gauge, which is why that works okay. Regards, Pete

So far I think all those with that problem missed the part about Active Camera. It isn't related to FSUIPC at all. Check the FS2004 Forum. Regards, Pete

No idea, sorry. Is this with all aircraft or only the PMDG one? You could try AXIS_THROTTLEn_SET (also parameter 0), which is the newer throttle control. Regards, Pete

As documented, you never need to register any third party programs or gauges with FSUIPC if you have a full user-registered installation. What tells you that? FSUIPC will not check things like that in a user-registered copy. What is the message? Is there anything indicating anything at all to do with FSUIPC in this in the FSUIPC Log? It sounds more a case of installation problems with the aircraft, but tell me more. Regards, Pete

You do realise there is a specific FS control for this, and all the bits in that word -- even, I think, assignable in FS's own assignments? Afterr all, they are standard functions available on the FS radio stack. The switches in the FSUIPC offsets are really aimed at application programs. The COM1 TX control is COM1 Transmit Select. The control you already know, you have stated it. SetNits and ClearBits do just only change the bits in the parameter you give. The offset you also know. And you know the bits: 2^7 which is x80 or decimal 128 -- 2^7 means "2 to the power 7" or 2x2x2x2x2x2x2 = 128, hex 80. Similarly 2^6 is x 40 (or 64) and 2^4 is x10 (16). Together these would be x50 (64+16=80). It's really all just simple arithmetic! There's no parameter "syntax" as such, it is just a number. For the "bits" controls it tells FSUIPC which bits to change. With a straight Set the whole value, not selected bits, is involved. No, that's always been a mouse-only operation, unfortunately. Regards, Pete

Whether it works or not, each time, is subject ot a spot-check type of arrangement, a bit like customs inspections. With a free installed copy of FSUIPC (i.e. not user registered), each application accessing it is supposed to have a key. The ILH TCAS gauge is freeware and has a free key issued to it, and as far as I know it uses this key automatically, so you shouldn't have any problem at all. Perhaps you have an older version, or a renamed one? Access will only work correctly with the original name. You don't say what version of FSUIPC you are using, but assuming it is the current supported version (3.40), then if you show me the Log file so I can see what is reported then I may be able to advise further. Else it would be a matter for the author of the gauge. If you are using an older version of FSUIPC please update that first. Regards, Pete

You misread it, I think. It says that if you already use FSUIPC, you need to get the latest version. This is because versions before 3.40 do not work with the updated FS. If you don't already use it at all, you don't need to upddate it!!! How do you work that out? You only need to pay IF you want to use all of its facilities. If you don't, you pay nothing. Please read a little more, it is all explained in several places. There are links to the SimMarket paybooth in this forum, in my documentation, and on the download site. How can you have missed them all? As far as I know none of them are in Switzerland. SimMarker is run by the same company who provide this Forum and are based in Germany. You got here, didn't you? Try http://www.SimMarket.com. That is not possible. I've never charged anything at all for any of my FS work in the last 10 years, not until end July 2003! Just forget FSUIPC if you don't already use it. But check if you do (look in FS, when running. Is there a Modules menu? If so, click on it. Does it loist FSUIPC?) -- it may have been installed by an add-on. If you do have it already, just dowload the 3.40 version (http://www.schiratti.com/dowson) and copy over the FSUIPC.DLL from the ZIP into the FS Modules folder. Forget about paying for it unless you want to -- read some of the docs first, see if you think it will be useful to you. Regards, Pete

I have an Athlon 64 FX 53 (which I think runs at a speed of about twice yours), along with an ATI 9800 XT Pro, and even that won't attain 50 fps consistently, with nothing else -- including no clients or even WideFS (it is my GA machine). My main PM FS PC is a P4 3.2 with a Parhelia, and that is certainly smoothest limited to 20 fps. My previous system, a 2.4 GHz P4, is now used for the PM GC - it was far too slow for FS2004, and only just decent enough for FS2002 in my opinion. Regards, Pete

Sounds like the website has been changed. Sorry, no one told me. The information I publish in the dcumentation (and in that OLD thread in this forum) was copied, with permission, from the SimMarket website. Looks like I shall either have to update it, or just refer to the website. Obviously the website which sells the product will be more correct than a very old thread here. Would there really be any doubt? Sorry, I jave no idea. That's a question for your bank I think, It isn't my subject. I do programming and technical support. BTW, you entitled this "paying for FSUIPC 3.40", but you don't pay for 3.40, the registration covers all versions 3.xxx. Regards, Pete

I'm not sure it is WideServer being overwhelmed -- it looks like the link with your client. Perhaps you have changed something there? After all, you already said you tried with the older WideFS too. BTW I've never seen any sustained 50 fps possible at all on any system so far, let alone with any WideFS also running. You must have very fast hardware all round! (It is water-cooled?) Are you going to continue here or in the PM newsgroup? It is very confusing having you come at me from all directions! :wink: Regards, Pete

Ah, sorry, that last log crossed with my message. I've only just seen it! (Why not use the PM newgroup for Logs, BTW. I am getting very confused talking to you in two places at the same time!). These errors are indeed, bad. They show that the link to the Server is getting seriously blocked on occasion: ... but the reason for this is probably this: The link to the Server is probably being overwhelmed by WideServer trying to send far too many frames per second. A maximum of 65 and average of 43?? Phew! What have you set your FS frame rate limiter to? Pete

F2 or THROTTLE_DECR should work but that's for both engines (or at least all those selected by E + ...) For two separate reversers you'd need to use THROTTLE1_DECR and THROTTLE2_DECR of course. Whether it's a good idea or not I don't know. After all, pushing them forward again won't operate F3 or THROTTLE INCR -- unless you programmed its Press action to Throttle Decr with repeat, and release action to THROTTLE1_SET/THROTTLE2_SET, with a parameter of zero (to immediately set idle again when you move them forward, unpressing the button). Pete

F2 or THROTTLE_DECR should work. Whether it's a good idea or not I don't know. After all, oushing them forward again won't operate F3 or THROTTLE INCR -- unless you programmed its Press action to Throttle Decr with repeat, and release action to THROTTLE_SET with a parameter of zero (to immediately set idle again when you move them forward, unpressing the button). Pete

Well, I normally run with the frame rate limiter set to 20 or 25 fps in any case (I have 4 WideClient PCs to feed too!) I think there is a slight improvment in FS9.1 overall, but it is nothing compared to the BIG performance increase I got from the latest Matrox Parhelia drivers, which are now very very good. Regards, Pete

How have you programmed a reverse thrust on a button? In FS reverse thrust is an axis, ranging from idle to 25% (or thereabouts, it varies by aircraft) of full thrust via the reversing shrouds. This 25% would be represented by -4096 in FS terms. They provide a reverse operated by Shift+P? How odd. The Shift+P assignment operates FS's pushback by default. Have you cancelled that assignment, ior does the PMDG assignment override it? If the PMDG facilities don't work I'm afraid you need to contact PMDG support. I'm really not at all sure what they are doing with a single button for reverse -- is that supposed to immediately set full reverse on both engines? Well, in FS default, keypress "F2" decreases thrust, and when it gets to idle (0% thrust), further pressing of F2 will move the thrusters into the reverse zone, so you could have a button assigned to F2, with a repeat option set so you can keep the button depressed. You should be able to achieve the same with the THROTTLE_DECR control. You can use FS assignments or FSUIPC for this, it wouldn't matter which. Note that the throttle axes themselves must be stable at idle (0%) otherwise they will interfere and prevent reverse engaging. Calibrate so that you always get zero when they are pulled right back. Again, this can be in FS or FSUIPC but the actual numbers are shown in FSUIPC so it may be easier there. Hmmmhaving a button to engage reverse is realistic, is it? It most certainly isn't correct for a 737! :wink: A correct approach for a 737 is to have two interlocked reversing levers with, I think, three detentes as well as the 'off' position -- something like idle, arm, and full reverse. The "arm" is used to operate the shrouds but keep the engine idling, the reverse is used to apply the full reverse thrust (a few seconds later -- I think there's an interlock), and the idle is used to let the engine spool down again BEFORE the shroud is put back into normal position. Then you can disengage it. I don't know of any aircraft for FS which simulates all this. Regards, Pete

It is a standard Windows program and can be closed just like any other. Simply find its window and click on the close button (X) top right. Or right click on its entry in the task bar and select close. Thanks, but no. And there's nothing wrong with any of the logs you've shown here or in the PM newsgroup. The only reason I wanted to see the closed log was to check what WideClient's frame rates are -- the "Data rates" shown by PM modules are the rates IT sees changes, not necessarily the rate WideClient is seeing them. Regards, Pete

Sorry, what does that mean? It is you showing me logs, not vice versa! But that is the overall average since WideServer started. It includes all the period of FS running, including FS loading aircraft, sceneries and so on, and time waiting for clients. You only ran FS for something under 9 minutes altogether. The maximum is showing as 30 which seems good. What is the FS frame rate limiter set to? where's the WideClient Log? Of course, especially from the WideFS perspective as nothing has changed which would affect you adversely, as I keep saying. Well, something has obviously changed. There are no errors or problems occurring in WideFS (though, again, you've not yet shown me a complete Wideclient log). If you suspect the FS 9.1 update, run the uninstaller and re-test. Pete

It's been done for quite a while for the Aerowinx 747 Precision Simulator (PS1). Look at the links on the right-hand side of the http://www.schiratti.com/dowson page -- those marked "(PS13)" should be relevant. What's "the GPL"? WideFS and FSUIPC relate to Microsoft Flight simulator. I have absolutely no idea what "Flight Gear" is, but I am assuming it is nother flight simulator judging by your text. Nothing of mine is designed for anything but FS, you'd need to do your own programming for another sim. Regards Pete

This shows nothing except the initial connection and ending on a disconnection. Please do a complete session, closing both FS and WideClient down, and send both logs. I see you a duplicating things here and in the PM newsgroup. If you want me to look at detailed and COMPLETE logs, ZIP them up and attach them over there. Regards, Pete

I think that with nothing else to do and no real information to work on it jolly well ought to be fast! :wink: Don't forget that the network is being used separately by PM. It isn't just WideFS using the network. Have you tried an ealrier version of the GC or other PM components? Regards, Pete

From what versions before? Two separate things there -- "PM frame rate is poor"? Which rate is that, the graphics rate, the data rate it measures itself, or the actual frame rate WideClient measures? There's a lot of difference depending on what you mean. "PM GC is very delayed" may either be a symptom of a poor GC graphics update rate or blockages on the Network. Sight of your WideClient and matching WideServer Log files might be useful to differentiate between these. Close both down first so we get frame rate summaries at the end. On the whole FS9.1 is a bit faster. The only real difference with WideFS 6.401 (from 6.3xx and earlier) is that errors are retried with a slight gap (a fraction of a second though), rather than immediately, so hopefully allowing an already blocked path to unblock rather than back up -- I believe the delays some folks reported with earlier versions derive from long queues of blocks someplace in the Windows TCP/IP stack. No, none at all. Best to allow all to default. Regards, Pete

Without FSUIPC installed there will be parts of the Dash 8 code not doing anything, or doing something different. It is certainly worth mentioning this to the PSS support folks as it may help narrow the area in which they should be looking. HOWEVER it may simply be the resulting difference in memory -- assuming the problem does derive from uninitialised variables, which it certainly sounds like. Odd though with the "switch off FS9 and restart it" -- but, again, the memory contents may simply be different. Regards, Pete