mwa05

Hi John, I did not read the two messages together. I love HM's English! I read the last message with a new .exe as cancelling the previous post with the first amended .exe and the manual entry requirement so I took no action with regards to a DetectToConnectDelayAuto=240 when uploading and using v741003c. Now that I understand that they went together, I have now added DetectToConnectDelayAuto=105 to v741003c and can confirm it works! I have done several new starts, and it connects consistently. I have run out of night to do a full flight however I think we have progress; I have attached the last log for good measure. Kind regards, Mark FSUIPC7.log

Hi John, Using v741003c, I disabled auto start. So, when MSFS is active and after I press Fly Now and the aircraft is loaded, I then go to FSUIPC which launches but does not connect, and I then select connect now and then launch PF3 and the hotkeys work. That log is attached. Kind regards, Mark FSUIPC7.log

Hi John, I tried v741003c however there is no difference I am afraid. I have enabled buttons and keys, and I started the flight and could not connect, In the game, I then exited FSUIPC and PF3 and restarted both and like the previous versions, the hotkeys then worked, Both the logs are attached this time, the original flight and then the restarted flight where it worked after closing down both. Kind regards, Mark FSUIPC7.log FSUIPC7_prev.log

Hi John, I now understand the information re stopping FSUIPC and restarting (which I did not know) so I will approach it that way next time. When you say I did not activate logging for Buttons and Keys, is that a selectable item somewhere in FSUIPC? Or is it the logging function for Buttons and Keys in PF3 you want to see? When you say no Hotkeys were registered; I don’t know what to do with that statement? I know that, as I could not use them to transmit to ATC. I don’t have any hotkeys mapped by me via FSUIPC, the mapping is done by PF3 when you launch it. That is the function that is not working? Sorry for being a bit thick, I’m just an old bloke trying to get something to work again that has worked for years. Bear with me, I can do some more testing tomorrow night! Thanks, Mark

Hi John, Please find attached log using 7.4.9, which is registered and automatically launches with MSFS. I have found that using the DetectToConnectDelayAuto does not seem to make any difference regardless of =30, =75 or =90 however = 75 in one instance of my testing worked properly on initial launch. What does work consistently, after finding you have no hotkey connection (when you want to call for airways clearance) is quitting FSUIPC and PF3 in game, and re-starting FSUIPC and PF3 and then the hotkeys will connect and operate as normal. So that is the work around, currently. And this log should show me stopping and restarting. Regards, Mark FSUIPC7.log

Hi John, I use Dave’s software (PF3) and did not have the issue in 7.4.8 however I can’t use the Key Press in 7.4.9, which means you can’t initiate contact with ATC. Can I ask what was the DetectToConnectDelayAuto default in 7.4.8? If it is 60 seconds in 7.4.9, a starting point (for me) would be to manually add the entry using the last default value, as that worked, assuming there was a timing change between the two versions. My version is licensed and auto starts with MSFS. Thank you and regards, Mark

Hi Pete, Just a quick report to close this off to finality. I cannot recreate my own issue even by swapping the old ini back in. Something got corrupted on my old PC which found its way into the new build (by copy and paste) but rebuilding the ini on both has fixed the issue on both, but I cannot narrow it down. As I said above, straight out placing the old ini back in (in the old PC) does not bring the critical moment back. Rebuilding the ini seems to have "cleared" it on going (despite putting the original back in to force the issue). If somebody in the future ever comes along and says my AI stops talking on climb and never comes back, just tell them to rebuild the ini to start with... that was the magic key. Now I can't for the life of me, repeat it. I get "Opened separate AI Traffic client okay" all the time. He was always missing in the log pre ini rebuild. Thank you for your kind assistance and patience. Kind regards, Mark

Hi Pete, Definatively, deleting the ini and rebuilding a new one, and resetting everything back up through the interface has solved the problem, as I have also done it on the old retired from simming PC and it is "fixed" now too. Everything works as it should; and works like it never has for at least 6 years on two different installations. I have listed the differences between the ini files below; from reading the manuals regarding each entry I can't see why any of these would stop the client. The old ini value is on the left and the new (default) value is to the right of the /. All other values are the same in both. FixControlAccel=Yes/NoFixMachSpeedBug=Yes/NoNewDeleteVehicleForAES=Yes/NoTurbulenceRate=0.5,2.5 /1.0,5.0TurbulenceDivisor=40,40,80,80/20,20,40,40WindSmoothness=1/2MagicBattery=Yes/NoRudderSpikeRemoval=Yes/NoElevatorSpikeRemoval=Yes/NoAileronSpikeRemoval=Yes/NoTimeForSelect=0/4TimeForLuaClosing=1/2ConsoleWindow=130,130,1123,649/No such entry in new ini[AutoSave]Interval=10/60Files=1/10But not enabled in either[WideServer]WideFSEnabled=No/Yes[Monitor]Only in old ini but nothing underneath it. What I have not done is a one by one elimination (using the old no longer in flight sim service PC) but first, if I get time later today, I may put its old ini back in and see if "it" is back and reverse engineer from there. I would like to get to the bottom of it, but I'm so pleased that everything is now working as it was meant to. I'll let you know how I get on. Kind regards, Mark

