Pete Dowson

Thanks. It gets stuck in the routine which is calling Windows to find the registry stuff to convert: your FSX flight path: "C:\Users\Jerry\Documents\Flight Simulator X Files\" into a UNC ("Universal Naming Convention", I think) path so that it can be accessed from other PCs. Now I know where is it getting stuck, I'll put logging into that routine (it is quite small) to see why. Later, Pete

Sorry, your problem is the same as what? you don't mention a problem except "no modules dropdown", and the files you provided show everything is running fine! There never is a "modules dropdown" in FSX -- that was FS9 and before. A solution to what? I see no problem in the files and you don't described one. Regards Pete

Yes. since there IS an FSUIPC4 log file produced, the DLL.XML file must be okay, so I didn't need to see that. The FSUIPC4.LOG file shows that there's an installation problem: Looking also back to the Installation log file, I now see this: which means that you are running the original buggy version of FSX but have installed later versions of SimConnect (SP1 and SP2/Acceleration) which are incompatible with the old FSX version. You need to update your FSX installation -- either buy and install FSX Acceleration, or download the SP1 and SP2 updates and install them in that order. Make sure you run FSX between the two. The only other alternative, if you really want to stick to a buggy and inefficient version of FSX, is to uninstall both SimConnect SP1 (the 61242 version) and SimConnect SP2 (the 61259 version). Do this via the Programs and Features part of Windows settings. Note, however, that if you do this you risk making your FSX incompatible with many other current SimConnect clients. Regards Pete

It's only "better" because it is automatic, saving you putting any parameter changes in. Now you've got the right parameters (the ones advised by the documentation, in fact, if you do have difficulties), it makes no difference. I don't understand why the Broadcasts aren't seen by another PC on the same workgroup. Makes no sense to me. But then I moved off Vista as soon as I could. Win7 is soooo much better! ;-) Regards Pete

Sorry, I don't know what that is but it isn't 'the file'. Please simply open it in Notepad, select all, and paste it into a message here. Was there no FSUIPC4.LOG file produced again? You didn't say. You only said it didn't work. Pete

No that's the Install log. if there's an FSUIPC4.LOG file it's called FSUIPC4.Log. If it isn't there then FSUIPC4 wasn't loaded, so that's why I suggested trying the new Installer. If the new installer doesn't help I need to see the DLL.XML file, because it would then appear that it is corrupted. You can find that here: C:\Users\Anders\AppData\Roaming\Microsoft\FSX Regards Pete

Is there an FSUIPC4.Log file in the FSX modules folder? If there is please paste its contents here so I can see what it is doing. If not, please use this link to download a later Installer and see if it helps: Install FSUIPC 4.634 If that doesn't help, please find the Installer log, also in the FSX Modules folder, and show me that. Regards Pete

