Pete Dowson

I have xclass installed as well, in any case. Thanks. This confirms what you say, but doesn't show why. What I really need to know is whether it is okay with 4.10 (attached in this thread earlier). Because if it is, then it must be purely down to the fact that FSUIPC 4.11 is now waiting for SimConnect to supply the "IS USER SIM" flag, and it isn't arriving very promptly. If it is okay with 4.10 then could you go back to 4.11, enable SimConnect logging (as described in the FSX Help announcement above), and re-test. Keep it short, but long enough to prove the problem. then Zip up the SimConnect log for me. I'll need that to discuss this meaningfully with Microsoft, because it would mean there's a SimConnect bug which will need fixing. Then I shall have to try to find a work-around. The fact that there are occasional enroute airliner flights without flight numbers indicates SimConnect is also being a bit cavalier about some of the less essential data FSUIPC asks for. Did that never occur before 4.11? Regards Pete

Possibly, though more information is the prime requisite, and other tests as stated. If you want to send a ZIP (and it must be Zipped), please send to petedowson@btconnect.com. Regards Pete

Sounds like a connection difficulty, not a TCAS tables problem. You need to start TrafficLook AFTER FS is running. Which version of FS? Which version of FSUIPC? What other programs are running? There's no difference to FSUIPC whether traffic are on the ground or in the air -- the only difference in treatment is the range at which they are included. Flight numbers are not assigned until the aircraft are under ATC control and actually commencing a route. You don't get flight numbers for aircraft injected by programs like VoxATC or multiplayer-type applications. Flight numbers are also discarded for aircraft not reported as in a state known to be ATC-related, so the state is important too. e.g. "Init" or blank would not warrant a flight number, whereas Taxi and Enroute would. As you say later, there are no attachments. Anyway, the log file will show nothing about AI traffic unless extra logging is enabled. Otherwise the file would become huge pretty quickly. The first thing I'd need to know are all the details, like versions of everything, what else is running, and what you've changed recently. Apart from what i mentioned earlier regarding 4.11 and FSX+SP1 there's been no difference in anything regarding AI traffic in FSUIPC for about four years. So I obviously need to know what's changed just recently. If you do mean FSX+SP1 and FSUIPC 4.11 then I need to know whether it was okay with 4.10, and I need a lot more information about what else is running and what you are doing. I've tested it all thoroughly on two different systems and cannot get anything at all to go wrong. In case of FSUIPC4, please look in the FSUIPC4.LOG and see if there are any errors reported. If the SimConnect connection is playing up, that would more likely explain things. Regards Pete

Yes, but I don't know why you are reading any "" in any case. Regards Pete

Ray Proudfoot (visiting me today) and I have just flown three flights with RCV4.3, with ASX running (both on a separate PC to FSX), and FSUIPC 4.11, and the ground traffic detection and RCV4.3 interaction worked fine in all three flights. TrafficLook confirmed this. So, sorry, I am puzzled as to how they can be missing on your system. We'll need some process of elimination to see if there's a specific cause. Once I know more I can maybe suggest some logging options which would tell us more. Regards Pete

Okay. The "" marks around the strings in this log are added by the logging. they are not actually part of the string data returned by FSUIPC. they are there in the log so you can see any leading or trailing spaces. Okay. But it might be a good idea for your code to test for and strip off quotes at either end in any case. I doubt that they'd occur in real titles. Regards Pete

I cannot reproduce any problem with FSUIPC 4.11 and TrafficLook showing Ground Traffic. Have you checked with just FSX, freshly loaded, and TrafficLook? If you are getting a situation with TrafficLook not showing ground traffic even when you can see it (the range is much shorter than for airborne traffic), then I need a lot more information in order to track it down. Like if it occurs always or only when some other add-on is running, or only after a flight reload, or use of multiplayer? If I can't set up a situation in which it occurs I will have to work out what extra logging I can get to show the problem from the inside. Regards Pete

Yes, that is perfectly correct. The wind hits the tailplane causing the nose to try to face into the wind. The same happens in a sailboat -- left to itself a boat with a taut enough sail will turn into wind and the sail will flap as you lose way. It isn't an "issue", it is basic physics. When you are actually flying it is completely different. The whole aircraft it moving IN the airstream, not pivoting on anything. As far as flight is concerned only the relative wind matters, and that comes from your airspeed. You are then using the rudder (and aileron) to correct your ground track (course). If you don't understand this please try to read a book on basic flight. I'm sure it will all become clear. I am not a good tutor. ;-) Regards Pete

