Pete Dowson

Well, there's no harm in asking. Sorry if the answer wasn't the one you wanted. Regards, Pete

That's what I thought you meant, and as I said, it is not possible -- unless PM was simply frozen, or running in demo mode. But this is a question for PM, not me, in any case. Good idea. you should be able to get a new key easily enough. Regards, Pete

You are addressing this to the wrong person. If you want your stick fixed for free I suggest you contact the makers. If you want it calibrated better then try Windows, whose "Games Controller" is supposed to do such things. Every user of FSUIPC wants something different from it. If I made each desirable part free, what would be left? It isn't a realistic nor sensible request I'm afraid. You can of course download the SDK and write your own program to control the throttle, or you can try some of the other offerings for axis programming, like FS-Communicator. Regards, Pete

Hope you mean in terms of fatigue and work, not that something happened? Best wishes (to your wife too) No, only the problems of using the two eyes together whilst they are totally different. The 'new' eye has gone off a little and seems to want to be out of focus like the old one now -- the surgeon said it's my brain trying to make sense of it all! When I get the other eye operated on so they match better I'll be okay (he says). I am hoping this will be done on the 14th July now (that's the best date I could get from the Hospital). My wife got back from her hip operation yesterday, and is walking around using a couple of sticks. This is only 6 days after her hip operation! Amazing! Best Regards, Pete

Hmmm .. good luck! You will need the FSUIPC SDK (from http://www.schiratti.com/dowson), but working out how to move the platform in response to the simulators accelerations (all of which are available for FS2002 and FS2004) is something which I would have no idea about -- it obviously isn't just a matter of applying the numbers. You need to make the platform move in ways that make the occupant(s) feel as they would in the real thing, without actually moving the platform as the real thing moves. Not sureI know that Ralph Robinson (R & R electronics, makers of the EPIC) has been involved with some folks in the U.S. building and programming one, using EPIC for the PC interface of course. Maybe a web search will find other contacts. Ah, you are quite far advanced then. So the EPIC reference isn't correct for you. I'd take a look though the data available to you from FS and plan how to make use of it first. Learn to program a bit, even VB should be okay -- not sure how clever it has to be if you already have the interface to the hardware sussed. Regards, Pete

FSUIPC 3.30 will help. It has been imminent for a while and still is. I had hopes for a Release this weekend but it looks like being early to middle next week now, but I'll get to it as soon as I can. My eyes have been proving more troublesome than I anticipated. Regards, Pete

Hi JD. I sent Peter 3.253 to try and he has confirmed that the problem has been solved. Thanks for the offer though! Best Regards, Pete

I don't think that is at all possible. I think you mean that the PM software is frozen, hanging? What does PM support say to that? You had no errors on this Client for over 20 minutes, but then a short-lived problem where it had a difficulty sending something to the server. This may have been because you had FS loading a file or something. There's nothing significantly wrong though. The only other error: 1900603 LAN data received: PREQ ulSize=276, ulTime=22330, uSum=22431, fUsed=0 20 00 00 FE 04 00 AC 0C 00 00 74 02 00 FE 02 00 1900603 --> Sumcheck error! 1900603 Size Act=287 Exp=287, Sum Act=22737, Exp=22431 1900843 GetRecv() missed block? Sequence 22330 jumped to 24012 1934571 Reception maximum achieved: 39 frames/sec, 4930 bytes/sec Looks as if the client PC was frozen (hardware or driver problem) for a while -- quite a while judging by the gap in the block numbers (22330 to 22431 -- 100 blocks missing!!!) Again, with WideServer: 1925547 Retried 137 times: sends blocked for over 5 secs! (0 of 349 sent), Error=10035 (skt=3716) 1930563 Retried 135 times: sends blocked for over 5 secs! (0 of 361 sent), Error=10035 (skt=3716) 1930766 Send ok but needed 5 attempts! (360 of 360 sent) (skt=3716) 1956578 Retried 137 times: sends blocked for over 5 secs! (0 of 381 sent), Error=10035 (skt=3716) 1961594 Retried 136 times: sends blocked for over 5 secs! (0 of 395 sent), Error=10035 (skt=3716) 1962813 Send ok but needed 32 attempts! (395 of 395 sent) (skt=3716) 1974641 Send ok but needed 134 attempts! (369 of 369 sent) (skt=3716) 1987422 Send ok but needed 109 attempts! (380 of 380 sent) (skt=3716) 1998781 Send ok but needed 115 attempts! (302 of 302 sent) (skt=3716) Those errors look real bad, but before that there was absolutely nothing wrong for over 32 minutes. So it doesn't lok like there's anything wrong with the Network, at least with the WideFS linking. Errors like Sends from the Server being blocked, or needing many retries, are usually caused by hangs or problems in the Client, but as seen in the Client Log these aren't occurring in Wideclient. The prime suspect in my opinion will be the video drivers, the OpenGL parts used by PM. If they hang or cause problems it will affect everything else on the same PC, whereas is there were problems inside the PM code itself the network should still run okay. If it isn't the video side, then some intermittent problem on the Network Card (unlikely) or a virus. I think you need help from the PM folks. WideFs is doing okay here, honest. It looks most likely to be video drivers, but as I said there are other areas. Check with them for some advice. Regards, Pete

Better not rush though, as your Log shows that FSUIPC is actually crashing on your FS2000 installation. It traps its own crashes and logs them, as that way not only do I avoid crashing FS but I'm able to get more information, which FS and WinXP in particular are otherwise very reluctant to give me! I'm sending you my latest Beta to try, just in case it is now fixed. There have been a *lot* of changes since 3.22. If that fails too I shall have to get FS2000 up and running again, to see for myself. Regards, Pete

Thanks, but my eyesight won't be fixed till the other eye is operated on. I see the surgeon tomorrow and hope for an early date. Meanwhile using one eye at a time is tiring. Please ZIP it and send it to petedowson@btconnect.com. Did you check the Technical option I mentioned, and try it switched on or off (whichever it isn't?), or is your copy not user-registered? Regards, Pete

I just mostly use the defaults without any problems, though I think you probably should check that The Network device property "Link Speed/Duplex Mode" or similar is set to 100 Full rather than Auto modes (I think Auto slows it down a touch). Receive buffer maximum of 64k if that's there. For TCP/IP it is best if you assign fixed IP addresses to each PC rather than have them being looed up and assigned each time. And if you've then got nothing else using IPX/SPX, uninstall that protocol on every PC. (If you use WidevieW you won't be able to, however). For more authoritative network advice I'd ask Katy Pluta over in the FS2004 forum. She has helped me a few times! :) Regards, Pete

Check the FSUIPC options in the "Technical" page. This is the relevant part of the FSUIPC User Guide: I'm not sure what's happening with the sign reversal -- the FSUIPC fix was originally designed for FS2000 because it can get the sign wrong by itself. With FS2000 not being used very widely any more, and of course many many developments for FS2002 then FS2004, maybe some error has been allowed to creep in. I can investigate this, but can you please see if you can get it down to basics. No Radar Contact or AdvDisplay needed. Just try setting a higher altitude with A/P Alt Hold on, and see what V/S is set, and similarly a lower one. If you can reproduce it easily that way, fine, just tell me. If not then we need to examine the details of your previous experience more. Like are these specific altitudes (what to what), and is Radar Contact's co-pilot doing anything or are you in sole command? Sight of the FSUIPC Log would be useful too -- especially if you enable "Extras" logging first. Thanks. Regards, Pete

Sorry, I've absolutely no idea what the panel is doing. You really do need to ask the folks who did itt, or at least someone who knows a little about panels. I don't even use any. The first thing I would do is try a complete re-installation of the panel. After that you probably need to check the list of Gauges accessed according to the PANEL.CFG file against the gauges you have installed. It is possible that one is missing, misnamed, or misplaced. Regards, Pete

The log showed the gauge registered. You don't need to keep doing that. The business about restarting the program, for an aircraft gauge, would simply mean reloading the aircraft. If you want to you can close FS and restart FS, but surely you must have done that at some stage in the course of this thread in any case. Once the gauge is correctly listed in the FSUIPC.KEY file you can forget about registration. That's over and done with. Your panel problem is not at all related to FSUIPC access registration. Regards, Pete

"Final" answer? sorry, I really have to be prepared to answer most if not all questions. :wink: In terms of actually typing the name and key into FS, of ocurse you can only enter one at a time. But then you can "Ok" out of that and re-enter the same dialogue to register another, and so on, all day if you like. All that dialogue does is do a little bit of processing on the data and save it to the FSUIPC.KEY file. Nothing more, nothing less. It is the list in the [Programs] section of the FSUIPC.KEY file to which FSUIPC refers when a program, gauge or DLL requests access and does not provide a Key directly through the FSUIPC interface or via its Version Information details. (You see there are several (easier) ways for programmers to make the access automatic, and many do. But sadly many also do not). For programs with only alphanumerics in their names, you could actually simply edit the FSUIPC.KEY file and add the keys there. Accented characters and non-alphanumeics have to be eliminated -- excepting the "." in ".gau" and ".dll" for those two types. EXE files omit the whole ".exe" part. No, that's wrong. There is absolutely no limit whatsoever to how many are listed. All FSUIPC does is look to see if the program has a correct KEY in the [Programs] section of the FSUIPC.KEY file. It doesn't matter how many are there, but you can't have two programs with the same name. Regards, Pete

That's all fine. Sorry, I think there must be something corrupted in the FS installation someplace, most likely to do with the scenery stuff. As to why it seems okay without FSUIPC but not with, that is most likely a difference in the memory layout with the extra module installed. One last thing you can try -- set the InitDelay parameter to, say, 3000 or even more, to make FSUIPC refrain from infiltrating FS's main window for that number of milliseconds (3000 = 3 seconds). This is a long shot, but since, as I said, FSUIPC isn't even doing much other than gathering information at that time, there's not much else that can be changed. If that fails I can only suggest a re-installation of FS. Regards, Pete

Yeah, that's all fine. As I thought, the panel problem isn't related to any FSUIPC access problem. Sorry, I think you need to recheck the installation of the panel and its gauges. Regards, Pete

That's odd, because FSUIPC doesn't really do anything that early. What version is it? Let me see the Log file. Mostly problems like that are down to something corrupt in the installation of FS, but you say it is a fresh install. Try deleting the FS9.CFG file just in case, though, so that it creates a new one and loads a default flight. Regards, Pete

Hmmmthat's not possible. Version 3.22 dates from only a few weeks ago, not 2 years. This clearly shows that the program whih is not registered is Squawkbox, and it will be because you are using an unregistered copy of FSUIPC, and haven't entered the program registration Key for Squawkbox. Please see the Freeware Keys sticky thread above. Regards, Pete

That wouldn't normally be any symptom of FSUIPC registration, but let me see the FSUIPC Log, and your FSUIPC.KEY file -- Only the [Programs] section please. Pete

The program name for EXE filesis just the name before the .EXE part, but for Gauges and DLLs it is the whole name -- i.e. in this case you would enter "A330.gau" (without the quotes). This is why the emboldened title part in my Freeware Keys list includes the .gau and .dll parts but never the .exe parts. Regards, Pete

Sorry, I'm not sure where I come into this. Is this with a specific aircraft, using FS controls via Options-Controls-Assignments, or are you using something to do with my programs? The battery and alternator switches in FS are independent, but can be ganged to the off-position in some panels I think. Please try to be more specific when you ask such questions. I have great difficulty guessing what you are trying to do and how you are trying to do it. :( Regards, Pete

Once the Key has been entered once it is remembered in the KEY file. there's no need to reenter it each time you run FS or load an aircraft. If you load an aircraft with an unregistered gauge, then register it, you should be okay if you then reload that aircraft -- but possibly, because of the way FS works, to restart the Gauge you may need to load a different aircraft in between to force FS to restart the gauge. Regards, Pete

First, bear in mind that the GF displays aren't driven by FSUIPC. For the rotaries, if you go to the Buttons page of FSUIPC's options and turn the knobs you should see FSUIPC display some joystick, button number. Each rotary has 4 such numbers, fast and slow, clockwise and counter-clockwise. For each one you can assign Keystrokes or FS Controls. I think for PMDG you have to use Keystrokes. The ones you need will be listed by PMDG someplace. Sorry, I can't help you there -- I don't use any panels at all. If when you are turning the knobs FSUIPC doesn't see them, you need to install the latest GF Config program and driver from the GoFlight website. Regards, Pete

This question was asked privately, but I am posting it and the answer here as I think it will interest others: I cannot guarantee that other folk's gauges and DLLs work -- that is their responsibility. All purchasing FSUIPC does is (a) give you access to many useful facilities and (b) saves you having to register any add-ons for FSUIPC access, other than FSUIPC itself and WideFS if you use that. As for the freeware F16.GAU key provided, it is correct and does work for some folks, as you will find from other messages here, but I believe it has a programming error in it which makes this problematic at times, depending what other things are loaded first. Unfortunately, I am still awaiting a Log file from someone who reported this, and haven't seen it yet. If it is indeed the error I think it is, I will provide a work-around for it in FSUIPC 3.30, which may be out within a week or two. If you want to wait for 3.30 and try it then, and you aren't interested in other FSUIPC facilities, then by all means do so. Regards, Pete