|
Post by joethebro on Apr 24, 2019 12:42:47 GMT
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.
|
|
|
Post by aerofoto - HJG Admin on Apr 24, 2019 23:06:52 GMT
If that (jet way) data isn't included within FSX version MERCURE 100 .... then .... that's because we've never had it to start with. As the MERCURE is Mario's own simulation I prefer he only address this particular matter .... so .... I'll drop him a line, when I can, and we'll see what he can come up with later on .... OK Mark C AKL/NZ
|
|
|
Post by joethebro on Apr 25, 2019 0:04:43 GMT
Thank you very much, that would be awesome !!! Im trying to see if i can get a temp fix at this time on my own. Not sure if its gonna work but hey, thats what backups are for.
Again, thank you sir
|
|
|
Post by joethebro on Apr 25, 2019 14:42:14 GMT
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.
Thank you
|
|
|
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.
Mark C AKL/NZ
|
|
|
Post by joethebro on Apr 25, 2019 22:20:02 GMT
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 .
Thanks either way. Now its the waiting game.
|
|
|
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.
Mark C AKL/NZ
|
|
|
Post by mariopilot - HJG Guest on May 5, 2019 21:37:09 GMT
Hello all,
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.
|
|
blahblahgats
CV-990
Moods not good right now, lost to grown men in their 40s and 50s.
Posts: 22
|
Post by blahblahgats on Jun 16, 2023 7:07:24 GMT
Hello, I had this issue too when i got the VC-10, so as such, yesterday i said "I want jetways for the VC-10!" So as such, i got to take a Exit code from the AI MD-83, saw how the jetway would go, and then edit its values, tested it out, edit again, test it out and so on and so forth, and like 30 minutes later i got right! [exits] number_of_exits = 1 exit.0 = 0.3, 52.6, -4.887, 1.0, 0 This is my first time of editing the values of the CFG file, so its probably bad for you.
|
|
|
Post by Thales Coelho on Aug 7, 2023 18:22:11 GMT
Hello,
Those CFG edits works whith SODE Jetways?
|
|
|
Post by aerofoto - HJG Admin on Aug 8, 2023 4:03:27 GMT
"IF" .... we're talking about the HJG hosted DMFS VC10's .... and "IF" FSX version CFG based EXIT data for these simulations (meaning the revised data which we/HJG offer per the "YELLOW HILITED" files on the VC10 downloads pages) is not already there, then, the reason for that is because the last DMFS released versions of these simulations didn't include it. And the reason for that is because "prior HJG getting their grubby little hands on these files" the DMFS VC10/C1K simulations (panels at least) were never previously fully FSX portable .... a fact that DM himself acknowledged. Thanks to George CARTY's efforts though these simulations (what we offer and panel-wise) "ARE" now FSX portable .... featuring the fixes we applied to them (among the other DMFS simulations/panels too) and as much earlier publicized on this forum. Someone else earlier posted in regard to apparently using MD-83 FSX CFG based EXIT co-ordinates for the DMFS VC10's, but, this "is not" the best solution .... in all due respect to that persons desire to want to try'n help" Again .... "IF" FSX CFG based EXIT data based data isn't provided by us (for the VC10's), then, I'll get it looked at later. Got other RW priorities on the go at the moment though so this won't happen overnight .... I'm sorry Mark C AKL/NZ
|
|