Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

113 Excellent


About akriesman

  • Rank
    Senior Member

Contact Methods

  • Website URL
  • Skype
    Allen Kriesman

Profile Information

  • Gender:
  • Location:
    Arlington, Texas USA
  • Interests:
    Flight simulation development takes a lot of my work and free time. Outside of that, I enjoy spending time with my wife Liberty. We are both into sports, art (all forms) and music (alternative). When I really have some spare time, I like to play guitar.


  • Facebook Profile

Recent Profile Visitors

1,080 profile views
  1. Unfortunately, separating out the C17's right now is a bit of a problem because the software we use clusters all library objects into one BGL file for each section (i.e *CharlestonKCHSLibrary.bgl). So, this will require a partial software rewrite to separate out some library objects into different BGL files. But, I will look into seeing how much of a rewrite that would require. As far as the Boeing facility goes, TBH I did not even know it was a Boeing facility. So, we were just placing some large static aircraft at that location. We will have to see if we can locate some static 787 models.
  2. When we mention POI's in CityScene products, we are talking about custom buildings that have to be modeled outside of our software using some type of high end 3D modeling software (like 3DSMax). Some of these POI's can take a few days to model each. Others take as little as an hour each. POI's also have textures unique to that object. All of the other buildings in our CityScene products are also custom buildings. But, the they are modeled quickly with our in-house software and use shared texture sheets. Sometimes, we can get them to look very POI-like though by selecting textures that are very close. But, we do not have the ability to add an infinite number of details to buildings as you would outside in a 3D modeling package. Of course, when you have over 300,000 custom modeled buildings, it would be impossible to model them all manually in a 3D modeling package. So, just because a building is not on the POI list, it doesn't mean that it is not present at all. It just means that the modeling might be less accurate (different degrees) than one that was modeled manually using 3D modeling software.
  3. FWIW, Charleston is a large and scenic area that has not already been done by any other developer at all. And, there are 5 airports in the scenery area. So, it was done as an experiment more than anything to gauge the interest in very large, but slightly less popular areas. Unfortunately, I didn't expect it to take 11 months. It ended up being a very long project.
  4. There is one other thing that I want to mention. This information came directly from the LM devs when testing V4.5. Make sure that your Orbx Libraries are above any Orbx products that use them. This will cut down on search times during loading with V4.5 (I don't know about other sim versions that are pre-V4.5). It is probably good practice to make sure that the Orbx library layer is at the very top of your scenery library.
  5. The P3D V4.5 load time fix strictly applies to products that have a lot of custom models. Because CityScene products are made up of nothing but custom object models, those products were most affected by the load time "bug". All CityScene products should see a big benefit in both load times at startup within an area and also in flight when approaching a CityScene area. I can't speak for non-CityScene products with V4.5 because I am not familiar with the internals. The Netherlands uses some CityScene logic. So, it should benefit from V4.5 in theory. All I know is that more custom models (non autogen buildings), the more you will see an improvement in V4.5. CityScene users here are reporting big improvements with V4.5. As far as the Netherlands goes, I am not familiar with all the ways it is constructed internally. I will touch base with the rest of the team and see how V4.5 is impacting non-Cityscene products.
  6. I just stumbled across this post. We are currently working on a CityScene Charleston project.
  7. That is awesome. Yes, with P3D V4.5, you should see huge improvements in CityScene products in two ways: Load times when starting within the scenery are greatly reduced. Load times when entering the scenery area from outside the region are greatly reduced. Perhaps #2 above is even more important as it affects in-flight visuals. Enjoy V4.5. I really feel like it is a game changer for complex scenery products.
  8. As most of you here already know, P3D V4.5 was released today. This new version addresses the load time "bug" that we located several months ago. For those that do not know, this "bug" has been present ever since the original FSX release back in 2006. It is became more noticeable as terrain scenery products, like CityScene, provided tens or hundreds of thousands of custom scenery objects (non-autogen). Facts that we learned about the load time "Bug": The more complex the scenery product, the longer the load time. The more 3rd Party scenery products installed on the user's system, the longer the load time. When you combine the two above, load times seem to increase almost exponentially. When you have long load times when starting a flight within a scenery area (i.e Barcelona, Orlando, Gold Coast), these long load times will also impact visual performance when approaching the scenery area during flight. This can result in building textures that repaint slowly, blurry terrain, etc. The faster the aircraft, the more the long load times impact your terrain visuals. Once the scenery is fully loaded however, the performance issues go away on any supported sim platform. P3D V4.5 should make your CityScene product experience, in particular, much more enjoyable. The long delays at the 6% loading mark should be dramatically decreased. As a result, the loading of CityScene areas when approaching from well outside should go much, much smoother. Other comments related to the V4.5 release: For Orlando users, I would now recommend using the custom residential building option over residential autogen objects with V4.5. It is no longer necessary to worry about the load time impact that the Orbx libraries have on scenery products, especially CityScene products. We will need to update the internal product documentation to reflect this. As far as I know, V4.5 changes should not impact "photoscenery" or autogen load times. The fix specifically addresses non-autogen scenery objects that are extremely abundant in an area. I would not expect the load time anomaly to ever be fixed in FSX or FSX-SE, as these products do not appear to be supported anymore when it comes to sim engine enhancements. I want to thank all the devs at LM for making this issue a priority when we brought it to their attention several months ago. As a scenery developer, addressing this issue is a real game changer and we will all benefit from it. I also want to thank our customers for their patience, while waiting for us to come up with a solution in Orlando. This is related to both the P3D V4.5 fix and also Orlando V1.1. Remember, the P3D V4.5 fix ONLY applies when the simulator is stuck for a long time at the 6% mark while loading scenery (10-20 seconds is normal). If you are having load time issues prior to or after the 6% mark, that is another topic and should be addressed elsewhere. Cheers all, Allen Kriesman
  9. FWIW, here is what the Disney and Epcot area should look like.
  10. Hello, I just checked the scenery and both Spaceship Earth and Cinderella's castle are indeed present (P3D V4 as tested) A couple of people have mentioned this though. You might look at your scenery layering and make sure that the FTX_AA_ORLANDO layer is above all other layers, except for FTXAA_ORBXLIBS. Also, just a thought. Make sure that your default "Orlando" layer (not the FTX_AA_ORLANDO) is disabled if you are running P3D V4.
  11. Bill, I just checked the scenery and both Spaceship Earth and Cinderella's castle are indeed present. A couple of people have mentioned this though. You might look at your scenery layering and make sure that the FTX_AA_ORLANDO layer is above all other layers, except for FTXAA_ORBXLIBS.
  12. Guys, Unfortunately, it was pointed out to us that switching back to custom residential buildings will cause duplicate buildings in many locations. Something must have went wrong in the last production build. The problem is being addressed and a new patch should be out within 24 hours. This problem will only appear if you have V1.1 and switch back to custom residential buildings (instead of autogen houses). We now have to maintain 2 sets of AGN files to support the new options, which adds another layer of complexity to FTX Central. So, for those that have not yet installed V1.1, I would just wait for the update (hopefully tomorrow).
  13. Carlos, I really don't know the answer to this as I don't have that product. One of our beta testers had the product and tested it. I was not even aware that people were making modifications to support this product.
  14. There are no autogen buildings used near either the KMCO or KORL airport. I just checked the terminal building at KMCO are present for me. Also, the autogen building option only replaces custom houses with autogen buildings. Commercial buildings and High Rises will always be custom buildings.
  • Create New...