FS has never supported any "switch" function for reversers. The nearest you can get is Throttle Decr (the control normally assigned to the F2 key). Try that, with repeat whilst pressed enabled. Sorry, what do you mean "I have but", where "have" you got this and why isn't it doing what your programme expects? There are two controls I see -- INCREASE DECISION HEIGHT and DECREASE DECISION HEIGHT. Don't you think one of those might be relevant? Regards Pete Cheers Craig

I'll check here. Is this only with FSUIPC 4.11? I had to make a change for FSX+SP1 because SimConnect was returning different User Aircraft IDs and SP1 was installed, and often FSUIPC would lose all contact with User Data. In FSUIPC 4.10 the change unfortunately made the User Aircraft also go into the TCAS tables, which caused continuous collision warnings in properly equipped airliners! I fixed the latter in FSUIPC 4.11, eliminating the user aircraft from the TCAS tables by reading a SimConnect variable called IS USER SIM, or some such -- but this means I have to wait for that to be returned. Maybe SimConnect isn't returning this for ground aircraft? I'll do some tests here later today. Last time I did check with TrafficLook I am sure I saw ground traffic, but I'll re-check. Meanwhile, in case you no longer have it, I attach FSUIPC4.10 -- can you try it with that and let me know? Just put the DLL into the FSX Modules folder (save your 4.11 first). If the difference is between 4.10 and 4.11 I will have to review what SimConnect is doing and think again. BTW TrafficLook is simple a demo/test for FSUIPC's TCAS tables and is just as valid for FSX as FS2004. It, along with other FSX goodies, is supplied separately now, in the FSX Downloads above. Regards Pete FSUIPC410.zip

Correct. Looks like a misprint I made (back in January!!). It's of size 256. Well, it isn't a difference in FSUIPC. I don't add anything or take anything away. Which Flight simulator is this? FS2004 or FSX? If FSX, as sounds likely, it'll be a difference in how SimConnect supplies it. I can check. If it is supplying them with such variations I may need to scan for and remove " characters so that comparisons and aircraft-specific checks will work consistently. Sorry, same result for same aircraft, or does the result follow the title? Maybe it's your code? Or whatever FSUIPC interface wrapper it is you are using for your language (is that VB?). I can try it here, but first I'd like to know which version of Flight Sim you are referring to. Just in case it is your code, could you Monitor 3D00 please, change various aircraft, and show me the resulting Log. To do this go to FSUIPC's Logging options, right-hand side, set offset 3D00, type ASCIIZ, and select "normal Log". Please always consider using Logging for debugging purposes. You can actually log exactly what your program is reading or writing (IPC read and write logging) as well. That is what it is for. Also, you can check directly what 3D00 is containing by using FSInterrogate, as supplied for such purposes in the SDK. Regards Pete

You can send the control to FS by program, if it is a program you are talking about. Why would you want them to assign a key to do a job you can do directly? They would need to expect there to be a "loading" progress bar on screen when you execute the control, however. It should be fairly short-lived, though, for most aircraft. Regards Pete

I've tested saving and viewing Flights in the Flight selection menu now on three different systems, including one Vista system in full screen mode, and two XP systems, one with an ATI card and another with an nVidia, both Windowed and full screen modes, and all of the flight snapshots are perfect. Sorry. It sounds as if there's some sort of problem with the video drivers on your setup, just possibly exacerbated by timing differences which may occur when FSUIPC is running. I suspect you'd get the same with any other busy SimConnect client. Regards Pete

Oh, yes. Okay. Anyway, the problem is fixed in 4.11. Thanks for reporting it in time! ;-) Pete

Odd, then, that others have succeeded. Maybe TeamSpeak has been changed since it used to work? See for instance http://forums.simflight.com/viewtopic.php?t=42038 . There is actually a section in the WideFS Technical documentation entitled PTT (push to talk) for Roger Wilco, AVC and TeamSpeak and TeamSpeak gets its own little section within that, telling you the exact details you need to know. Regards Pete

FSUIPC3 keys won't work with FSUIPC4. They are different products with different keys. Please check the User Guide for purchase details. Regards Pete

