Ray Proudfoot

PFPX + TopCat still working great for me. They have promised to continue with licence renewals so when I need to install these programs on a new PC I trust they will be good to their word.

I run PFPX on a different machine to P3D which may be a factor. Now that I’m aware of it it’s easy to check.

Check your PFPX temporary folder. C:\Users\Public\Documents\PFPX Data\Temp Mine contained a significant number of tmp files going back many months. I cleared them all out without any perceived impact on PFPX. I'm not sure why these are never cleared out except by manual intervention.

Sorry about the confusion. What do you think about filtering default airports that have a runway length of 5000ft or greater? Google Earth used to show a great number of airports until their management decided to remove the feature. All the more bizarre when you consider it has a flight simulator feature! 🙄

Hi Peter, that didn't fix it. It seems only addon airports are exported, not all the default ones.

Hi Peter, I think I've discovered the reason most default airports haven't been exported. This setting in Addon Organizer. I'll turn it off and try again.

Hello Peter, Sorry for jumping in on someone else's post but I have the same problem. Debug pack attached. In short, I followed the instructions and makerunways ran and created the info which now appears in GE Pro. But for France there are only 5 airports listed - LFBO, LFML, LFMN, LFPG and LFRS. I own all these airports but I was expecting all the default airports to be listed too. There are several hundred default ones. Does the process import those too? The reason I want to have all airports available is because Google decided to remove airports from GE Pro and despite writing to them about it they haven't replied. 20220106-12h40m29_SIMstarterNG_DebugPackage.zip

That's a good idea, thanks! I will post on their forum.

Hello Peter, On reflection the complexity of how these few executables are managed doesn't really justify the work required to handle how they are processed by SimStarterNG. There is a reference in the add-on.cfg which points to another file from which the executable is listed. One is SODE which I'm sure you're aware of. Its impact on P3D is probably very small anyway. Others point to executables associated with programs from AIG (Ai aircraft) and again, how much they impact on performance is unknown. Sorry to have bothered you. I do use the Run function to assign an AM to those programs listed.

@Capt. PERO, The latest version of P3D v5.3 has a new section in the prepar3d.cfg for [JobScheduler]. This allows P3D to be assigned to specific cores acccording to the CPU used. The recommendation from Rob Ainscough is to keep the cores P3D uses away from the OS. Third party executables should also be assigned to separate core(s) and I use SimStarterNG Run section to do this. I have assigned things as follows to my i7-8086K 6 core CPU without HT enabled... Core 0 - OS Cores 1-4 - P3D Core 5 - Third-party programs such as ASP3D, ChasePlane, LittleNavConnect, Aivlasoft EFB Server. This works very well but there is one area I have no control over. Executables launched via Add-On.cfg are automatically assigned to all cores. To change this I have to select each one in Task Manager and change the Affinity Mask to core 5. Could you please consider adding functionality to allow those executables launched via Add-On.cfg to be assigned to a specific core(s). Thanks.

Found where it's stored. Sim Config Manager - Tweaks.

P3D v5.3. On a recent flight I noticed the rising moon was way too large. Looking at suneffect.cfg in C:\ProgramData\LM\P3Dv5 its current size is 2072 compared to 900 for the sun. Given they are very close in their apparent size I edited that file and changed the moon size to 900. Saved and exited. Loaded P3D via SimStarterNG and after closing it I checked the suneffect.cfg and it's changed back to the original 2072. Does SimStarterNG store this somewhere? I can't find where?

@PettyCR, the author is ill so you’l just have to be patient. I would guess the new settings in Prepar3d.cfg need to be included in SimStarterNG. There’s nothing wrong with the way this topic has been handled. The only problem is with your attitude.

Could well be the reason but I'm sure Cpt Pero will work it out.

With the release of P3D v5.3 today I imagine a compatible version of SimStarterNG will soon follow.