FSDreamTeam forum
Products Support => Los Angeles support FSX/P3D => Topic started by: KingCat on September 17, 2011, 06:51:31 pm
-
When can we expect AES support for KLAX?
Jon
-
It's linked to the destiny of the FS9 version: if we'll end up doing it, AES support will come but, if KLAX will remain FSX-only, GSX is not too far away, and will be free to use all our airports.
We had a longstanding agreement with Oliver, that we'll support AES as long we do FS9 versions of our products, since we don't have a comparable solution for FS9.
-
Oh, that's really too bad then, since GSX will not support moving jetways.
I guess I will seriously have to consider if I'm going to buy this product. It looks wonderful, but if I have to work without moving jetways, that's a showstopper for me. :( This sounds the same like having a Ferrari, but with a steeringwheel that doesn't move...
Jon
-
Oh, that's really too bad then, since GSX will not support moving jetways.
??? KLAX HAS moving jetways, right now.
What GSX doesn't do, is to *add* moving jetways to 3rd party scenery that don't have them, but all our FSX sceneries always had moving jetways, without AES.
-
Oh, that's really too bad then, since GSX will not support moving jetways.
??? KLAX HAS moving jetways, right now.
What GSX doesn't do, is to *add* moving jetways to 3rd party scenery that don't have them, but all our FSX sceneries always had moving jetways, without AES.
Its not the same thing, FSX Generic Jetway animation is not accurate nor does it work properly (Nothing to do with FSDT) Plus the support for second Jetway animation is not supported either. This may be a deal breaker if AES support is not going to happen for LAX.
-
Its not the same thing, FSX Generic Jetway animation is not accurate nor does it work properly (Nothing to do with FSDT) Plus the support for second Jetway animation is not supported either. This may be a deal breaker if AES support is not going to happen for LAX.
One of the things we are planning for GSX (maybe not the initial release, but it's definitely planned), is to replace the FSX jetway animation system entirely. We are bit by bit replacing all the default things we don't like, KDFW and KLAX, for example, don't use any default runway lights/papis, we'll eventually get to the jetways too...
In any case, the issue raised was "I have to work without moving jetways, that's a showstopper for me.", as if the jetways were static, but that's no the case with KLAX, that has moving jetways right now.
-
In any case, the issue raised was "I have to work without moving jetways, that's a showstopper for me.", as if the jetways were static, but that's no the case with KLAX, that has moving jetways right now.
That's not the reason why I posted this topic. I already knew that FSDT KLAX has moving jetways. But that's not the same as AES-support. In fact, even the default KLAX has moving jetways, and that's also not the same as AES-support. I'm sure I don't have to explain the differences between default moving jetways and AES-jetways.
Saying that AES-support is depending on whether or not a FS9-version is going to be developed, makes no sense to me, because I think it's pretty clear that's not going to happen. You've said it yourself that it's going to take months to adapt the FSX version to a suitable FS9-version (time better spent on new FSX products).
I just hope that this topic gets more comments from other users who also would like to see AES-support for the FSX version.
Jon
-
That's not the reason why I posted this topic. I already knew that FSDT KLAX has moving jetways. But that's not the same as AES-support
Maybe that was your intention, but as it was written, it sounded like you thought KLAX had static jetways.
I'm sure I don't have to explain the differences between default moving jetways and AES-jetways.
Which is why we'll likely revamp the FSX default jetways system in GSX too, because we don't like it too, main reason because we don't have any control over it.
Saying that AES-support is depending on whether or not a FS9-version is going to be developed, makes no sense to me
It makes sense, because we'll provide our own FSX solution soon enough, for free (in our sceneries). It's not that we are happy having users spending additional money to add features to our product that we could offer ourselves.
We supported AES so far only because we didn't have anything comparable for FS9 and never had the slightest intention to do any research in doing it. We agreed about this with Oliver more than 2 years ago (when he first learned about GSX), and he understood our position.
because I think it's pretty clear that's not going to happen. You've said it yourself that it's going to take months to adapt the FSX version to a suitable FS9-version (time better spend on new FSX products).
I haven't said anything like that. I only said it's not decided yet, because we still haven't started looking into it. I clearly explained what the issues are, so people wouldn't mistakenly thing we don't want do to the FS9 version for reasons different than sound technical problems.
-
In any case, the issue raised was "I have to work without moving jetways, that's a showstopper for me.", as if the jetways were static, but that's no the case with KLAX, that has moving jetways right now.
That's not the reason why I posted this topic. I already knew that FSDT KLAX has moving jetways. But that's not the same as AES-support. In fact, even the default KLAX has moving jetways, and that's also not the same as AES-support. I'm sure I don't have to explain the differences between default moving jetways and AES-jetways.
Saying that AES-support is depending on whether or not a FS9-version is going to be developed, makes no sense to me, because I think it's pretty clear that's not going to happen. You've said it yourself that it's going to take months to adapt the FSX version to a suitable FS9-version (time better spent on new FSX products).
I just hope that this topic gets more comments from other users who also would like to see AES-support for the FSX version.
Jon
Another rude prospective customer >:(
-
Until GSX is fully implemented with correct jetway animation which will be some time in the future, could we not get AES for LAX? It should be up to the user if they want to spend money for the AES credits. Can we please get AES for this airport? You said yourself the jetway animation will not be in the initial release. The jetway movement now in your scenery sucks compared to AES.
-
Another rude prospective customer >:(
Unfortunatley anything goes on the net and people tend to say things they generally probably wouldn't if they were talking to Umberto face to face.
In all seriousness, I knew people liked moving jetways, but I had never seen a complaint about the actual animation of them. Personally I dont really even care since I am usually busy preparing to fly rather than fixating on the animation sequence of the jetways and to me it would be a waste of developer time and resources to pour more time and energy into improving it. I wonder if real airline pilots even really watch them extend or retract, or if they can even see them from the cockpit? I doubt it.
Maybe a groung crew, jetway, and AI sim would be a good idea for Aerosoft to develope in the future since I see a lot of posts where people are more concerned about these features than actually simulating flight.
-
Until GSX is fully implemented with correct jetway animation which will be some time in the future, could we not get AES for LAX? It should be up to the user if they want to spend money for the AES credits. Can we please get AES for this airport? You said yourself the jetway animation will not be in the initial release. The jetway movement now in your scenery sucks compared to AES.
That would be an ideal compromise, quite agree with you. I am sure Oliver could have his arm twisted ever so slightly.
-
Another rude prospective customer >:(
Unfortunatley anything goes on the net and people tend to say things they generally probably wouldn't if they were talking to Umberto face to face.
In all seriousness, I knew people liked moving jetways, but I had never seen a complaint about the actual animation of them. Personally I dont really even care since I am usually busy preparing to fly rather than fixating on the animation sequence of the jetways and to me it would be a waste of developer time and resources to pour more time and energy into improving it. I wonder if real airline pilots even really watch them extend or retract, or if they can even see them from the cockpit? I doubt it.
Maybe a groung crew, jetway, and AI sim would be a good idea for Aerosoft to develope in the future since I see a lot of posts where people are more concerned about these features than actually simulating flight.
I suppose to some, airport purchases are based on wether it has AES support or not. Some maybe prefer the immersion factor having AES when simulating real life airline operations. And then there are those who park at the threshold, and gun it. I think once GSX is released, this issue will probably never rear it's ugly head. :)
-
Until GSX is fully implemented with correct jetway animation which will be some time in the future, could we not get AES for LAX? It should be up to the user if they want to spend money for the AES credits. Can we please get AES for this airport? You said yourself the jetway animation will not be in the initial release. The jetway movement now in your scenery sucks compared to AES.
+1
But I doubt AES-support is going to happen. Simply because AES is a competitor for GSX in FSX.
Jon
-
Dear all,
Once upon a time I bought cloud9 KLAX hoping it get AESed some day. Unfortunately this never happened. In fact I never flew into cloud9 KLAX. An abandoned installation.
And now, years later and after a late move to FSX, the same thing again with KLAX?
What a disappointment!
Until now, I purchased every single airport from FSDT and I admire your work. You are the best.
But without AES it is a showstopper for me too. And an improved GSX cannot be expected soon.
Therefore, I would kindly encourage you, Umberto and the FSDreamteam, to re-consider the AES issue.
This would be highly appreciated.
Have a nice day
Goetz
-
But without AES it is a showstopper for me too. And an improved GSX cannot be expected soon.
GSX is not very far away, and we believe what it has to offer, even in the initial release, which will be free to use at our airports, will far compensate the fact that it will still use the FSX default jetway animation system, which might be a target for improvement in its future releases.
And, although GSX works automatically at every airport, it HAS the ability to be specially optimized for a specific airport, and KLAX has already been made taking into account this. We'll need to have an important airport specifically tailored for GSX to showcase it as best as possible, and there's no better choice right now than KLAX.
-
Another rude prospective customer >:(
I wonder if real airline pilots even really watch them extend or retract, or if they can even see them from the cockpit? I doubt it.
Sean,
On most aircraft the captain can see the jetway operator, but they only look if the gate agent is attractive!
-
I can only agree. Was same for me.
No AES......No KLAX.
Sorry for my bad English.
greeting
Michael
-
I can only agree. Was same for me. No AES......No KLAX.Sorry for my bad English.
GSX will offer you similar functions, way better graphics, sounds and animations, and will free to use at KLAX.
-
But without AES it is a showstopper for me too. And an improved GSX cannot be expected soon.
GSX is not very far away, and we believe what it has to offer, even in the initial release, which will be free to use at our airports, will far compensate the fact that it will still use the FSX default jetway animation system, which might be a target for improvement in its future releases.
And, although GSX works automatically at every airport, it HAS the ability to be specially optimized for a specific airport, and KLAX has already been made taking into account this. We'll need to have an important airport specifically tailored for GSX to showcase it as best as possible, and there's no better choice right now than KLAX.
Umberto, out of curiosity, are you able to tell us what kinds of special KLAX specific things you guys are putting in to GSX? I am very much looking forward to GSX and now that KLAX is out I'm wondering what you guys have in mind.
-
Umberto, out of curiosity, are you able to tell us what kinds of special KLAX specific things you guys are putting in to GSX? I am very much looking forward to GSX and now that KLAX is out I'm wondering what you guys have in mind.
Although GSX is automatic, it's likely there will be specific issues depending on the airport configuration.
Take B50 at KLAX for example, the normal Pushback direction for all the parkings on the same row would be "Right", so you'll end up with aircraft nose pointed towards the exit, and this is how is configured in our AFCAD, just like the default AFCAD, so GSX would normally read that info, and act in consequence OR present the user a Left/Right choice, if the parking is labeled as "Both".
But B50 is special, because it's the first parking in that row, and it's too close to the wall so, a "Right" Pushback that would orient the airplane correctly towards the exit, would result in the airplane going being pushed inside the wall, and a "Left" Pushback would result in the wrong orientation for the exit, facing the wall.
For those special cases, GSX can have its specific "FSDT KLAX" configuration file, that will tell in this case not to use the standard algorithm to find the path, but go to a specific AFCAD node, for example the one at the exit.
Other airport-specific customizations includes the ability to specify parking size restrictions (overriding the AFCAD size) in order not to place service vehicles inside buildings, the availability of specific Visual docking aids at certain gates, etc.
And, we can also specify the handling operator for each airport (if we want), and having vehicles with different liveries at every airport, it's just a matter of providing the operator logos, without having to repaint the model entirely, so it's also easy to do, even for users.
All these customizations can be linked to a specific AFCAD so, we can configure GSX differently depending on which scenery for a specific airport is installed, and this is valid for both default airports and any 3rd party airport, without requiring any interaction or special support from the original developer. In fact, even the current version of ParkMe already comes with a customization made for FlyTampa's Hong Kong, which adds some Docking System there, and this was just ParkMe in its current status: the GSX customization features are far more advanced.
-
Sounds very cool. I was thinking about the gates where there's a wall to one side and how one would be pushed back from them. Very clever. Can't wait.
-
I have to agree that I would like AES for KLAX but it isn't a showstopper - I already bought KLAX.
I think the main issue is with the jetways - that's one area where AES shines. I think a modification of the default animation would be a good idea for GSX but the double and triple jetways need to be animated as well. Even if KLAX was AES'd, we wouldn't get the double and triple jetways because it is my understanding that FSDT has never separated the 2nd and 3rd jetways from the terminal which means that they are not animated at the FSDT airports with AES (I have not checked every airport but I believe Oliver stated this at one time).
When AES v2 is released, I am sure it will be improved quite a bit. It is expected to have a lot of new features and I fully expect to use GSX and AES at the same time. I love AES but I don't like that it is not available everywhere (for obvious reasons). For the non AES airports, GSX will be great.
Umberto, since GSX is so close, is it possible to post an updated list of the features in the GSX backdoor forum? Right now, the features are buried in a 156 post thread and I am not really clear on what it will include. Is it in beta? Will it have left side cargo loaders? Will the pushback be fully automated? Will their be a utility for configuring the exits? Maybe if there was something more concrete, people may be more comfortable with waiting for GSX.
-
I think the main issue is with the jetways - that's one area where AES shines
It's only area that GSX doesn't cover at the *moment*, but for everything else, you'll see when GSX is out...
it is my understanding that FSDT has never separated the 2nd and 3rd jetways from the terminal which means that they are not animated at the FSDT airports with AES (I have not checked every airport but I believe Oliver stated this at one time).
The only reason why we haven't prepared double and triple jetways for animation (except JFK, were we have the working A380 jetways), it's because FSX can't use them, but iss to be expected that, when we'll work on replacing the FSX jetway animation system, this will not be an issue anymore.
When AES v2 is released, I am sure it will be improved quite a bit. It is expected to have a lot of new features and I fully expect to use GSX and AES at the same time
It will surely be improved but, I seems to have read that will still be cross-platform on FS9 and FSX, which means it will never have the same animation quality, especially for humans.
I love AES but I don't like that it is not available everywhere (for obvious reasons). For the non AES airports, GSX will be great.
Our goal is to make GSX the preferred option everywhere, not just at non-AES airports, you'll want to use AES only for the jetways, until we remade them.
Umberto, since GSX is so close, is it possible to post an updated list of the features in the GSX backdoor forum?
There will be updates for it, of course. Right now, the features are buried in a 156 post thread and I am not really clear on what it will include.[/quote]
Is it in beta?
We are keep testing it every day, since many months, since it's a product that requires way more testing than a scenery.
Will it have left side cargo loaders?
Maybe not in the initial release, but we are planning a specific GSX Cargo expansion, which will include not just animated vehicles too see, but even actual *operations* to do, like assignments with efficiency evaluation, profit to be made, etc.
Will the pushback be fully automated?
Yes.
Will their be a utility for configuring the exits?
Not initially, but the program is compatible with the AES config files so, if your airplane already has them, it will just work, and if it doesn't have them, you can always use AES itself to edit doors that GSX will use. We might eventually do our own utility too.
-
"Not initially, but the program is compatible with the AES config files so, if your airplane already has them, it will just work, and if it doesn't have them, you can always use AES itself to edit doors that GSX will use. We might eventually do our own utility too."
That's huge IMHO. Animated jetways and service vehicles have been around since the Simflyers days. I never used them, however, because it was too difficult to remember all of the different key combos and frequencies implemented by different developers. That is was makes AES to appealing - it is standardized for every supported scenery and it sounds like GSX will build upon that.
-
Animated jetways and service vehicles have been around since the Simflyers days. I never used them, however, because it was too difficult to remember all of the different key combos and frequencies implemented by different developers.
Yes, because in those days, using Com frequencies on the sceneries was the only easy way for a scenery to add some interaction.
BTW, as soon as we had our own scenery handler module, even in FS9, we got rid of the frequencies used as triggers, and had things that ease the usage, like automatic airplane type detection with different jetway animations based on it, or service vehicles that appear at gates dynamically depending if there was an AI (or user) airplane on that spot. We had things like this in Cloud9 EHAM which was released 6 years ago, but they were cumbersome to do in FS9 and weren't as flexible as we wanted. FSX is totally different, because we can blend the user interface much better with the default UI.
-
I hope GSX is better than Park Me. I pulled into gate 52B last night and it said no parking was available. Really?? You say we can use the animated gates and this Park Me function yet first gate I pull into, nothing is available. So why is this and with GSX will it be at EVERY gate?
Secondly, if you all ever hope of surpassing AES, you all hopefully will put the jetway animation rewrite at the top of your priority list once thee initial release of GSX is out.
-
I hope GSX is better than Park Me. I pulled into gate 52B last night and it said no parking was available. Really??
I've already explained it in this thread:
http://www.fsdreamteam.com/forum/index.php?topic=4719.0
There's no ParkMe at all at KLAX because, the *current* version of ParkMe that is distributed with our sceneries now, works only with some kind of Docking system and, since the real KLAX airport doesn't have any Docking systems right now, there's no ParkMe at KLAX. If you want to check ParkMe, have a look at KJFK or KDFW, there's plenty of gates that supports it.
GSX's ParkMe, which will replace entirely the current ParkMe, supports Marshallers too, so it will work at ANY gate of ANY airport.
If that specific airport has a customization file that specifies some parking stands having Docking systems, that airport will have Docking system at those parkings, and Marshallers everywhere else. Without a customization file, all parking stands will use Marshallers.
You say we can use the animated gates and this Park Me function
I've said you can use animated gates at KLAX, which is of course true, but said nothing about ParkMe at KLAX, if you mean the *current* ParkMe.
You WILL be able to use GSX ParkMe at KLAX, for free, as soon as it's released, because it will enable Marshallers (maybe we'll add Docking systems to TBIT, even if we don't know if they'll be there, I'd say it's likely).
If there's an animated jetway or not doesn't have any relationship with ParkMe, they are entirely unrelated, but in GSX, the presence/absence of a jetway will affect whether a Passenger Bus and Stairs will appear when embarking/disembarking
-
I had been hoping that AES would come to KLAX, but with GSX on the horizon, I don't really need it. I do echo the concerns concerning the default jetway animations, which usually looks simply weird. However, hearing Umberto say that they might make their own animation for it, I'm confident that this will end up great. I for one will use a mix of AES and GSX. AES will be used at those airports with static jetways, ergo, the airports where GSX will not be able to move jetways. GSX will be used at airports that either have no jetways or where the jetways are not static - FSDT's airports being the primary example of those of course.
I'm very curious to how you are going to implement a new jetway animation system. Is this something that will be controlled by GSX (so default and new system will co-exist), or will it be something that will utterly replace the default animation system? I mean, it's not exactly like replacing textures...
Concerning ParkMe, I never realized it could be used outside of FSDT sceneries. I thought it was tied to FSDT sceneries. That's the reason I also never used it, because I have AES for all my airports and as such ParkMe was never very useful. Now that I know this, I'll be seeing where and when I can use it.
On a seperate note, due to all the talk about ParkMe and all, I started digging into the KLAX manual. To be honest, with sceneries I hardly ever look at manuals except when I review them, but I'm glad I've looked into KLAX's. It's amazing, all the stuff you have done. The FAROS system especially! When I took off at KLAX today, I thought it was some kind fo glitch... I'm glad to stand corrected and I'm pleasantly surprised by all of this. Plus, performance is actually good, too (that is completely contrary to what I thought). Kudos!
-
Concerning ParkMe, I never realized it could be used outside of FSDT sceneries. I thought it was tied to FSDT sceneries. That's the reason I also never used it, because I have AES for all my airports and as such ParkMe was never very useful. Now that I know this, I'll be seeing where and when I can use it.
I think you missed something in my explanation: you CAN'T use ParkMe at non FSDT airports right now. The current version of it, that comes with all our airports now, works ONLY at our airports and ONLY at parking stands with a Docking system, because the current version doesn't support Marshallers.
With GSX you'll be able to use ParkMe at every airport, because it will replace the *current* ParkMe entirely which means, at FSDT airport it will offer all its features INCLUDING those that were part of the actual ParkMe for free, and by purchasing it, you'll be able to use it at every other airport INCLUDING all the rest of the GSX features.
AES will be used at those airports with static jetways, ergo, the airports where GSX will not be able to move jetways. GSX will be used at airports that either have no jetways or where the jetways are not static
Or you might use AES just for the jetways...
-
Somewhere I read something about a special file for FlyTampa's Hong Kong, which is why I thought ParkMe would work at other places also. Sorry, my bad!
I didn't know you can use AES for jetways only. I mean, the stairs and all that will also move to the plane if the jetway moves to the plane...
-
I am so very happy you are NOT using AES to move the jetways. I do not think AES is a finished product and it requires a lot of work which I don't think the developer wants to do. It took a long time for him to make it compatible for KSFO. The vehicles he uses to ferry passengers, like the busses, or pick up/deliver luggage have European markings and that doesn't look very good here in the good ole USA. Kudos for giving us moving jetways with this excellent product!!
Best regards,
Jim
-
I am so very happy you are NOT using AES to move the jetways. I do not think AES is a finished product and it requires a lot of work which I don't think the developer wants to do. It took a long time for him to make it compatible for KSFO. The vehicles he uses to ferry passengers, like the busses, or pick up/deliver luggage have European markings and that doesn't look very good here in the good ole USA. Kudos for giving us moving jetways with this excellent product!!
Best regards,
Jim
That it took look to get it compatible with KSFO was not, I think, because of him, but because of the impedning release of v2.0. When it was released, AES support came very quickly.
-
This is why I'm getting FSDT GSX! It works with ALL airports for FSX and other cool stuff! ;D
-
Is it going to work with ALL airports or Default and FSDT airports?
-
I am so very happy you are NOT using AES to move the jetways. I do not think AES is a finished product and it requires a lot of work which I don't think the developer wants to do. It took a long time for him to make it compatible for KSFO. The vehicles he uses to ferry passengers, like the busses, or pick up/deliver luggage have European markings and that doesn't look very good here in the good ole USA. Kudos for giving us moving jetways with this excellent product!!
Best regards,
Jim
That it took look to get it compatible with KSFO was not, I think, because of him, but because of the impedning release of v2.0. When it was released, AES support came very quickly.
Right. For the most part, if the files are sent to Oliver, they will be implemented within 6 weeks or so. It really is amazing that for so long, Oliver has delivered an update every six to eight weeks. I will agree, however, that the development time and the fact that airports are developed at Oliver's discretion limit AES. I know there is a lot of controversy over LatinVFR and Oliver isn't developing for it right now. With GSX, it will work at their airports. Not to mention all of the airports that AES will never developed that still need ground services. Virtually all airports that do not have jetways will never be developed by AES so that leaves a lot of room for both products to coexist.
-
Is it going to work with ALL airports or Default and FSDT airports?
It will work with all FSDT airports, for free.
It will work with any other FSX airports (both default or 3rd party) if purchased.
-
Is it going to work with ALL airports or Default and FSDT airports?
It will work with all FSDT airports, for free.
It will work with any other FSX airports (both default or 3rd party) if purchased.
But if a 3rd party airport does not have moving jetways, GSX is not going to make them movable, right?
Jon
-
But if a 3rd party airport does not have moving jetways, GSX is not going to make them movable, right?
That's what we always said, right from the start when GSX was first announced: GSX it's an FSX-only product, and we believe that a proper FSX scenery should at least support what FSX offers even in its default airports, which includes moving jetways.
What's wrong, really ? It seems that without adding moving jetways, there's nothing left for GSX to add. There are many services that GSX will add at ALL airports, including 3rd party, which makes it worth using.
And, of course, we are discussing just the initial release.
-
It seems that without adding moving jetways, there's nothing left for GSX to add.
How long after the initial release can we expect to wait for the moving jetwats? If it isn't this year, why not reconsider sending LAX to Oliver?
-
How long after the initial release can we expect to wait for the moving jetwats?
Since we don't even know the initial release date now, it's even more difficult to give an estimate for upgrades.
If it isn't this year, why not reconsider sending LAX to Oliver?
As I've said, we'll support AES if we manage to do an FS9 version, which is something more tangible and concrete right now, rather than a future GSX update.
-
How long after the initial release can we expect to wait for the moving jetwats?
Since we don't even know the initial release date now, it's even more difficult to give an estimate for upgrades.
If it isn't this year, why not reconsider sending LAX to Oliver?
As I've said, we'll support AES if we manage to do an FS9 version, which is something more tangible and concrete right now, rather than a future GSX update.
That's the music to my ears, Umberto. Thank you a million times.
-
With so many people commenting right and left I am so confused! AES: are the additional features that are added to the simulation like: boarding, cargo loaders, catering trucks. GSX: the same but better..... Right? The whole jetway issue is a completely different subject that is controlled outside AES or GSX? so basically FSDT is working on a better way to make the jetway attach to the airplane....? Yet at the moment jetways are working on KLAX? but not how they ate supposed to be? Please someone clarify.
-
After thinking about this for a bit, I think there may be a clash between GSX and AES. I think it will be easy to overcome but it would require cooperation between Umberto and Oliver. I also think cooperation will be necessary because people that like AES will like GSX. I bet most will want to use them together and pick the best parts of each utility. I also don't think GSX will replace AES because of the current jetway issue, the fact that a lot of people have invested in AES credits and the probable release of AES NG. The good news is I bet a lot of people will buy both.
The clash - with AES, the marshallers and baggage loaders automatically appear when you set the parking brake and stop the engines. If you are using both GSX and AES at an airport and you want to use the GSX marshaller and baggage loaders but the AES jetways, you will end up with duplicates. Right now, the only way I know to stop the AES baggage loaders is to remove the cargo doors from the intelliscene file. If both GSX and AES use the same imtelliscene file, you would be deactivating the cargo doors for both utilities.
Oliver can overcome this by adding all AES functions to their options window.
-
Dear all,
Once upon a time I bought cloud9 KLAX hoping it get AESed some day. Unfortunately this never happened. In fact I never flew into cloud9 KLAX. An abandoned installation.
And now, years later and after a late move to FSX, the same thing again with KLAX?
What a disappointment!
Until now, I purchased every single airport from FSDT and I admire your work. You are the best.
But without AES it is a showstopper for me too. And an improved GSX cannot be expected soon.
Therefore, I would kindly encourage you, Umberto and the FSDreamteam, to re-consider the AES issue.
This would be highly appreciated.
Have a nice day
Goetz
With all due respect, Umberto, he makes a good point and i do agree with him. GSX sounds like a very promissing product and i'm truly looking forward to it, especially after seeing the trailer for it. I've allready purchased KLAX and i was very impressed with it, though finding out later on that it may not be supported by AES is a little bit dissappointing. (yes, i know it's my own fault for not checking that before the purchase, however i don't regret buying it)
I know you have said that GSX is not far away, but to be fair we have heard this Soon(TM) many times before from many developers and "Soon" usually becomes a bit longer than that, this also considering that GSX won't support moving gates in the initial release, means that it's most likely will take some time before we'll see the gates lining up perfectly with the aircraft door(s).
At least, i (and probably many other customers) would be very grateful if you considered looking into the AES support, even if you don't make an FS9 version of KLAX
-
Hi,
I have to agree, until GSX is ready for release I would hope FSDT sends all their airports (KLAX Included) for an AES update.
-
Hi,
I have to agree, until GSX is ready for
Same here I cant stand seeing those wheels at the gate tuck down into the ground on my FSX and they don't even look realistic without AES setings. Please make AES compatablity I am very excited for GSX but i know many of us who migrated to FSX were hoping we would finally get a LAX with AES since LAX version 1 couldn't offer it
-
With all due respect, Umberto, he makes a good point and i do agree with him. GSX sounds like a very promissing product and i'm truly looking forward to it, especially after seeing the trailer for it.
I can only repeat and confirm, AES support will come if we'll do an FS9 version, which is something we are looking into it right now, but it it will stay FSX only, it won't make any sense for us, since we have our own solution soon enough. That's the agreement we had with Oliver since years.
-
Yup, I also wish for continued AES support for all FSDT FSX sceneries until "the day" we have moving GSX gateways.
I could understand the developer's position if GSX (with moving gateways) was to be release in the next week or month, but I rather doubt it too. Isn't it a simple matter of fowarding Oliver some textures or something?
-
Yup, I also wish for continued AES support for all FSDT FSX sceneries until "the day" we have moving GSX gateways.
All our FSX sceneries already have moving jetways, by default, right now, and they will suffice until a better version will eventually come with GSX.
-
I can only repeat and confirm, AES support will come if we'll do an FS9 version, which is something we are looking into it right now, but it it will stay FSX only, it won't make any sense for us, since we have our own solution soon enough. That's the agreement we had with Oliver since years.
Please make a FS9 version Virtuali. :)
-
Great NEW Airport Add-on KLAX........
Just my 2 cents worth ...... :) <grins>
Please add FSX • KLAX - to AES ....support for Now ....with Oliver...
As the Credit cost is Not a Big Issue with me or probably other simmer's ...lol
Will Most Likely Use Both GSX...... Still drooling for RELEASE & AES
Can't wait to get GSX .....WOW.... Thanx
*****************
As I live in Alaska, and work with NorthLink Virtual Airlines ....
with Hubs in Anchorage, Seattle, Calgary....
Also looking for Pilots - 18 yo - 99 • • • Join / Fly our Great VA • for Northwestern USA • Over 400 plus Routes
Northlink Virtual Airlines • http://www.northlinkva.com/zfsdt.htm (http://www.northlinkva.com/zfsdt.htm)
Routes Served: Alaska / Horizon • Westjet • Northern Air Cargo • ERA Aviation • SkyWest • Polar Air Cargo
(http://northlinkva.com/zforum-img/!-northlink-w-ceo-signature-e90-03-693x330.jpg)
-
Please make a FS9 version Virtuali
Already said in countless of other threads that we ARE trying.
-
Now, I totally understand the entire no-AES if no-FS9.. But this has just made me more excited for GSX. I mean, one thing I love is having jetways hook up to AI traffic. At FSDT's airports, I had to choose between AES and the AI gates. With this new add-on I'll be able to GSX my aircraft, and have AI jetways work, correct?
Honestly, I'm not a fan of having to wait, but this does make me excited about what is to come. Once you guys fix the FSX jetway animations, I don't think anyone will be using AES anymore if they can use GSX. :) However at many 3rd party airports AES will be the only option because of static jetways. (unless we can find a way to use AES only for the jetways and GSX for the rest, provided it is as high quality as the previews make it seem).
-
At FSDT's airports, I had to choose between AES and the AI gates. With this new add-on I'll be able to GSX my aircraft, and have AI jetways work, correct?
It's likely that if we'll replace the default jetways in GSX, it will be for the user airplane only, like AES. However, we still haven't looked into all the issue so, don't take it as a definite answer.
-
Yeah i like it no more AES support its a shame that you have to pay that much ammount of ppoints to have a few Airports for AES available. I would never say it sux because the product itself is a innovation but the way it´s being published is just like aerosoft always do... They just want our money.
Thats my point!
-
After thinking about this for a bit, I think there may be a clash between GSX and AES. I think it will be easy to overcome but it would require cooperation between Umberto and Oliver. I also think cooperation will be necessary because people that like AES will like GSX. I bet most will want to use them together and pick the best parts of each utility. I also don't think GSX will replace AES because of the current jetway issue, the fact that a lot of people have invested in AES credits and the probable release of AES NG. The good news is I bet a lot of people will buy both.
The clash - with AES, the marshallers and baggage loaders automatically appear when you set the parking brake and stop the engines. If you are using both GSX and AES at an airport and you want to use the GSX marshaller and baggage loaders but the AES jetways, you will end up with duplicates. Right now, the only way I know to stop the AES baggage loaders is to remove the cargo doors from the intelliscene file. If both GSX and AES use the same imtelliscene file, you would be deactivating the cargo doors for both utilities.
Oliver can overcome this by adding all AES functions to their options window.
Yeah, that's what I have been thinking about too. As it is, there is no way to simply disable parts of AES. Either you remove entries in the intelliscene.cfg (bad idea) or you remove AES from the airport (even worse idea). So I do think that GSX and AES will have to work together somehow in order to use them together, as you suggest Umberto. If they will not work together and thus produce duplicates, then I know I will choose to use AES and not GSX at airports that have moveable jetways with AES only.
-
Toooo.... Many Fires to put Out before • Initial GSX first release
You Folks at FSDT probably feel like Missoula Smoke Jumpers • Trying to put them Out ;D ;D
****************
There has been many Great Airports, recently released for FSX.....
KDFW, KDEN, KLAX ............... and PANC (Proud to own them ... <grins>
With these Great Fantastic Airports, and the coming release of GSX --- It may be too late for this addition to GSX
but Please consider the following, for inclusion in the next release ....... Please .....
****************
I would sure like to see a Inter-Active • • Follow Me, Pick-up, AND/OR --- Van, Tug, and maybe a Push-Back / Fuel - Vehicles • •
that you could Drive Around and View The Great Features and Scenery ...... and or view your plane getting baggage loaded,
to view other aircraft getting loaded ( Not sure if the Baggage Loader's - - load other AI ... Aircraft arond the Airport ).
I know I Hate trying to ..... Drive a Plane up a Vehicle Ramp / Street / Highway ..... to Get a View and a Picture or Screen Shot at a Arrival .... Parking
Garage.... etc......
It would be idea to have say a Utility Pick-up - for Runway Lighting .... being able to drive to the end or along a runway.....off of tarmack .... of course ...<grins>
..... to be able to watch take-off's and landings
{{ With say the Vehicles as a MS - separate class of plane to steer with Joystick / Mouse • • • or have a GSX drop down Menu to drive a vehicle ... and to change
your view point ..... ie: look forward, left, right • • • Say something like the EZDok .... Viewer ...... • • You say you have a Flexible Core in GSX ... so it may be
able for you to implement ......Maybe.... }}
{{{ FROM - Above "Vehicles as a MS - separate class of plane to steer with Joystick / Mouse " .... is probably NOT the Best way to go here ... as you would have to
load plane and lose the Your CURRENT --- Docked Aircraft .....Gerrrrrr }}}
************
Awe....... Inter-Active ...... Avatar's .............. But that is a Whole another can of Worms...... <grin>
************
THANX AGAIN FOR YOUR GREAT PRODUCTS...... ::) :) ;D ::)
(http://northlinkva.com/zforum-img/!-northlink-w-ceo-signature-e90-03-693x330.jpg)
-
AES is important for me because of the precise pushback function. And I doubt that any other addon program will offer this service soon. So I hope the airport will be added in the future. Normally I would not buy an big Hub without AES.
-
AES is important for me because of the precise pushback function
Pushback it's one of the main GSX features, it will work automatically with every FSX airport, and we'll also be able to customize it to work even better with specific airports, even 3rd party ones. There will be multiple different vehicles, in several types and shapes, with human characters as drivers, wingwalkers coming in and out of the vehicle with different custom human animations for each tow truck model, sound effects, speech, etc.
-
..but the way it´s being published is just like aerosoft always do... They just want our money.
If that was truely the case, you would've had to purchase the base pack in addition to credits, and there would be no zero credit airports supported.
-
Hello,
first of all Thanks a lot for this great Airport, i have a lot of Fun with.
Of course for me is AES too very important, and its said to here that in the next AES Verson maybe will not KLAX supportet. Today i read in the Aerosoft forum a statement from the question of the support of KLAX with AES from Oliver Papst:
"Yes,
the link will show, what will happen in future.
But, there is no "agreement" from my side done, to only support them until they end doing FS9 Versions, statements of Umberto Colapicchioni could be missinterpreted here.
I offered them to support there products for all available FS Versions, as long as they want it. This was the offer at the beginning and is still present from my side.
If they now don't want to continue the cooperation, I will accept that of course. "
Here is the link to the Thread: http://forum.aerosoft.com/index.php/topic/48712-aes-klax-for-fsdt-aes-v-214-when-will-it-be-available/
-
Perhaps we are not entirely clear on the definition of "support":
to have a scenery supported by AES, support is required by BOTH parties, the developer must do the scenery in a certain way and give Oliver some source files, then Oliver has to work to create his own part.
When I've said "we have an agreement with Oliver what WE would support AES until we do FS9 version of our sceneries" I was obviously referring only to OUR part of the "support", and we informed Oliver a while back that, if we would release a scenery with no FS9 version, we would not support AES, because by that time we would probably have our own alternative solution in FSX, and he understood the point, so he knows very well what I meant.
Although it might seems strange that the availability of the FS9 version would affect the AES support, even in FSX, it DOES make sense because, since we don't have a solution for ground services in FS9, we need AES in FS9 so, the airport has to be made to be easily adaptable to AES ANYWAY, otherwise it would be difficult to port back in FS9.
But, if we decide to drop FS9, this means we'll not be bounded by doing the airport in a specific way because of AES in FS9, and it's even possible that, due to GSX, we'll have to design the FSX version instead differently, especially in case we'll get rid of the default jetways system to be replaced by our own.
In THAT case, a release of an FSX-only airport, GSX already released and with a new jetway animation method, it's very likely that we'll not support AES anymore, but that would be really obvious: what would be the point, considering that the scenery would have same (or better) features by default, without purchasing anything extra, since GSX will be free at our airports ?
-
Makes alot of sense of what you're saying Umberto. Using jetways as a principal aspect for the best prospects, GSX down the line should be able to move all the jetways with less haste then the default FSX RTH. :)
-
I am another person holding off on KLAX until it has moving jetway, pushback and "follow me" support. My thing is this, as an owner of more airports than FSDT models (like most others here), I will always need AES! Thus, we (FSDT customers) will need some sort of guarantee that GSX and AES can co-exit flawlessly. If there is a hint of conflict in the programs, I will ditch KLAX and all future FSDT projects like a bad habit. AES supports more airports so my loyalty lies with them.
-
I am another person holding off on KLAX until it has moving jetway, pushback and "follow me" support.
KLAX already has moving jetways right now, as with all our other airports. It will of course get Pushback and FollowMe too with GSX, for free, once it's being released.
My thing is this, as an owner of more airports than FSDT models (like most others here), I will always need AES! Thus, we (FSDT customers) will need some sort of guarantee that GSX and AES can co-exit flawlessly.
GSX obviously will not create any problem on its own by the mere fact it will be installed, because it's you that will activate it, it will not do anything if not called.
If there is a hint of conflict in the programs, I will ditch KLAX and all future FSDT projects like a bad habit. AES supports more airports so my loyalty lies with them.
GSX supports ALL 20000+ FSX airports including 3rd party ones from day one with ALL its features (Pushback with Wingwalkers, Marshallers, FollowMe, Catering vehicle, Baggage Loader, Passenger Stairs, Passenger Buses) all using advanced human animations and 5.1 surround sound, with hundreds of easy to customize liveries that can be localized to every single airport, even at the parking level (like, having United equipment on a United parking, and AA equipment on an AA parking of the same airport)
The only thing that it will not add, will be "Animated jetways for 3rd party airports that have them static", because we would have had to charge separately for this, and we believe that having to charge per-airport JUST for having "Animated jetways for 3rd party airports that have them static", doesn't make much sense.
Since we are fairly sure that, after GSX is released, most users would want to use GSX for everything and AES for "Animated jetways for 3rd party airports that have them static", the potential conflict should be solved by AES, that would need to add a feature to use just its jetways on a supported airport, instead of having them moving automatically together with its other objects, like passengers stairs for example.
GSX will never be problem because it doesn't do anything unless you activate it, using our standard YouControl menu.
-
The only thing that it will not add, will be "Animated jetways for 3rd party airports that have them static"....
I'm confused, Umberto... I thought you mentioned that animating jetways was planned for an update after release, but nothing had been mentioned about charging per airport. Are you just planning to add custom jetways to those with default animation?
-
I'm confused, Umberto... I thought you mentioned that animating jetways was planned for an update after release, but nothing had been mentioned about charging per airport. Are you just planning to add custom jetways to those with default animation?
We would have to charge per-airport only if we were adding moving jetways to 3rd party airports that don't use the default FSX animations, exactly like AES, because that would require interacting with the developers, just like AES, which is NOT something we are prepared to do right now.
When I've mentioned replacing the default FSX jetways animations, it could only work for airports that already use the default FSX jetways: all the default ones, and the 3rd party ones that use the default FSX method, like our own.
The comment was made because the issue raised was the default FSX animation is bugged (it surely is) and if we would drop AES support for our FSX-only sceneries, they would not get feature-parity with AES, even after GSX release.
This wouldn't be an issue, if we'll eventually replace the default jetway animation method, if only for our own airports (but with the side-effect that *any* other FSX scenery using default jetways would be enhanced too).
That we don't have any intention entering in the tricky business of having to deal with a single airport separately and having to deal with different developers, which would then force us to charge per-airport, which is not something we want to do, was clearly said right from the start, and this haven't changed.
However, GSX HAS the ability to create custom files for any airports, to better fit compared to the generic algorithms that relies on the supplied AFCAD, which means we CAN customize any airport to fix any potential issues (like specific problems in certain spots), even 3rd party ones, without any interaction with their developers, without even having to distribute alternate AFCAD, it will be done entirely within GSX.
-
virtuali - Thank you for that very detailed response. I am also worried about movable jetways and my current 3rd party airports that work with AES now, what will happen to them when I install GSX?
-
I am also worried about movable jetways and my current 3rd party airports that work with AES now, what will happen to them when I install GSX?
Nothing will happen to them. That's the biggest problem. You'll have the same "old" default moving jetways.
Jon
-
virtuali - Thank you for that very detailed response. I am also worried about movable jetways and my current 3rd party airports that work with AES now, what will happen to them when I install GSX?
Since GSX doesn't deal with jetways, just installing GSX will not do anything to your AES airports. And, GSX doesn't do anything automatically if you don't call it, and it doesn't modify any files of your airports so, until you call it, it will be as if it never existed.
But, until AES will be upgraded to allow to call its moving jetways separately from the rest of its procedures, you will have to chose if using AES or GSX at that airport, otherwise the two set of vehicles will clash into each other.
If and when AES will allow to just call its jetways independently from the rest of its procedure, you will able to use AES for jetways (which GSX doesn't do) and GSX for the rest of the services, which is probably what you'll want to do in the end.
-
That we don't have any intention entering in the tricky business of having to deal with a single airport separately and having to deal with different developers, which would then force us to charge per-airport, which is not something we want to do, was clearly said right from the start, and this haven't changed.
Could make for an interesting licensing deal with Aerosoft... Virtuali would get the source files from Oliver for custom jetways, and the credits we purchase from Aerosoft would activate either AES or GSX.
-
Could make for an interesting licensing deal with Aerosoft... Virtuali would get the source files from Oliver for custom jetways, and the credits we purchase from Aerosoft would activate either AES or GSX.
Jetway source files belongs to the original developers, not to Aerosoft. And besides, if we would decide to chase that market, we could replace them entirely with our own models, which should be fairly easy to do, since the original developers already made the work to be AES-compatible.
Believe me: it's in the best interest of AES allowing his users to be able to use AES jetways only, once GSX will be out. It's the only way to keep it relevant, other than the FS9 market (which we are not interested in the slightest bit), of course.
-
Just my 2 cents...
I wish FSDT would give its customers the CHOICE of AES or GSX. I would like to buy KLAX but I'm waiting for AES support first, so the sooner it is ready the better and more sales for FSDT! I'm sure GSX will be great but until it arrives I would like AES at KLAX.
Please listen to your customers FSDT and offer both AES and GSX and let customers decide which ones they prefer.
Keep up the good work :)
-
As we said right from the start, AES support was tied to the release of the FS9 version. Since we gave a go on that one, AES support will come too.
-
That is superb news, thank you Umberto! :)
-
As we said right from the start, AES support was tied to the release of the FS9 version. Since we gave a go on that one, AES support will come too.
So I guess that brings us back to my initial question in this thread: "When can we expect AES support for KLAX?" And by that I mean AES support for the FSX version of KLAX. ;D
Jon
-
Probably when the FS9 version is complete.
-
Umberto
Sorry for raising this one again, but on the basis that you are going to release LAX for FS9, please confirm whether there will be AES support at LAX for both FSX and FS9 versions? If yes, I will buy LAX for FSX in anticipation of AES support coming later. I know GSX is due soon too and I'm looking forward to trying that too!
Thanks and keep up the good work :)
-
We haven't done anything to prevent AES working in either version of the scenery, we'll send the needed files to Oliver very soon, so it will be all in his hands now.
-
we'll send the needed files to Oliver very soon, so it will be all in his hands now.
It seems the files are still in transit!
releaselog AES 2.14:
KLAX from FSDreamteam is not included, I still wait fort he promised sending of the needed Data.
When I get them, the airport will follow next time.
-
There's already an AES discussion here:
http://www.fsdreamteam.com/forum/index.php?topic=5054.msg46845#msg46845
So, no need to cross-post.