GSX 1.3 Released

[Crashdive]

... just asking 

[Crashdive]

Hi Umberto,

as I was saying, after downloading and re-installing the whole thing again the same thing:
except this time I ONLY have the luggage truck. Nothing else. No pushback truck, no baggage loader, no catering service and no fuel truck. Nothing...

To be quite honest: I am sick and tired of this. I might be the only person who has this problem, never the less, I do.
So I am going back to AES. Just because nobody else has reported this problem doesn't mean it doesn't exist. There is a first for everything, and obviously I stumbled upon a bug in your program that prohibits me from using it to it's full potential.
Sad though, as I really liked it when it worked.

I understand I am not entitled to a refund and I won't even ask; but whoever ask's:
No, I would not recommend it.

thanks for your support and good luck in all your future projects.

Regards,
Cr@shdive

[virtuali]

except this time I ONLY have the luggage truck. Nothing else. No pushback truck, no baggage loader, no catering service and no fuel truck. Nothing...

That's really not possible, but will find it out.

To be quite honest: I am sick and tired of this. I might be the only person who has this problem, never the less, I do.

Yes you are the only one. Which doesn't *obviously* mean we don't BELIEVE you have the problem, just the problem has nothing to do with GSX, and it's something specific to your system.

Just because nobody else has reported this problem doesn't mean it doesn't exist. There is a first for everything, and obviously I stumbled upon a bug in your program that prohibits me from using it to it's full potential.

No. Something in your system is AFFECTING GSX.

No, I would not recommend it.

Wrong. Wrong, and wrong again. Since you don't obviously want to embarass yourself not recommending something that works for everybody else, maybe it's best to investigate what's wrong with your system.

You are saying "I'm going back to AES", could be your problem has simply being caused by the fact that AES, with the help of FSUIPC, removes ALL ground objects from a parking, including GSX ones ?

There was ANOTHER thread here, interestingly named "I give up":

http://www.fsdreamteam.com/forum/index.php?topic=6274.msg54992#msg54992

Of another user that was misled thinking this was a GSX problem, when in fact it wasn't. Try to apply that FSUIPC setting, and see if it makes a difference.

[Crashdive]

Then why did everything work before the latest update?
I have not added anything new since I first installed GSX, neither have I deleted and/or modified anything.
This is just bizarre...

[virtuali]

Then why did everything work before the latest update?

Can you just TRY what I've suggested ?

[Crashdive]

Oh boy...  where do I start:

First of all: Umberto, you were absolutely right! It was something on my system that screwed everything up.
The culprit identified is AES. I am aware you told me about it.


What I didn't know at the time is this:
I had AES before GSX.
Anyway, to make a long story short: No idea where, somewhere here in the forum I read a post from Bruce Hamilton(?) where he stated that GSX is reading any airplane from the Intellicene file created and/or modified by AES.
I had no idea... and here is how I found out:

When I opened the aircraft thingy from within FSX addon manager/ coautl powered products (excuse me if I don't remember the correct wording) I noticed that all the cargo doors where disabled and I wondered why.
As everybody who uses/used AES in the past knows, the first thing you do is configure your particular aircraft; eg. doors, nose wheel, height's etc... I think you all know what I am talking about.
Here is the thing: Once I installed GSX I disabled all the doors I didn't need from the AES Aircraft configuration so I would not have AES and GSX sending loaders, staircases etc. Everything worked fine until I updated GSX. What happened was once I installed the newest upgrade, GSX read the Intellicene file thing and determined since I disabled the cargo doors in AES that there are none - hence the 'no show' of anything except the luggage truck.
Once I enabled the doors back in AES, I re-installed GSX right on top of the existing one I had. Fired up FSX, called ground support for both AES and GSX and Voila: both showed up. So I dissabled them again in AES so it would only start GSX and guess what:

It worked!

I am sure there might be a few of you out there who might have similar experiences and getting frustrated. But trust me: this works.

So, I don't really know what to say except: I am an idiot!
I am sorry and apologize to anybody I might have offended, especially FSDT - Umberto.

Let me just say this: It works. Period.

Once again:
Sorry. I did not mean to offend anybody or anything, but please try to understand the frustration. No excuse, I know.

Kindest Regards,
Cr@sH

[virtuali]

Ok, I'm happy you finally found out the problem. Fairly sure it wasn't a GSX issue...

In any case, now that GSX has an integrated airplane editor and its own GSX.CFG file, you can control GSX more easily if you use that one, without having to touch AES. This because, the GSX.CFG file (if present) will take priority over any other file, even over the GSX internal database, and of course over the intelliscene.cfg file too.

This means, if you have any reasons to keep all your doors disabled in AES for any reason, you can keep them disabled without affecting GSX, by doing this:

- Open the GSX Aircraft configuration menu

- It will open with the current config, edit all your doors to re-enable them

- Press the "Save" button, this will create a GSX.CFG file for that airplane, that will take precedence over anything else.

[Crashdive]

I am doing just that as we speak, editing all the doors to re-enable them.

Either way, thanks again for your support and sorry me being such an idiot.

Regards,
Cr@sH

[blueskydriver]

Hi Umberto,

I am not sure where to post this question, so please move it to the correct thread, if needed.

As you know I am using AES and GSX in a fullsize sim (maybe others do as well) and I've asked about the idea of having GSX menu screens to be usable via a remote computer like AES. Thus, is there a chance in a future update that this might be possible? If you've already completed this and I just missed a posting/update, will you please point me in the right direction?

Otherwise, I do hope that you'll get time to make this addition/option available because it'd be much nicer to not see the selection screens across the three projectors anymore...

Thank you so much for a great program(s),

John

[virtuali]

I've asked about the idea of having GSX menu screens to be usable via a remote computer like AES. Thus, is there a chance in a future update that this might be possible?

Yes, this has been discussed several times already, and we are thinking about it. However, it would more more like an API access to GSX functions, it would be up to a 3rd party developer to do something with it, including controlling from a remote system.

[blueskydriver]

Hi Umberto,

It has been a good while and I am thinking about the API for the remote control function for GSX like that of AES (see previous post above). As you posted that a third-party using the API would be fine, but why not add this feature into GSX yourself? The ability to select the same onscreen choices from a remote client computer surely would be easy for you. You do such great work already and your programming skills are top notch, so I'd think it be something you'd would enjoy making.

Plus, It would be a very nice feature to market in an GSX update. I believe you'd find many people who would be happy with this type of feature; especially, me...

John

[virtuali]

As you posted that a third-party using the API would be fine, but why not add this feature into GSX yourself? The ability to select the same onscreen choices from a remote client computer surely would be easy for you

Because our resources are limited, and better spent to do something would be of interest of *all* GSX user FIRST and then, only after all missing features that interest *all* GSX users are in, we might think about adding things that interest only a small minority of users, those that use more a PC.

And, in any case, it would be quite an effort doing an API so, I can only confirm that, in case we'll add an API, we'll only add the core functions to interact with GSX, but something like network connections should be made by the developer. Not that this is really an issue: we'll not reinvent any wheels here: the API will probably use the official Simconnect functions (just like the API from PMDG, for example), this means there's theoretically no difference between accessing locally or on a different computer, since Simconnect can work just the same.