Pete Dowson

Yes, that is why there is extensive documentation in the Advanced User's guide for the button parameters, including examples. Comments ARE retained in that section too. Flags for options checked. All those things should be programmed via the options screen, as I said. Regards Pete

Which documentation? User or SDK? Yes. The Programmer's guide in the SDK lists an "aircraft on ground" flag. Regards Pete

Sounds like the SimConnect bug which causes FSX to crash when one SimConnect client tries to read FSX data whilst you are being prompted to allow a newly-installed client to run. This is mostly fixed by the SP1 update for FSX, which you don't appear to have installed. (I say "mostly" because it doesn't fix 100% of cases). You have two choices: one is to temporarily disable your other SimConnect clients (ones loaded by the DLL.XML or EXE.XML files), by renaming them, for instance. Then run FSX and get FSUIPC "approved" (you can optionally tell Windows to always approve programs signed by me, Peter L Dowson, which would allow easier updates), and finally close FSX and re-enable the other programs. If you are not sure what you have running which is conflicting, show me the DLL.XML file, and, if you have one, the EXE.XML file. They will be found in the same folder as your FSX.CFG file -- Documents and Settings\\Application Data\Microsoft\FSX (or slightly different for Vista). The other choice, which is a good move in any case as it fixes a load of other stuff, is to download and install the SP1 update for FSX. By the way, there is a later version of the FSUIPC4.DLL available in the FSX Downloads announcement above. (4.156). Regards Pete

I've never heard of this "Sarah.dll". Certainly it is no part of FS9 or anything of mine, and neither "wants" anything from it. When you say that it's "the socket that connects to" your ISP, what do you actually mean by that? What do you know of it? Windows sockets are supported by intrinsic parts of Windows, a section called Winsock -- wsock_32.dll is, I think, the usual main socket support for all of the Ethernet API calls. It sounds like something has been installed which has replaced or hooked into part of Windows and, evidently, doesn't do the job properly. [LATER] From Googling on "Sarah.dll" it looks to me as if it is some sort of invasive hook installed with a thing called "fritz!dsl" or "FritzBox", whatever that is. Looks like a type of Spyware but it might be related to whatever firewall you have operating there. Sorry, but it really is a problem on your system unrelated to FS9 or WideFS. Try Googling on these things. Maybe there's a solution out there less drastic than uninstalling stuff. Regards Pete [Ooops .. I see I've edited your message instead of quoting it. I've done that twice recently! Must be this new Forum design. I'll need to get used to it. Sorry!]

I have just noticed this announcement on Avsim: Maybe using the FSX version will help? Pete

I never did receive any more information from you to help me narrow this down, but I had some time this morning to browse through my code. I found one place where my conversion form the FS2004 version was incorrect, and would certainly result in some PH values being set to zero when the original value (which you should have seen in your Log files too!) was most certainly not zero. I have fixed this in version 4.92, today, 15th August 2007. This updated version will be available for download from the FSX Downloads announcement above later today. Please try it and let me know. Please note that yours is the first actual feedback on EPICINFO5 since I released it for testing by EPIC users last September. I am a little at a loss to test properly here, not being an EPIC user these days. If you have any further problems, please do include the Log itself, as this would have certainly helped in the cases you mention. [LATER] Okay -- 4.92 is available now. See the FSX Downloads announcement. Regards Pete

If their USB driver interfaces with FSUIPC for all of its FS connectivity, then yes, it will work via WideFS too. However, if it produces a standard joystick-type interface which you then make assignments to via FS or FSUIPC, then it would only work for button assignment, not axis assignment, because WideFS doesn't transmit axis values. Assuming you've not bought the hardware yet, then to be safe I recommend you contact FlightDeck Technology and ask them. If you already have everything then you should be able to try it, or even read about it in the documentation (?). Regards Pete

Never heard of a problem like that before, sorry. I'm afraid none of the details you gave relate to the problem at all. If it only happens when a client connects it sounds like it may be down to a bad Network driver in the FS PC, so possibly uninstalling and re-installing the network card/device (via the Device manage) may help. To narrow down the location of the problem in FS you should find, when the crash occurs, a place in the notification where you can "click for more details". This will tell you where in FS it crashed, including location (an 8-digit hex address) and a module name, like 'FS2004.exe' or 'api.dll'. See if that helps too. Regards Pete

Not sure why you are posting here about it as it really cannot be anything to do with FSUIPC. Please make sure you submit the problem to Microsoft when the crash notification appears with that option. Also see if it happens without the "iFly" add-on, as if it doesn't you may wish to notify them, assuming they support its use in FSX. Incidentally, the currently supported version of FSUIPC4 is 4.152, not 4.15, and there is an interim update for that (4.156) available in the FSX download announcement above. Regards Pete

Don't look for offsets there -- they are most certainly the domain of the SDK where you will find a complete document listing and explaining thousands of them. Normal users, even "advanced" ones, don't normally need to know anything about those. [Axes] 8=1Z,256,D,17,0,0,0 //17 prop1 9=1R,256,D,42,0,0,0 // reverse throttle 2 10=1V,256,D,41,0,0,0 // reverse throttle 1 numbers 17 41 42 are FS functons I figured out by looking for change and a list of those whould be handy, so I can fix errors in my INI The reason the [Axes] and [JoystickCalibration] sections aren't fully documented there is that it is not intended for users to edit those manually. It is much easier to change those on-line in the Options. The "advanced" documentation for Buttons and, to a lesser extend, Keys, is there because there are many programming-type things you can do with those which cannot be done on-line. Anyway, the D (Direct to Calibration) function numbers 1-44 equate to the position these have in the Joystick Calibration tab -- 1 to 4 on page 1, 4-8 on page 2 etc. So you can make a list fairly easily if you wish. I don't want to encourage folks to bypass the on-line setting methods for those sections. There's no general convention for comments in Windows "profile" documents, as my INI files are. I explicitly allow for them in the sections I expect folks to edit manually, but not in the others. I suspect any you add will get stripped next time you change anything on-line. FSUIPC doesn't do any of that, it is a function of the way Windows maintains INI files via the Profile API. I've always left everything to Windows. The [buttons] section, in particular, has a lot of extra 'parameter' type handling specifically to retain comments and even add error messages when appropriate. The other sections really are best dealt with as intended, via the options. Good, but I've no idea what was happening, but it is confirmed that it was something at your end, or with your ISP. The Forum administrators have confirmed that the Server to which the download links connect is not the same one which was recently updated (it's even in a different country!) and that there's been no change at all as far as those links are concerned. Weird. Regards Pete

Sorry, I've no idea what is happening, but it something at your end, or with your ISP. The Forum administrators have confirmed that the Server tp which the download links connect is not the same one which was recently updated (it's even in a different country!) and that there's been no change at all as far as those links are concerned. Weird. Anyway, glad you got what you wanted eventually. Regards Pete