Hi Pete, Happy Easter. On the flight back to Sydney yesterday I had several hours to devote thought time to this problem and I also re-read this entire post from beginning to end and the biggest hint came from me. It is possible that I have solved the problem. Last night I completed a successful flight; like I have never had before, using RC4. The clue was "I pretty much replicated my set up from my 2011 PC to my 2016 PC I built last year" and "it happens on that PC as well" (but I was oblivious to the problem until recently) and I thought back to how I installed FSUIPC on the new build. I copied and pasted a lot of my set up entries. Using the first principle of fixing FSX, delete your .cfg and let it build a new one, I deleted (removed and stored) the FSUIPC ini and let it build a new one and I reset everything back up using the control panel. And flew. I have only done the one flight but the "critical" moment did not occur and AI remained known to FSUIPC all flight, and thus to RC4 and thus, chatter to gate. The traffic listed in TrafficLook was the same as in the Sim. I have not done a comparison yet between the ini files to see what was different thus what may have been causing it but I will do, and of course, do some more flying but I wanted to let you know up front what has happened. I will report back some more after doing a bit more flying. ?? Kind regards, Mark

Thanks Pete, I have read all three posts. And thank you for checking all of this. My first post is accurate and the subsequent posts really were attempts to give more information as we were trying to get on the same page and they inevitably could have become unhelpful. The behaviour (as opposed to what is happening technically) is consistent and - ... maybe the nub of the matter. But the what is quite confounding as there is not much to eliminate, AS16 is the only application running apart from the ATC add on (RC4 or PF3) and I only have MT6a and FTX AI installed, with only one active at anyone point in time and the result with both is the same. And I only have my origin and destination airport active in scenery editor (thus all others are default). MS ATC works, so there is a solution right there that I may just have to live with. I don't have any other traffic bgl's active. Some airports I have come with their own AI but I have deactivated them by using the bgl search tool in MT6a. Add on airplanes are PMDG 737, 747, 777, FSLabs A320, iFly 737, AS A318-21, Majestic Q400 and Ant's Winjeel. Apart from the Winjeel (I have never tried) the outcome is the same with all of them. I have another PC which still has FSX installed, with all of my previous add ons and set up (that my wife now uses and all the Sim stuff is on its own drive and is all protected) and it happens on that PC as well. So, it maybe something I have done to both or both have whatever "it" is on it. As I pretty much replicated my set up from my 2011 PC to my 2016 PC I built last year. Given the old PC has 4 times more on it than my new one, it narrows the possibilities so any eliminating and reinstalling I will do on the old one as I am not too fussed about "stuffing" that one up as it is ostensibly retired. All I need to do is plug in the joystick and load the latest FSUIPC on it. I will do. I am away until Friday (iPad's are handy as I sit in a cafe having breakfast) so I will do that over the weekend (on the "in service" PC) and see where that takes us. Thanks again. Mark

No problems at all Pete, I am tied up over the next week until Good Friday anyway, so as we say, in your own time!

Hi Pete, Try this from SYD starting position S 33 56.6 E 151 11.0 HDG 223 to S 35 03.3 E 149 57.6. "It" should occur before S 35 E 149. A different route from MEL starting position S 37 39.6 E 144 50.5 HDG 043 to S 36 10.9 E 147 04.2. "It" should occur before S 36 E 147. Kind regards, Mark

Okay, I see what you want to do. I will put something together hopefully tomorrow- I have ran out of night! Cheers, Mark

Good question. Not immediately but in a minute or so one was however the others did not show on my ND. I have MT6 too, and without being too fancy, if you do a flight plan DCT WOL H65 RAZZI Q29 ML and depart Sydney 16L climb to FL320 with AI capped at 75 (or 100, or even greater, I have found it makes no difference on the route) with your slider at 35 (MT6 recommended for real schedules) you should with some certainty be able to reproduce it. Canberra is the airport on route with only a few aircraft on the ground. Or DCT DOSEL Y59 TESAT DCT SY depart Melbourne 34, and climb to FL310 you can reproduce with Albury (usually no more than two SAAB340 on the ground). They may work for a start to save you a bit of time. If I can help in anyway, let me know. Kind regards, Mark

