Jump to content

EmilG

Members
  • Content Count

    321
  • Joined

  • Last visited

  • Days Won

    16

EmilG last won the day on January 25 2014

EmilG had the most liked content!

Community Reputation

239 Excellent

About EmilG

  • Rank
    Gliderpilot

Recent Profile Visitors

5675 profile views
  1. Guys, it has became very apparent that OOM issues, though possible in heavy environments, are not anymore specifically related to LGTS. It has nothing to do with the way we developed it as some people suggested, or anything of that sort. As I will say again, it's a matter of polygons and textures when the user is inside the area of interest. That has been tested extensively and trimmed even further to allow significant amount of free VAS in the latest patches. Another 'symptom' of bad or 'problematic' development is judged by the footprint that is left after you leave the scenery area. And to
  2. download v3, install Default setup. re-run and choose the LITE setup you need.
  3. Now you see the 'troubled' world of the developer who wants to 'push the limits' in FSX (p3dv2.0 is another story-more flexible). Having NGX always in mind, the ideal testing would involve getting VAS readings on a clean FSX setup. That would be the true VAS load. Then one by one, after each add-on, test again. Try different display settings, test again. This would of course take ages, and the amount of testers that would have to participate, to include all possible add-ons and hardware setup combinations would be more than the actual buying community! inefficient. Our testing team was com
  4. That's what I meant, we did not add custom autogen models, because 1) it would create many conflicts with other add-ons and 2) the models would not 'blend in'. There is no other way to control the scenery density other than the patch.
  5. There is no autogen in the scenery, everything is controlled from the .BGL files, which we are optimizing from here to deliver the patch versions. You will have noticed the nice blend of the scenery models on top of the terrain, this is because the terrain is 'shaded' to match the overlaying models. This would not be possible with autogen, let alone the 'hell' we'd have gone through if we had our own custom autogen models (thank you FTX). The autogen slider will only control 3D lights.
  6. yes..it's named Thessaloniki X City Configurator [v3.0].exe
  7. Thanks, appreciate that, like said before I do want you to 'fly the scenery' as much as you do. So this patch is the best we can do to allow good visuals and some more room for your other 'goodies' That's almost a 700mb file, so I guess it'll take some more time. About procedure. Once you receive v3.0, just run the default setup once. Then, you are free to choose the one you want.
  8. A new City Congifurator (v3.0) should be at your AS accounts. The LITE II version is further optimised, keeping visual reduction at minimum possible. From some testing, I gained another 200-300MB on top of the 500MB you gained from v2.0. On my setup, the lighter version gives me less memory load than FT Dubai. (I don't own MMMX-cant tell). With more than 1.1GB of total free space (on the NGX) on our advised settings, we are claiming much less than the '''fair''' VAS for a detailed scenery as this is.
  9. You can attach here or via email to : support@flightsimdevelopmentgroup.com
  10. Guys, can you please send here your DLL.XML and EXE.XML files which should be located user %APPDATA%\Microsoft\FSX We can make some good use of those, we can run a few 'diagnostics' on them and provide more help. Thanks!
  11. Hi again, glad that this 'by mistake' change in setup fixed your problem I understand that possibly other add-on sceneries make use of the Scenery Density slider more than we do. If it is set at Ext.Dense before&during the flight it can load up the memory. LGTS is 'insensitive' to that slider, so you can keep it at normal to keep VAS at bay, without loss of our scenery density on final. (btw: If you want a VFR tour on the Twotter, make sure you reload the Default stuff ) Your other add-ons possibly give you the extra 500Mb above what I have on the NGX (3.1-3.2GB) in my vanilla s
  12. Just to add up to what Oliver said above. The configuration posted above by me (post 75) gives you 800-1GB (!) of free VAS on the NGX with almost all the eye-candy you want on your approach. That's pretty much what Flytampa's Dubai gives you too. It's up to you to spend all that free memory by selecting other settings than those advised, multiple add-ons- FTXG, weather, etc..etc.., or whatever else you want.
  13. Reason we are sure about our product is all about testing, and this has been tested with various diferrent setups. I will make our results public if need be, but for now here is what LGTS will gives me on a vanilla setup FSX SP2 (+REX) LITE II configuration ( LITE gives same results +50-100MB) All options active from our manager tool I seriously believe that a 800MB-1000MB margin for memory is more than enough. FSX Settings VAS READINGS Loaded at the Apron ON APPROACH FROM LGAV (FLytampa) LANDING (important as all the grass models start loadin
×
×
  • Create New...