Andrew Kewley Posted February 1, 2014 Report Share Posted February 1, 2014 ok, having had it running, I closed FSX but when I restarted, wideserver within FSUIPC doesn't seem to initialising. Wideclient is trying to find something but fails and stays at the "waiting for connection" stage. I've tried running the FSUIPC installer again checking that the reg keys are ok and it says everything is fine. The only log is from wideclient - there is no log created in the modules folder of FSX. FSX had been running for just under 20 minutes when I closed and obtained the log from wideclient. ********* WideClient Log [version 6.999b] Class=FS98MAIN *********Date (dmy): 01/02/14, Time 22:19:10.705: Client name is FLIGHTSIM 141 LUA: "C:\Users\Andy\Documents\WideFS\Initial.LUA": not found 141 Attempting to connect now 141 Trying TCP/IP host "AlpinePC" port 8002 ... 141 ... Okay, IP Address = 192.168.0.80 21169 Error on client pre-Connection Select() [Error=10060] Connection timed out 21169 Ready to try connection again 22230 Attempting to connect now 66347 Trying TCP/IP host "AlpinePC" port 8002 ... 66347 ... Okay, IP Address = 192.168.0.80 132554 Trying TCP/IP host "AlpinePC" port 8002 ... 132554 ... Okay, IP Address = 192.168.0.80 198823 Trying TCP/IP host "AlpinePC" port 8002 ... 198823 ... Okay, IP Address = 192.168.0.80 265093 Trying TCP/IP host "AlpinePC" port 8002 ... 265093 ... Okay, IP Address = 192.168.0.80 331362 Trying TCP/IP host "AlpinePC" port 8002 ... 331362 ... Okay, IP Address = 192.168.0.80 397631 Trying TCP/IP host "AlpinePC" port 8002 ... 397631 ... Okay, IP Address = 192.168.0.80 463838 Trying TCP/IP host "AlpinePC" port 8002 ... 463838 ... Okay, IP Address = 192.168.0.80 530076 Trying TCP/IP host "AlpinePC" port 8002 ... 530076 ... Okay, IP Address = 192.168.0.80 596283 Trying TCP/IP host "AlpinePC" port 8002 ... 596283 ... Okay, IP Address = 192.168.0.80 662552 Trying TCP/IP host "AlpinePC" port 8002 ... 662552 ... Okay, IP Address = 192.168.0.80 728759 Trying TCP/IP host "AlpinePC" port 8002 ... 728759 ... Okay, IP Address = 192.168.0.80 795028 Trying TCP/IP host "AlpinePC" port 8002 ... 795028 ... Okay, IP Address = 192.168.0.80 861297 Trying TCP/IP host "AlpinePC" port 8002 ... 861297 ... Okay, IP Address = 192.168.0.80 883371 ****** End of session performance summary ****** 883371 Total time connected = 0 seconds 883371 Reception maximum: 0 frames/sec, 0 bytes/sec 883371 Transmission maximum: 0 frames/sec, 0 bytes/sec 883371 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 883371 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2014 Report Share Posted February 2, 2014 ok, having had it running, I closed FSX but when I restarted, wideserver within FSUIPC doesn't seem to initialising. Wideclient is trying to find something but fails and stays at the "waiting for connection" stage. I've tried running the FSUIPC installer again checking that the reg keys are ok and it says everything is fine. The only log is from wideclient - there is no log created in the modules folder of FSX. FSX had been running for just under 20 minutes when I closed and obtained the log from wideclient. If there's no log produced by FSUIPC4 then it isn't running. If there's an FSUIPC4 log, but no WideServer log then FSUIPC is running, but WideServer is disabled. Please clarify. Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 There is an FSUIPC log as below. According to the main screen for FSUIPC, widefs is enabled - this is confirmed in the fsuipc.ini ********* FSUIPC4, Version 4.928 by Pete Dowson *********Running inside FSX on Windows 7Module base=6CD90000User Name="Andy Kewley"User Addr="knight_iom@yahoo.co.uk"FSUIPC4 Key is providedWideFS7 Key is provided 0 System time = 01/02/2014 23:15:35 15 FLT UNC path = "\\ALPINEPC\Users\Owner\Documents\Flight Simulator X Files\" 31 Trying to connect to SimConnect Acc/SP2 Oct07 ... 31 FS UNC path = "\\ALPINEPC\Alpine_C\FSX\" 171 LogOptions=00000000 00000001 171 SIM1 Frictions access gained 171 Wind smoothing fix is fully installed 171 G3D.DLL fix attempt installed ok 171 SimConnect_Open succeeded: waiting to check version okay 171 Trying to use SimConnect Acc/SP2 Oct07 3229 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3229 Initialising SimConnect data requests now 3229 FSUIPC Menu entry added 3244 \\ALPINEPC\Users\Owner\Documents\Flight Simulator X Files\default.FLT 3244 \\ALPINEPC\Alpine_C\FSX\SimObjects\Airplanes\Airbus_A321\Airbus_A321.AIR 57486 Sim stopped: average frame rate for last 37 secs = 35.7 fps 61854 System time = 01/02/2014 23:16:37 61854 *** FSUIPC log file being closedAverage frame rate for running time of 37 secs = 35.7 fpsG3D fix: Passes 13091, Null pointers 0, Bad pointers 0, Separate instances 0Memory managed: 4 Allocs, 4 Freed********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2014 Report Share Posted February 2, 2014 There is an FSUIPC log as below. According to the main screen for FSUIPC, widefs is enabled - this is confirmed in the fsuipc.ini Okay, I see you closed FS around 50 seconds after it loaded its default flight. Why? What was on the screen then? The thing is, FSUIPC doesn't think you are ready to fly yet and so hasn't started any of its additional services. When it does that is will have these entries in the log: (this is just an example from my system. Note that this is a full 3 minutes after starting, 2mins20secs after it loaded the default flight): 182022 Aircraft="Boeing 737-800 Paint2" 182068 System time = 31/01/2014 15:03:40, Simulator time = 15:01:20 (15:01Z) 184096 Starting everything now ... Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 Hi Pete, I've just the sim running for about 20 mins (it's still running now) and this is the log from FSUIPC: ********* FSUIPC4, Version 4.928 by Pete Dowson *********Running inside FSX on Windows 7Module base=6C770000User Name="Andy Kewley"User Addr="knight_iom@yahoo.co.uk"FSUIPC4 Key is providedWideFS7 Key is provided 15 System time = 02/02/2014 10:08:18 15 FLT UNC path = "\\ALPINEPC\Users\Owner\Documents\Flight Simulator X Files\" 47 Trying to connect to SimConnect Acc/SP2 Oct07 ... 62 FS UNC path = "\\ALPINEPC\Alpine_C\FSX\" 187 LogOptions=00000000 00000001 187 SIM1 Frictions access gained 203 Wind smoothing fix is fully installed 203 G3D.DLL fix attempt installed ok 203 SimConnect_Open succeeded: waiting to check version okay 203 Trying to use SimConnect Acc/SP2 Oct07 3681 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3681 Initialising SimConnect data requests now 3681 FSUIPC Menu entry added 3713 \\ALPINEPC\Users\Owner\Documents\Flight Simulator X Files\default.FLT 3713 \\ALPINEPC\Alpine_C\FSX\SimObjects\Airplanes\Airbus_A321\Airbus_A321.AIR 716934 Sim stopped: average frame rate for last 693 secs = 35.2 fps 923775 Sim stopped: average frame rate for last 200 secs = 34.7 fps There is no widerserver log being created in the FSX modules folder. However, the wideserver entry in the FSUIPC ini file shows: [WideServer]WideFSenabled=YesAdvertiseService=1Port=8002Port2=9002 The wideclient log is showing: ********* WideClient Log [version 6.999b] Class=FS98MAIN *********Date (dmy): 02/02/14, Time 10:13:46.866: Client name is FLIGHTSIM 218 LUA: "C:\Users\Andy\Documents\WideFS\Initial.LUA": not found 218 Attempting to connect now 312 Trying TCP/IP host "AlpinePC" port 8002 ... 312 ... Okay, IP Address = 192.168.0.80 21325 Error on client pre-Connection Select() [Error=10060] Connection timed out 21325 Ready to try connection again 22370 Attempting to connect now 66472 Trying TCP/IP host "AlpinePC" port 8002 ... 66472 ... Okay, IP Address = 192.168.0.80 132710 Trying TCP/IP host "AlpinePC" port 8002 ... 132710 ... Okay, IP Address = 192.168.0.80 198808 Trying TCP/IP host "AlpinePC" port 8002 ... 198808 ... Okay, IP Address = 192.168.0.80 265014 Trying TCP/IP host "AlpinePC" port 8002 ... 265014 ... Okay, IP Address = 192.168.0.80 331284 Trying TCP/IP host "AlpinePC" port 8002 ... 331284 ... Okay, IP Address = 192.168.0.80 397553 Trying TCP/IP host "AlpinePC" port 8002 ... 397553 ... Okay, IP Address = 192.168.0.80 463760 Trying TCP/IP host "AlpinePC" port 8002 ... 463760 ... Okay, IP Address = 192.168.0.80 529967 Trying TCP/IP host "AlpinePC" port 8002 ... 529967 ... Okay, IP Address = 192.168.0.80 596236 Trying TCP/IP host "AlpinePC" port 8002 ... 596236 ... Okay, IP Address = 192.168.0.80 662505 Trying TCP/IP host "AlpinePC" port 8002 ... 662505 ... Okay, IP Address = 192.168.0.80 728774 Trying TCP/IP host "AlpinePC" port 8002 ... 728774 ... Okay, IP Address = 192.168.0.80 794965 Trying TCP/IP host "AlpinePC" port 8002 ... 794965 ... Okay, IP Address = 192.168.0.80 861125 Trying TCP/IP host "AlpinePC" port 8002 ... 861125 ... Okay, IP Address = 192.168.0.80 927332 Trying TCP/IP host "AlpinePC" port 8002 ... 927332 ... Okay, IP Address = 192.168.0.80 993477 Trying TCP/IP host "AlpinePC" port 8002 ... 993477 ... Okay, IP Address = 192.168.0.80 1059746 Trying TCP/IP host "AlpinePC" port 8002 ... 1059746 ... Okay, IP Address = 192.168.0.80 1125953 Trying TCP/IP host "AlpinePC" port 8002 ... 1125953 ... Okay, IP Address = 192.168.0.80 1192222 Trying TCP/IP host "AlpinePC" port 8002 ... 1192222 ... Okay, IP Address = 192.168.0.80 1258491 Trying TCP/IP host "AlpinePC" port 8002 ... 1258491 ... Okay, IP Address = 192.168.0.80 1324667 Trying TCP/IP host "AlpinePC" port 8002 ... 1324667 ... Okay, IP Address = 192.168.0.80 1390827 Trying TCP/IP host "AlpinePC" port 8002 ... 1390827 ... Okay, IP Address = 192.168.0.80 1457080 Trying TCP/IP host "AlpinePC" port 8002 ... 1457080 ... Okay, IP Address = 192.168.0.80 1523287 Trying TCP/IP host "AlpinePC" port 8002 ... 1523287 ... Okay, IP Address = 192.168.0.80 1589494 Trying TCP/IP host "AlpinePC" port 8002 ... 1589494 ... Okay, IP Address = 192.168.0.80 1655701 Trying TCP/IP host "AlpinePC" port 8002 ... 1655701 ... Okay, IP Address = 192.168.0.80 1721908 Trying TCP/IP host "AlpinePC" port 8002 ... 1721908 ... Okay, IP Address = 192.168.0.80 1788083 Trying TCP/IP host "AlpinePC" port 8002 ... 1788083 ... Okay, IP Address = 192.168.0.80 1854228 Trying TCP/IP host "AlpinePC" port 8002 ... 1854228 ... Okay, IP Address = 192.168.0.80 1920388 Trying TCP/IP host "AlpinePC" port 8002 ... 1920388 ... Okay, IP Address = 192.168.0.80 1986595 Trying TCP/IP host "AlpinePC" port 8002 ... 1986595 ... Okay, IP Address = 192.168.0.80 2052801 Trying TCP/IP host "AlpinePC" port 8002 ... 2052801 ... Okay, IP Address = 192.168.0.80 2118962 Trying TCP/IP host "AlpinePC" port 8002 ... 2118962 ... Okay, IP Address = 192.168.0.80 2185153 Trying TCP/IP host "AlpinePC" port 8002 ... 2185153 ... Okay, IP Address = 192.168.0.80 2251375 Trying TCP/IP host "AlpinePC" port 8002 ... 2251375 ... Okay, IP Address = 192.168.0.80 2317629 Trying TCP/IP host "AlpinePC" port 8002 ... 2317629 ... Okay, IP Address = 192.168.0.80 2383726 Trying TCP/IP host "AlpinePC" port 8002 ... 2383726 ... Okay, IP Address = 192.168.0.80 2449902 Trying TCP/IP host "AlpinePC" port 8002 ... 2449902 ... Okay, IP Address = 192.168.0.80 2516093 Trying TCP/IP host "AlpinePC" port 8002 ... 2516093 ... Okay, IP Address = 192.168.0.80 2582269 Trying TCP/IP host "AlpinePC" port 8002 ... 2582269 ... Okay, IP Address = 192.168.0.80 2648476 Trying TCP/IP host "AlpinePC" port 8002 ... 2648476 ... Okay, IP Address = 192.168.0.80 2714745 Trying TCP/IP host "AlpinePC" port 8002 ... 2714745 ... Okay, IP Address = 192.168.0.80 2781014 Trying TCP/IP host "AlpinePC" port 8002 ... 2781014 ... Okay, IP Address = 192.168.0.80 2847299 Trying TCP/IP host "AlpinePC" port 8002 ... 2847299 ... Okay, IP Address = 192.168.0.80 2913568 Trying TCP/IP host "AlpinePC" port 8002 ... 2913568 ... Okay, IP Address = 192.168.0.80 2979806 Trying TCP/IP host "AlpinePC" port 8002 ... 2979806 ... Okay, IP Address = 192.168.0.80 3046029 Trying TCP/IP host "AlpinePC" port 8002 ... 3046029 ... Okay, IP Address = 192.168.0.80 3112235 Trying TCP/IP host "AlpinePC" port 8002 ... 3112235 ... Okay, IP Address = 192.168.0.80 3178489 Trying TCP/IP host "AlpinePC" port 8002 ... 3178489 ... Okay, IP Address = 192.168.0.80 3244696 Trying TCP/IP host "AlpinePC" port 8002 ... 3244696 ... Okay, IP Address = 192.168.0.80 3310965 Trying TCP/IP host "AlpinePC" port 8002 ... 3310965 ... Okay, IP Address = 192.168.0.80 3377110 Trying TCP/IP host "AlpinePC" port 8002 ... 3377110 ... Okay, IP Address = 192.168.0.80 3443316 Trying TCP/IP host "AlpinePC" port 8002 ... 3443316 ... Okay, IP Address = 192.168.0.80 3509586 Trying TCP/IP host "AlpinePC" port 8002 ... 3509586 ... Okay, IP Address = 192.168.0.80 3575777 Trying TCP/IP host "AlpinePC" port 8002 ... 3575777 ... Okay, IP Address = 192.168.0.80 3641999 Trying TCP/IP host "AlpinePC" port 8002 ... 3641999 ... Okay, IP Address = 192.168.0.80 3708206 Trying TCP/IP host "AlpinePC" port 8002 ... 3708206 ... Okay, IP Address = 192.168.0.80 I don't know if it's relevant but in the FSX window, the title doesn't show "waiting for client" as I would have expected it to. For the sake of reference: Both PC's are on the same workgroup which. All the ports, and specifically 8002 and 9002, are allowed through the firewall in both in and out configuration. Drives are mapped and have full read/write access. I have no reason to believe that any of that is relevant as the problem seems to be that FSUIPC isn't starting wideserver but having read through a number of other posts, you do ask to confirm that the network setup is correct. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2014 Report Share Posted February 2, 2014 Hi Pete, I've just the sim running for about 20 mins (it's still running now) and this is the log from FSUIPC: Well something is preventing FSUIPC from sensing that the sim is ready to fly. It isn't receiving the aircraft name from Simconnect to start with. The only time I've seen this before was with P3D v1.0 when it was started with the SIM in PAIUSED mode. I don't know if it's relevant but in the FSX window, the title doesn't show "waiting for client" as I would have expected it to. That's because FSUIPC has started anything yet. It is waiting for something which isn't happening, as I say. Several things to try to get more data: 1. If the SIM is paused, unpause it and see if that helps. Then make sure your startup flight doesn't have it paused. 2. Go into FS's Flight menu and select a different flight and/or aircraft. See if that makes it start. 3. In case it's some problem with the default flight or default aircraft, try changing it. Rename or delete the flight: \\ALPINEPC\Users\Owner\Documents\Flight Simulator X Files\default.FLT Let me know the results. Just look in the log to see if you get a "Starting everything now" message. No need to keep posting more logs until I ask. Regards Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 I'd love to know why / how that made a difference but yep, changing the a/c and/or default flight did the trick... connected within seconds!! cheers, Pete! :) Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2014 Report Share Posted February 2, 2014 I'd love to know why / how that made a difference but yep, changing the a/c and/or default flight did the trick... connected within seconds!! cheers, Pete! :) Perhaps if you've still got the original flight file I could try it here. Of course it may well be inter-related to other settings, but, you never know. Regards Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 I don't unfortunately but the flight was saved as "default" with the default flight checked. The aircraft was the FSX default A321 in a cold and dark state at EGBB, gate 1 (Gary Summons FSX scenery). Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 ok, perhaps not... just started FSX and the same problem is back. I've deleted all the saved flights and changed aircraft, airports.. wideserver isn't starting up. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2014 Report Share Posted February 2, 2014 ok, perhaps not... just started FSX and the same problem is back. I've deleted all the saved flights and changed aircraft, airports.. wideserver isn't starting up. There's something very odd going on ... FSUIPC needs to see certain essential messages from Simconnect before it decides the SIM is set to fly. It seems one or other of those isn't getting sent. That's worrying as it suggests a Simconnect installation error. There is some logging you can enable which may point to what is missing. Please add these lines to the [General] section of the FSUIPC4.INI file: Debug=Please TestOptions=x800 Then run FSX, till you are sure it isn't working correctly. close down and show me the whole of the Log file. Regards Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 Vatsim is connected ok via simconnect so why FSUIPC is having a problem with it but here's the log: ********* FSUIPC4, Version 4.928 by Pete Dowson *********Running inside FSX on Windows 7Module base=6C770000User Name="Andy Kewley"User Addr="knight_iom@yahoo.co.uk"FSUIPC4 Key is providedWideFS7 Key is provided 390 System time = 02/02/2014 18:31:38 390 FLT UNC path = "\\ALPINEPC\Users\Owner\Documents\Flight Simulator X Files\" 421 Trying to connect to SimConnect Acc/SP2 Oct07 ... 421 FS UNC path = "\\ALPINEPC\Alpine_C\FSX\" 546 LogOptions=00000800 00000001 562 SIM1 Frictions access gained 562 Wind smoothing fix is fully installed 562 G3D.DLL fix attempt installed ok 562 SimConnect_Open succeeded: waiting to check version okay 562 Trying to use SimConnect Acc/SP2 Oct07 3494 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3494 Initialising SimConnect data requests now 3494 FSUIPC Menu entry added 3510 ## EV_SIM=stop 3510 \\ALPINEPC\Users\owner\documents\flight simulator x files\Startup Flight.FLT 3526 \\ALPINEPC\Alpine_C\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR 3526 ##: ST_SIM=stop 20592 ## EV_START 20592 ## EV_SIM=start 33556 ##: ST_SIM=start 36099 ##: ST_SIM=start 38688 ##: ST_SIM=start 41216 ##: ST_SIM=start 43758 ##: ST_SIM=start 46270 ##: ST_SIM=start 48797 ##: ST_SIM=start 51324 ##: ST_SIM=start 53867 ##: ST_SIM=start 56426 ##: ST_SIM=start 58937 ##: ST_SIM=start 61449 ##: ST_SIM=start 63992 ##: ST_SIM=start 66581 ##: ST_SIM=start 69108 ##: ST_SIM=start 71698 ##: ST_SIM=start 74257 ##: ST_SIM=start 76784 ##: ST_SIM=start 79358 ##: ST_SIM=start 81901 ##: ST_SIM=start 84475 ##: ST_SIM=start 87017 ##: ST_SIM=start 89576 ##: ST_SIM=start 92165 ##: ST_SIM=start 94724 ##: ST_SIM=start 97282 ##: ST_SIM=start 99825 ##: ST_SIM=start 102368 ##: ST_SIM=start 104895 ##: ST_SIM=start 105784 ## EV_STOP 105784 Sim stopped: average frame rate for last 85 secs = 24.5 fps 105784 ## EV_SIM=stop 107422 ##: ST_SIM=stop 109981 ##: ST_SIM=stop 111276 ## EV_START 111276 ## EV_SIM=start 112508 ##: ST_SIM=start 115051 ##: ST_SIM=start 117609 ##: ST_SIM=start 120121 ##: ST_SIM=start 122648 ##: ST_SIM=start 125160 ##: ST_SIM=start 127734 ##: ST_SIM=start 130308 ##: ST_SIM=start 132866 ##: ST_SIM=start 135393 ##: ST_SIM=start 137936 ##: ST_SIM=start 140448 ##: ST_SIM=start 143006 ##: ST_SIM=start 145518 ##: ST_SIM=start 148045 ##: ST_SIM=start 150572 ##: ST_SIM=start 153131 ##: ST_SIM=start 155673 ##: ST_SIM=start 158216 ##: ST_SIM=start 160728 ##: ST_SIM=start 163240 ##: ST_SIM=start 165782 ##: ST_SIM=start 168325 ##: ST_SIM=start 170837 ##: ST_SIM=start 173380 ##: ST_SIM=start 175907 ##: ST_SIM=start 178465 ##: ST_SIM=start 181008 ##: ST_SIM=start 183582 ##: ST_SIM=start 186125 ##: ST_SIM=start 188668 ##: ST_SIM=start 191179 ##: ST_SIM=start 193722 ##: ST_SIM=start Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 2, 2014 Report Share Posted February 2, 2014 Vatsim is connected ok via simconnect so why FSUIPC is having a problem with it FSUIPC is "connecting" to Simconnect too. It simply isn't receiving the information is is requesting. Here, this part of the Log shows the connection AND the menu entry being added: 562 SimConnect_Open succeeded: waiting to check version okay 562 Trying to use SimConnect Acc/SP2 Oct07 3494 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3494 Initialising SimConnect data requests now 3494 FSUIPC Menu entry added It also receives START and STOP messages from Simconnect, as shown in your log. But it needs a lot more -- a LOT more! The main thing it isn't getting, which is illustrated by the log messages which AREN'T present, is the One Second timer calls. It is these which tells it SimConnect is actually alive, and it is on these which it depends to start everything up. The ONLY event FSUIPC is receiving from SimConnect is the "Start" / "Stop" one. There's no point in WideServer being started because there's no information FSUIPC can supply to it, and nothing it can do. Literally. Something is badly wrong. And FSUIPC is logging EVERYTHING it sees which might be relevant to this, and it isn't seeing anything, so there's no clue. In case it's all down to some sort of start-up interaction with other add-ons, you could try delaying FSUIPC's startup. The INI parameter InitDelay controls that. You can set a delay in seconds (0 to 120). There's also one other internal logging option which might just reveal more, but i'm not optimistic. It involves adding the line LogExtras=x400 to the two you already added. The log might be pretty big though -- unless really nothing is happening. Also, as a last resort you could try getting a SimConnect log file. There are instructions for this in the FAQ subforum. These logs may well be far too large to paste here, so ZIP them and send it to me at petedowson@btconnect.com. I'll certainly take a look, but quite honestly I'm not hopeful. Something is messed up in your FS installation, or there is some really severe interaction with other add-ons. (In fact, maybe that's another step which can be taken -- eliminate other add-ons one by one. The fact that you did get a success once does perhaps indicate some sort of interaction going o). Note that I've never seen anything like these symptoms before. In the few other cases of things not starting the logging you have now enabled point to a specific single cause, like the Aircraft name not being received (turned out to be a corrupt AIRCRAFT.CFG file). But in your case there simply appears to be nothing happening. Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 This is a clean install on a brand new machine. The only thing, other than your software, is the FSX version of UK2000 which was installed at point of manufacture less then a week ago. I've tried deleting the fsx.cfg and allowing it rebuild.. that worked once then it failed again. Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 Log file sent to your email address. Just for the sake of checking, I've just run squawkbox across simconnect and it joined up to FSX without a problem. Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 2, 2014 Author Report Share Posted February 2, 2014 Incidentally, and this may be totally irrelevant, but FSUIPC is creating a default flight called "previous flight". I've not, to the best of my knowledge, asked it to do that so wondered if it might be somehow holding onto settings that is preventing a clean startup of the wideserver component? Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 3, 2014 Report Share Posted February 3, 2014 Incidentally, and this may be totally irrelevant, but FSUIPC is creating a default flight called "previous flight". I've not, to the best of my knowledge, asked it to do that so wondered if it might be somehow holding onto settings that is preventing a clean startup of the wideserver component? No. The Previous Flight production is in lieu of FSX doing it -- FS9 used to do it and a lot of folks like to set this as their default flight so they start up next time where they left off. It cannot do any harm -- it is saved on close down and would only be reloaded if you set it to be the default or if you loaded is explicitly. Log file sent to your email address. That's no use. I can't get that message with such an attachment, and it is way too big in any case. I did ask you to ZIP it. A ZIPPED text file is much much much smaller and is accepted okay. Just for the sake of checking, I've just run squawkbox across simconnect and it joined up to FSX without a problem. And FSUIPC connects as well. It is simply that it isn't getting the messages it needs. As I said already. Did you bother trying the IniDelay as I suggested? Dd you get a SimConnect log as I suggested? Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 3, 2014 Author Report Share Posted February 3, 2014 Hi Pete, Have resent the file zipped as requested. I did take on board what you said about simconnect, i'm just trying to give you as much information as I can so you can offer a solution that will allow me to use your software. Another thing that might be worth mentioning is that somebody suggested letting fsx rebuild the fsx.cfg file. I did this and wideserver fired up the first time but on closing and restarting it didn't. Could it be something in the fsx.cfg that is causing the problem? Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 3, 2014 Report Share Posted February 3, 2014 Have resent the file zipped as requested. Right. One contributory factor is that FSUIPC seeing lots of changing axis values from one of your devices. Immediately it enables the direct input scanning it receives the initial values from each of 10 joystick axes: 1794 ###JOY### Event seen, ID=65820 (0x0001011C), Joy=8, value=-7226 1794 ###JOY### Event seen, ID=65821 (0x0001011D), Joy=9, value=-11483 1794 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10064 1794 ###JOY### Event seen, ID=65823 (0x0001011F), Joy=11, value=-10709 1794 ###JOY### Event seen, ID=66292 (0x000102F4), Joy=5, value=-10709 1794 ###JOY### Event seen, ID=65763 (0x000100E3), Joy=0, value=0 1794 ###JOY### Event seen, ID=65762 (0x000100E2), Joy=1, value=0 1794 ###JOY### Event seen, ID=65720 (0x000100B8), Joy=6, value=7040 1794 ###JOY### Event seen, ID=65721 (0x000100B9), Joy=7, value=7040 1794 ###JOY### Event seen, ID=65764 (0x000100E4), Joy=2, value=0 Now those are fine -- that just "sets the scene" for latter scanning when things might be changing, but axis #10 is constantly changing. For example: 435742 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10193 435805 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10064 436039 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10193 436086 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10064 436413 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10193 436538 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10064 436803 ###JOY### Event seen, ID=65822 (0x0001011E), Joy=10, value=-10193 That's the axis assigned to "throttle 3 set". It's wobbling between two values constantly. Not a real problem, just a performance irritation. Now I'm not saying that this is the cause of the failure of FSUIPC to start everything, but it might be a good idea to temporarily disconnect whatever device that is and re-test. When we do get things sorted it will be worth doing a proper calibration on that device to find a stabile non-jitter setting, at idle presumably. Looking at the other problem shown up in the log ... these errors from SimConnect: 44741 Exception 12 "TOO_MANY_REQUESTS", Ref 3377, Index param -1 on unknown request! 44741 Exception 12 "TOO_MANY_REQUESTS", Ref 3378, Index param -1 on RequestDataOnSimObject for AI Aircraft id=2728 [0x00AA8] These occur at a ridiculously high rate. It's as if SimConnect is completely overloaded. I've not seen anything like that before. I've seen the odd occasional such failure, and it usually occurs when many SimConnect clients are clamouring for attention at the same time. So, I repeat my previous requests / suggestions: 1. Get a SimConnect log 2. Try the InitDelay The former would be most educational as it will show ALL of the requests made to SimConnect from every add-on running. Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 3, 2014 Author Report Share Posted February 3, 2014 As per email (and more for the benefit of anyone else trying to read this thread for continuity purposes) I added the 30s delay, recalibrated the throttle commands and rebooted the pc. It has since started the wideserver element 3 times on the trot. Pete: you should have the email with the simconnect log... as stated in the email, your thoughts on it would be handy - especially if I need to edit something :) Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 3, 2014 Report Share Posted February 3, 2014 Pete: you should have the email with the simconnect log... as stated in the email, your thoughts on it would be handy - especially if I need to edit something :) Please clarify, was this log from AFTER you'd applied the "InitDelay=30" change? It looks like it. Anyway, it's as I thought -- SimConnect is being swamped during startup. And in fact one of your Squawkbox modules is getting lots and lots of errors repeating throughout. I'm surprised you don't report a problem with that. Here's the timing during the startup as logged (the number on the left is the elapsed time in seconds): > 4.06666 [255, 1]Open: Version=0x00000002 Name="SquawkBox AI Control" > 4.06674 [128, 1]Open: Version=0x00000004 Name="PMDG_Options" > 4.06675 [129, 1]Open: Version=0x00000004 Name="PMDG_Events" > 4.06676 [130, 1]Open: Version=0x00000004 Name="PMDG_Sounds That's 4 SimConnect clients connecting almost at the same time. The SB AI control module gets some errors, the first being almost immediate: > 4.31907 [255, 5]RequestClientData:ClientDataID=0, RequestID=0, DefineID=0, dwReserved1=-1, dwReserved2=0 < 4.31910 [255] >>>>> EXCEPTION=25, SendID=5, Index=-1 <<<<< Exception 25 is ILLEGAL OPERATION! What is it doing sending lots of illegal operations? Another part of SB then connects and gets an error immediately: > 4.39201 [254, 1]Open: Version=0x00000002 Name="SquawkBox_Transponder" > 4.39223 [254, 15]SetClientData:ClientDataID=0, DefineID=2, Flags=0, dwReserved=1, cbUnitSize=1, pDataSet=200988708 < 4.39224 [254] >>>>> EXCEPTION=31, SendID=15, Index=5 <<<<< Exception 31 is OUT OF BOUNDS Before FSUIPC connects there are another 115 or so more of the ILLEGAL OPERATION errors, mostly then from that Transponder module, Then FSUIPC connects after 32 elapsed seconds: > 32.68946 [131, 1]Open: Version=0x00000004 Name="FSUIPC4" Then the ILLEGAL OPERATIONS by SB continue .... another 30+ before FSUIPC gets a look in. Once FSUIPC starts its requests then of course there are many. The log continues with occasional spurts of SB errors, and lots and lots of AI traffic reads by FSUIPC -- you are at a busy airport for AI by the look of it! But things are otherwise settled by then. Regards Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 3, 2014 Author Report Share Posted February 3, 2014 Yes, Pete. This was after the changes/calibration you suggested. That squawkbox thing is slightly concerning. I followed the installation instructions explicitly - would it be worth removing and reinstalling on the simulator side? The machine running the other side of it & wideclient was actually switched off when I grabbed that log. Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 3, 2014 Report Share Posted February 3, 2014 Yes, Pete. This was after the changes/calibration you suggested. That squawkbox thing is slightly concerning. I followed the installation instructions explicitly - would it be worth removing and reinstalling on the simulator side? I don't really know. Maybe SB has always done this and they've not noticed, or programmed around it somehow. If there's an active support still for SB then it might be worth reporting it and asking the question, but I suspect it's long since been left unsupported? At least I haven't got any responses from the authors for a while. If it seems to work correctly for your purposes then I'd leave it. It may not harm performance once it's settled down. Pete Link to comment Share on other sites More sharing options...
Andrew Kewley Posted February 3, 2014 Author Report Share Posted February 3, 2014 The website does say that there is no further support for SB. I think that old adage of "if it works, leave it alone" could well apply! Thanks for your help :) Link to comment Share on other sites More sharing options...
srcooke Posted February 3, 2014 Report Share Posted February 3, 2014 As a SB user of many years I noticed this with interest so ran a check myself. Both the AI & Transponder modules are producing the same multiple errors. I would add that these errors are logged after the FSUIPC connection at > 3.26100 [74, 1]Open: Version=0x00000004 Name="FSUIPC4". The first error 25 at < 10.46126 [190] >>>>> EXCEPTION=25 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