Page 1 of 1

Opening exits ?

PostPosted: Fri Jan 23, 2009 4:55 am
by gypsymoth
I'd be grateful if someone could tell me which file controls the opening of exits?  I have Mike Stone's at9 with opening exits but the 757-200 which doesn't & I don't know where to go to check it out.  :-?
Thanks.

Re: Opening exits ?

PostPosted: Fri Jan 23, 2009 5:38 am
by Daube
the animations of the exits and the exits themselves are directly integrated into the model, there's no way you can edit them.

The only thing that you can edit is the speed of those exits, in the aircraft.cfg.

Re: Opening exits ?

PostPosted: Fri Jan 23, 2009 8:15 am
by gypsymoth
Thanks - I thought someone might say something like that!

Re: Opening exits ?

PostPosted: Fri Jan 23, 2009 1:32 pm
by RAFAIR100
This thread has galvanised me into trying to address a problem which has bugged me since pussy was a kitten.       I can generally get the main exit to open with SHIFT + E.      But, when there is more than one exit, or a tail ramp, I press SHIFT +E then quickly hit 2.    Nothing happens.      Where am I going wrong?

Re: Opening exits ?

PostPosted: Fri Jan 23, 2009 1:44 pm
by Groundbound1
[quote]This thread has galvanised me into trying to address a problem which has bugged me since pussy was a kitten.       I can generally get the main exit to open with SHIFT + E.      But, when there is more than one exit, or a tail ramp, I press SHIFT +E then quickly hit 2.

Re: Opening exits ?

PostPosted: Sat Jan 24, 2009 5:58 am
by microlight
The exit assignments are normally controlled by this entry in the aircraft.cfg file, like this:

[exits]
number_of_exits=4
exit_rate.0=0.4                               ;Percent/second
exit_rate.1=0.2                               ;Percent/second
exit_rate.2=0.4                               ;Percent/second
exit_rate.3=0.4                               ;Percent/second

Unfortunately, it doesn't stop there. As you might have noticed, sometimes the exit (or pushback) key commands don't work as you expect them to. This is usually because some gauge or other in your panel is issuing 'invisible' repeating key-event commands in the background that interfere with the normal panel operation. The pushback issue is effectively solved with Rob Barendregt's excellent pushback gauge V4, and there is an exit control gauge which I haven't tried (exit_gauge_v1.1.zip, this and Rob's gauge on Avsim) that might suit your need.

;)