padrot

Hello everyone, I also experienced this error earlier today when modifying some options in the game settings to improve FPS and it gave me these 2 errors (one at a time) when starting the game and it wouldn't get past the splash screen because it didn't even show the main menus (a tragedy). "0xc0000005" & "VCRUNTIME140.dll" What I remembered the last thing I did was that I activated DirectX 12 (beta) and from then on, it was only CTD. Not being able to load properly the game to modify that parameter to DirectX 11, I had to look for the configuration file (I remember in Prepar3D it was in "appdata" folder and it was called "prepar3d.cfg"), so I had to look for a file similar that the MSFS2020 (steam edition) could had and I located it in the following path: "C:\Users\YOU_USERNAME\AppData\Roaming\Microsoft Flight Simulator" The file that I opened and modified with notepad is called: "UserCfg.opt" There I searched and found the property called: "PreferD3D12", it was with a value of "1" (one), I changed it to "0" (zero), I saved the changes and I ran the game again. Bingo, I was finally able to play again without any CTD. That was my story, I hope it can help someone, who like me, suffered in finding the solution after several hours of trial and error, I was able to solve. Courage to all those who continue to have this disastrous nightmare of CTD's, have a prompt solution and can enjoy such a wonderful simulator. Regards.

When I changed PC a few years ago, I had the same problem and I solved it in the following way: I made a backup of the FSX's DVD in ISO format and save it to a USB, so I just mount the image in Windows and that's it. I hope this help you.

Everything seems correct in your code, Juliett Alfa.

Thanks for the info, regards

Hello fclaass, could you tell me What is the application you use to see the AI traffic on the map? Thanks.

I thank you Christoph, great contribution for us. I will try all the addons you shared with us as soon as I can and I will definitely enjoy it. Regards

Hi Tony, I found the add-on you're requesting, it says it's for FS2004, so I don't know if it still works for P3Dv4 or v5, we should try it. I share the link Regards

Thanks for your tutorial, Christoph. I have a question, What are they and how do you get those addons that I highlighted in bold? I can't find anything about those 2 DLL's in the file "addon.xml" I appreciate your guidance, regards

Well, I have a shortcut on the desktop of the XML config file, there I modify it if necessary during the flight and press the "reload xml" button. About the time it takes to adjust the AI, let's say to a change in active runways, I haven't done that test yet but it would be interesting to know the behavior of the AI traffic. Regards Dirk98

I modified you some capital letters in the parameters that were with errors. On the probability to assign on the landing or takeoff runways, in you case being two runways, in both they must add 1 (one). Example probability parameter: * Runway 27R takeoff: <Probability>0.7</Probability> * Runway 27L takeoff: <Probability>0.3</Probability> -------- 1.0 (always returns 1) * Runway 27R landing: <Probability>0.8</Probability> * Runway 27L landing: <Probability>0.2</Probability> ------- 1.0 (always returns 1) In case of not adding probability in the parameters, the program will automatically have the following values: Example probability parameter: * Runway 27R takeoff: 0.5 * Runway 27L takeoff: 0.5 -------- 1.0 (always returns 1) * Runway 27R landing: 0.5 * Runway 27L landing: 0.5 ------- 1.0 (always returns 1) <?xml version='1.0' encoding='utf-8' ?> <Parameters> <Airport> <ICAO>EGLL</ICAO> <ActiveTakeOffRunway> <Runway>R27L</Runway> <Probability>0.6</Probability> <EmptyWeightLimit>23000</EmptyWeightLimit> </ActiveTakeOffRunway> <ActiveTakeOffRunway> <Runway>R27R</Runway> <Probability>0.4</Probability> </ActiveTakeOffRunway> <ActiveLandingRunway> <Runway>R27L</Runway> <Probability>0.4</Probability> </ActiveLandingRunway> <ActiveLandingRunway> <Runway>R27R</Runway> <Probability>0.6</Probability> </ActiveLandingRunway> </Airport> <EnableFastTakeOffs>1</EnableFastTakeOffs> <AllowTakeOffDistance>6000</AllowTakeOffDistance> <TaxiSpeedLimiter>30</TaxiSpeedLimiter> <runwayTaxiSpeed>29</runwayTaxiSpeed> <enableRollthenTakeOff>1</enableRollthenTakeOff> <minCrossingRny>2000</minCrossingRny> <isGUIVisible>1</isGUIVisible> <voidTimer>1000</voidTimer> <TaxiSeparationMultiplier>1.8</TaxiSeparationMultiplier> </Parameters> Regards

