Pete Dowson

Sorry, you need to explain more. I have never heard of either "force sender" nor "Yoda". Have either of them got anything at all to do with any of my own software? FSUIPC.FSI is merely a data file for FSInterrogate -- it is part of the FSUIPC SDK. What are you doing with it? You most certainly don't want it in the FS Modules folder -- it should be in whatever folder you installed FSInterrograte into. Are you a programmer, writing an FSUIPC client program? And, sorry, but I've never heard of "FSUIPC-Helper" either. What is that? If you are talking about some sort of Force Feedback system for FS I have to tell you that nothing I've ever written has anything whatsoever to do with force feedback. Incidentally, by entitling your message just "Help" you aren't exactly likely to attract any specific answers from anyone who may know anything about what you are talking about. Best to re-phrase your questions, make sure you are in the right Forum, and re-submit with a much more specific title. Regards Pete

I'm sorry if you thought it came across as upset or rude. Neither was my intention. I was only trying to express my extreme astonishment that anyone could make such mistakes such as not seeing the word "Install" indicating an Installer (remember you said you couldn't SEE it!), nor copy a completely incorrect file (not FSUIPC nor DLL) into a Modules folder created by something else. I try my best to make things obvious, and in fact the FSUIPC4 installation is much more automatic and easier than ever before even without reading the manual. FSX is a complete departure by Microsoft and an installer became a necessity. I really don't know how I could have made anything more obvious than it is -- hence my astonishment as shown in my response. If you don't want to ask any more questions here because you think you will be ridiculed, that's fine by me, but if you browse through the many many pages of this Forum you will see that I do try my utmost to be as helpful as I can. There is simply a limit beyond (below?) which I cannot see how to help folks at all. Sorry. Regards Pete

How did you "move" FSUIPC4.DLL when no such file is provided in the FSUIPC4.ZIP you must download? It is NOT an "FSUIPC.zip" file -- that would be FSUIPC3 for FS9 and before. Please READ the words in the download site! The version for FSX is clear, it is "FSUIPC4.ZIP". The Installer is in the Zip, rather obscurely (?) named "Install FSUIPC4.exe". How on Earth can you mistake it? And oddly enough there is also a User Guide with actual Installation instructions inside! Phew! Please do try to actually look at things. Pete

That's the thing. I thought the need for separate CFGs for different assignments and calibrations was removed when I added the Axis Assignment facilities into FSUIPC. Both assignments and calibrations can be made aircraft-specific, and using "ShortAircraftNameOK=Substring" you can easily make it all automatically change from one set to another without even reloading FS! Have a look. If that's all you want to do I'd rather it was done that way than add the multiple INI file facilities back. Regards Pete

No, sorry. But FS RealTime runs quite happily on the same PC. If you are using a processor with 2 or 4 cores, even FSX does not use them all 100% so it won't even impact performance. I use a little program called "Atomic" to make sure all my PCs have exactly the same, correct time too, so it would all work fine. Anyway, there are surely many more things to coordinate between two copies of FS, if you are trying to run them together. Doesn't the FSX shared cockpit or multiplayer facility operate the time too? Regards Pete

No, sorry, not if you want all that data. I really don't know any more about FSI2 than what i've found out by playing with it. You are interested in bits I've never used before. If you don't select any options in the "copy to scratchpad" dialogue you only get the single lines I showed. If you are wanting this format for some display or access utility I would have thought that was sufficient? Categories, expressions, FS versions seem, er, rather unimportant by comparison? However, you could easily convert that 3-line format to a single line one using a decent Search and Replace facility, like the one in UltraEdit 32 (the editor I use). Just replace all occurrences of CR LF (\x0d\x0a) by , in one pass, then all occurrences of ,0000: by \x0d\x0a0000: in a second pass. You could get rid of unnecessary stuff like the strings for 0000:, Token-ID, Category:, and Expression: in the same way. Pete

FSUIPC3 of course. FSUIPC3 is for FS9 and before, FSUIPC4 is for FSX and later. Please do peruse the Announcements above. Even the download sites tell you this too. The current version of FSUIPC3 is 3.82. Your "XP 64" part is totally irrelevant because FSUIPC is an FS module -- so it runs inside FS as part of FS. If FS runs so does FSUIPC. Pete