I get a better response from the links now than before! Strange! I have emailed the administrators for advice. I cannot do anything myself. The FSUIPC4 installer installs several documents, including the User Guide and Advanced Users guide. The fact that it does is also logged to the Install LOG. All the installed files go to the FSX Modules folder, and the message box announcing success says so! Maybe you need to re-install if you have deleted these files. Please check. If your installation failed I need to see the Install log please! Pete

There seem to be several in your situation, but it not only works fine here, but since they changed the Forum software, they are much more efficient. Possibly there's a change in the IP address to which the link resolves and some ISPs are using name servers which aren't up to date still? I'll point it out to the Forum Administration, but there's nothing I can do myself -- the links are all better than before, if anything, just like the speed and design of the Forum. Regards Pete

Ooops! Sorry -- looks like I Edited your message instead of merely Quoted it! Doesn't it accelerate anyway if you select the "repeat whilst pressed" option? If you are using the INC/DEC controls then it is really the same sort of thing as holding the + key down or the mouse button on the gauge. Otherwise, without writing a client program to do it, the only way I can think of is to program each way to not only do the INC or DEC but also to increment a count in one of the free user Offsets and test that to see whether to do several more INCs and DECs in the same button push. You'd need to reset the count when the button is released. No, it is all covered in the Advanced User's guide, supplied in the FSUIPC Zip package. They are all working fine as I type this, so if they were down it couldn't have lasted very long. Regards Pete

There's nothing whatsoever wrong with the link. Check with your ISP -- there's evidently something wrong your end. Regards Pete

3.72 is a long way out of date. Please use the current version, 3.75. I cannot support old versions. This is a video driver issue. I really cannot offer any solution other than to try different video settings or a different driver version. Are you perhaps using one of the new DX10-capable video cards, like the 8800 series? The new DX10 Vista drivers for those are known to be a little flakey at present, at least it seems so from what I have read. There may not be a fully working driver yet, if it's a DX10 card. I can only suggest trying different video driver or FS display settings. It may be related to the anti-alias or filtering, for instance. Of course, for FSUIPC settings, which are really not needed to be accessed very often (in fact not really at all once you have things set up as you like), the easiest work-around at present is simply to swap to Windowed mode before accessing them, and swap back afterwards. SP1 for Vista, postponed TWO years? I can't believe that! Surely it cannot be so? I have one PC with Vista installed but I'm hardly using it because of all the problems and real annoyances -- I'm waiting for MS fixes. In any case I suspect it is new video drivers you really need. Regards Pete

