Pete Dowson

Okay, so it has loaded FSUIPC4 (that's where is sees the export it mentions), but it hasn't called it at all yetFSUIPC4 isn't actually running. Turning them off doesn't remove their hooks unfortuanately. I suspect the only sure test would be to uninstall them. Please first though do review the other reports here -- I think AVAST is being used by one person without a problem, and I think there might be other settings in Zonealarm that may need changing. Privacy, or making FSX trusted or something, I think. Buy all means, whatever you find, resolved or not, please be sure to write to tell_fs@microsoft.com to make sure they consider all the angles on this. I have been feeding all this data to them as I get it, and I hope they will get back to me with some clear advice or statement soon, but pressure and iformation through the proper routes from the users who are suffering cannot be a bad thing. Regards, Pete

Seems they have a bug then? Unless you are trying to use it without paying for and registering FSUIPC? I think that is needed. Elite have never contacted me, never asked to use my program nor requested any support. I'm afraid they need to sort their own problems out. Regards Pete

Are you programming buttons in FSUIPC4 too? If not how are you controlling what is displayed. Would you like to explain more? There's no change to GFdisplay, nor GFDev.dll. I cannot easily test your INI here as I don't have GoFlight equipment any more. If it worked before, with FSUIPC3, it should be okay. The NAV, Transponder and COM radio offsets are working fine in FSUIPC4, so I really cannot say what is wrong. If you want me to look, I can check FSUIPC Log files -- you'd need to enable IPC Read and Write logging in FSUIPC. Please make sure nothing else is using FSUIPC at the same time otherwise it will be too confused. Do things methodically and write down exactly the sequence you used so I can piece that together with the Log to see where it is going wrong. Pete

Insolence? Do you actually know what it means, as it cannot possibly apply here? Please read it again. I merely asked the obvious question as to how effectively the same post appeared twice, together (which you have answered well), and I pointed out I'd answered in the other one as it was the first I'd seen! You surely didn't want me to cut and paste the reply here too? What's the matter with you? Your response to my civility is most certainly completely unnecessary and not wanted, thank you very much. I'd rather you not come here again with that sort of attitude. Pete

Why post effectively the same question twice at the same time? I've answered as best I can in the first of the two I saw. Pete

In FS2004 and before the only way Multiplayer (as opposed to AI) traffic showed in FSUIPC's TCAS tables was by something like AIBridge, or, I think, the later versions of Ivap and Squawkbox, injecting the data into those tables as well as injecting the multiplayer aircraft details themselves into FS via the published MP interface. Without something actually providing the data on the MP aircraft, FSUIPC doesn't know about them. Its tables are populated by facilities in FS (and FSX in this case) to read details about AI aircraft. As far as I'm aware, there is not yet an SDK for FSX multiplayer, which is certainly different to previous versions, so I don't know how it is possible that you are currently using add-on preograms which generate MP aircraft. However, if they can do it then they can certainly inject the details into FSUIPC4, because that interface I present has not changed. I'm not sure what you mean by "but nothing seems to work in Multiplayer. WideFS shows as connected" -- WideFS really has absolutely nothing whatsoever to do with multiplayer. In fact I've never done any programming for multiplayer at all. I know nothing about it. Are you actually trying to use the FS2004 version of AIBridge? I wouldn't have thought that would work -- doesn't it depend upon the MP interface to FS? That is entirely different in FSX I think. I have seen some statements that say that Microsoft will not be opening up Multiplayer for use in the way it has been used in the past. Aren't the Squawkbox and Ivap and FSInn writers having to program the aircraft injection for FSX via Simconnect, creating them effectively as AI aircraft? Take a look at the various websites and check the news. I've only looked at the FScopilot/FSinn site, and that seems to confirm this. If that is true then all those "ex-MP" aircraft will show up through FSUIPC because they will look like AI aircraft. In fact they will mix with AI aircraft unless you turn the traffic right down on the sliders. Let me know what you find out please. It isn't an area I can afford to spend much time on at the moment, too much else to do I'm afraid. Thanks. Regards Pete

I think I can explain it ... In some Beta version of FSX the SimVar for the fuel pump switch seemed to work okay for writing as well as reading. So in my tables I marked all of them (the 3104 one for Engine 1 and 3125, 3958, 3A18, 3AD8, 3B98) as 'OK' for writing. Then I found that writing wasn't working (in a later Beta of FSX I think), and unmarked this -- on all of those offsets, excepting 3104 which I missed! Duh! What happens is that, on a write to a SimVar which doesn't support writes an exception is generated by SimConnect, which eventually gets back to me (all these things are aynchronous). When I see the exception on this write, I add another flag "Write Error" which makes future attempts bypass the SimVar writing section and operate using events (controls) instead. I think this explains all your results -- the business of many settings before FS is full ready is probably explained by the delay in SimConnect getting the row of Exceptions back to me. It is easily fixed and will be so in the next update, this weekend. If you cannot wait I can send you an interim version, but I'd rather not if you don't need it. Thanks! Pete

Okay. I'll email you something this afternoon. Pete

What security program(s) are you using? I think merely switching things off may not help. Depending on which package you are using there may be a "privacy" setting which needs adjusting too. But there appear to be different issues with different packages. Apart from completely uninstalling any third party security software, which seems to work (though some partial measures have laso been successful), I know of nothing else you can do. I'm hoping that Microsoft will be able to resolve this, but that may take time. Please read through the thread about this which already exists: http://forums.simflight.com/viewtopic.php?t=56507 I think that sums up all we know so far. Unless SimConnect works almost all add-ons are dead in the water! Regards Pete

Okay, I've found out what I think is happening. Luckily in this case it isn't one of those simconnect blockages I was afraid of. With all these sequences involving a SELECT 1-4 after the control, I intercept them and forward them, but with a different SimConnect prioriy -- this is deliberate so I don't get them back again in an infinite loop. That applies to the Engine select, the Exit select and all the 1-4 selection keys, but for some reason it doesn't actually apply to the Pushback control. It works for a registered user because it refers to the pushback state in the offset (I allow an infinite time for the turn in a pushback, as I can tell whether it is still pushing or not, but only 4 seconds, default, for Engine and Exit selection). So, the pushback control is not currently actually being intercepted at all, only detected. The select 1 or 2 controls are intercepted and routed through with a different priority. This should still work -- I can only think that the change in priority somehow changes its association within SimConnect. I'll fix that by intercepting the pushback control too, but I think, in an unregistered copy, I'll bypass all interception in any case as it is pointless as the intercepted controls cannot be adjusted then in any case. Thanks for the report. This'll be fixed in an update I'll release on the weekend, but if you need it more urgently let me know and i'll make you an interim (though of course I'd rather get on and do more;-)). Regards, Pete