Okay. Then the broadcasts from the Server are definitely NOT reaching the client, which either means the client is running an old version of Windows (before XP), or you've not got the WorkGroup names the same as you said. Please double check the workgroup names. Win7/Wista and XP default to different names, so you can't rely on just leaving it. I name mine "PETES" throughout. Alternatively, you CAN put "ServerName=VICKY_PC" and "Protocol=TCP" into the [Config] section of the WideClient.INI (don't touch the Server end, or the Ports). But it would be better to have it operating automatically. Pete

Looking at the FSUIPC4 log you supplied, it seems to get stuck during initialisation, before logging the FLT UNC and FS UNC paths. So, just to check if that is where we need to look, I've added a little extra logging in that area. Please download FSUIPC 4635a by clicking this link, and copy it into your FSX Modules folder. The edit the FSUIPC4.INI file, adding these two lines to the [General] section: Debug=Please TestOptions=x400 Then run FSX, get the crash, and show me the FSUIPC4.LOG. Thanks, Pete

Well, in that case it is no wonder that WideClient couldn't connect. The server end won't be WideServer and won't understand the WideFS protocol, so rejecting the connection. Pete

That simply shows that nothing even attempted to connect to it. But it does show the Server name: VICKY-PC And the fact that it is broadcasting its details for WideClient to find: 16131 Broadcasting service every 1000 mSecs You do NOT set any IP address in the Server files! WHY are you changing anything? You should really leave all alone. Do NOT change the port numbers. There's never any need unless you have other FS programs using the same ports already. The one you chose could well be taken or invalid for all I know. Why port numbers? Wherever did you read you needed to set those? And if your network is working AND they are truly in the same Workgroup, you should not change anything. No protocol line, no IPaddress line. Even if you do specify things it is usually best to give the ServerName, not the IP address. And you provide no information for me to help .... no logs, no details of the error, nothing? I think you'd be better off deleting the WideClient INI file and the complete [WideServer] section in the FSUIPC4.INI file, and trying again without making any changes at all. THEN show me both logs. Regards Pete

Hmmm. I've not had any user which such a persistent problem since FSX came out. Seems you either have a corrupted FSX install, or just possibly a bad game device driver. There's not much I can do from here to check those things. You could check Window's game controllers to see if there's anything listed which shouldn't be. You never had an Epic installed at all, did you? If you don't know what that means, never mind. I really need the module name, and address, which is actually crashing. You said earlier that you don't get any information, that the SYSTEM actually hangs. Do you still confirm that? You have to do a hardware reset or switch off and on again? If so then it really must be at driver level, as in a games device driver or even, possibly, a video driver, though that sounds rather unlikely as video things are nothing to do with any FSUIPC start-up. If you cannot get any more details, eg by clicking a button on the failure screen, or from the Windows error log, then all I can do is work on a lot of extra logging in FSUIPC4 to find out what point, exactly, it reaches before things die. This could take a while, and I can't start till next week, so the more investigation you can do your end the easier and maybe quicker it is going to be. Regards Pete

Well that's only the WideClient log -- half the story. Network connections between PCs have at least two ends. The server is operating at the FS end, and there will be a WideServer log there, showing what it did. The thing that concerns me in your client log is this: What have you been changing in the WideClient INI file? Why port 50300, and if you want to use that port (assuming it's legal and available), have you changed the settings in the Server too, to match? Is that IP address correct? Why are you specifying IP addresses? Providing both your PCs are in the same workgroup you shouldn't need to change anything at all in either INI file. Please tell me what you are doing and why you are doing it and I might be able to help. Generally it is best to stick to the documented methods, which really involve no messing with INI files at all. Regards Pete

Hmmm. Over 500 aircraft being generated for such a location? Sounds a bit odd. But I'm glad the fix works. EXE's or DLL's being loaded automatically that you don't want can be stopped by removing the relevant section from the EXE.XML or DLL.XML files. In this case, your EXE.XML file was as shown below. Just remove the RED section to stop REX2 weather engine loading, or trying to (it probably fails if you uninstalled it): <?xml version="1.0" encoding="Windows-1252" ?> - <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> - <Launch.Addon> <Name>Real Environment Xtreme - Weather Engine 2</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Real Environment Xtreme 2.0\rexwxengine2.exe</Path> </Launch.Addon> - <Launch.Addon> <Name>Saitek Panel(s) Plugin for FSX</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe</Path> <CommandLine>-run</CommandLine> </Launch.Addon> - <Launch.Addon> <Name>GoFlight Hardware Interface</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\GoFlight\GFDevFSX.exe</Path> <CommandLine /> </Launch.Addon> - <Launch.Addon> <Name>Saitek Panel(s) Plugin for FSX</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanelsFS9.exe</Path> <CommandLine>-run</CommandLine> </Launch.Addon> - <Launch.Addon> <Name>Saitek DirectOutput RadioStack</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe</Path> <CommandLine>-run</CommandLine> </Launch.Addon> </SimBase.Document> Be sure to use a plain text editor, like NotePad to do this. Do NOT use WordPad or any word processor. Regards Pete

Providing it isn't used in any money-earning role, and it is your own good self using it for demonstrations and explanations, that's fine. It would be like anyone have people round to their house to see things and have them explained. The FSUIPC registration scheme is intended to allow you, the purchaser, to user it as you like, on your PCs, or on any PC's, but for your use only. In other words, it is associated with you, not the machine. This is different from many licenses. Regards Pete

