I found out that altitude settings for this scenery crossed the scenery borders and affected other FS2K default sceneries. Practically speaking, you still were able to take-off from, say EBBR, but once you crossed ebcv's default altitude (201 feet), FS2K did not allow you to descend lower than that any more, hereby prohibiting landings on other airports with a lower altitude.
This update to ebcv10 corrects this issue and a few other minor items. By doing so, I had to set ebcv's altitude to 62m (203,4 ft) which is 1m higher than in v1.0. This won't affect flying very much.
I did not yet receive any feedback on this issue but if you were exposed to it, please accept my apologies for the inconvenience. FS2K scenery engine is new and Microsoft did not document the new features yet. So designing a new scenery for FS2K is a rather tiresome trial and error process.
Installation: just unzip the *.bgl file and overwrite the previous ebcv.bgl file.
