Pete Dowson

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

It won't help anyone here, you need to tell_fs@microsoft.com. I think they are working on all this stuff now. At least, i darn well hope so! Pete

We never had any "offsets" for this. There are plenty of FS controls related to eyepoint, though I've no idea what they all do. Please see the list of FS controls. If you want to "send controls" via offsets, check offset 3110. Regards Pete

Yes, that's why the 32F9 offset was added. Yes, as documented. It also isn't held on if the brakes are decreasing. Well, it is held for a whole second (enough for at least 30 normal WideFS transfers and at least that number of Logic loops in pmSystems), so it shouldn't be a problem even if you simply "blip" the brakes. That was the whole reason for the 1 second hold. Have you got a very slow (i.e. high) pmSystems cycle time set? Regards Pete

These are control inputs (not read-outs) for the application of brakes with a pressure-decay release, as opposed to proportional brake inputs directly (eg from analogue toe brakes on pedals). The function dates back to FS95/FS98 and has been retained in FSUIPC all this time because it is used by some drivers for toe brakes, such as those for the Aerosoft GA28R cockpit. Sorry, I don't know anything about "strange values" getting into these locations -- show me some logs with the values Monitored (see FSUIPC Logging facilities) if you want me to check, but I think you are monitoring entirely the wrong thing to determine brake usage. It may only work because of the way your toe brakes are connected and driving FS. The braking indicator at 0BCA is more reliable, but the offset especially added for your precise need is the one at offset 32F9. Regards Pete

Ersorry, I'm lost. You want more than 8 (eight) programs started by FSUIPC3 or FSUIPC4, or you are just not clear on what to do? The facilities for FSUIPC3 or FSUIPC4 to run programs for you when you start FS are set by parameters in the appropriate FSUIPC INI file. The one for FS2004 is called FSUIPC.INI and is in the FS2004 Modules folder. The one for FSX is called FSUIPC4.INI and is in the FSX Modules folder. They are simply text files and can be edited in Notepad or any other text editor. The instructions for creating the [Programs] section in those files and putting the parameters in for each program you want to run should be clear enough -- there's only one line for each program to be run, after all. How complicated can it be? Please check the section in the Advanced User's guide entitled Programs: facilities to load and run additional programs I'm sure you shouldn't find anything difficult. It's only relegated to the "Advanced Users" documentation as it isn't a commonly used requirement and unnecessaary in the general Users Guide. Regards Pete

Well, obviously you can reduce it. For example, 0.9 is less than 1.0, so if you set 0.9 you would have reduced it! I've no idea what value you should use. On my PMDG 737 the value is 1.0 and everything works as it should. Evidently the model aircraft you have behaves differently. Why not simply do a binary chop (halve it, then halve the difference etc) till you arrive at a value you like? Pete

Yes, you need FSUIPC3 installed in FS9. It's available from the Schiratti download site. Doesn't the ActiveSky install do that, or at least explain anything? Yes, but not at the same time, and yes, and the FSUIPC version for FS9 (3.71 at present). They won't be running at the same time in any case as you surely cannot run both FSX and FS9 at the same time on the same PC. Even if you could, how would ActiveSky know who to talk to? Pete

Looking at the end of that file: This shows that the last amendment was, in fact, the addition of the MyTraffic version of the traffictoolbox -- FSUIPC4 currently always adds itself to the very end, just before the " terminator. The question therefore arises -- how was the MyTraffic part added. When I bought and installed MyTrafficX I had to edit the DLL.XML myself -- does it now come with an installer which does this? If so, then please send a report to the MyStraffic support for Mr. Renk to attend to, as that needs fixing. If on the other hand, you had to edit yourself, then possibly you made a small error? I have changed the FSUIPC4 Installer to do this: 1. Create a completely new DLL.XML, placing its own entry first. 2. Copy any other entries (except its own) from the original DLL.XML, keeping the same order. This will, I hope automatically correct the sort of problem you found when re-installing FSUIPC4. Regards Pete

No version of the FSUIPC4 Installer has ever omitted any part of the complete section needed. I don't know how your file got corrupted like that, but if you think you can reproduce it, would you mind kindly sending me the original DLL.XML file which you start with, before installing FSUIPC4, so I can see what is happening? Did you install anything AFTER FSUIPC4 which may have changed the file? The Installer, if it finds no DLL.XML file at all, writes the whole thing. If it finds a DLL.XML file but no mention of FSUIPC4, it adds its complete section -- and ALWAYS includes all the lines necessary. What it doesn't do is check all the lines are correct from a previous installation, so that's probably something I can improve upon. I may do that for the next release. Thanks, Pete

Sounds like either an aircraft sensitivity scalar setting (in the specific Aircraft.CFG file), or possibly you have the Yaw Damper engaged and that is being rather over-effective? Regards Pete