It was uploaded last night -- version 4.156, in the FSX downloads announcement. I had to make additional changes for FSX, which appears to operate the spoilers rather differently internally. Version 4.156 works perfectly. Regards Pete

Good, glad you sorted it. Not annoyed so much as a little exasperated at times! ;-) (and f course I am not renowned for my patience ;-) ). Regards Pete

Dear Pete , :? Confused :cry: Sorry , I need more explanatory details :idea: about this assignment in FS2004 & FSUIPC 3.75I'm a newbie about FSUIPC :roll: Thx for your help ... Which part confuses you? Perhaps you should please (please)_ read the User documentation first? There's even pictures in there, directed specifically at "newbies". I really cannot offer the same level of documentation here!!! If you cannot see the helpful pictures, load up FS2004 and do it there. Just go to FSUIPC options (ALT M F in FS2004), then select "Buttons and Switches" tab, then press your button, then select Assign to Control (right-hand-side), then find the "Offset float64 set ..." control in the drop down, set the Offset and the Parameter. If you'd bothered to go and look you'd have found all this really easily. Crying about it "as a newbie" without trying to help yourself at all is not going to solve anything. :-( Pete

Good. I've got another small fix to make (Spoiler Inc/Dec, as per another thread), so by the time it gets into the Downloads Announcement it wil be 4.156 or 7. Regards Pete

Actually, Galicia is the North-West-most province of Spain, just North of Portugal. Our son lives right near the border with Portugal. Our last railway holiday (in June) was through Hungary, Slovakia and southern Poland -- very good, reliable railway system including superbly kept steam locos. Good. Regards Pete

The FSUIPC Spoilers inc and dec added controls, you mean? ... ... Ah! The problem is that the "SpoilerIncrement" parameter, which always used to be written to the FSUIPC INI for version 3 is not currently written to the FSUIPC4.INI file, and it consequently defaults to zero instead of 512 as documented. Good catch! I'll fix that in the next update. Meanwhile, just add: SpoilerIncrement=512 (or whatever you prefer) to the [General] section of the INI file and it will work fine, though note that you have to be in the air for spoiler adjustment -- on the ground you can only arm them which will deploy them fully automatically. Regards Pete

Please try the attached version 4.155 and let me know. If okay i'll put it up in the Downloads Announcement. Regards Pete FSUIPC4155.zip

Okay. Thanks. I'll bear it in mind! Problem there is that is really does need 3 buttons. One to request pushback. As you start being pushed you look out the side windows to see when you then need to select the '1' or '2' ("SELECT 1" and "SELECT 2" controls, I think they are). That makes three buttons. You make the selection about one plane-length from the line you want to be on. Then to push the original push button again to stop it all when lined up - it's a toggle. FSUIPC does include the necessary code to make sure you can actually look sideways between the Pushback request and the selection -- FS doesn't actually allow that else. I suppose you could work out a way of using two buttons -- you'd have to hold the button down till you wanted the turn selected, then release it -- program pushback on both button "press" and the Select 1 or 2 on the release. Two problems I can see with that: first you probably cannot hold the button in and get another button seen to select a view. Second, you'd have to push the same button again after, to stop the pushback, which leaves a spare "select" key operating. that's probably harmless, but you never know. Most of this can be programmed around using FSUIPC's conditionals and flags, editing these in the FSUIPC INI file, but it can become more complicated than it is worth. Best to try the way I said first. Just came back from a short visit to my son in Galicia. Next one starts at the end of this month -- Serbia and Bulgaria, steam railways again. ;-) Regards Pete

Yes, sorry. Saw it just after I posted. I think I know what is going on. I tried some experiments. Basically, it now seems to be failing to initialise some of the parameters in the Comms control block, and leaving them set to the previously set values -- so a lot depends on previous usage of that Port. The change I actually did was to include the \\.\ part of the name in the port spec when building the new block. That helped in certain reported cases with USB ports, but it seems to have this side effect. I'll upload a revised version when I've figured out what to do. Apologies for the inconvenience. Regards Pete