Well I was successful in getting data exported from FSI2 by selecting the lines in the normal "variables" view, right-clicking and selecting "Copy Variable-Info to Scatchpad", then going to "Tools-Scratchpad" and saving the results as a text file. This gave me entries in the form: 0000:0130, "Current flight plan [FSX]", "ASCIIZ", 256 bytes 0000:0230, "Absolute time (FSX)", "FLT64", 8 bytes 0000:0238, "Clock Hour", "U8", 1 byte 0000:0239, "Clock Min", "U8", 1 byte 0000:023A, "Clock Sec", "U8", 1 byte 0000:023B, "Zulu Hour", "U8", 1 byte 0000:023C, "Zulu Min", "U8", 1 byte 0000:023E, "Day of Year", "U16", 2 bytes 0000:0240, "Year", "U16", 2 bytes 0000:0242, "Zulu month of year", "U8", 1 byte which looks pretty much like csv format -- Offset, "name", "type", size. Right? Regards Pete

That isn't possible during download! I assume you mean when you ran the Installer? What exactly did you download? Didn't you notice that a complete log of what the Installer is doing was also produced and displayed? It will give more details. You should find it in the FSX Modules folder too. I don't know "FSFlying School", but if it is producing this message you need to contact them. If you mean FSUIPC4's installer came up with this message, then see above. You said you "uninstalled everything". Does that include FSX? Did you remember to un- and re- install the SP1 and SP2 or acceleration updates too? In general the message means that your FSX installation is in a bad way, that the SimConnect modules in Windows' Side-by-Side library are not properly installed and accessible. The Install log would confirm this, or otherwise. There is an Announcement above ("FSX Help" which does explain how to repair that (but it is very difficult if you are using Vista), but check the log first. Pete

Please do NOT try to install version 4.20, as it is quite old now and completely unsupported. Check announcements above and always make sure you are using the current versions before asking for support. Either you've moved FSX without uninstalling and reinstalling correctly, or you've got a corrupted or previous (rolled-back?) Registry. You aren't supposed to identify the path to FSUIPC, but the path to FSX.EXE -- you didn't bother to read what it was asking for? It needs to find FSX so it can install! Since your registry is wrong, it needed help from you -- YOU then have to find FSX for it!! I see Jim kindly pointed you to a Registry fixer for FSX, but you should know that if you'd followed the instructions and provided the FSX.EXE path to FSUIPC4's installer it would have optionally fixed it for you too. Anyway, please don't use out of date versions of FSUIPC. I cannot support you if you do. Regards Pete

...and what version number is this "latest FSUIPC version", please? (Everyone says "latest", but they mean "latest they are aware of" which isn't always the same -- some "latest versions" have turned out to be a year old and 10 versions outdated!). I don't know this "NOTVAM", but FSUIPC can only see the GoFlight buttons and so on if the GoFlight driver, GFDev.DLL is installed in a place it can find it. Please check the FSUIPC documentation, and look in the Announcements above where you can find the DLL if it isn't installed with your GoFlight software. Regards Pete

Interesting -- I didn't think anyone used that facility, so when I did the re-write for FSX I quietly dropped it. I expect I could add it again. I'll have a look. Not this week though. Regards Pete

What data is it meant to be reading? The fact that it recognises it is connected means it read some data. Have you tried using the facilities provided to see what is going on? I am particularly thinking of the IPC read/write lohhing in FSUIPC. Sorry, that is very old and completely unsupported. Please update if you want any useful help. Check the Announcements above for valid versions. What does that mean? Regards Pete

WideServer only runs on the FS computer. Do you mean WideClient by any chance? Two WideServer's connected? Huh. Please expand on this, I've not idea what you are talking about now. No. Regards Pete

And what does the Client show? Please show me the WideServer.Log from the Server and the WideClient.Log from the Client. These files are produced explicitly so that you and I can see what is happening. They are the first place to look. Not really a good idea. If you really want to make WideFs bypass all its automatic systems, why not use the Name of the Server rather than the IP address? Then you never have to worry about it changing. Also, if you provide an explicit Server you also need to provide an explicit Protocol parameter. No point in that. Folder sharing is for Explorer and other file access needs. Wideclient and WideServer talk directly to each other, not via files. It's probably to do with firewalls, but you need to provide more information -- specifically the Log files, which you can paste here. That is why they are produced, to tell you what is going on! Also you need to at least mention what version of Windows you are using at each end. And please make sure you are using an up-to-date supported version of WideFS (see the Announcements above about that). Regards Pete

You mean the data supplied with FSInterrogate, that you can add to yourself? Isn't there an export function? I seem to recall something about one -- check the documentation.I don't know of any other way of getting it. Pete

You are right. It should be easy. Sorry, I don't know what they've done wrong, I don't have any ordinary gear. All my stuff is PFC (www.flypfc.com) -- I do the driver for it! ;-) Well, there are certainly some odd sets of assignments, and in two aircraft no assignments at all for the main flight controls. Weird. You might want 3 or 4 throttles sometimes, but in general two throttles, two mixture controls and two prop pitch controls will cover almost all your aircraft. Maybe you want a lever for spoilers and maybe reverser (though it's usually easier to have the reverser operated by the throttle lever being pulled back more), but these are more esoteric things, to look at when everything else is working well. And then the first thing to do is make sure all the regular axes are still set correctly. Sometimes it is easier to copy the Axes section to one for the aircraft (i.e by editing the INI file), and then modify that on-line. Also you should, by then, checkout the "ShortAircraftNameOk" parameter -- if you update to the latest FSUIPC version (3.82 for FS9, or 4.30 for FSX) you'll find an article about that, contributed by a user, at the back of the User Guide. Reset the defaults in the on-line options? That only resets the stuff in the Weather and Miscellaneous tabs. It doesn't touch anything to do with axes or calibrations. All those settings were yours -- the saved 'calibrations' showed you never calibrated, and the axis assignments were the complete mess I described. And you couldn't have deleted the INI file to "reset to defaults", otherwise there'd be no Axes sections at all. Regards Pete