Hi Pete and Good Morning! Well, success this time, in so far as I ran without RC4, and with just two TrafficLook.exe's open, one for airborne and one for ground, and I got a restart traffic scanning once I left the Departure Airport reality bubble - the log is attached and there were about 6 aircraft airborne and 1 on the ground (Albury). Interestingly, both the Airborne and Ground TrafficLook files were empty after the restart and remained empty, even though right clicking the screen in sim, and looking at the list of AI aircraft and selecting them to see where they were (about 6 flying and 1 on the ground) clearly showed AI aircraft still active, I closed both TrafficLook files and restarted them but apart from showing user, and my details, i.e. altitude and frequency etc, were empty and not showing the aircraft that were active. So whatever "it is", it killed TrafficLook as well, apart from me showing in it. Which is what happens with the ATC programs - they keep talking to me. Interstingly, MS ATC recognised and kept talking to the AI after the restart - it knew about them but TrafficLook did not. The FSUIPC log from this mission is attached. However, apart from it showing that I was going to desktop to check TrafficLook, the log (in notepad) etc I don't really see it pointing to anything but I am not an expert. Kind regards, Mark FSUIPC4.log

Hi Pete, Wilco. Interesting- I only use RC4, AS16 and FSX/A. That is all that is running but I do have AIDupe.dll that eliminates duplicate AI (which can be quite a lot with MT6a at high slider settings). It is easily disabled but for now I will just run a flight without RC4 with TrafficLook as suggested, https://library.avsim.net/search.php?SearchTerm=aidupe&CatID=root&Go=Search I will install TrafficLook and try later today. Kind regards, Mark

Hi Pete, Please find attached my log file. I flew MEL-SYD; I actually saw on TCAS the traffic disappear where the issue normally happens after I leave the depature airport reality bubble. I checked the AI and there was about 5 airborne and one static on the ground. I can't make much sense of the log file but it does not contain a ***restarting*** so maybe I did not have that and this test has not worked? Murphy's law of course... It is pretty late so I don't have time to start again so if this is no good, please let me know and I will do it again tomorrow. Kind regards, Mark FSUIPC4.log

Hi Pete, roger that, I misunderstood. We are on the same page. No, it was just my (poor) way of (inadequately) explaining what I experience- we are "there" - from the above, your results agreed with mine - no restart if the only traffic were all airborne. Kind regards, Mark

Hi Pete, imprecise language on my part, I certainly understand that restart is the result of the core failure. Yes, the event seems to be triggered when leaving the reality bubble of your departure airport where there is a lot of traffic to enroute, when you go from say 85 captured AI to something a lot less if the "a lot less" includes an airplane on the ground. If you leave the departure airport reality bubble and the "a lot less" are all airborne, then the issue does not seem to occur. No, only one or two on the ground, but at least one not doing anything. But the rest airborne. A bit hard to answer but what I can say is on the two occasions that I have managed to do a full flight from a SYD to MEL or MEL to SYD and AI Chatter did not break, it appears that when I left the departure airport reality bubble (where there is a lot of AI) and the AI goes from say 85 to 11 (or 14 or pick a relatively modest number) then if all of that traffic is airborne (as opposed to one or two being on the ground static at say Albury or Canberra) then it works through to destination. But that just maybe coincidence as I only definitively checked all AI positions as I flew the second time it worked. Unfortunately the first time it worked all the way to destination I didn't. Obviously all AI were responding all flight (why on these occasions as opposed to others is the mystery) thus not requiring a restart. I do have my TCAS in FSUIPC ini set at 80nm, which is the recommended setting in the RC manual. I have had it at 0 which is off and it made no difference to this issue. It was one of things I tried in problem solving before I first reached out for help. That is interesting, so my coincidence referred to above was probably just that. Roger, wilco over the weekend and I will attach the file. Thanks Pete, I do really appreciate your help. Kind regards, Mark

Hi Pete, I just did the flight with Radar Contact, with the .ini as described above and the [Traffic] set at75/95/5/5/95/25, and slider 100% for airliners and with 15 AI airborne I got restarting traffic scanning which broke the AI Chatter. I sat in silence for the rest of the flight. The difference between the successful flight and this one seems to be that the successful flight had all airborne aircraft when I left the departure airport reality bubble whereas this flight had one aircraft on the ground Canberra shut down at the gate. Sorry I could not post better news. If you ever find out what it is and fix it, I will be eternally grateful but given I seem to be the only person on Earth it happens to, I also understand if you just leave it alone. I have come full circle, which is restarting traffic scanning on my PC breaks AI Chatter using RC4 or PF3. Transmissions to me continue to work perfectly. I should just go to zero AI! Kind regards, Mark

