trisho0

Well, FS2Crew decided to create it then I don't worry about it Patricio Valdes

Great, I will let RAAS take care of runways.

John, I was reading that PDF manual and it is exactly what you posted. My question now is, how FSCREW RAAS will read the runways ID if such information is outside the MSFS2020? Regards, Patricio Valdes

I don't understand. I ran the Make Runways from my backup folder which has nothing to do with MSFS2020. Should I run the program from MSFS2020 folder? I am intended to use it for FSCREW RAAS (Runway Awareness and Advisory System). Obviously RAAS will need to see the runways ID. I appreciate your help on this. Patricio Valdes

I ran Make Runways File: Version 5.13 intended for MSFS2020. The Make Runways at the end it generated several files as SceneList.txt and several csv files. Where those files should be placed? Patricio Valdes

I did Windows restore and now FSX gives error and working as Demo (lol). So, at a later time I will see how it goes. Patricio Valdes

Days ago, I did the reinstallation FSX and Acceleration Pack. Preserved the Scenery.cfg with my add-ons. Used now the new FSUIPC4.dll and still CTD. Patricio

I already checked VC++ Redistributable several versions installed. P3Dv4.5 and P3Dv5.3 working fine with FSUIPC. So, I think FSX should be OK. I will give a try with your DLL file. Crossing fingers (lol). Regards, Patricio Valdes

I am using FSX without FSUIPC for over than a year as posted here because of the problem in question. Yes, I can run FSX without any issues with FSUIPC "Off". Attached is FSX "About" showing the sim version. I remember, installed the FSX SP1 first which is the original and then installed the SP2 which is the Acceleration Pack. The FSX is not the Steam but the first original. I had been using FSX since built and it was working with FSUIPC just fine until it started a year ago with FSX CTD. I know it has to be a fix but no ideas. Regards, Patricio Valdes

Dear John, thanks for helping me on this "nightmare". FSUIPC has been "off" for almost over than a year due to CTD from unknown reason. NoWeatherAtAll=Yes instruction didn't help. I will explain here, I launch FSX SP2 and it pops up the typical Microsoft Simulator X screen and then it shows "Free Flight" page you know the default. Next, I don't touch anything just leaving such screen opened. Suddenly, FSX closes with no error message at all. Is it possible to make a different FSUIPC to handle the sim in a different way? I mean, it could be isolating some instructions via INI file to prevent CTD. I noticed from INI file Fsuipc detects Windows 10 instead of Windows 11. This detection I don't think is the issue because the problem started with Windows 10 anyway. I have to mention a reinstallation of FSX didn't help. Regards, Patricio Valdes FSUIPC4.ini FSUIPC4.log FSUIPC4_prev.log

How to do or where to add this instruction? I have the same Fsuipc behavior the FSX does CTD if load the sim with Fsuipc. Patricio Valdes

Thanks Pete. Finally resolved!

Ran MakeRwys again and Success! I guess now is OK? Make Runways File: Version 5.13 by Pete Dowson FS version code =#5 Using "LorbySceneryExport.exe MakeRwys_Scenery.cfg" LorbySceneryExport executed: Checking for "MakeRwys_Scenery.cfg" Reading Prepar3D v4 scenery: The CFG file being used is: "D:\Lockheed Martin\Prepar3D v4\MakeRwys_Scenery.cfg" 680 scenery layers to be processed ============================================================================= I found an incomplete Area scenery lines from Scenery cfg file.

I wonder how MakeRwys couldn't run with Admin Rights. After running just fine without Admin Rights, I can see a line: ... ERROR: failed to run Lorby program, error=740!. This occurs with P3Dv4 only. (FSX and P3Dv5 run just fine.) Here I posted the beginning of the contents: ------------------------------------------------------------------------------------------------------------- Make Runways File: Version 5.13 by Pete Dowson FS version code =#5 Using "LorbySceneryExport.exe MakeRwys_Scenery.cfg" ... ERROR: failed to run Lorby program, error=740! Reading Prepar3D v4 scenery: The CFG file being used is: "C:\ProgramData\Lockheed Martin\Prepar3D v4\SCENERY.CFG" 486 scenery layers to be processed =============================================================================

Just ran the MakeRways inn P3Dv4.5 again but without Admin Rights and attached the Runways.txt for analysis. If I run the MakeRways again WITH Admin Rights, it appears the error in question. Any ideas, to give another try or simply leave it alone? Due to the filesize I can't attached it here to go: https://drive.google.com/file/d/1NDgpybnScs8ekgjTfRiiNvsvfv4Yr-Ep/view?usp=sharing Please, let me know and thanks for your Support.

Many thanks for your help. Attached the text file and the sim in question is P3Dv4.5 I will run again the MakeRwys later after Support, it will run OK without Admin rights as I did before. Runways.txt

After reading manual I ran the MakeRwys.exe file and got error message make runways failed to make fstartrc rws file. I ran it as Administrator. But I ran without Admin rights, and it was fine. Why the manual says Must be run as Administrator?

Then I could give a try with an older FSUIPC Installer version. I think it could be good try since never had problems with FSUIPC in the past years with FSX. Patricio Valdes

Eventually I visit this thread to see if I find another people with FSX Fsuipc CTD. So, it appears I have to keep Fsuipc disabled to fly comfortable. I don't think FSX in my system needs to be reinstalled since I don't have any issues with my flight plans at the moment. Keeping an eye for new Fsuipc version. Patricio Valdes

Good idea, replacing EXE and DLL files from my backup to the FSX folder and testing further. Selecting another flight and aircraft marking as default. Then activating FSUIPC and see what happen. I will report results. Patricio

Hi Pete, I have 2 different backup of FSX which they were working fine with FSUIPC. So, I was overwriting the Weather folder and the FSX.exe file and it appears CTD anyway. What files can be replaced for further testings? Patricio

I renamed the FSUIPC Key file and removed INI file. Launched FSX leaving loading not touching anything else just watch on the monitor screen. FSX had CTD and silent. Attached INI and Log files. Regards, Patricio FSUIPC4.ini FSUIPC4.log

Good, I will activate the FSUIPC from dll.xml file and with the registration removed. So, in case if it still FSX doing CTD because of FSUIPC then I will leave FSUIPC disactivated. So far I can use FSX without issues as longer if the FSUIPC is sleeping (lol). To do a FSX reinstallation will be a pain reinstalling payware addons and aircrafts plus ORBX. On the another hand, if I have to do a FSX reinstallation instead then simply the FSX sim will go out of my system. I never did any FSUIPC settings anyway. I will see what happen with FSUIPC registration removed ... Best, Patricio

I mentioned at the very end of my first statement as: ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// Tried the sentences added to FSUIPC.ini file (without success): [General] WeatherReadFactor=0 NoWeatherAtAll=Yes ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// Patricio Valdes

1. Before sim CTD I just launch FSX and after 1 to 3 minutes without any other actions FSX suddenly closes without message. 2. FSUIPC.log attached. 3. Deleted all files with wx extension from C:\Users\Patricio Valdes\Documents\Flight Simulator X Files and still not a success. 4. I had to change the "False" back to "True" in the FSUIPC Disabled line of dll.xml in order to keep FSX free of CTD. I can't see what to edit or try to keep FSUIPC working friendly with FSX (lol). Patricio Valdes FSUIPC4.log