Okay, so FSUIPC4 is most definitely not even being loaded. Examining the Install Log more carefully I see that you have two distinct FSX.CFG files, for different users, indicating that FSX is being run with different Windows log-in details. This is most unusual. Is this correct? I'm wondering if the Installation was done for a different user to the one you are running FSX as? Here are the locations of the two separate FSX.CFG files: "C:\Dokumente und Einstellungen\Admin\Anwendungsdaten\Microsoft\FSX\FSX.CFG" i.e. as user "Admin", and ""C:\Dokumente und Einstellungen\User\Anwendungsdaten\Microsoft\FSX\FSX.CFG" i.e. as user "User". There is a difference between what has been going on with these two, because the DLL.XML file, which tells FSX what add-on DLLs to load, existed BEFORE you installed FSUIPC for the "Admin" user, but not for the "User" user. It seems you must have added or installed something for the "Admin" run of FSX before you installed FSUIPC4. Perhaps you can find the two files and show me them? They are both Text files. Here are their paths: "C:\Dokumente und Einstellungen\Admin\Anwendungsdaten\Microsoft\FSX\DLL.XML" "C:\Dokumente und Einstellungen\User\Anwendungsdaten\Microsoft\FSX\DLL.XML" I need to check that they are both correct, as I don't know which you are using when you run FSX. At the same time it might be worth getting a SimConnect log to see if SimConnect is even attempting to load FSUIPC4. Instructions for that are given in the FSX Help Announcement. Don't do the repair part, just get the Log and show it to me. Finally, check that you have not got my name listed an an "untrusted publisher". This is possible if you ever, unknowingly perhaps, refused permission for my program to run. To check this do the following: 1, Run Internet Explorer 2, In IE, go to Tools - Internet Options 3. Click on the "Content" tab, the the "Publishers" button 4. Check that there's no "Peter L. Dowson" entry listed in the "Untrusted Publishers" tab. If there is, select that entry and click the Remove button. Regards Pete