Its un-installer obviously forgot about the EXE.XML entry! Glad I worked it out right -- though you shouldn't have gone to that extreme. Now, even if you fly back to the place you originally started out at it should be okay, because the traffic will be added more gradually and SimConnect should cope with the requests FSUIPC is making. Where was that, by the way, and were there large add-on airports there? Meanwhile, however, as a test, could you revert to the original start-up place, after installing this test version of FSUIPC4: FSUIPC 4635. This should be okay up to twice as many aircraft. It only asks SimConnect for one (larger) batch of data for each instead of two smaller. If it still fails then SimConnect just isn't going to cope and all I can do is put a stop to reading AI traffic when I get the first few error responses. Now, there was a reason it was implemented as two separate chunks -- because SimConnect gave errors if asked for AI only values with the ID referring to the user aircraft. Now normally that wouldn't happen but I think when changing to mission mode -- or maybe it's multiplayer, I don't recall -- and/or back again, the User Aircraft ID changes and it gets notified in the same way as an AI aircraft. Very annoying. With this version, if that's still a problem with the later versions of SimConnect, there could be errors logged when that data is requested. Hopefully not, but I don't know how to repro the condition at present. More research might be needed to see if I can let this change go live for all. Let's see if it fixes the original problem, first. BTW you might want to keep the TrafficX crew updated as to our findings, to let them know it isn't anything specific to TrafficX, just to do with airport and traffic density settings. Regards Pete

The first thing you are doing VERY WRONG is openly publishing your FSUIPC key! I may have to invalidate that one now! Even though I've now obliterated it with X's I've no idea how many unscrupulous thieves might have seen your details first. Did you rerun the FSUIPC4 installer and re-register? Just copying in the KEY file won't be enough. Else send the details to me at petedowson@btconnect.com and I will check them for you. Pete

No, not at all. This is an intriguing problem and I'd like to get it resolved. You don't want me having sleepless nights, now, do you? :-) Right. So does the "WideFS problem" only occur after you've run tCC, but then not when you reload FSX, or does it occur every time after you've run TCC until you re-install TrafficX? If the latter, then I think I know what is happening. Your start-up flight is in an area which is dense in terms of busy airports, or has some large airport add-on, for which TCC is generating a HUGE amount of traffic -- well over 500 aircraft, right off the bat! I suspect if your start-up location was elsewhere it wouldn't be a problem. Yes. That's loading REX weather engine -- which didn't seem to get a lookin in the period logged -- plus others. Here's the list: Saitek Panel(s) Plugin for FSX GoFlight Hardware Interface Saitek Panel(s) Plugin for FSX Saitek DirectOutput RadioStack Seems to want to load the Saitek panel plugin twice. That'll stop those things above running automatically. Is that what you want? You'd needn't make any changes to either DLL or EXE XML files -- now I've discovered what is going on, neither of them are the problem. I'm putting together a test build of FSUIPC4 for you to try for me. I've modified it to, hopefully, allow up to 1000 AI aircraft. Later ... Regards Pete

Got it, analysed it, replied -- see previous message to the one you just posted. I just don't understand why any of this is anything to do with this "TCC". Whendo you run it and why, except after adding new scenery? Pete

Got it via email. Thanks. I see now why you got in a mess with the SimConnect.INI, and how you ended up with an odd name like "moduleSimconnect ... for the filename -- the Forum left characters out of the FAQ post! The log shows a lot more Simconnect stuff running than shown in the DL.XML file you found. Are you sure there was no EXE.XML file? These are the SimConnect clients running (in the order they start up): Saitek FSX Plugin VimaCoreX Saitek DirectOutput Radiostack FSUIPC AFXModuleFSX That last is from a scenery designer, isn't it? Airport Facilities Designer? There's no sign of your traffic thing here. Was this SimConnect log one taken during a session where WideServer didn't start? It looks like there's simply too much AI Traffic data being requested for SimConnect to supply information on them all, then things get messy. I think Simconnect has a limit of 1000 requests. I currently need 2 per AI aircraft, and there are about 540 AI aircraft being generated by your Trafficx in the first 4 seconds! I don't know what I can do about that. I'm thinking. I've not met it before -- none of the other traffic programs generate over 500 aircraft withing the current "reality bubble". Regards Pete

