Cloud9 Support > General Cloud9 technical support

AES

(1/1)

geoffbecks:
Does this mean there is a possibility of some more of their airports working with AES in the future,??  :P

virtuali:
I'll say is very unlikely to affect existing Cloud9 products.

Those will be mantained and their installers will be updated in order to give users less problems with our products and/or better compatibility with newer OS and OS upgrades, but we don't plan going back to work on the Cloud9 sceneries, unless a showstopper bug that wasn't found until today would eventually surface. But no new features.

The main advantage of this agreement for existing Cloud9 users, will be ( hopefully ) better support and less installation problems.

However, since we now have the freedom to reuse parts of the work made for Cloud9 to create new versions of those sceneries, if and when we'll decide to remake any of them, we'll try to take into account AES compatibility.

geoffbecks:
Correct me if Im wrong but does it not just entail you giving permission to Aerosoft and access to the program for the work to be carried out at their end in order to get the sceneries to work with AES and bring these airports to life.?? I would love these to get the workover and wake them up.

virtuali:

--- Quote from: geoffbecks on November 29, 2009, 01:19:35 am ---Correct me if Im wrong but does it not just entail you giving permission to Aerosoft and access to the program for the work to be carried out at their end in order to get the sceneries to work with AES and bring these airports to life.??
--- End quote ---

No, permission it's not enough.  It might work for some sceneries, but not all of them.

Some sceneries (like KLAX) were made in a way that the main buildings and the jetways were modeled as a single piece, which has a positive impact on fps (that's why KLAX is faster than EHAM, that's why EHAM had AES), but would require us to go back at modeling of the original KLAX and separate the objects, which is something we were not willing to do for several reasons: one because this would mean lowering the fps even for users *not* using AES OR, to the very least, to distribute and mantain two different separate set of files, which still is a burden. And, of course, there would be the actual work involved that someone has to do and, it couldn't be economically justfied ONLY with the supposed increased of sales given by AES, which is not very significant, I have to say.

We decided to support AES with FSDT, mostly as a curtesy to our users, not because we see any particular increase of sales because of it.

It certainly doesn't *hurt* sales having it, that's why we support it for FSDT, since it doesn't cost anything to do the sceney in a certain way, if this is taken into consideration from the START. But the increase in sales that can be attributed to AES is so small, that it simply can't justify going back to a scenery that was developed long ago, before AES came out, and retro-fit it doing actual modeling work on it.

With not so much additional work (in case of KLAX), we could update the scenery with the new runways, port it to FSX, and have a new product, with AES included.

Navigation

[0] Message Index