I've been looking at your Axis assignments in FSUIPC. They do seem very strange. What aircraft are you loading when you have those strange results you mention? I'm not sure why you are making your axis assignments aircraft-specific. Are you using the axes differently for each aircraft? Normally I wouldn't expect this sort of thing unless you had, for example, helicopter controls for helicopters, Airbus-type joysticks for Airbuses, Yokes for regular GA and other airliners, and so on. THEN you might need the joysticks changed automatically according to the loaded aircraft. Look (I've annotated these with the specific assignment meanings) [Axes] 0=0X,1,F,65763,0,0,0 <---- ailerons via FS (newer control used) 1=0Y,1,F,65694,0,0,0 <---- elevator via FS (older generic control used) 2=0Z,4161,D,4,0,0,0 <--- all-engine throttle via FSUIPC 3=0V,518,F,65766,0,0,0 <---- trim via FS 4=2X,3600,D,41,0,0,0 <---- reverser for Engine 1 only via FSUIPC 5=2Y,1143,F,65820,0,0,0 <---- engine 1 throttle via FS First: TWO separate axes both assigned to throttle? One for Engine 1 only, the other for all engines? What's the logic in that, please? Second, it is a bit weird to use a mixture of "Direct to FSUIPC calibration" assignments (the 'D' entries above) and normal FS controls ('F'). Not sure why you've done that. It isn't that it won't work, it is just a bit inconsistent. But the really really BAD thing about all of those assignments is the "Delta" value in each one. Those are the figures marked in red. The default Delta is 256, and there are lots of notes in the documentation saying when you might want to change it -- they are very few occasions you would ever want to! The values you have there are ridiculous, and are sure to mess things up. So, why are you messing with the Delta in the first place? What are you trying to achieve? I can tell you what you are achieving: Remember, a Delta of N means "whenever the input changes by N or more, send a message to FS or FSUIPC to recompute the setting and action the control". In other words, ignore petty insignificant changes less than N, as they won't do anything useful, will simply flood the system with useless requests or cause jittery axes which are no good to man nor beast. Performance will suffer and the user will wonder what's going on. The default of 256 was chosen with care. The total range, if calibrated in Windows, for any axis, is likely to be in the order of 32768 or thereabouts. Most potentiomenters or optical devices used in joysticks have at most about 100 distinguishable positions or steps, and in many cases a lot less -- even good quality slider pots often only reliably give about 40 useful positions. There may be more values arriving than this, but you get several different values for the same apparent slider position, so they aren't usefully distinguishable. By using a default Delta of 256 we are allowing up to 128 distinguishable positions -- a lot more than most inputs can provide. In other words, ample. So, in 2 of your axes above you are telling FSUIPC to send every change, to waste a lot of time doing nothing. And in the the others to are doing the reverse. You are telling FSUIPC to send hardly any changes at all. In the worst case (4161 on the throttle) you are saying "this axis is so useless that there are only 32768/4161 = 7 positions which I need you to recognise". Can you explain WHY on Earth you've made all these changes? You haven't actually bothered to do the important stuff like calibrate your axes, but you've messed around with Delta values to no obvious purpose? With the other Aircraft Settings, bewilderingly you have a similar mess. With two of them you seem to be pretty bereft of axes altogether: [Axes.DHC-2W 16798] 0=0R,1,D,4,0,0,0 1=0U,1,F,65697,0,0,0 Both of these axes are set to the Throttle control (the generic all-engine throttle) -- one direct to FSUIPC, one via FS control! No aileron nor elevator control for this aircraft? Do you only use the keyboard to fly it? [Axes.DHC-2W O-16555] 0=0Z,1,F,66292,0,0,0 1=0R,4479,F,65773,0,0,0 Both via FS, one for the modern "AXIS mixture" control, and the other for the older generic mixture control. Again, two axes for the same FS action, obviously causing conflict. And again, this aircraft needs no aileron, elevator or throttle? In conclusion, I advise you to delete the whole shebang. Concentrate on using FS assignments until you can get you head around the FSUIPC facilities a bit more. Please read the documentation supplied and try to follow its advice! I can help by answering specific questions, but please don't go off half-cocked making such weird and wonderful settings and wondering why things don't work. The facilities provided by FSUIPC are powerful, but with power comes some responsibility else you make a powerful mess! Pete

"Programmatically" meant "by program", so if you count a programmer who can write a program to interface to FSUIPC and extract the information a "developer", then, yes, it is what a developer can do -- but it would have to be the developer of TCASid unless you were to develop your own version or get someone else to do so. You can have multiple instances of the INI file loaded at different times by different loads of FS, if that's what you mean -- same as you can have different FS CFGs used in different sessions. If you only want to use TCASid in one session and other programs needing the other data in another session, then you could do that. But it would seem to be easier in that case to set the option the way you want it and perhaps make the INI file read-only so it can't be changed again. If you can still use TCASid with the option set the way it doesn't want it, I could consider and INI file facility to prevent it being changed. But you've missed the boat for the current round of updates. Ask me again in a week or two. Regards Pete

