Pete Dowson

Ah, I see. yes, they are okay -- it is the Manifest Probing which is not finding some versions of SimConnect. both the Installer and FSUIPC scan the versions of SimConnect available and then select the one best for it to use at the time. The failed matches (because you don't have those versions) evidently get logged. I'd not noticed that before. The process of manifest probing is carried out as advised by Microsoft as the best way of providing proper compatibility to all versions of FSX whilst still being able to take advantage of updated facilities when they are available. What is the problem, though? Just that this worries you, or what? Have you got a problem using FSUIPC4? This manifest probing is not new to version 4.152. It was part of the changes made in 4.10 for FSX pre- and post- SP1 compatibility. Pete

Sorry, I don't understand where or what you are seeing, nor what the resulting problem is. Can you translate any of these for me? And where and when do you see these messages? The installation looks okay. What happens when you run FSX -- is there an FSUIPC4.log? Regards Pete

.AIR files are binary files, like program files but containing data tables and the like. Folks who manage to modify them or create them do so by hacking them in binary. Very precarious! There used to be some programs around which helped with small areas, but I don't think any one really cracked the complete file thoroughly. These days more and more of the parameters contained in the AIR file are adjustable in the Aircraft.CFG file. But please don't ask me about them -- I am in no way an aircraft designer. You need to ask around on another Forum, one more oriented to aircraft design. Regards Pete

Well, since I made it nearly a year ago (!) yours is the first report back from any EPIC user. It is completely untested software, and until now I thought completely unused software too! I do not use Epic at all, now, so I can only check things using the Logging. What I could do with is a full Epicinfo Log showing the "bad" figures, with your notes saying what they should have been. Knowing the aircraft being used would help too -- and of course the version of FSUIPC4 (or make sure you are using the latest, which is 4.152). In that case it may be better to do a complete analysis when you are closer to finishing? I don't think there have ever been any controls for the RMI -- it was and still is a mouse-only pair of switches, local to the gauge, as far as I know. Did you ever find any for FS9? If they are mouse-only I can only suggest using something like Luciano Napolitano's "Key2Mouse" program. Regards Pete

Okay, I've found a way you can connect FSXplanner without either the SimConnect.xml or the SimConnect.cfg file. I have done some research on the Port being used, by default, by SimConnect for its default local connection. It seems to choose one at random, usually in the 1000-4000 range. There are tools to tell you what ports are open at any time (and who by). The tool I used is "OpenPort": http://www.freedownloadscenter.com/Netwnload.html which is a freeware one. Download and install that. Then run FSX. When it is ready, run OpenPort. You will get several ports opened by FSX.EXE. If you have my WideFS enabled there will be the default WideFS ones (8002 and 9002), but there will be one for local address 127.0.0.1 and remote address 0.0.0.0. Its connection state will be "LISTEN". The local port number for that is the one you need. Load FSXplanner, go to the Simconnect connection status window and enter the port number there, then press Connect. Regards Pete

If you mean in FS2004 or before, I have no idea -- it must be a secret. I do believe there have been products in the past which managed to create "dynamic" scenery aircraft -- the traffic which preceded AI traffic in versions now long gone. Of course you may be referring not to multiplayer traffic, which is supported in FS2002 and FS2004 via a multiplayer interface -- the on-line flight programs use these facilities to show the other fliers' aircraft. The multiplayer traffic are not "static aircraft" either. The MP interface is documented someplace -- in the Microsoft MP SDK I think. Check MS's flight sim support sites. If you mean in FSX, then it is no secret how AI traffic can be "created" on the fly. I know VoxATC also injects AI traffic. They are not "static planes", but AI traffic planes, created, possibly with their own flight plans, via the facilities to do this in SimConnect. It is all documented in the SimConnect SDK which comes with the Deluxe edition of FSX. Regards Pete

Sorry, I really don't know enough about pmSounds to tell you. I just use it as it comes. I think you have to program the link to FSUIPC offsets in the pmSounds INI file. Please check pmSounds documentation or ask Project Magenta themselves. There are also some PM forums, with visitors who may be able to help, at http://www.mycockpit.org/forums/forumdi27981&f=99 (not sure if you need all of that complex-looking link!) [LATER] I just occurred to me that you possibly know how to do it, and were simply asking for some offsets to use which won't conflict with other programs. If so then the general user area is that from 66C0 to 66FF inclusive. This is actually allocated for general use with my "GFdisplay" program, but that's in the user's hands too. ;-) Regards Pete

