Hi there!
I went in and checked my rework of Achim's Methwold and the bridge is there, due north of the main runway.
I haven't noticed any problem, other than the different approach you and I take at our GSL work. I work according to a given scenery and I worry about gobs only when the notorious gob overlap bug occurs. I save the single scenery layout and all the objects I placed into an empty cfs2.gls using the MB built-in key combos taught to us by Lindsay Watts.
I then exit MB, go to the root \GSL folder and rename cfs2.gls to the scenery it reflects, in this case as an example, JHS_UK_Methwold.gls.
Then I add this single *.gsl file to a cumulative, theatre dedicated cfs2.gls with GSLEdit. Afterwards I archive away the reworked scenery *.lay and *.gls in case I need to go back and make changes. A necessity which arises every so often, for new objects available or when I discover an historical aerial view and realize my work is quite fictional.
I seem to understand you work at a single *.gls file, for upload purposes which changes your perspective completely. Hence the problem of a bridge laying over two gobs.
I prefer having single *.gls files always at hand, this also allows me creating more sparse early war and thick late war layouts. Methwold and its bridge work fine in my cumulative cfs2.gls, I never noticed a problem, even if it covers two gobs. I have several airports covering more than one gob, mostly with forest patches and trees, that I place away from the airport.
Have a nice w-end!
Stef
Bookmarks