Yes, please do. Pete

Okay, sorry -- it applies to all aircraft. Silly little bug. I tested the main code, the calibration itself, using my FS2004 INI file parameters. They work. It's only the dialogue which reads the number of detentes from the wrong place (the old FS9 place). It'll be fixed in the next FSUIPC4 update, probably Saturday. If you can't wait I can email you a fix this afternoon, but it really would be better for me to get on and do more things. Thanks & Regards Pete

You have a bad FSX installation then. When FSX installs it puts Simconnect.dll into the Windows "side-by-side" folders, somewhere like: C:\WINDOWS\WinSxS\x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.60905.0_x-ww_429211e9 That's where it is on my system, anyway. Without SimConnect installed no add-ons which use it, including FSUIPC4, will be able to connect to FSX. I really don't know how you managed to install FSX without SimConnect also being installed, but you may want to try several things: 1. Use the FSX DVD to attempt to "repair" the installation. i think that a repair option does appear if you move to install again. 2. Completely uninstall it and try again. 3. Report the install problems to tell_fs@microsoft.com so they may fix them in an update. Let me know how you get on, please. Regards Pete

If you have installed FSUIPC4 in FSX and registered it, you can put GFdev.dll into the FSX modules folder and FSUIPC4 will see it and load it. Then FSUIPC4 will, in its buttons section be able to recognise the Goflight buttons and knobs and you can program them. Please check the User Guide. GFdev.dll only allows third party programs like FSUIPC4 and Wideclient to see the buttons so you can program them. It doesn't provide a ready-made solution like the correect GoFlight drivers. And neither FSUIPC nor Wideclient drive GoFlight displays and indicators, though my GFdisplay program (http://www.schiratti.com/dowson) can be programmed to deal with those too, as you wish. There's no ready-made install-and-go solution except from Goflight themselves. My efforts offer flexibility but require work akin to elementary programming on your part. You can mix both too. Regards Pete

