Pete Dowson

Thanks Steve. I'll try it on Win7. Pete

Okay, wilco. Thanks Pete

Will I still be able to use my P2A version 2 installation whilst evaluating version 3 (and in particular testing it on my Windows 7 PC currently running version 2). Thanks Pete

I expect you've no access because you are only evaluating Prosim, and haven't actually purchased it. I can't think of any other reason. I can only suggest you contact them through the purchasing mechanism -- surely there must be some way of asking questions there? I don't really recall such things as it was a very long time ago that I moved to Prosim from Project Magenta. Regards Pete

It sounds like you are using the AIG utility which injects the traffic with a proper routing. This cannot work properly with the FSUIPC traffic limiter, because almost as soon as FSUIPC deletes one, the injector re-injects it. I did ask the developer to either avoid re-injecting deleted aircraft, or at least wait a while till it does. I don't know whether any such thing was implemented -- I stopped using it and only use the ready-made AI plans (i.e the complete set of BGLs). The limiter works well then. Pete

No, it isn't. I use the file on a separate PC to display on a small monitor inside my cockpit. I use a Lua plug-in running under WideClient. It works fine. I'm using the latest P2A, Beta 5o. Pete

Inside the WideFS.zip package there's another ZIP called "TextMenu display Lua package". Check the section in the PDF in there for Text File display facilities. Note that this was aimed at P3D. With MSFS the SimConnect text facilities won't work. Pete

With Pilot2ATC you can assign a button or keypress (I use a quick press on my PTT button on the yoke) to operate "say it", which will handle all the responses you need. You really only need to say a few easy phrases yourself (like the "ready to copy", as you say, to get initial clearance). I never need to use the P2A window itself. I display the Conversation Text file on a small in-cockpit screen using a facility designed for this in WideClient and a Lua plug-in. My Pilot2ATC runs on a separate WideFS client PC which is connected to my headset and overhead speakers. I use a Lua plug-in ("triple-use") to have three functions on the yoke's PTT button: Short single press = Say It (acknowledge in general) Press and hold = PTT Short double press = Say again? These are assigned to keypresses via WideFS's "KeySend" facility. Pete

See my reply in the FSUIPC support forum. Pete

Thanks. I think the problem is that your Windows 10 (I assume?) appears not to have long pathnames allowed. The normal maximum is 260 characters, but this restriction can be overridden by using that \\?\ prefix. From Windows documents I'd assumed that this would work no matter which build of Windows is being used -- it was okay on three different versions on PC's I have. However, it is noticeable that the last line logged on your system is showing a pathname longer than 260 (discounting the "" envelope, which isn't used in the actual windows calls). In fact it's the first path longer than 260, at just 261 characters! Perhaps I should log also the version and build number of the Windows version in use. But could you tell me (use WinVer) please? And maybe try to update. Using Google I have found this: 4.3 Enabling Windows Long Path (Windows 10 - 1803 build) Click Window key and type gpedit. msc, then press the Enter key. ... Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem. Double click Enable NTFS long paths. Select Enabled, then click OK. Could you try that please? There's also a way of editing the Registry instead. See https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ Let me know please. Pete

Thanks. They are identical to mine. Without being able to reproduce the problem here, I am stuck really. What is most puzzling is the missing "scenerylist.txt" file. That is produced before the folders are processed. Please ZIP up the entire Scenery.txt file and send it. Something odd must have happened before the file processing stage started. Also, please tell me where you installed MakeRwys.exe -- in a folder of its own? I'm having some difficulty trying to understand exactly what "Exception code: 0xc0000409" actually means. It isn't in the official MS lists. This website: https://www.minitool.com/news/0xc0000409.html suggests it might be a system error rather than a specific program bug, and that you should run system file checker. I also found this How to fix the 0xc0000409 error Press Windows key + R to open up a Run window. ... In the Troubleshooting tab, click on Windows Update (under the Get up and running tab) and choose Run the troubleshooter. Wait until the initial wizard detects the problem that is causing the issue. Pete

No! Certainly not! Thanks. I'll look at that, but it might be a while. I suspect all it will show is data being read which makes no sense. It might be quicker for you to trying repairing/reinstalling. If I do manage to locate the problem in MakeRwys processing it is likely that all I can do with it is to terminate tidily with an error message, which still wouldn't give you the results you need. If I can by-pass the error then I will. I'm wondering if it would help if you sent me the contents of those two folders. You could try ZIPping them up and sending to [email protected]. Pete

If things were okay the next line would be: "\\?\C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-devmode\Edition\templates\AssetGroups\SimObjects\airplanes\singleprop-empty\SimObjects\Airplanes\MyCompany_AssetName\texture\" ***** Processing MSFS official scenery (Asobo=1) so I'd guess that there's some corruption either in that soundai folder, or in this texture folder. Was there any crash data for MakeRunways in the Windows Even Viewer? Please check. There should be a SceneryList.txt file as well -- please check. That is produced before this processing begins. If that completes then there is definitely some error in one of those two folders I mentioned. It would need to be repaired somehow. I'm not sure whether MSFS offers any repair options for installation -- if not then I think it will mean a re-install. Going by the pathname, the files where it stops seem to be related to devmode. Perhaps disabling devmode with remove them from the list. Pete

"Runways.txt" is the log showing what happened, so you need to look at that. Pete

Google is your friend! 😉 https://en.wikipedia.org/wiki/List_of_aircraft_type_designators Mind you, though those are the official ones, listing 74T, 74X, 74Y, 74V for 747 freighters of different series, there's no guarantee that the aircraft models supplied for the sim have the correct ones defined in their Aircraft.CFG, so you do still need to check there. Pete