ORLANDO SCENERY SIMULATOR

The short term solution we have identified in your User Guide, which is to disable other layers before flying in Orlando if your load times are excessive. Because the Orbx libraries are very large and complex (and not used in Orlando), deactivating this layer alone during Orlando flights will have the greatest impact.Īt this point, we have a short term and long term solution. In fact, on a clean system with only CityScene Orlando, it takes me no more than 6 seconds to get through the 6 second load mark. If the users system has a lot of 'libraries' of objects across their system, each one of these libraries seems to get searched for each object in the BGL file, even though it is pretty clear that a call to perform a library search is not necessary.Īfter discovering this, we realized that by disabling other products in the Scenery Library that are not relative to the Orlando region, the 6% load times dropped down to almost nothing. Then, as it loads regular BGL scenery files, it checks each object in the file to see if it is a library object. What P3D is (apparently) doing for every BGL scenery file (going all the way back to FSX) is that it first searches through all active layers in the scenery library and makes a list of BGL files that are object libraries. Instead, load times appear to grow exponentially depending on the number and size of object libraries active in the Scenery LIbrary. We had always thought that the load times at the 6% mark were linear and depended on the amount of custom objects in a CityScene scenery. What we did is to use ProcMon (Process monitor) on P3D V4 and monitor the way scenery was being loaded. So, we spent a good week or so researching the issue to try and understand why some people had quick load times and others were dragging. Just to note, CityScene Orlando does not reference any object libraries.ĭuring testing, we had reports that the sim was hanging at the 6% mark anywhere from 6 seconds to about 5 minutes max. Orbx provides a very large object library that is shared among lots of products.

ORLANDO SCENERY SIMULATOR

The core simulator provides library objects. This allows them to be shared and reused by any scenery package. Most scenery packages, not just CityScene products, have buildings that are placed in object libraries. Nearly all CityScene objects are native custom models that are unique to the CityScene scenery. When your load times hang at the 6% mark, FSX/P3D is trying to load custom object models. Others on the beta team had lower and others had much higher. I myself as the developer had 3 test machines and my longest load time was 5 min 30 sec. We discovered early on that because of the number of custom buildings in this scenery, load times were quite long. This could get a big long and complicated. I will give you a little background history on things regarding the beta testing of this product. First, the goal of these Cityscenes is to keep all load times under 5 minutes max.

Orlando scenery