And you've not reported this for the nine months since FSX was released? Or have you collected all versions and only tried them recently? No. You are the very first in all this time. Shame it wasn't reported in time for an SP1 fix. I can see if it happens here of course, and if it does report it to Microsoft -- because if it does happen generally it will be some sort of SimConnect problem which they can possibly supply a workaround. FSUIPC4 is not like previous versions, it is 99.9% SimConnect interfaced. The minor exceptions (getting the list of controls from CONTROLS.DLL) tend to be very minor and static (i.e. happen once, or not at all until used). I've got to go out now, but I'll try it later. Regards Pete

Okay, never mind about the INI file -- I've reproduced the case where it is logging the Aileron changes notified from SimConnect. I'll fix it in ther next increment (4.105, or maybe 4.11), within the next few days. Thanks for letting me know. Regards Pete

Let me see the INI file -- looks like a Monitor entry is there, or possibly a LogExtras. There's no such thing as "disabling logging". FSUIPC always creates a log. It will log certain things always. However, certainly these: should only appear if there's a LogsimC or Monitor entry for 0BB6, or a specific LogExtras value set, introduced (temporarily, for 4.104 only, to debug one user's specific problem which turned out not to be a problem anyway). I need to see the INI. Regards Pete

Ah, so cutting down on video objects reduces or erliminates it? In that case it may well be a video memory thrashing problem. How much video memory have you got? Regards Pete

It can't be a "big deal" if the Installer said everything was okay, because that means it worked. However, it does seem odd. Certainly there's nothing like that on XP. In my Vista Home Premium I can't find anything either. Let me check I'm looking in the same place. Computer - Properties - Manage - Event Viewer - Windows Logs - Applications. Right? I have no Install FSUIPC4 errors listed there. I do have SimConnect RTM, Beta4 and SP1 installed, but not Beta3 on that PC, so if it is logging an error because that one is missing it isn't logging it here. Or if it is, it isn't where I'm looking. Strange. Maybe it's related to some security settings someplace which we have set differently. Regards Pete

No, not possible except in one circumstance -- a bad key for FSUIPC which looks okay and is accepted, but which is actually made by a pirate key generator. If, when you register FSUIPC again, you get a repeat of the problems, Zip up the FSUIPC.KEY file and send it to me (petedowson@btconnect.com) and I can check that. Regards Pete

I don't think you really need to, and I wasn't assuming you did know. However, it is fairly self-explanatory -- a system for having different versions of a Library (as in "DLL") simlutaneously installed and available for use by whosoever wants to use them. This allows folks like the MS FS Team to change SimConnect, or whatever, completely, should they need to, without destroying compatibility with programs written to the older interface. Yes, I assumed you were, and that's why I was trying to explain that if the system is logging this it will only be for information, as it will also be reurning it to FSUIPC's Installer. ErI didn't think you were. How could it refer to my Installer if you were? Sorry, we seem to be talking at 100% cross-purposes. Fine, then. There is no error at all then. So what's the beef here? Does the Install log list the Versions of SimConnect it finds? That's the result of the loop, and that loop is the only time the Beta3 version would be checked for. I can do so next time I power up the vista PC. Is it something you are concerned about? I'm certainly not sure why it would flag it as an error if the program is catching errors, as it is. Maybe it's a Vista bug. Regards Pete

Hmm. I've not heard of any problem like that. I, like many others, have AutoSave enabled all of the time. Since it's a change-of-view problem I'm wondering if it might be video driver related, and all that AutoSave is doing is altering the timing slightly. How often is autosave saving files? Try less often, see if it crashes less easily, more often, see if it crashes more easily. AutoSave is doing nothing more than calling a SimConnect routine to save the flight every so often. Between those intervals it is completely dormant. Please do make sure you are sending the reports to Microsoft when requested, then try different video settings -- eg Windowed / Full Screen, less or more video options -- reduced mipmapping, filtering, etc. Some combination may be critical. Also look for different video drivers. If you are using Vista I have heard that some of the Vista video drivers aren't too stable yet. Regards Pete

What am I supposed to be looking for? What is the problem you need solving please? Only this is wrong: All this shows is that the FSUIPC key in the FSUIPC4.KEY file is not a valid Key for FSUIPC4 with that user name and address. Not having FSUIPC4 registered won't stop applications working, it will only stop you using the extra user facilities. Regards Pete