Jump to content

Pilot Plus

External Developer
  • Posts

    195
  • Joined

  • Last visited

Posts posted by Pilot Plus

  1. 1 hour ago, razalom said:

    Purchased Bristol the other day and for whatever reason its basocally unflyable for me in VR (and even on the Monitor is pretty bad). All other purchased and premium airports have no issues. Even if I drop the settings way down the stuttering in both modes is bad but of course in VR its not a good idea.

     

    Have deleted rolling cache, have deleted the content.xml file, have check the LOD sizes for both in the UserCfg file and they are 1.15 or lower

     

        {Terrain
            LoDFactor 1.150000
        {ObjectsLoD
            LoDFactor 1.000000
       

    VR

        {Terrain
            LoDFactor 1.000000
        {ObjectsLoD
            LoDFactor 1.000000

     

    The Community folder I have basically removed everything and still the same issue. Disable the addon and EGGD area works fine. Any clues as really like this Airport.

     

    AMD 5800x

    RTX 3090

    32GB DDR4 RAM @ 3600

     

     

     

    Hi @razalom

     

    Sorry to hear you are having issues.

    We have just received & assigned your support ticket, one of the team will continue to assist you on the support platform.

     

    PP

    • Thanks 1
  2. On 9/1/2021 at 4:49 PM, renault said:

     

    Hi Adam

     

    I have rolling cache disabled on my machine. I have tried setting LODs to 3.0  seven times now.  Six of those tests, resulted in a "lockup" when

    the "Fly" button was pressed . One time  out of the seven the scenery loaded normally.

     

    Leaving LODs set at 2.0 results in a flawless load.  I can only conclude that as both you and I found,  it can work  with a LOD setting higher

    than the maximum MS2020 setting of 2.0 , but I don't feel that this is reliable advice based upon my testing. 

     

    But I'm glad it worked for you

     

    I had the Dev Console active , but could not find anything that was odd.  I have 64GB ram and both it and VRAM were very underutilized 

     

    I have copied Pilot Plus @Pilot Plus on this note, as they may be able to shed some light on a possible root cause of this behavior, assuming that

    the requirement to keep LOD set to a maximum of 2.0  is not propriety to their  coding for the scenery.

     

    Cheers

    Pete

     

     

     

    Hi Both,

     

    The LOD setting seems very hit and miss and inconsistent. In office, both our machines have identical hardware - yet one can load consistently with 3.0, and the other needs to be reduced to 2.0.

     

    Our guess currently is that this LOD factor has some impact on the 1m resolution mesh that is abundant at the airport, and perhaps why this option affects EGGD, but other airports without DEM are not as affected badly.

     

    We are investigating potential ways in which me may be able to squeeze more out of EGGD without harming the product quality and taking in user feedback.

  3. Hi,

     

    Thanks for your kind comments and for your request. As we are a small development team (primarily 2 full time developers) we have to allocate our resource efficiently and based on where the majority of our audience is. At the moment we have not began work on EGTK for X-Plane, but it is a possibility for the future.

    • Like 1
  4. 42 minutes ago, EasternT3 said:

    @Pilot Plus I’ve seen/heard you have EGGW on your development plan but I’m hoping for the future you’ll consider EGNX, EGCN and EGNJ, 3 great airports with a fair bit of traffic.  (Albeit I’m a bit biased as they are my locals)

     

    Thankyou for your suggestions,

     

    We are yet no officially announce any of our future airport projects! - the latest will always be found on our roadmap: https://pilotplus.io/roadmap/

    • Like 2
×
×
  • Create New...