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