Thanks for continuing to improve this amazing add-on Federico. Enjoy your well-deserved vacations and I'll be here to support everyone in this great community. Regards

There is how this condition "ATCModel" is added for certain aircraft use a specific runway.

I did the test using the 23's runways and it worked perfectly. Now I will add 'probabilities' to detect if this trigger any bugs. I will keep testing. UPDATE: After adding "probabilities" in the XML file, AI Traffic behaved smoothly. Deducing, the cause of the problem could have been these 2 lines: <ApproachName> XXXX </ApproachName> <ApproachType> ILS </ApproachType> I will continue to test more airports to be 100% sure of this, although at the moment, I'm 90% certain that it's the issue. Regards

Hello everyone, Thank you to everybody for the suggestions and solutions that you have given me. Today I has done some test again at the same airport but now using the opposite runways due to live METAR (same as last time, only now the winds are coming from a different direction). So far so good in terms of arrivals and departures, the IA traffic use the correct runways in both cases (05R & 05L). <?xml version='1.0' encoding='utf-8' ?> <Parameters> <Airport> <ICAO>MMMX</ICAO> <ActiveTakeOffRunway> <Runway>R05R</Runway> </ActiveTakeOffRunway> <ActiveTakeOffRunway> <Runway>R05L</Runway> </ActiveTakeOffRunway> <ActiveLandingRunway> <Runway>R05R</Runway> </ActiveLandingRunway> <ActiveLandingRunway> <Runway>R05L</Runway> </ActiveLandingRunway> </Airport> <enableFastTakeOffs>1</enableFastTakeOffs> <allowTakeOffDistance>6000</allowTakeOffDistance> <taxiSpeedLimiter>30</taxiSpeedLimiter> <runwayTaxiSpeed>29</runwayTaxiSpeed> <enableRollthenTakeOff>1</enableRollthenTakeOff> <minCrossingRny>2000</minCrossingRny> <isGUIVisible>1</isGUIVisible> <voidTimer>1000</voidTimer> <TaxiSeparationMultiplier>1.8</TaxiSeparationMultiplier> </Parameters> I will try again with a custom METAR so that the 23's runways are used and determine if it's an AFCAD problem or it was simply a failure of the XML code. Regards to everyone.

Hi Federico, First of all, congratulations on your work making this wonderful addon, which we so wanted to have existed for a long time for P3D and which had not yet been achieved with this quality in how you are doing it. I have been testing some airports with the latest version you published and I have noticed in this airport, MMMX, that the planes land on the opposite runways and others on the correct ones that I have specified in the "config.xml" file, which causes that in the taxis of those arriving on the 'wrong runway' invade the "runway in use" while the plane taking off on the "correct runway" end up "colliding". The take-offs are working perfect in the "runway in use". <?xml version='1.0' encoding='utf-8' ?> <Parameters> <Airport> <ICAO>MMMX</ICAO> <ActiveTakeOffRunway> <Runway>R23R</Runway> <Probability>0.9</Probability> </ActiveTakeOffRunway> <ActiveTakeOffRunway> <Runway>R23L</Runway> <Probability>0.1</Probability> </ActiveTakeOffRunway> <ActiveLandingRunway> <Runway>R23R</Runway> <ApproachName>MX450</ApproachName> <Probability>0.1</Probability> </ActiveLandingRunway> <ActiveLandingRunway> <Runway>R23L</Runway> <ApproachName>MX401</ApproachName> <ApproachType>ILS</ApproachType> <Probability>0.9</Probability> </ActiveLandingRunway> </Airport> <enableFastTakeOffs>1</enableFastTakeOffs> <allowTakeOffDistance>6000</allowTakeOffDistance> <taxiSpeedLimiter>30</taxiSpeedLimiter> <runwayTaxiSpeed>29</runwayTaxiSpeed> <enableRollthenTakeOff>1</enableRollthenTakeOff> <minCrossingRny>2000</minCrossingRny> <isGUIVisible>1</isGUIVisible> <voidTimer>1000</voidTimer> <TaxiSeparationMultiplier>1.8</TaxiSeparationMultiplier> </Parameters> What could this be? Is it a bug or did I miss adding something to the code? I appreciate the help you could provide me. Regards.