ARCO

I do not use Envshade/Envtex anymore since I installed REX Environment Force in May, but do I remember correctly that Envtex was in the scenery.cfg file and had to be on the very top of it? Can you check that it is so? If that is not the issue, uninstall Envshade and see if your issue is solved. If not, read second post section F of this topic from Elaine: Good luck!

If you want to keep it simple and beautiful, Rex Environment Force and Sky Force in full automation mode, that's it and wonderful! I had ASCA, ENVTEX, ENSHADE and deleted all of them. Now this, of course, is purely personal and you will get many other advices on this matter, I am sure, in the end, your opinion will remain the best!!!

That's a bit harsh to say the least on those who initially installed Central as suggested by ORBX, Ian... I was among those who welcome Central 4 because it allowed to install all ORBX products outside P3Dv4.5, using xml as LM has been recommending to all developers for quite sometime now, so as to allow a cleaner and easier to manage P3D system. That is when all problems happened for most (all?) users who had followed this new way of installing ORBX products, because their scenery.cfg file was literally destroyed and became unusable unless one accepts that a 20 minutes scenario loading time is normal, even after reordering the sceneries as they were initially. ORBX then released a new version and recommended to users NOT to migrate, and in any case NOT to have ORBX Base outside P3D because it was causing problems for which LM had been requested for help. So now to say that these problems were caused by users is incorrect. Evidently if one does not migrate ORBX products outside P3D, the problems are de facto eliminated, but so is the clear advantage and main objective of having all ORBX products outside the sim folder...!

There: https://orbxdirect.com/ftxcentral

Matt, you may like to keep it that way, but since it is an abnormal loading time of P3D linked to a scenery.cfg file that would need some clean-up, it is really up to you to rectify it, David's problem is related to the ORBX Central install/uninstall problem and has no connection with your situation. What you describe cannot be considered as normal with P3Dv4.5, for starters, do you have Default Terrain as your very first file on your scenery.cfg as active? Did you check the priorities of your meshes, ORBX products, add-on airports (with and without xml, LC files position and are you satisfied they are in the correct order of priorities? Where does your P3D loading freeze, at 6 or 70%, that would shed some light on the probable cause.

ORBX Objectflow 2 is also present in my P3D Documents Add-on files with xmls, so I would not touch these as their path relates to FTX v3. However, I do not have the other folders you mention and I would first open the xml in Notepad to see if their path includes FTX or not, if not, move them outside the Add-on files to see if they are the culprits. If it works that way, they can be eliminated later on. To detect wrong paths with Lorby P4AO, check on the scenery list if any of your scenery is shown in pink, if so, verify what the link is and if there is an error, you can see which scenery you have to de-activate within P4AO, it will then turn red. Most likely those three files you have listed above should be shown in pink since the xml would relate to a non existing file, hence your loading times.

David, can you check in your Documents, P3D Add-on files if by any chance you have any OrbX xml files still there (in particular for Objects), this is exactly what happened to me, there were two files that had been left over after I un-installed all my OrbX stuff after the Central 4 fiasco and I was - like you - experiencing long scenario loading times since P3D was trying to find those files that had been deleted but with remaining xml. Once I removed them, I was back to normal loading times. Make sure you scrutinise all places where the previous OrbX Central 4 were (I cant be more precise because I am not near my PC), I had to manually search and eliminate all files related to Central 4 that were not removed. I would bet this is your problem, not so much your Autogen. In case you dont have it, please download this excellent freeware available here Lorby P4AO, this will assist you in finding wrong scenery paths and correct them, this is what saved my day.

Hi David, Did you install OrbX Central 4? Did you migrate your OrbX sceneries out of P3D? Did you install OrbX Global outside P*D? Please give more details about what you have done with your OrbX products, if this long loading time happened after you re-install OrbX products then look no further something is messed up in you scenery.cfg file and some priorities are not correct creating this slow processing of all your scenery files by P3D, but we would need to see it to guide you, and understand what actions you have taken before you had this problem. My personal advice if you have done any of the above, would be to (1) un-install all your OrbX products and (2) re-install FTX Central v3 then (3) re-install all your OrbX products within P3D, (you will have every opportunity to use Central v4 once it is finally fully operational). Your loading times will - should - be back to normal. I had this very same problem after using one of the first iteration of the infamous Central v4 and had to do exactly that, I am now back to normal loading times within less that one to three minutes depending on the complexity of the chosen scenery. Good luck.

