Author Topic: GSX reading altitude correction file  (Read 2343 times)

ManojYadavKp

  • Newbie
  • *
  • Posts: 25
GSX reading altitude correction file
« on: November 21, 2017, 11:50:40 am »
Hello,

I'm facing the same issue as mentioned in this thread: http://www.fsdreamteam.com/forum/index.php/topic,15379.0.html

In my case, I'm using this scenery: http://www.flightsim.com/vbfs/fslib.php?do=search&fname=muscat_ooms_fsx.zip

My priority in the Scenery Library is correct, with the Addon Scenery at the highest priority.

Any idea why this would happen?

Thank you.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: GSX reading altitude correction file
« Reply #1 on: November 21, 2017, 04:22:59 pm »
The problem is caused by the scenery unusual size for an AFCAD, as explained here:

http://www.fsdreamteam.com/forum/index.php/topic,16598.msg118066.html#msg118066

ManojYadavKp

  • Newbie
  • *
  • Posts: 25
Re: GSX reading altitude correction file
« Reply #2 on: November 22, 2017, 12:34:48 pm »
Got it! Thanks.

ManojYadavKp

  • Newbie
  • *
  • Posts: 25
Re: GSX reading altitude correction file
« Reply #3 on: December 09, 2017, 03:37:41 pm »
The problem is caused by the scenery unusual size for an AFCAD, as explained here:

http://www.fsdreamteam.com/forum/index.php/topic,16598.msg118066.html#msg118066
Instead of manually adding this, will it be possible to edit it inside GSX settings? Can that be done?

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: GSX reading altitude correction file
« Reply #4 on: December 11, 2017, 01:49:00 pm »
Quote
Instead of manually adding this, will it be possible to edit it inside GSX settings? Can that be done?

What's would be the difference ? You would still have to enter the same number. Just do it in the .INI, as explained in the post. The only thing you must be careful, is to insert the parameter name correctly, respecting upper/lower case, as I've said in my last post of that thread:

Quote
And, the command is case sensitive, so it should have been entered as such:

airportCacheMaxBGLSizeBytes = 4000000