Hmm. No idea then -- check that there's no SimConnect.CFG file in your "My Documents" folder. I can't think of anything else. Sorry. Pete

I don't know XML. And gauges for FS9 don't necessarily work in FSX. Have you any other problems apart from this FS9 gauge? How do you use it? What does it do and what is the problem? Doesn't the author respond to you? If I need a file to put in a panel, please send a file. Attach to a message to petedowson@btconnect.com. Pete

Yes, but best please to change that back, and get 4.151 -- now available in the FSX downloads announcement above. Sorry for the kerfuffle. Pete

I found a stupid error in the "AxisIntercepts" logic which could cause a loop in some circumstances -- mainly because an axis value is being intercepted from SimConnect at one level and re-transmitted at a higher level. It can be avoided by the "AxisIntercepts=Yes" parameter, but better to simply download 4.151 which I've will provide via the FSX downloads above as soon as I can sort it out and re-test. Regards Pete

Meanwhile I'm cross-checking on some other FSX installations here, just in case ... .. QUESTION: Do you have joysticks in FSX completely disabled? I think I've reproduced a hang problem, not necessarily at the splash screen (but I suppose possibly so, depending on when the incident occurs) which seems to be related to a complete absence of FSX-assigned axes. Still checking [LATER STILL] Something else to try: set "AxisIntercepts=Yes" in the FSUIPC4.INI file. Add it if it isn't there. Let me know please. Pete

There is no change whatsoever which could do that, not in FSUIPC itself. In fact FSUIPC isn't even running then. And you should never have to delete any INI file -- a "clean start" is a lot of work for those who use FSUIPC for calibrations, assignments, buttons and switches! On each and every new update there are always several such reports, and they have, so far, all been down to the known SimConnect problems with security checks. You are probably falling foul of the SimConnect problem with multiple clients. Was there a security prompt, or have you previously told Windows to accept all programs from me? What other SimConnect clients are you running? If you cannot spot the problem I would need a lot more information: 1. Update state of FSX 2. Windows version 3. Install FSUIPC4 log from Modules folder 4. Any partial FSUIPC4. log (though there won't be a relevant one if FSUIPC isn't being loaded and the problem is, indeed, the SimConnect one already known about). 5. A SimConnect log -- see the FSX Help announcement above for how to get one of these. Regards Pete

I've just tried the program, on the same PC as FSX, and honestly I don't know what they've doneit looks designed to work properly on a Networked PC. But even then it is wierd, as when you ask it to connect it displays an (editable) IP address and Port to useI don't know anywhere in the SimConnect interface where this can be defined outside of the SimConnect files (XML and CFG), and I don't understand the need for them. The SimConnect DLL refers to those files and uses the settings there. Maybe they don't use the SimConnect DLL, but have somehow worked out how to bypass that application-interface part of FSX and are going direct to the SimConnect server port inside FSX itself. Anyway, the result is that they appear to need the XML file (not the CFG file) in order for it to work on the same PC as FSX. All I did was this: 1. Install the contents of the FSXplanner ZIP into a folder ("FSXplanner"). 2. Copy the SimConnect.xml file to the same folder as the FSX.CFG file (which is where it must go for FSX to see it). This will be your Document and Settings folder, under \Application Data\Microsoft\FSX, assuming you are using WinXP -- it is a little different on Vista. 3. Delete the SimConnect.cfg file. I ran FSX, then the planner, told it to connect (with its default IP address and Port), and it did. FSUIPC4 was still running okay -- the Add-Ons folder was still there. Even though this does work, it would still be best, for the future, to edit the SimConnect.xml file and change the protocol in the "default local" section from "IPv4" to "Auto". Regards Pete

I don't know what they have done to make it such a mess. There are plenty of SimConnect client programs and none of them need either the SimConnect.xml nor the SimConnect.cfg files for a reliable connection -- they are most definitely primarily forgetting programs to connect over a Network. I do now have the program, but have I've really not got time to try today. Maybe later this week, or early next week. But if I find it doesn't work with default connection to FSX it is not I that can fix it, but the programmers. As you will see in their own Forum I have pointed out that it is more complex than necessary and suggested they simplify it. When I get a chance to try it I will let you know how I fare --- assuming they don't have a better version available by then! Regards Pete