Not for a user. Programmatically all the information can be obtained other than through that user facility. You cannot run two instances of FSUIPC in one copy of FS! Where do you read such things? All you can do is change the option back in the FSUIPC Options menu. Pete

Yes, but that is the INSTALL log, not the run-time log from FSUIPC, which is called FSUIPC4.LOG, as I said. If there is an INI file then FSUIPC4 must have been loaded by FSX and run, unless you made that file yourself, of course. This is very slow going, isn't it? In FSX, in flight mode, is there an "Add-Ons" menu entry, with FSUIPC listed, or not? What is the problem you are actually trying to report? If FSUIPC is being run but fails to provide a Menu entry then it will probably be a SimConnect problem. The FSUIPC4.LOG file will tell us. If there is no Log file then FSUIPC is not being loaded. We need to distinguish between these two cases first. This may now get delayed till next week. I am away from tomorrow till late Monday, visiting my daughter. Regards Pete

In FSUIPC's options, go to the Axis assignments Tab, and make it recognise one of the axes. The joystick number is shown at the top. (This is all in the documentation, which it might be useful to peruse at some stage). No, because I cannot reach your machine from here and move the levers whilst FSUIPC is scanning the joysticks. Can I now? :roll: Why start messing with Aircraft-Specific settings, confusing yourself, before you even have the basics working? Just looking at your calibration entries, it seems that you have not actually really CALIBRATED for many, if any, of your axes at all, no matter which joystick they are on. If you aren't going to bother to calibrate in FSUIPC there is no point whatsoever of using FSUIPC for your controls. Look: [JoystickCalibration] ... Aileron=-16380,-512,512,10000 Elevator=-16380,-512,512,16380 Rudder=-16380,-512,512,16380 LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 ElevatorTrim=-16380,-512,512,16380 Flaps=0,16380 Throttle1=-16380,-512,512,16380 Throttle2=-16380,-512,512,16380 Mixture1=0,8192,8192,16380 Mixture2=0,8192,8192,16380 Spoilers=0,16380/16 Reverser1=-16380,16380/8 Reverser2=-16380,16380/8 Reverser3=-16380,16380/8 Reverser4=-16380,16380/8 Throttle3=-16380,-512,512,16380 Throttle4=-16380,-512,512,16380 All those red values are the defaults, assumed by FSUIPC if you don't do the calibration. I really cannot believe that all of your axes perfectly fit into FSUIPC's ideas of values which "may be close". You need to follow the simple numbered calibration steps for each and every axis! Please do refer to the documentation! Regards Pete

But do you actually TEST from a real keyboard too? That's the main point. Those are NOT filenames. You have Windows set to hide real filenames from you! The "Text" document is probably the Log, and the Config file is probably the INI file. There will also be a KEY file with your Registrations: I've no idea how Windows calls that these days. Probably a Settings (confusing it with Registry files).You are supposed to understand that if you have Windows annoyingly converting filenames into its "standard" descriptions! That's why I suggested you check the INI file. There is no way I have any settings being lost here. Something is not right on your setup. And 3.81 is now out of date. Please download and install 3.82. What previous version had any Mouse Macros? Sorry, this is all meaningless. Unless you can help me by providing meaningful information, like Logs and INI files, I cannot help you any further. Switch on Buttons and Keys logging (only!) in the Logging tab. And check the INI, as I said. Don't attach files. If you do short tests they will be relatively short Text files, both the LOG and INI. You can paste them here. If the files get large I'll give you an email address to send them, but they should not be for some simply Key tests (using the Keyboard). The INI file is most certainly NOT an application, but a normal Text file, like any other standard Windows CFG, INI or settings file. It can be opended in Notepad or any text editor. Since "uninstalling" consists of deleting the FSUIPC.DLL, and re-installing consists of putting it back again, it can make not a blind bit of difference. You could delete the INI file (with FS not running) so it reverts to defaults, then start again, if you feel you made some incomprehensible mess somewhere. I am away from tomorrow morning until late Monday (a long weekend visiting my daughter), so this may have to continue next week. Pete

Not necessarily. That's all okay, though it shows you are a bit out of date with FSX (no SP2). Was there no FSUIPC4.LOG file in the Modules folder? That's most important to check. Also whether there's an FSUIPC4.INI file. Regards Pete