But i think you miss a big point when you say it's no dramatically changes at ENBR.
New taxiways, some of them opened already and new Terminal underway.
Nothing comparable to the changes at KORD, for example. And, fact a new Terminal is not completed, it's reason enough not to think about an update right now.
Well, of course you are right in this, but...., it's a big but, in our region (Norway) there have been so many negative comment's on your (Cloud9) scenery, because of the long ongoing flickering apron\taxiway issue, that you made a fix for (i would say," fix lite"), some time ago.
If people comments things on their our community places, instead of reporting problems on the developer's forums, the one and only effect would be that fixes will be delayed, since we can't obviously go reading forums everywhere for comments, and much less if they are in Norwegian...it's obvious that, if there a 2-3 people complaining on our forums, we can only assume the problem is minor.
And one more thing, in FSX we don't even have moving jetway's!!!!
It wouldn't be the first FSX scenery that has fixed jetways. In fact, we are one of the very few developers that adds moving jetways in FSX. The problem is, FSX doesn't support well the kind of jetways at ENBR, which are unusual because they move only up/down, it gave too many problems. I don't think other FSX sceneries with static jetways (basically all of them, except ours...) are getting low sales because of that.
(Many simmers have been thinking tree or four times before bying this sceney.)I'm sure, if you had redone ENBR up to date and at same level of detail like JFK and Zurich, your sales also had been much better. The main reason for low sales with ENBR, are this factor's and that is the true.
No, it's not. Most of the sales for a scenery are made in the very first months, from there you can assess how the final sales will be.
ENBR was released in Feb. 2007, even before FSX SP1. At that time, there was no flickering issue, the problem became apparent only after FSX SP2 was released, at the end of the year, because both SP1 and SP2 changed many things regarding ground polygons, which caused the flickering, but sales were already very low compared to other sceneries even when there was no flickering.
Both PHNL and KDFW had flickering issues in their initial release, possibly even more annoying that ENBR, it didn't affect sales at all, even before the solution was available.
The real reason is, there's no enough interest for a scenery in Norway, it's the same reason why we stopped doing Italian sceneries long ago.
In any case, the whole issue is, this is a scenery published and (still) owned by Cloud9. We are not Cloud9, Cloud9 was just our customer for the activation system, and the former scenery designer that did ENBR now work with us, but when we took over support for Cloud9 products, we clearly said support would only mean support users with reactivations, keep the sceneries usable with regard to forward compatibility with our later sceneries and eventually fixing problems that might prevent loading the scenery due to OS updates, etc.
Keep the scenery updated to reflect the real world changes, is really outside of the scope of the support agreement we have with Cloud9. Yes, we *can* do a remake of scenery, if we want, but then it's our choice about which sceneries would be commercially feasible for a remake, and I'm afraid ENBR doesn't fit the description.