Pete Dowson

You mean "not repeating", I assume? This will simply be because FSUIPC keeps a list of the last few programs which registered with it so it doesn't need to check them again. Since I removed the checking it doesn't know the program name and doesn't need to keep a list because it isn't re-checking each time. Despite the extra lines in the Log, I assure you the new method is faster! Of course not. as I told you, there is no access registration checking now. The logging of the key is only for information. Oh dear. Please do refer to the very first answer I gave in this rather extraordinary thread. I said: If there is any "problem" it is only that I am puzzled as to why you think it is a problem in the first place, even warranting spending all this time on investigating things I know about and which are designed that way. If you are seriously just objecting to having multiple lines in the Log, then I'll make a note to make them optional in future, possibly only logging them if "Extras" are requested in the Logging. But it is in no way a priority item, and it most certainly isn't a "problem" as far as I can see. Otherwise, if you are just trying to be helpful, then, thank you very much, but there was no need and I thought I'd answered it all in the first reply. ;-) Regards Pete

Wherever you told SimConnect to put it, of course. You did read the Announcement at the top of the Forum about how to get SimConnect logs, didn't you? Remember, I said to you: You should have included the Log with the report to Microsoft -- you'll need to send another now. Regards Pete

No, the new FSUIPC4 for FSX is a completely new program and needs new registration codes for both FSUIPC4 and WideFS7. Be sure to order the bundle, not the individual programs. You will get a good discount as a recent purchaser of the FS9 bundle. Regards Pete

Not for FSUIPC, no. It is quite a complex application to try to control FS in such a manner, expecially from GPS data which is relatively sparse and needing smooth interpolations between values. FSUIPC is really not much more than an interface for program such as the one you want. GPSout is a different animal altogether, only needing to throw data already collected by FSUIPC, as part of its interface job, out of a serial port. Regards Pete

Good! Pete

"Very rapidly"? I don't know about the A32o gauge, but for ASV6, at around 25 bytes each 6 seconds, even in a 12 hour flight it will grow by less than 180kb. Are you really seriously that short of disk space? I am finding it very hard to get excited by all this I must admit. Regards Pete

I think it is odd that it is writing its Key every few seconds, yes, but if it is working okay it isn't really a problem. Although your log will grow slowly, it is started again on each FS session so it shouldn't present a disk space problem. Whether this is new behaviour or not I couldn't say. I'd need to delve into my archives to find earlier FSUIPC code to see whether I would have logged every instance in earlier versions. I really don't have time right now. Regards Pete

You are using Project Magenta? You didn't say. That does make a huge difference you know!!! All the PM offsets are listed in the PM Offsets documentation on the PM website. You never actually mentioned "this function", only a general question encompassing almost everything, thus: Perhaps if you asked specific questions then you'd get more help? So far all I've gleaned from you is not much more than "we got this hardware ..." (I assume it is hardware, you don't actually say, unless "PCB" = "Printed Circuit Board"?) and pretty much "we don't know how to use it". There's plenty of information, but at present I can't see what you are actually asking for! Regards Pete

What is the actual problem? What doesn't work? Why are you looking at the log? Pete

It sounds like you've enabled the steering tiller but do not have or are not using the steering tiller axis (e.g. as fitted in the PFC 737NG). Your observations are precisely what will happen with a steering tiller -- you use that on the ground, but as speed increases the rudder becomes more effective instead and above around 60 knots the rudder is 100% and the tiller is 0%. Just disable the steering tiller. Maybe you enabled it inadvertently whilst browsing? Regards Pete

There's no actual connection between GF's software and FSUIPC except within SimConnect. I'm afraid that, at present, SimConnect appears to be rather unstable when dealing with more than one demanding client. You could get more information by generating a SimConnect Log (there are instructions at the top of this forum for this), and if you do I will gladly look at it so that I can reinforce as much as possible the bug reports I have already submitted to Microsoft. Please include the FSUIPC4 log as well. But at the same time, in any case, I urge you to report all such problems to tell_fs@microsoft.com, in as much detail as possible (including your system) and the SimConnect Log. I am hoping that most of the SimConnect problems have now been reported in sufficient detail for MS to identify the causes and fix them, and that these fixes will be in the first "update" for FSX which we may see in the New Year. Meanwhile I'm afraid it's a matter of muddling through. Regards Pete

What do you mean by "empty"? FSUIPC is just logging the fact that some program wrote that key to offset 8001. Since FSUIPC doesn't check these now, it doesn't go to all the bother to find out what the program is, but I left the logging of the Key as possibly useful information. Why does it worry you? It's certainly a little odd for a program to continually write its key to 8001 (in this case every, what, 6 seconds or so), and I don't know why it is doing that. Even the "ATN.GAU" does it three times in quick succession. But this isn't new in this version of FSUIPC. The key "9G9LCNT2MDUY" is allocated to ASv6,"ActiveSky 6" by "HiFi Simulation Software", if you want to contact them about it. Regards Pete

I would count that as a good thing. If someone went to the bother of installing it, I wouldn't expect them to want it disabled. If you want it disabled, please disable it each time after installing, or simply don't bother installing it again. This really is a benefit for those who don't realise it has been disabled (possibly by accident or another installer) and re-install it in the hope that it will be mended. Regards Pete

