ibsicus

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

1 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Profile Information

  • Gender
    Male
  1. Hello everyone, After some rough days iv'e finally fixed the problem, with the help of the tech support at Hifi Tech Inc. They sent me a beta update for an upcoming fix, which seemingly fixed the problem permanently. The only catch to it is that you need to run FSX FIRST and not ASN. So everything is fixed and I am a happy pilot haha. Look out for the upcoming patch fixing this. Regards Francesco
  2. Hi again, Just wanted to add my simconnect log file from my FSX server pc. 0.00000 SimConnect version 10.0.61259.0 0.00197 Server: Scope=local, Protocol=Auto, Address=::1, Port=49861, MaxClients=64 0.00377 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.00454 Server: Scope=local, Protocol=IPv6, Address=::1, Port=49862, MaxClients=64 0.00533 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=49863, MaxClients=64 As you can see there is some strange behavior, each time I restart FSX it generates a new port to be used, despite the fact that I specifically choosed port 500 to be used in my .xml config file. So in a way or another FSX is not using the port I am specifying it to use. Another thing I noticed using CurrPorts program. When starting FSX the first time, the FSX.exe uses port 500, but once i restart FSX it will use a different port, like shown in the simconnect log. Funny thing though is that looking at currport, it looks like the laptop gets connected to port 500 on the server. The connection always gets established. It's somehow FSX which doesnt redirect the system port to itself. If that makes sense in any way... Anyways I will get to the bottom of this. I am here with a friend who is a developer, so hopefully we can sort this out faster since we are more people coming with suggestions.
  3. Okay so I reinstalled ASN again and this time I didnt install any xml file on the client pc, despite the simconnect.cfg file which I know has to reside in the My Documents folder on the client pc. I can now confirm to you, that this does not resolve the problem. The problem remains exactly the same, and the behaviour too. First time launching FSX, ASN connects perfectly. But once you try to relaunch them then they never get connected to each other. Iv'e taken the problem to a higher level at the Hifi Tech support, which I hope they will be able to sort out. As soon as I have a real solution for the problem then I will report back. The same problem is discussed in the Hifi Tech forums started by me. I am still open for suggestions though, more eyes on the problem will only speed up the process in resolving this issue. Regards Francesco
  4. There must be something I've completely misunderstood then. I followed a video on YouTube by Frooglesim and in his video he makes the xml file on the server pc. But he then copies it inside his ASN folder too on the client pc. More specifically in the simconnect files folder which resides inside ASN. But of course I can now see what you mean, if both my client and my server are configured with the xml then it's bound to cause a conflict. I will give it a try without the xml on the client pc and see if that works. Thank you again for the support. Sent from my GT-I9505 using Tapatalk
  5. Hi bedgie, thank you for the reply. Your theory makes a lot of sense, and I've been thinking that it could be a possibility too. Tell me one thing, do you change only the simconnect.xml on your server with FSX or also on the client running ASN? This problem is existing both in W7 and W8 as I know. Sent from my GT-I9505 using Tapatalk
  6. Hello , I am returning back, because apparently my problem is still existing, despite reinstalling ASN outside the Default folder. For some reason I was able to get 3-4 successful connection last time I tried. But today when I am finally ready to fly, I start up FSX first time and ASN works. Great. Then because I had to install some liveries I shut down FSX and ASN. I then installed my livery, and thought let me start up again and this time have this long waited flight. I then fire up ASN first, and then FSX. But unfortunately ASN remains at Waiting for Simulator and nothing ever happens. Unless I ofcourse restart totally my server pc running FSX, but that is annoying to do each time. JSKorna: By opening AI Traffic tool I get the message "Connected to Flight Simulator". But I notice that first time I run FSX and ASN I get similar message but with the addition of "Received 2". Therefor this case is still open for suggestions. Regards Francesco
  7. Getting back to my issue, I tried to run ASN in compability mode W7 but with no success. I then tried to run both FSX and ASN in compability mode W7, but again no success. I then tried to run ASN in compability mode Vista, but still no success. I need to get to the bottom of this problem, because I am sure other users with W8 are having same problem. Therefor I digged into my ASN logs and found both the ASN log and Simconnect log that ASN generates too. Here you have a snippet of the simconnect log, as you can see it looks like there is no apparent connection to the server running simconnect. And this is the ASN log file, which looks like it's working fine connecting to the servers shared folders. I don't know if I mentioned earlier, but I am also running latest FSUIPC and WideFS server paid versions.
  8. Apparently the port does indeed get closed after some time, but turning on ASN and FSX doesnt start up the connection again. In my ASN logs there is a simconnect log that says it cannot connect to simconnect. So there is still no solution to this weird problem...
  9. Okay I did some digging and found something interesting. I noticed that ASE would connect to FSX only the first time i run FSX. Once I shut down FSX and try to rerun it again it won't connect to ASE. But if I then restart my server pc and then start up FSX again then ASE would connect. So I thought it has to be something with the ports to do, that maybe they don't close properly when shutting down fsx. So I tried to run the command netstat both on server and client. Interesting enough when ASE was connected to FSX it would show up as CONNECTION ESTABLISHED. But once I shut down FSX then on the server pc, running netstat it would say TIME_WAIT, and on the client pc, running netstat would give FIN_WAIT_2. Which means that its waiting to get command to close the port, but this eventually never happens, so therefor the port remains in use. So even if i restart FSX the port is still in this "used" state, and the only way to get it out of that state is by restarting totally my pc. I am now investigating if there is a way to manually close down the port connection upon fsx shutdown. Will report back with some news!
  10. There seems to be some problems if using Windows 8 and Simconnect. For some reason I am only able to get ASE to connect once with Simconnect, but it is very random. If I shut down FSX on my "server" machine and ASE on my "client" machine, and then reopen FSX and ASE, then ASE will just be sayin "Waiting for simulator". Sometimes to make it work I need to change the port used and then for some reason it will connect again, but it's never a 100% fix, sometimes it works, and sometimes not. I cannot figure out what the problem is, I would love to hear from some of you experts in here, if you have any problems with simconnect on Windows 8. FYI I am running Windows 8.1 on server side and Windows 8 on client side. Before you all ask for it here are my settings: - SimConnect.xml: (This file is placed on server pc where the fsx.cfg file is present. On my client machine this file is placed in my ASE "Simconnect files" folder. <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <Address>192.168.0.11</Address> <MaxClients>64</MaxClients> <Port>500</Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Scope>local</Scope> </SimConnect.Comm> </SimBase.Document> And SimConnect.cfg: (This file is placed on my client machine ASE "Simconnect files" folder. Furthermore this file is also placed in the Documents folder on client pc. [simConnect] Protocol=IPv4 Address=192.168.0.11 Port=500 MaxReceiveSize=4096 DisableNagle=0 I have another SimConnect.ini file which is on the server pc in Flight Simulator X Files folder. It looks like this: [simConnect] level=verbose console=0 ;RedirectStdOutToConsole=1 ;OutputDebugString=1 ;file=c:\SimConnect%03u.log ;file_next_index=0 ;file_max_index=9 I have both FSUIPC and WideFS server paid versions. And these are the files I am sharing from my server with FSX on. The files are shared with FULL ACCESS to everyone on my local network. - Flight Simulator X Files - %USERS%/AppData/Roaming/Microsoft/FSX/ - My whole FSX SDK Directory - My whole FSX game directory folder. Hope some experts can come with some input. I am especially interested if anyone knows precisely how where simconnect loads from. Does it load from FSUIPC.dll or anywhere else? I am trying myself to troubleshoot where the heck the problem might be, but since the successful connects are so random, I cannot come to any conclusion of what it might be. One last note, I have installed the FSX SDK along with all the updates. On my client PC ive installed Simconnect. The following versions are installed: - 10.0.60905.0 - 10.0.61242.0 - 10.0.61259.0 Regards Francesco