Tigerhawk

Hi John, I'll use 240 and see how I get on. .ini file attached. Cheers Dave FSUIPC7.ini

Sorry John, The next time the hotkeys didn't work again. I closed FSUIPC and restarted it and the hotkeys worked. Logs attached. FSUIPC7.log FSUIPC7_prev.log

Morning John, I ran the new installer, hotkeys worked first time and also on a subsequent start of MSFS. Logs attached for your info. Cheers FSUIPC7-init.log FSUIPC7-init2.log

Hi John, Unfortunately this didn't work as the hotkeys were unresponsive, as before. When I was successfully setting it manually I was using 330 Delay, the auto set it to 200. Log and ini attached. FSUIPC7.ini FSUIPC7.log

Thanks John, I tried the 105 as I saw you had suggested it, I didn't realise it was a bespoke figure! I'll stick with the 240 and see how it gets on. Dave

Hi John, I've just done a couple of tests using 7.4.10c. First with Detect.....Auto setting at 105. This failed to connect, but did after closing and opening FSUIPC and PF3 (see 2 logs with 105 added to FSUIPC). Then with Detect....Auto value at 240. This did work straight away (see log with 240 added). Hope these help? Dave FSUIPC7105.log FSUIPC7105_prev.log FSUIPC7240.log

Hi John, I again had the problem using 7.4.9 and used Mark's suggestion to stop FSUIPC and PF3 and then restart them (which worked!). Log and PrevLog attached. FSUIPC7.log FSUIPC7_prev.log

I don't have a massive amount ( I don't think!) - 26 folders:-

Hi John, Log attached using 7.4.9 - no response with PF3 using Hotkeys Dave FSUIPC7.log

Pete, You are a man who knows his onions! Excellent support. Runways.txt is too big to attach, even after zipping (67.3mb), I've attached the scenery list. I Could send you a OneDrive link for runways.txt if you need to see it? Many Thanks Dave SceneryList.txt

Thanks Pete. Under the circumstances that seems like the best thing to do! I’ll leave it in your capable hands!

Hi Terry, Did you ever get this sorted as I am having a similar problem?

Thanks for your input John, Unfortunately I find that even more obscure than Pete's suggestion. I sort of get what a symbolic link is - I presume I need to create a link (e.g - "D/New Link" linked to "C:\Users\David Hawxwell\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe") in order for the file name length to be much shorter? But what I don't understand is what type of link I need, nor how MakeRwys would then use the "D/New Link" rather than the original as I assume MakeRwys gets the location of MSFS from the Windows registry. Sorry to being a little confused, like Pete I just cannot understand what has caused this issue?

Thanks Pete. I don’t understand it either. Nothing has changed on my pc apart from Windows updates and MSFS updates. Same virus software etc. Can’t think of anything else that has changed. Not even installed anything new since July as far as I can remember.

Hi Pete, I have updated Windows to 19043.1237 also. I've tried using both the gpedit and registry methods of enabling long path names, but still with exactly the same outcome. I've had a look at the symbolic link instructions. I don't know if I'm being dense, but I'm afraid I haven't a clue how to do this to enable MakeRwys to use the link, or even how to even create the link or which type! Any advice?