Im not sure if this would be the right place for it. But was wanting to inquire on fixing the jetway and baggage loaders not working for Mario Noriega’s Dassault Mercure.
I have looked over the aircraft.cfg and noted that it only gives the animation speed for the doors, no coordinates for any of the door locations. Was wondering of anybody has their own set of coordinates that would work. I would like to be able to use GSX and the default jetways with this aircraft.
Well, it was a bandaid. Got the jetway to connect to the primary exit on the Mercure, But looks like it may have broke the custom coding to the rear passenger exit and rear service exit access with both the shift-E 3 & 4 keystrokes and the panel buttons with both 2d & VC. The buttons are clickable, but will not actuate the rear doors. All other pax and cargo doors function as normal. I’ll be patient to wait for an answer and possible fix from you and Mario Noriega on all this.
Post by aerofoto - HJG Admin on Apr 25, 2019 20:04:02 GMT
YEP .... things like hat can happen.
The MERCURE is virtually a stand alone product .... in that one can't substitute it's panel/gauges, or sound pack, for alternative options .... and if one attempts to edit various FDE parameters then such may have an adverse effect on something else too.
I have informed Mario .... so as you say .... the best we can do is await his advice.
Yea, i read that in the manual about all the custom coding that was implemented in the simulation. Saw similar when i had it loaded in Model Converter X. When i did swap back to the backup aircraft.cfg, I did get full door usage/actuation back. The only difference between the two was the addition of the exit.0 and coordinate line. Yea, its not an issue tho, definitely don’t mind waiting for an answer back from Mario Noriega. Would rather have the fix from the source .
Post by aerofoto - HJG Admin on May 1, 2019 3:26:47 GMT
I have mentioned the MERCURE jet way data omission to the project author.
He's currently tied up in regard to R/W business commitments .... but .... is now aware of this omission and "WILL" look at it "as soon as he's able to do so" .... so .... bear with us please .... since addressing this minor omission may not be as straight-forward as a simple data edit.
Post by mariopilot - HJG Guest on May 5, 2019 21:37:09 GMT
I have investigated this. The jetway can be activated, although the cargo doors cannot be properly setup. FS-X supports only a maximum of 4 doors. These are configured to be the passenger doors, 2 front, 2 rear. Tops I could do was to get the FSX conveyor belt to line up with the rear R pax door... Sorting this issue out will require swapping things around in the model and the panel (so that I could assign door.3 to the rear cargo door for instance). The current CFG for the jetway to work is as follows:
[exits] number_of_exits = 4 exit.0 = 0.2, 38.0, -5.3, 0.544, 0 //front L exit.1 = 0.2, 38.0, 5.3, 0.544, 2 //front R exit.2 = 0.2, -38.0, -4.57, 0.456,2 //rear L exit.3 = 0.2, -38.0, 4.57, 0.456,1 //rear R //exit.4 = 0.2, 26.7, 4.317, -3.28, 1 //cargo F //exit.5 = 0.2, -15.744, 4.22, -3.15,1 //Cargo C //exit.6 = 0.2, -27.7, 3.82, -2.82,1 //Cargo R
I have provided coordinates for the other doors in case GSE users or someone clever figures how to operate doors 4 to 6 from within FSX. As you can see I have assigned the rear right pax door to be of "cargo" type. The other two are set as "emergency" to avoid the conveyor belt from going there. May cause issues with jetways on the right side of the plane. An attempt was made to call "exit.4" when the variable controlling the animation of the cargo door reached 50%, but "exit.4" is simply ignored by FSX.