Why send screenshots, when all you needed to do, as instructed, is save the on screen log and attach or include that? That's why there is a "Save as" menu entry there!! How did you install FSX? Did you move it after you installed it? The "SetupPath" parameter in the Registry says you installed FSX into a folder: D:\Program Files\Microsoft Games\ but this looks very unlikely -- you would normally have it in a folder "FSX" or "Flight simulator X" or something, within Microsoft Games. Where is the FSX.EXE file? Obviously it wasn't found where the Registry says it should be -- that is why you get the error from the installer. And then why did you abort the attempt to locate FSX.EXE -- which would have enabled FSUIPC4 to be installed at least? Seems a strange thing to do. The installer has the ability to deal with the Registry problem, but only with your help, which was denied. Why? If your registry entries for FSX are in a mess then you will have problems with other Add-Ons for FSX in the future. I think you need to rectify your FSX installation before doing too much with it. Regards Pete

Good. Thanks for letting me know. Version 2.00 of the PFC driver is available now, by the way. It isn't much different to the 1.999b you are using, but the documentation is a little more up to date, at least, and there are a few internal tweaks (which you won't notice on your equipment anyway). You can find it now on the official download site, http://www.schiratti.com/dowson Well, I could do that, but I don't unless it's offensive. It may be useful to others in any case. Regards Pete

You mean it actually shows the wrong direction? What causes that then? If you mean change the reading on the gauge, then, no. Even if you could overwrite it it would be re-written by the FS simulation engine on the next frame or so. The only gauge you can offset is the gyro driven heading indicator where a "drift" can be applied. As already mentioned in this thread, it can be done using gauges especially written to simulate such things, but not with the defaults which read the FS values directly. Regards Pete

I am betting it will be a bad texture file, or something similar. Have you been trying any of the tweaks to speed FSX up at all? Maybe one of the files is corrupted. Before I try any tweaks or add-ons I always make a back-up copy of the folders affected (e.g. "Texture" as "OrigTexture") so that I can try going back simply by renaming (i.e. "Texture" to "NewTexture" then "OrigTexture" to "Texture"). Regards Pete

Don't FDS have any information? don't they know how to make them work? All the FSUIPC offsets are documented in the SDK. You need to download it from http://www.schiratti.com/dowson -- there's a sepcial update for FSX above if you need that. It won't list any private offsets used by third party drivers though. You'd have to ask them. Since I don't know anything about any FDS hardware or software I'm afraid you are asking in the wrong place. Do FDS has a website or email address through which you can contact them and get documentation? What made you purchase such things if they cannot be used? Regards Pete

Sounds like a bad install of FSX then. If you have the Deluxe edition you could try re-installing SimConnect by getting the SimConnect.msi file from the SDK and executing that. It might be a good idea to first find the Windows folder which contains the SimConnect.dll fiel 9do a search in Explorer), and deleting the folder entirely. The only other thing I see you have which is presumably using SimConnect is "FeelThere\Legacy\LegacyXHUD.dll". Does that work? Does FSUIPC4 work if you rename that? Are you running any other SimConnect programs externally to FSX? I'm afraid I'm away now until Sunday night at the earliest. Good luck! Regards Pete

Yes, I did see it. Disappointing. I was hoping for somethnig before Christmas I must admit. Regards Pete

What release is that? Have they offered the 'Gold' yet? I don't know. According to a user who has been testing things for me it was resolved on a later (Release Candidate) version of Vista, but possibly he only meant by using "Run As". I don't actually understand why I am not detecting the problem in the first place -- it tries a "Dummy run" write to the Registry as a test, but that must succeed, otherwise you'd get the warning and the Registration buttons would be greyed out. That's what happens here on WinXP at least. The only copy of Vista I have here is from the MSDN subscription I was given as a reward for becoming an MVP, but I see it is only Beta 2. I don't really have the time or space to install it in any case, and it doesn't seem worthwhile for such an early version. Regards Pete

No idea, but why not speed up pmSystems by reducing your cycle time of 50 down to say 20 mSecs and see if it helps? It is already running slower than FS if it is set to 50 mSecs! It would certainly be better running faster! Regards Pete

Changing the local time makes no difference, it effectively tells FS you are in a different time zone but not that anything else has changed. You need to change the Zulu time (023B). No, we never found a way to interact with the in-built ATC. Sorry. I've asked for such facilities in FSX, but they've not been agreed (yet) either. Regards Pete

It sounds like you are not running it in Adminitstrator mode -- the Registration cannot be accomplished otherwise (as documented). Try logging out and logging in as the Administrator, or possibly using "Run As ..." (it's in the right-click menu). There is code in the Registration section to detect whether you are running FS with sufficient privilege, and when that works it actually stops you attempting to Register and tells you why. But I've had two previous reports where this detection doesn't work, and I don't know why. The first time it happened was in a Windows Vista Beta version, but it was fixed in a later release of Vista. If you are running Windows XP I can only think it is a problem with a certain update level. I've tried to reproduce the problem here with no success at all I'm afraid. Please let me know the results when you run FSX as Administrator. Regards Pete

Well, even at 50 you should be getting 20 reads per second. What's the FS frame rate? I have pmSystems running at 20mSecs I think, both cycle times. And the same PC also runs ActiveSky, Radar contact, FS RealTime, AI Smooth and pmSounds, all via wideFS. Regards Pete