FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Petermuc3 on April 30, 2012, 03:13:27 pm
-
Hi,
I think I tried everything what was proposed in this forum, but I still cannot get the JS41 work correctly with GSX. GSX always asks for action exit 2.
There is no exit 2; I tried to change the GSX aircraft data within FSX but eg. if I delete exit 2 completely, it is back when I open the file again.
This is the GSX cfg
[aircraft]
nosegear = 6.65
refueling = 1
absoluteheights = 1
[exit1]
pos = -1.1 4.0 1.3 5.0
code = 1
name = exit 1
[exit2]
remove = 1
[exit3]
pos = -1.05 -2.95 1.0 0.0
code = 1
name = exit 1
[exit4]
pos = -4.0 -10.0 2.5 -5.0
code = 1
name = exit 1
[service1]
flip = 1
code = 3
name = exit 3
[service2]
flip = 4
code = 3
name = exit 3
[cargo1]
remove = 1
[cargo2]
pos = 1.05 -4.1 1.3 0.0
code = 2
name = exit 2
uldcode = AUTO
This is the AES intelliscene file
[Descr]
Type=JS41
[Geom]
Nosegear= 6.65
Door1=-1.1, 4, 1.3, 5
Door3=-1.05,-2.95, 1
Door4=-.9,-6.1, 1.45,-5
Rear= 1.05,-4.1, 1.3
Thanks for the help
Peter
-
There is no exit 2; I tried to change the GSX aircraft data within FSX but eg. if I delete exit 2 completely, it is back when I open the file again.
That the exit2 comes back if you remove the whole entry, it's absolutely normal: removing the entry doesn't mean you remove the exit, it means you are not customizing it so, GSX will re-read it again from the aircraft.cfg file.
That's why GSX has a "remove" command.
I think I tried everything what was proposed in this forum, but I still cannot get the JS41 work correctly with GSX. GSX always asks for action exit 2.
The problem is this, Exit 2 EXISTS in your GSX.CFG file:
Here it is:
[cargo2]
pos = 1.05 -4.1 1.3 0.0
code = 2
name = exit 2
uldcode = AUTO
So, GSX is asking for the cargo 2 exit. It's the CODE that makes GSX identify a door and asking for it, and the name is derived from that code. As you can see, the default name that GSX assigned to it is "exit 2", because it's an "exit with code 2".
The "remove = 1" command on the [Exit2] removed the 2nd passenger door, and it was set by GSX automatically because that door couldn't be found in the aircraft.cfg, but nothing would guarantee that door would have a "code = 2" ( so it will be called "Exit 2" by GSX ) even if it actually existed...
Usually, Exit 2 it's the cargo door, at least on default airplanes. Don't know if the JS41 use default commands for its exits, if it does, if the cargo door opens with Shift+E 2, you should be already ok and if it uses another "Shift+E number" command, it would be enough to change the "code = " to that number.
If, instead, doors on that airplane are opened using custom variables specific to that airplane, you will have to set "code = 0" to IGNORE that door, and services will ignore its status. In this case, we'd better have a look at that airplane, to add it to the internal database, with its custom commands added.
-
So where is exit 2 on the maddog 2010? I try to open the exit and there is no response from gsx,it just keeps beeping when all exits are open.
VR
Todd
-
As I've said in many other threads, there's already a Maddog config file in the sharing area that, according to its author, works well.
-
Hi,
I'm refreshing thread...
I have 2 questions about JS4100:
a. boarding/deboarding is beginning, although pax/cargo doors are closed - is it normal?
b. why is necessary set parking brakes to do any GSX's action? Parking chocks (which are enabled with this aircraft) are not sufficient?
Regards,
Lucas
-
a. boarding/deboarding is beginning, although pax/cargo doors are closed - is it normal?
The JS4100 is not an airplane supported by GSX so, I guess you are using a customization file you made, or downloaded from some place. In this case, you and/or the original customization file author, probably set the door to be Ignored, so that's exactly what that option is supposed to do.
b. why is necessary set parking brakes to do any GSX's action? Parking chocks (which are enabled with this aircraft) are not sufficient?
Since the JS4100 is not internally supported by GSX, GSX can't treat it as a special case. GSX has the ability to treat special cases like this, for example the Aerosoft A320 can use the Wheel Chocks instead of the parking brakes, but the ability to customize this is not available in the aircraft configuration editor that is accessible to users.
-
The JS4100 is not an airplane supported by GSX so, I guess you are using a customization file you made, or downloaded from some place. In this case, you and/or the original customization file author, probably set the door to be Ignored, so that's exactly what that option is supposed to do.
I don't understand what exactly customization file you mean :-[ I didn't download any files...
-
I don't understand what exactly customization file you mean
Maybe you should read the GSX manual then. If an airplane is not internally supported by GSX, you must create a customization file for it using the integrated aircraft configuration editor, or download a file made by someone.
If you don't do this, GSX won't work correctly on an airplane that is not already internally supported.
-
Thank you Umberto - I had to miss that...
-
Hi there i have been having the same problem only with the just flight bad 146-200 it keeps telling me, that i have to open exit one and two.
Please help. :)
many thanks
-
Hi there i have been having the same problem only with the just flight bad 146-200 it keeps telling me, that i have to open exit one and two
There's no "problem" you are having, that's how GSX works, if an airplane is not internally recognized, you must create a configuration file for it, using the airplane configuration editor included with GSX.
The QW146 has been released later, so GSX supports only the 3 Avro versions, that's why you see the Exit referred as "Exit 2", which is the default assignment for the cargo doors, when there's no GSX configuration at all.
We might add the QW146 to in a future update but, in the mean time, you can make it work with GSX by creating a configuration file for it. About the door's open/closed status detection, you have two choices, depending if the developer used a standard doors variable, or a custom XML expression.
If they used a standard door variable, you can simply select which one ( from 1 to 4 ), using the GSX airplane editor.
If they used a custom variable, you must write an XML expression to check for it, if you know how to do it. But if you can't, the easiest option would be setting GSX to Ignore that door's status, so the service will start right away without waiting for you to open that door.
Of course, all of this is explained in the GSX manual, when the airplane configuration editor is discussed.
-
Seems the original query was about the JustFlight 146, not the FlightOne/QualityWings 146.
-
Ok so how would i go about setting gsx to ignore door status? many thanks.
-
Seems the original query was about the JustFlight 146, not the FlightOne/QualityWings 146.
Doesn't change anything, my reply would be valid for ANY 3rd party airplane that is not already internally supported by GSX: that's the main point of having an airplane configuration editor in the first place!
If anything, the JF146 is likely easier to configure, because they *usually* ( I say "usually", because I never seen that particular product ) make simpler planes, with not many custom variables, which means it might be using standard doors commands, which are easier to find.
-
Ok so how would i go about setting gsx to ignore door status? many thanks.
As I've said in my previous reply, using the GSX airplane editor. The manual discuss it in detail.
-
Sure, I'm not disputing that, but the main point being that were you to do an update for the QualityWings 146, that wouldn't do any good for somebody who was using the JustFlight 146 unless by chance, the positions of the doors and what not were the same, which it probably isn't.
-
Even if an airplane model is the same, different developers might use entirely different reference points for their models, so measures will almost always never match.
Creating an airplane configuration for the doors locations is VERY easy using the GSX editor, what MIGHT be difficult is figuring out custom XML variables for airplane that don't use standard doors variables. That's why I've said that we might have to add a QW146 configuration ourselves, like we DID for the Avro models, because QW USUALLY use some custom variables for the doors.
But JF, USUALLY, makes simpler models using standard door variables, that are way easier to figure it out, you have only 4 choices to try at the most, so I don't see having to create a special GSX configuration ourselves for the JF model to be as useful as it would be for the QW model, because anyone should be able to create one, using the included airplane configuration editor in GSX.
Again, assuming this JF model is made using only standard door variables. If it's not, we would like to know about it (I didn't know that JF *had* a 146 model on offer, it's impossible for us to support our stuff and be aware of everything that's out there...), so we might consider adding it ourselves and IN THE MEANTIME, GSX can be configured to IGNORE the door's status, which is the option that will always work in any case so, there's absolutely nothing that prevents GSX to be used with any airplane out there, even one that is not natively supported.
-
Even if an airplane model is the same, different developers might use entirely different reference points for their models, so measures will almost always never match.
Well, yes, that's exactly what I just said.
-
Well, yes, that's exactly what I just said.
Yes, but I had to explain it better, for others that are reading this post, to clarify that an unsupported plane in GSX is not usually a problem, unless the developer used non-standard variables, which is not usually the case with JF.
-
Well, yes, that's exactly what I just said.
Yes, but I had to explain it better, for others that are reading this post, to clarify that an unsupported plane in GSX is not usually a problem, unless the developer used non-standard variables, which is not usually the case with JF.
Copy, sir.
-
Friends,
what should I do, to baggage car arrives on the left side of aircraft while boarding – is it possible?
Lucas
-
what should I do, to baggage car arrives on the left side of aircraft while boarding – is it possible?
Yes, you must create a config with a cargo door on the left side, and reversed. Meaning, the green arrow in the 3d aircraft editor should point OUTSIDE.
-
I'm not sure I'm able to do it.. :-\ I'll try..
Thanks!
-
Hi Umberto,
I did it, baggage car now arrives where it should. Thanks for help.
However, I can’t change stop position pax car – I would like to pax car stops a little farther, I mean closer to aircraft main exit, but changing its position via 3D Editor (same way like baggage car) didn’t bring the effect.
Anyway... there is another thing I would like to do – I mean: cargo and service doors check.
I suppose that I have to set "Door with Custom Open/Close checks", but the problem is: what should I enter in "Custom check" line?
In manual, stated:
Finding custom variables used by a specific airplane, requires a good knowledge of the FSX SDK.
Hmm, I don't have this knowledge :(
Second thing - JS4100 has cargo door on the left side of fuselage, but on GSX' Customize Aircraft window, all cargo doors are on the right side.
Thirdly: JS4100 has own Ramp Manager. This is pop-up window where I can (by mouse clicking on each element) put chocks, connect GPU, put safety pylons, etc. ...and also open aircraft’ doors.
Ok, so, where should I start... ?
Ps. Is it possible you help me a little?
Ps2. Maybe JS4100 & GSX users already have configuration with cargo and service doors checks and could share it?
Lucas
-
However, I can’t change stop position pax car – I would like to pax car stops a little farther, I mean closer to aircraft main exit, but changing its position via 3D Editor (same way like baggage car) didn’t bring the effect.
You mean the passenger bus/van ? That position cannot be changed by the 3d editor, it's calculated internally depending on the general location of the exits and the parking size.
I suppose that I have to set "Door with Custom Open/Close checks", but the problem is: what should I enter in "Custom check" line?
An XML expression that check that variable, like in the example in the manual, but with the actual sample name ( L:MyVar ), changed to the actual name used in that airplane.
In manual, stated:
Finding custom variables used by a specific airplane, requires a good knowledge of the FSX SDK.
Hmm, I don't have this knowledge :(
To search for a custom variable, you might use an hex editor to open the airplane .MDL exterior file, and search for names containing the "door" string, and hopefully you'll come up with meaningful results.
If you don't want to do that, then you don't set it, and use the option to ignore checks. Is there precisely for this reason.
Second thing - JS4100 has cargo door on the left side of fuselage, but on GSX' Customize Aircraft window, all cargo doors are on the right side.
As already discussed many times on the forum, to have cargo loaded on the left, you use the 3d editor to move one of the two EXISTING cargo doors on the right AND rotate it 180 degrees, so the green arrow points on the outside.
Thirdly: JS4100 has own Ramp Manager. This is pop-up window where I can (by mouse clicking on each element) put chocks, connect GPU, put safety pylons, etc. ...and also open aircraft’ doors.
And the question is ? GSX doesn't care and doesn't know HOW you open the doors. When you open a door, the end result is ALWAYS an internal FSX variable, which can be either a standard one, or a custom L: variable. So, either you instruct GSX telling it WHICH variable is used by that door, or you set it to ignore it.
Ps2. Maybe JS4100 & GSX users already have configuration with cargo and service doors checks and could share it?
I searched for it in the sharing area of our forum, but can't find one.