As Jim rightly says, static planes are part of the scenery, just objects almost like the buildings. The data at FSUIPC offsets for AI aircraft are to tell TCAS radar displays where the AI traffic is. AI traffic is not scenery, but flying or moving aircraft, being simulated almost like your own aircraft. These cannot be created by FSUIPC either, but defined as part of the AI Traffic system. Regards Pete

The Client log you showed proves everything is okay, with a good frame rate and transmissions for FSCommander working well. So there is simply something it doesn't like about the data. Maybe the FSUIPC installation is wrong or there is something wrong with the Key(s). To check these things I would need to see the FSUIPC log file for a session. be sure to close FSUIPC down first, before getting the FSUIPC log file. Regards Pete

Correct. Okay. Please let me know if it works with neither file. Maybe I should look at this "fsxplanner" program? Is it useful? Regards Pete

On the same PC? Remove the SimConnect.cfg file too. If you mean on the remote PC, then, of course, it won't work without a SimConnect.xml file, but that file needs the default Local section (no "Port") and your Global section. I did not suggest removing the "Global" section at all!! However, having tried that for some reason, the result implies you are talking about using FSXPlanner on the remote PC!? So you don't need that second local section at all. Try deleting that, as I suggested before. No, it isn't that there is such a file, it is only the contents of that file which are wrong. Please do as I suggested in the first place. Only if (a) this is a remote PC you are talking about (you've never said), and also there are other SimConnect programs on that PC you want to run. If there are it needs to be in your "my documents" folder. You do NOT want or need a SimConnect.cfg anywhere on the FSX PC. BTW Don't the suppliers of this "FSXplanner" program provide any support at all? Pete

You only need that file when using Simconnect programs on a Networked PC, remote from FSX. And doesn't this "FSXplanner" program then work okay on that PC? Try putting "Auto" in for the protocol there rather than "IPv4". I really don't understand why you'd need two "local" sections. If this one is overriding the previous one, then the explicit port definition will certainly mess up the other local connections. Try just taking it out. I'm sure local SimConnect connections do not have an explicit port capability -- there's no way the code called directly by the applications can set it or know about it in any case. Possibly it just might work if there were also a SimConnect.cfg file in your Documents folder which SimConnect.dll referred to, thus obtaining the specific Port number. But still you'd only need the one local section I think. Regards Pete

Vaguely -- it's a bundling deal offered by Project Magenta. I really don't know more than that, and I am not going to guess any details of a separate company's trading arrangements. However, bundles aren't the same thing as freebies, it is just inclusive pricing. Regards, Pete

That would be a crucial difference. In fact according to the receipts I've seen you spelled it "Dave Kauffmanjr" on the previous Key as well (the one purchased on 3rd October 2004). Not sure what that means. Sorry. Ah, goodso you are flying now!? Have fun! Regards Pete (Dowson)

Just about the only thing that could do that is a error in one of the three parts. Try cutting and pasting all three sections, not simply the Key. Assuming by "FSUIPC button" you mean the FSUIPC entry in the Modules menu, that is something else entirely --- probably a graphics driver problem, because the dialogue which appears is pure standard Windows. Try changing FS to Windowed mode first -- if it doesn't crash then it is definitely a graphics problem. There seem to be quite a few with these early Vista drivers. Otherwise you need to think what has been changed since the attempts which didn't crash FS. BTW I suppose you let FS2004 install itself into the default location -- Program Files etc etc? That's not really a good idea in Vista, since it protects all the Program Files folders. You may find quite a few of your add-ons having problems. I know it installs FS2004 as an "old" program, with fake (aliassed?) folders, but that seems to make things worse in some ways -- difficult to find things and confusion over what appear to be two of some things. I have a Vista installation on a Notebook, which I don't use for anything serious, only testing things like installation. It is running Home Premium. I must say I don't like Vista muchI am hoping that many of its nasties will be fixed in the expected SP1 update. Regards Pete

When you say "no go" what do you mean? Describe what you see, what happens please. Pete

Sorry, you are asking at the wrong place. I think what you are reading simply refers to a bundling deal which PM offers its customers. Everything about it is dealt with by PM, no one else. Regards Pete