dazzan Posted November 5, 2006 Report Share Posted November 5, 2006 Hi Pete I thought I should report this. I also experienced the problem that the addon menu disappeared. It was working fine until I was setting up IVAP to connect through simconnect. I disabled the loading of IVAP in the dll.xml file. I created a new file named "simconnect.dll" in the folder: C:\Documents and Settings\gilles\Application Data\Microsoft\FSX with the following content: <?xml version="1.0" encoding="Windows-1252"?> SimConnect SimConnect.xml False False IPv4 global 192.168.0.1 6810 After having created and saved that file, I started FSX, the addon menu had disappeared. When I close FSX and I delete that file simconnect.dll and start FSX again, the addon menu is there again. I found no solution for that problem. Many thanks Gilles Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 6, 2006 Report Share Posted November 6, 2006 I created a new file named "simconnect.dll" in the folder: C:\Documents and Settings\gilles\Application Data\Microsoft\FSX with the following content: You shouldn't do that! An XML file has filetype XML, not DLL. The SimConnect DLL is the compiled program part of FSX which loads and runs all SimConnect client programs! This XML file: <?xml version="1.0" encoding="Windows-1252"?> SimConnect SimConnect.xml False False IPv4 global 192.168.0.1 6810 should be called Simconnect.XML, and is only needed if you are running SimConnect client EXE programs on a Networked computer other than the FSX PC. After having created and saved that file, I started FSX, the addon menu had disappeared. When I close FSX and I delete that file simconnect.dlland start FSX again, the addon menu is there again. I found no solution for that problem. Why create the file, then? And odder, why call it SimConnect.dll? If you think you have found a bug in FSX you really need to report it to MS rather than me -- send all the details to tell_fs@microsoft.com. Regards Pete Link to comment Share on other sites More sharing options...
dazzan Posted November 6, 2006 Author Report Share Posted November 6, 2006 I am sorry. Yes, I try to run Ivap on a multi PC setup. And you are right, I have called the file simconnect.xml. Iam sorry for the wrong information I gave you tonight. Was a little bit late tonight Thanks Gilles Link to comment Share on other sites More sharing options...
dazzan Posted November 6, 2006 Author Report Share Posted November 6, 2006 Hi Pete I have send the corrected report also to Microsoft Thanks Gilles Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 6, 2006 Report Share Posted November 6, 2006 And you are right, I have called the file simconnect.xml. Ah .. so the problem you are saying is that if you set SimConnect to operate on multiple PCs on a Network, it either doesn't service any of the local Simconnect client programs, or perhaps just doesn't obey the DLL.XML and EXE.XML instructions to load them? If this is true it is extremely serious and certainly needs attention. I will try some experiments here. Thank you. Regards Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 6, 2006 Report Share Posted November 6, 2006 <?xml version="1.0" encoding="Windows-1252"?> SimConnect SimConnect.xml False False IPv4 global 192.168.0.1 6810 Okay, I've experimented and soon found the problem. I don't think you need report it to MS, except maybe to get it clarified in documentation somewhere. I'm not sure where you got the above content for the XML file from, but as far as I can tell, by including that file you are overriding the default setting for how SimConnect uses TCP/IP protocols in the current (FSX) PC. SimConnect is still loading modules according to DLL.XML and programs according to EXE.DLL, but it cannot communicate with them because you have changed the port and IP address. If I change your file to read: <?xml version="1.0" encoding="Windows-1252"?> SimConnect SimConnect.xml False False IPv4 global 192.168.0.1 6810 False IPv4 local 127.0.0.1 6820 Then everything works again. I'm not sure I need the Port number, and probably the Protocol should be Auto in any case to allow it to use IPv6 if installed, but the critical part is the 127.0.0.1 which universally means "this PC". I also set scope as "local" but, again, I'm not sure how necessary that is. Regards Pete Link to comment Share on other sites More sharing options...
Pack Posted November 6, 2006 Report Share Posted November 6, 2006 Hi: Peter, your post finally solved my problem. I also had the Simconnet.XML file for the Ivap remote operation and that caused that I did not see the add on menu, adding your new lines to the file added the add on option to my menu bar. I´ve tested to connect to the network with Ivap in remote operation and it works fine also. Thanks, Francisco Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now