Nothing I know of, sorry. The multiplayer stuff is one part of FS I've never delved into at all. Regards Pete

Really? I get the detente details from SimConnect. Are the other aircraft okay? I'll check later today and get back to you. Regards Pete

This really isn't an FSUIPC problem at all, but it may be related to Simconnect, which FSUIPC4 (and many new add-ons as they become available) will be using. It can also occur with no add-ons installed, though possibly the Simconnect activity does exacerbate it. It really needs attention in the FSX code. Can you please report it by email to tell_fs@microsoft.com. FS2004 had many such problems, including coming back with an all black screen. Most of those were fixed by the 9.1 update Microsoft released. There was certainly nothing I did or could have done in FSUIPC and, again, it wasn't only with FSUIPC installed it happened. More likely and hopefully in an update sometime to FSX. But please do report it as I suggested above. Thanks, Pete

Yes, there are (switchable) facisities in FSUIPC3 and 4 to deal with these. With FSUIPC you can even have intervening controls -- for instance during pushback you can look sideways out of the windows and determine when to use the 1 or 2 for turning. Ah, with it unregistered you don't have access to the facility I just described. FSUIPC monitors controls for logging but does nothing with them. Hmmm. Strange. The engine selection and pushback controls are like the joystick axis controls, in that FSUIPC4 intercepts them and passes them on, in case it is being asked to operate the facilities I mention above or to do joystick calibration. All other controls are merely monitored, not intercepted and forwarded. This works fine even for unregistered users EXCEPT for those who are using some thrid party security packages. I've not had your particular problem reported before, but there have been at least two folks with ridiculous delays building up on the joystick inputs -- 5 to 30 seconds (!!!) was quoted. Please see thread http://forums.simflight.com/viewtopic.php?t=56572. See above, that seems the most likely. Have you experienced delays in joystick response? Apparently they build up over time. Well, it all worked last time I checked, but of course I'm normally registered. I'll re-test without today. and let you know. Only if you opt to Log Weather details. All versions of FSUIPC have always read the weather at regular intervals. In FSX's case there are three weather reads normally -- at the aircraft (interpolated), at the nearest weather station, and the global settings. The first is read at the interval specified in the INI, the others at multiples of that. I did consider only logging it when it changed, as in FS2004, but in fact it changes nearly all the time so it was a waste of code. Hmmm. That is surprising as they are treated identically in FSUIPC4. To make sure we are comparing apples with apples and not with oranges, could you test the pushback not with your gauge but with the keystrokes as you are the E's and Shift-E's? And vice versa perhaps? Can you tell me exactly what security software you are running (firewall, virus, privacy). Check the other threads here, see if anything applies to you too. Maybe test without any of that? Meanwhile I'll do some more checking here to see why the E's and Shift-E's could be different to the Shift-Ps. Regards, Pete

Thank you! I thought they were okay, but I hadn't had time to do extensive tests. I'll mark it up ready for the next update. Regards Pete