Unless you use the "RAW" option in FSUIPC the Windows calibration is always applied. The Raw option tells Windows to supply the raw uncalibrated inputs from the device. I have no idea where it is in XP, though certainly it was always in the Registry for Win95/98. I haven't delved underneath the Windows interfaces for a long time (no need), but there are details of Win95/98 in my EPIC95 package still. Here, for example, are some Win98 registry entries (from the REG files in EPIC95.zip): [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\MediaProperties\PrivateProperties\Joystick\OEM\EPIC] "OEMName"="EPIC programmable system" "OEMCallout"="epic.vxd" "OEMCalWinCap"="EPIC programmable analog calibration" "OEMTestwinCap"="EPIC programmable system test" "OEMData"=hex:03,00,08,00,20,00,00,00 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\MediaResources\joystick\] "JoystickUserValues"=hex:00,10,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,ff,ff,00,00,ff,ff,00,00,ff,ff,00,00,ff,ff,00,\ 00,ff,ff,00,00,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\MediaResources\joystick\\CurrentJoystickSettings] "Joystick1Configuration"=hex:07,00,88,01,20,00,00,00,07,00,00,00,01,00,00,00,\ 01,00,00,00,01,00,00,00,01,00,00,00,01,00,00,00,01,00,00,00,ff,00,00,00,ff,\ 00,00,00,ff,00,00,00,ff,00,00,00,ff,00,00,00,ff,00,00,00,80,00,00,00,80,00,\ 00,00,00,00,00,00,80,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,1f,00,00,00,0f,00,00,00,00,00,00,00 "Joystick1OEMName"="EPIC" "Joystick1OEMCallout"="epic.vxd" [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\MediaResources\joystick\\JoystickSettings\EPIC] "Joystick1Configuration"=hex:07,00,88,01,20,00,00,00,07,00,00,00,01,00,00,00,\ 01,00,00,00,01,00,00,00,01,00,00,00,01,00,00,00,01,00,00,00,ff,00,00,00,ff,\ 00,00,00,ff,00,00,00,ff,00,00,00,ff,00,00,00,ff,00,00,00,80,00,00,00,80,00,\ 00,00,00,00,00,00,80,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,3f,00,00,00,0f,00,00,00,00,00,00,00 FSUIPC doesn't access any of this stuff directly. It simply asks Windows for readings from Joystick N via "joyGetPosEx" calls. A flag tells Windows whether RAW or CALIBRATED values are required. Regards Pete

It's because FSX's SimConnect closes me down so quickly, without any prior notification. It's why I couldn't implement an automatic save of "Previous Flight" on close down too -- the facility I need which they omitted in FSX! I always used that to make sure my aircraft is found next time where I parked it last time. :-( The PFC driver does actually send out the correct code sequence to clear down all the avionics displays, but they get purged from the serial port driver by the threads and processes disappearing. I have found a way around that, using a more persistent thread and delaying tactics, and have it working here, in a new version of PFCFSX.DLL, but I had a couple of other things to do before releasing it. It will be version 4.00 and should be available tomorrow, or soon after. Meanwhile, I suggest that when you finish your flight you cut the engine(s) and turn off the master battery and avionics before closing FSX. They displays will go off then in any case. Seems a sensible and realistic thing to do at the end of a flight? Regards Pete

You don't mean you never even calibrated them in Windows first? :shock: FSUIPC and FS both just read what Windows provides, so if you use uncalibrated joysticks I'm surprised you got anywhere close! Even so, if they remain perfectly alighed they it sounds like they must be digital rather than analogue pots. Pete

No, sorry. SimMarket do all the work leaving me to develop and support, and they are very effective. I asked the management and they said you "paid by check via paypal, and paypal just like anyone else waits for the check to clear before sending any payment". This is why they cannot do anything about it. I maintain a small PayPal balance for immediate purchases, which makes the difference. Regards Pete

Actually, now that the system has been fully automated most of the time they are supplied within minutes, not even hours. This only doesn't apply for uncleared monies, such as through unvalidated PayPal or cheques through the post. The PayPal method was only added recently of course. A validated PayPal account should be pretty much instantaneous -- it has been for me through SimMarket for other purchases. I'm very sorry -- I don't know who you spoke too, but I've found the management to be very helpful, friendly and first class. I have no intention of moving as they have always been excellent. I shall of course forward your complaints, but I'm sure you must be misinterpreting something here. Regards Pete

These are not the "factored" values, which would be in degrees. For where? 40.62 degrees North and 0.378 degrees West? How can I tell where you are? Is "Result" a floating point value? I don't see it defined anywhere. If it is an integer value it cannot retain any good value. Yes, as does the documentation. And what is the result in FSInterrogate? You don't say. How can I compare your result? Pete

Why is there any problem? I don't know Delphi, but the conversion is only arithmetic, involving multiplications and divisions only, as documented. I'm certain Delphi can do such things -- have a look at FSInterrogate, which is written in Delphi. Regards Pete