Afghan full map all runways extremely low LOD (No tarmac) [BUG]

[mossbros]

So over the week me and a friend decided to trial the Afghan map and to our surprise after trialling the 'full' map listed on the store page we both came into a bug where the level of detail for the map was incredibly low on all airfields, Camp Bastion, Kandahar and other were grass runways with no FOBS or embankments. 

On discovering this I went back to the store page and instead switched the trial to the [southwest Afghanistan] trial rather than the full one and it seemingly fixed it, I see this as quite a big bug as people buying the full map in early access will be getting a bugged version

(I'm assuming there's simply something wrong with a config file somewhere, as when we changed the trial to the sectioned region the files didn't even need downloading) 

Obviously, the problem with this is that people pre purchasing the full map, currently are getting a fully broken version. 

[BIGNEWY]

12 minutes ago, mossbros said:

So over the week me and a friend decided to trial the Afghan map and to our surprise after trialling the 'full' map listed on the store page we both came into a bug where the level of detail for the map was incredibly low on all airfields, Camp Bastion, Kandahar and other were grass runways with no FOBS or embankments. 

On discovering this I went back to the store page and instead switched the trial to the [southwest Afghanistan] trial rather than the full one and it seemingly fixed it, I see this as quite a big bug as people buying the full map in early access will be getting a bugged version

(I'm assuming there's simply something wrong with a config file somewhere, as when we changed the trial to the sectioned region the files didn't even need downloading) 

Obviously, the problem with this is that people pre purchasing the full map, currently are getting a fully broken version. 

Hi, 

apologies but the trial is currently bugged, and is showing low detail in areas that should have detail like at the airfields. 

This has been reported and should be fixed soon. 

thank you