While on the topic of [extra_user_folder]
Deploying a scenery package for foo under the the Documents folder yields the following structure
->Documents\Aerofly FS 2\addons\scenery\foo\images\a.ttc
->Documents\Aerofly FS 2\addons\scenery\foo\images\b.ttc
->Documents\Aerofly FS 2\addons\scenery\foo\images\...
->Documents\Aerofly FS 2\addons\scenery\foo\places\foo.toc
->Documents\Aerofly FS 2\addons\scenery\foo\places\foo.tsc
->Documents\Aerofly FS 2\addons\scenery\foo\places\...
One benefit of this structure (in the absence of a scenery manager tool) is the ability to disable images or places
on a per scenery package level by hash tagging the the image or places folder
->Documents\Aerofly FS 2\addons\scenery\foo\#images\a.ttc
->Documents\Aerofly FS 2\addons\scenery\foo\#images\b.ttc
->Documents\Aerofly FS 2\addons\scenery\foo\#images\...
->Documents\Aerofly FS 2\addons\scenery\foo\places\foo.toc
->Documents\Aerofly FS 2\addons\scenery\foo\places\foo.tsc
->Documents\Aerofly FS 2\addons\scenery\foo\places\...
However if you want to move the scenery packages off C: drive
using [extra_user_folder] the corresponding hierarchy does not work
E:\Aerofly\MyScenery\scenery\foo\images\a.ttc
E:\Aerofly\MyScenery\scenery\foo\images\b.ttc
E:\Aerofly\MyScenery\scenery\foo\images\...
E:\Aerofly\MyScenery\scenery\foo\places\foo.toc
E:\Aerofly\MyScenery\scenery\foo\places\foo.tsc
E:\Aerofly\MyScenery\scenery\foo\places\...
However the following structure does work
E:\Aerofly\MyScenery\scenery\places\foo\foo.toc
As well as
E:\Aerofly\MyScenery\scenery\places\foo\places\foo.toc
but does prevent
E:\Aerofly\MyScenery\scenery\places\foo\#places\foo.toc
to disable a package presumably since the "places" token has already been detected in the path
Is there a reason these Documents and [extra_user_folder] hierarchies need to be different?