This is the sign that your scenery.cfg file is not in good shape, wrong priorities or wrong xml links. In order to identify the culprit(s) you have several ways, starting with the easiest, download the Lorby freeware P4AO on AVSIM and see if any of your scenery comes with a red or pink tag, if so, rectify the path until it becomes green, then you should be OK. In case this does not resolve your problem, would you remember what change you made to your sim (new scenery add-on or ORBX Central for example) when this problem started? If so, de-activate the last scenery add-on (either within P3D scenery or Lorby P4AO) and start your sim, if it loads OK, then I would recommend to uninstall that latest scenery and re-install it, something probably went wrong during the initial installation. If you installed ORBX Central 4 and migrated your ORBX products, my advice would be to revert to FTX Central 3. It is well documented that the new ORBX Central 4 has created this problem that you describe for many simmers who followed the initial recommandation of ORBX to migrate their products. If none of the above helps, are you able to post your scenery P3D listing, so that we can help you with the priorities? As a good practice for the future, make a back-up of your scenery.cfg file, it will help you to recover immediately in similar cases.

Thank you everybody, fantastic AVSIM's fans and great helpers when goings are getting tough, I finally could get rid of the two xml hidden in my P3Dv4 documents add-on files related to ORBX thanks to P4AO and Aivlasoft EFB Database builder getting stuck on these particular xml, I cannot recommend enough this extremely useful freeware (P4AO from Lorby) as it saved my day on numerous occasion, today by recuperating my previous working scenery.cfg file which I had wisely saved before installing this ORBX Central v4! Now everything is back to normal with super fast loading times and no more blurries. This sad episode is over and I can get back to our wonderful hobby which is about... flying!

Good for you, so did I, but I am not back to my previous scenario loading times of 1 to 3 minutes, do you care to indicate what you did to revert to v3, here is what I did: Uninstalled one by one all ORBX products on v4 Cleared any remaining files in the ORBX Libraries Un-installed v4 through Windows 10 Installed FTX v3 Download and installation of all 30 products All sceneries are correctly aligned and Vector properly configured as it was before Force Migration Checked scenery library with P4AO, and found that everything was correctly ordered as it was before Started P3D, loaded a scenario and ... find myself with a freeze progress bar at 69% like with v4, So what else should I do please? Thanks for your help.

Thank you Maxime, I also found that using P4AO was OK finally, after some trial and error, but that - unfortunately - did not at all solve the scenario loading time (15 to 24 minutes) with a i7 8700K and 32 GB RAM. This is at this time the main challenge for me. Are you experiencing this as well? Blurries were only, as you describe, low and fast when on approach, otherwise everything looked OK, but I certainly did not scrutinize the ground textures the way you did it in your testings (I had read that thread at ORBX). So it really looks that in spite of implementing the xml, one would need to revert to version 3 if we want to use ORBX products for the foreseeable future. Their support is far too slow and it is difficult to understand how a tested and released product can have so major shortcomings. Thank you for your kind and precious input. With best regards,

Thank you Oliver, if only ORBX support was like yours....! With kind regards,

Thank you Oliver, I understand your points. FYI I have used P4AO this afternoon to reorder the sceneries, making sure all ORBX files would be (as they were before migration) below my FSAID files and all my airport add-ons (many of them). Apparently P3D took it without any problem. I had also reordered ORBX files as they were under v3 and again all went well. Since I have not flown yet with this new scenery.cfg file, I cant tell if it will have an effect on the blurry texture, but what is certain is that it did not change one thing to the scenario loading time where it freezes as soon as it gets on Loading auto-generated scenery (presumably ORBX files), this is where the 15 minutes go, the rest of the loading process is absolutely similar to what it was with v3. Bear in mind that all 29 ORBX products have been migrated to the SAME SDD as the one where P3D and Windows are (I have only one hard drive), hence there is no apparent reason for this excessive loading time for the auto-generated scenery as far as hardware is concerned. Remains as you mentioned in your reply duplicates, I used P4AO tp eliminate them (there were a few in the ORBX files and they are not listed anymore. )When going through the list of each ORBX files, I found duplicate numbers and first thought they were duplicate files, but going to the path, they apparently were part of a package with different names inside, so I avoided touching them. As a matter of curiosity, is there a way to open a saved scenery.cfg P4AO file with a word editor, I'd like to check what has changed in the ORBX file names? Again, many thanks for your kind help. Best regards,