Ouch! I've just had a look at the FAQ post about SimConnect logging and I think I see what was confusing you. This damned new Forum software has messed up the file, making, in particular, the "File=" line in the example INI file all wrong. That makes the sentence about "" also all wrong. Sorry. These threads and posts were transferred by SimFlight en bulk to this new software and it seems much of the erstwhile intelligent formatting has gone completely belly-up. I've adjusted that particular post to read better, after some trial and error. Please, if you see anything else thast no longer makes sense, do just ask me to look at it and check if there's another formatting foul-up! Regards Pete

Possibly this JS41 is an add-on aircraft which does not use the standard FS controls? If it is by PMDG then I suspect nothing in the autopilot is standard. If you merely want to test that assignments to the switches and knobs on your M-Panel are working, then please use a default aircraft which responds to FS default controls. When programming add-ons I'm afraid you must do your own research and work things out yourself. I think most PMDG controls have to be by assigned keystrokes, or maybe mouse macros, but seldom by FS controls, especially for the A/P. I'm afraid I am really not able to obtain every single add-on there is and do all this for everyone. You have what is called a "Do It Yourself" kit. In this case, though, I think you might be in luck because others have got there before you and worked some stuff out. Please check the J41 threads in the User Contributions sub-Forum. Of course, if you mean "knob" not "knobs", as there is only one. You need to understand, though, that the knob and buttons change function depending on the little mini-joystick selector. Those changes are built into the device. Regards Pete

What is it about it you don't understand? You just place a very short text file, with the name "SimConnect.INI", into your "My Documents\Flight simulator X Files" folder, with lines in it, as illustrated, telling SimConnect what to do. The ONLY line which you normally need to change is the one starting "File=". You just set that equal to the pathname of the Log file you want. If you put File=C:\MYLOG.TXT it will save the SimConnect log to your main C: disk root folder, and name it "MYLOG.TXT". What could be simpler? [LATER] I've just had a look at the FAQ post and I see this damned new Forum software has messed up the file, making, in particular, the "File=" line in the example INI file all wrong. That makes the sentence about "" also all wrong. Sorry. These threads and posts were transferred by SimFlight en bulk to this new software and it seems much of the erstwhile intelligent formatting has gone completely belly-up. I've adjusted that particular post to read better, after some trial and error. Pete

Right. That's the normal way -- it'll have replaced the FSX Traffic BGL files with its own. There;ll be no program involved in its running, only the normal FSX mechanisms. Right. That's the program which generates those BGLs so that the traffic matches the scenery you actually have installed. Yes, part of the same process really. Everything you say so far is similar to the other traffic packages -- I use 'MyTrafficX' which is similar. But TCC isn't running when you are running FSX, right? So how is the problem so persistent? Surely you are re-running TCC every time you run FSX? There's really not enough difference between the two operating systems to affect any of this. Maybe something else in the way the system is set up, but not the operating system itself. It really doesn't explain what is going on in SimConnect which causes all those problems shown in the FSUIPC log file. This is why I realy do need a SimConnect log. You've got the SimConnect INI file completely wrong then. Why not simply use the one from the FAQ I pointed you to, and change the path to point to wherever you want the log to go to? It doesn't have to go to the Modules folder if that's too complicated for you to work out. If it said C:\SimConnect%01u.log then it would just go to the root of the C: drive. Put it where you like. To produce a console log (which is no use to you) you must have the Console parameter wrong. Here's a typical SimConnect INI file: [SimConnect] level=Verbose console=No OutputDebugString=No file=D:\FSX\Modules\SimConnect%01u.Log file_max_index=9 See where it says "Console=No"? DON'T CHANGE THAT TO A YES! Where it says File=.... just set that to any piace you want. It doesn't matter as long as YOU can find it afterwards! I just happen to like keeping Logs together, so mine goes to the FSX Modules folder -- my FSX is in the folder D:\FSX., so it's easy. There's nothing complicated about that file. It's just a list of parameters telling SimConnect what to do! Just use the parameters as listed for you! Pete

It isn't a log. It's the file which tells SimConnect what modules to load. Apart from FSUIPC4 the only thing it's loading is VistaMare\ViMaCoreX.dll, which is okay. How is your TrafficX thing loaded? Is it an external program, and EXE? I thought the only Traffic program which injected FSX traffic "on the fly" was Ultimate Traffic. Most traffic programs produce compiled BGL files and don't run anything when FSX is running. Isn't TrafficX like that? Regards Pete