Hi Pete, I have just done the SYD-MEL flight with PF3 (with the .ini amended still as above) and on this flight, I cranked up the AI Traffic to 100% and changed my [Traffic] to 75/95/5/5/95/25 to ensure the maximum amount of airborne traffic which never went below 12 all flight and I never had a restart traffic scanning and AI Chatter continued all flight. I guess the next exercise is to keep those settings and do the flight with Radar Contact but maintaing a greater than 12 airborne AI seems to have eliminated the restart traffic scanning (well, it is only one flight but so far so good). Remembering I got the restart traffic scanning with MS ATC as well (but AI Chatter continued) My airline traffic slider was previously 40% (the recommended setting for FTX AI) with my [Traffic] as previously reported. Thus there maybe something in your theory about low airborne levels of AI. I don't have time tonight to do it all again with Radar Contact but will do during the week. If none of that made sense, sorry, I will try to re explain in the morning, it was a big day at work! Cheers, Mark

Thanks for the reply Pete, if I can help you in anyway, just shout out. Unlike most countries, Australia is not littered with airports. You can fly from Melbourne to Darwin and not go anywhere near an aerodrome for 4 hours until you pass Tindal (and that is a military airfield) just before TOD, thus for most of the flight, you are just getting the modest amount of traffic in your area based on the real world schedules in the AI program (I use the FTX AI Australia program for flying in Australia, which is very accurate and MT6a for flights outside of Australia). Maybe I should do a flight from Helsinki to London to test the theory on non receipt of data. Anyway, after using MS ATC today, despite the fact it worked all the way to destination, I now remember why I went to ATC add-ons and I think I would prefer to have a quiet flight with the add-on than ear candy with MS ATC but all the foibles it brings! Have a good Sunday. Kind regards, Mark

Hi Pete, Unfortunately, neither of these suggestions worked. On a SYD-MEL flight (16L.ABBEY3.WOL H65 RAZZI Q29 LIZZI.LIZZI3Z.16) I consistently get the restarting traffic scanning between RAZZI and TANTA (the next waypoint on track) and it is just after all of the SYD AI disappears (beyond reality bubble for SYD) and there are usually only 4 or 5 aircraft listed, 3 of which are usually airborne and 2 on the ground Canberra ahead and to the right of track. ATC to me continues perfectly, and AI continues working as well but for talking - I landed at a very busy Melbourne. If I look at my Radar Contact files, you can play back the last transmission the chatter.wav, pilot.wav and the controller.wav, made and my chatter.wav had a time stamp of 9.34pm 01/04/2017 and when I played it, it was a Cathay flight being told to resume own navigation, and that definitely was the last transmission in game. My pilot and controller time stamps were 10.36pm and that was my taxi to the gate instruction and acknowledgement. However, I noted not less than 20 AI in that hour, including two ahead going to same destination and they were 10 and 15 miles ahead respectively, same flight level and had to be on the same frequency. Neither were handed off to approach when I was on Centre just behind and neither were handed off to Tower when I was on approach. My FSUIPC log tells me that the rescanning occurred (converting the figures) around 9.36pm. I think the next thing I will try is a flight just using MS ATC (I will have to do some study to work out how to turn it back on it has been so long!) - I have the latest payware EditVoicePack XL and it is up to date so that should cover AI given my World Travel and Pacifica AI et al are turned off, and see where that takes me. I will let you know how I get on with MS ATC, and I will also do a flight with PF3 as well. I will keep the .ini as modified above with the entries you suggested. It may be a few days before I have done all of that. Edit/PS - I have just done the same flight using MS ATC (drawing on EditVoicePack) and I got the restarting traffic scanning in the same position but... it does not effect MS ATC. AI Chatter continued as per normal. So, I am not sure what that tells me other than the restart effects the chatter.wav operation somehow in Radar Contact (at least on my system) and, for some reason something happens in that piece of airspace to cause the rescan. Doing a PF3 flight will have to wait until at least Monday night, my sim time has run out, weekend family events beckon. Kind regards, Mark

Thank you for your continued support on this Pete. I do check the logs post flight and I have never had a Failed on SimConnect error. My whole set up works flawlessly and beautifully but for this one issue. And it has probably been like this forever and I had never noticed until I watched a live stream of a new product and I thought my Radar Contact does not work like that! I have a free evening as it turns out with wife and children elsewhere thus I will follow the suggestions above and will try some different flights and report back with some details. Kind regards, Mark

Hi Pete, I have made several flights using Super Traffic Board and Simconnect is not failing to provide AI Traffic data. When restarting traffic scanning due non reception occurs, nothing happens with AI (they are all still there and in front of me, on TCAS - I purposely flew behind two AI going to the same destination on the same track) except that, from the rescan point, the AI Chatter stops and no AI aircraft talks at all from then on all the way to the gate (Radar Contact). Is there a parameter I can use to stop the rescan as a test? It is odd in that it happens half way through a flight when there are less than a dozen or so aircraft within the reality bubble and at a time when the airplane your flying is not really doing anything intensive. Would using the [Traffic] option have any influence? I have it set to 100, and then 50 for all preferences and 25 for FPS. Kind regards, Mark