I installed ORBX Central v4 and migrated all my ORBX 29 products to a new library located on the same SDD but outside P3Dv4.5. Before doing this, initially my P4AO scenery cfg was orderly and working 100% (I saved that cfg file before moving to Central 4). Not anymore. I could after version 4.04 re-establish some order, but I have yet to understand why I am getting two problems: My close ground (looking down from the aircraft below 5'000 feet) ORBX textures are blurry (whereas this never happened before v4) The scenario loading times are now well in excess of 15 minutes (versus 2 to 3 minutes with v3) Could this be explained by a wrong order of my sceneries in P4AO please (the same question went unanswered on the ORBX forum). Thank you for any feedback. Windows 10, i7 8700K, 32 GB RAM, SDD 1TB Samsung Evo, Nvidia GTX 1070

The recommended procedure would be: Start EF (No need to open SF, EF will use it in the background automatically) Start AS16 Start P3D That's all. No need to select any theme unless you absolutely want one, EF will select ANY cloud that is appropriate according to the weather. from your SF library.

https://www.prepar3d.com/forum/viewtopic.php?f=6306&t=134099

Transition altitudes are different outside North America (where standard is 18'000 feet), but P3D (like FSX before) would apply the same transition altitude worldwide which is obviously wrong, ATC add-ons would rectify that and you can see on many high-end aircraft add-ons that the transition altitude of the airport you start your flight from would be indicated on the FMC. Unfortunately, you need to change it to 18'000 feet regardless of your location if you fly with P3D ATC. It is difficult to understand why this was not rectified by LM since add-on developers can do it, so could they! When you fly above 18'000 feet and press B, P3D will automatically select 29.92 (1013) as the standard pressure. When flying below 18'000 feet, pressing B will give you the actual QNH in the region where you are. So normally when you contact P3D ATC and fly below 18'000 feet, it will tell you the QNH of your area. Anywhere above 18'000 feet that information wont be indicated as it is the standard 29.92 (1013). When in transition ABOVE 18'000 feet simply press B and you will be OK when reaching your FL above 180 (or when you receive your clearance for a FL above 180, just select 29.92 (1013)). When descending transitioning BELOW FL180, press B it will give you the pressure in your area. If you happen to press B too early either climbing or descending before reaching 18'000 feet, your baro indication will be wrong and, hence, ATC will reprimand you for busting your altitude. The trick is that when you receive a clearance from say FL 260, "descend Altitude 12'000", the QNH will not be given by ATC (because you are above 18'000 feet), so that is when you need to press B after crossing FL180. You will notice though that after you cross 18'000, the first ATC message will include the QNH.

So do I, if you check their respective description, these two products are complementary to each other, not duplicate. You can obviously avoid FSAerodata if you don't absolutely want it, but you would still want to keep preferably Navigraph.

Did you make any change to FSUIPC (registered) AI traffic limiter by any chance without realising it? Did you limit your traffic in P3D and/or UTLive?

Great document Samaritano, clear and concise and from a real world AAL Airbus pilot, thank you!

Having seen that your system is identical to mine (although I run a 1070 that is weaker than your 1080 TI) I did not even OC but use the Turbo Boost, the FSL A320 will "fly" perfectly with no restriction whatsoever. I rarely use the PMDG 737 and erased the Aerosoft A320 quite a long time ago after trying the FSL bus. So if you have any reservation based on your hardware, be assured you run no risk at all and enjoy the most sophisticated simulation made available to us, even more so with its integration with GSX, making the flight preparation a lot of fun and the most interesting experience ever in my opinion. Oh, and don't ask about my frame rates, but rather about smoothness, I never ever look at the FR, but trust my own eyes to see if the simulated world around me is smooth or not, and yes it is indeed!

Hi Ray, Yes it works with PFPX V2 and Simbrief (in this last case, one must select the proper Aivlasoft V2 path in the FMS downloader). To verify my statement (I very seldom use PFPX so I did not remember for sure) I created a flight from LEBL to LOWW in PFPX v2, loaded my flight in P3D, started EFB v2 which opened at LSZH as the default airport, and as soon as my flight was on the P3D screen, EFB moved on to my parking position at LEBL with my MD82 selected automatically, and when I pressed FPL, EFB offered my flight plan from PFPX. Evidently this works flawlessly with Simbrief as well, since this is my usual flight planner.

Pete, The flight plan is not automatically loaded into EFBv2 as you suggested to Urs. However, when you load your P3D scenario, then EFB v2 will automatically be aware of all parameters including the airplane flown (provided there is a profile for it, but most current add-ons have one), the airport and the gate location (like in version 1), then when you press FPL automatically EFB v2 will offer you the flight plans available from THAT airport.

I too would not fly without it. The number of add-on aircraft profiles is a bonus and the aircraft you fly is automatically selected by EFB when starting P3D! Using both Simbrief downloader or PFPX to import flight plans is simple, when starting EFB, it automatically locates the airport you selected in your scenario and will only propose flight plans initiating from that airport, the developer really thought very hard to make our life easier!.