Intentional. FSUIPC4 is a completely new product. FSUIPC3 keys are for FSUIPC3. FSUIPC4 keys are for FSUIPC4. Please check the User Guide for details. BTW version 3.53 is many versions out of date and not supported in any case. The current version 3 is 3.70, with 3.71 due soon. Regards Pete

I think that path looks right if you allowed FS to install to its default place, but I've never done so (I like short paths like D:\FSX). If you are not sure you can put the log wherever you like. I only advise keeping everything related to FSUIPC4 in the Modules folder, keeps it 'tidy' to my eyes. Regards Pete

I am wondering if this is yet another symptom of the problems SimConnect has when there are third party antivirus, firewall or privacy hooks in place. So far there have been two clearly identifiable symptoms: 1. FSUIPC4 installs okay but never gets to talk to FSX -- no AddOns menu is produced. 2. FSUIPC4 installs okay and there's an AddOns menu and everything seems to work but there's a growing delay in joystick response -- 5 to 30 seconds have been reported! The Simconnect problems affect all add-ons which use it to interface to FSX. Simconnect uses TCP/IP protocols to interface between itself and FSX, even though they are both running in the same process, FSX. The security hooks placed by the assorted security programs certainly have enough privilege to be able to cause a blue screen crash. Is there an FSUIPC4.LOG file produced in the FSX modules folder at all? If so, please download the 4.011 version from the FSX announcement above and use that -- I added a bit more logging. Then show me the Log. If there is no log, then FSUIPC4 hasn't really started. Then we need a Simconnect log. To get this is a little more tricky: First, create a small Text file (eg in Notepad) containing: [simConnect] level=Verbose file=\Modules\Simconnect%01u.Log file_max_index=1 Fill in the folder stuff, then save this as "Simconnect.ini" in your "My Documents\Flight simulator X Files" folder. Now, when you run FSX, SimConnect will log all sorts of things to a file "Simconnect0.Log" in the Modules folder. See if that Log is there after the crash and if so, show that to me. Then delete or rename that Simconnect.INI file. Otherwise, when we do manage to solve your problem, the files will become HUGE (and I mean HHHUUUGGGEEE) with all the FSUIPC4/Simconnect interaction. Finally could you please do three more things: 1. Identify exactly what firewall, anti-virus and other privacy software you have running. Let me know please. 2. See if you can disable it all (not irrevocably, for now) and re-test. Let me know this too please. 3. Report everything to Microsoft by email to tell_fs@microsoft.com. Regards Pete

And at what stage was thishad FSX asked you permission to run FSUIPC4 yet? It takes a while before Simconnect even gets that far. Actually FSUIPC4 cannot make such blue screens, it simply hasn't the privilegeit sounds like something is wrong with your installation. I would advise you to uninstall and re-install FSX. Regards, Pete

Well, it won't be the priority. Certainly there may be bug fixes yet to come. I still have to release 3.71 of FSUIPC and 6.71 of WideFS. In general there is so much new potential in FSX which can't be applied back to FS2004 that I doubt there will be anything new in the way of user facilities in FSUIPC3. This is why, in the earlier monthos of this year I went furiously at it, adding all of the facilities I had been asked for that were still on my list. There are actually none left on the list! I someone comes up with a good idea which is easily applicable to both, I will probably implement it in both, however. .I assume you mean a shortcut? Well as you like, but you are only saving a few bytes of space. Seems an odd 'saving' really! ;-) Regards Pete

Actually that cannot remove the menu entry as far as I can tell -- it needs a specific call to Simconnect to remove it. Furthermore, a DLL cannot really crash in a process without crashing the process -- FSX would have crashed. FSUIPC4 runs in the same main thread as most of FSX. The "previous flight" facility is broken in FSX. There is such a file saved in the same folder as FSX.CFG, but that only exists whilst FSX is running, so it is useless for the main purpose. All of the path identification code in FSUIPC4 uses Windows APIs and the Registry. After seven years dealing with FS versions in different languages i know how to obtain these. Just check the FSUIPC4.LOG file, the paths that matter are always logged there. Regards Pete