Dash 8 pro released!

[Flying Penguin 44]

"That's as far as I've got, if I get my rudder working I'll report back.  They really need to make a config utility for this...."

 

 

 

 

I really apreciate your time and skill on this but i am a pilot not that much into this ini.file configuration changes if you understand so i will properly leave the 4 x smoother experience out of the sales speech and wait for something user handy to come along. 

 

Thanks alot anyway  ,  :wink: 

 

Michael Moe

 

I wouldn't give up, it really is a different beast even if just with the yoke mapped.  I'll post up my config file when I finish it (hopefully tonight), then it will be a drag and drop.

[Michael Moe 495]

I wouldn't give up, it really is a different beast even if just with the yoke mapped.  I'll post up my config file when I finish it (hopefully tonight), then it will be a drag and drop.

 

Thanks but i dont understand what you meen by "just the yoke mapped".

 

Right now my situation is a SAITEK Yoke , A Trottletek 737 thrust unit and SAITEK rudderpedals,

 

So far they all "work" 

 

Michael Moe

[Flying Penguin 44]

Thanks but i dont understand what you meen by "just the yoke mapped".

 

Right now my situation is a SAITEK Yoke , A Trottletek 737 thrust unit and SAITEK rudderpedals,

 

So far they all "work" 

 

Michael Moe

 

By default, the Q400 Pro relies on FSX/P3D feeding it control data, using this config edit allows it to work with the joystick outside the confines of FSX (hence why they can poll at 125hz).

 

There is no reason everything has to come through FSX, or everything through the alternate method.  Right now, my yoke comes through the Q400 specific interface, whilst FSX provides the data from my pedals and my throttles.  As far as I'm concerned, they all "work", i.e. I can use them all to fly the aircraft.

 

When I say I can't get my rudder to work yet, all that means is I've reset it to be handled by P3D (just like it was in the Pilot edition), not that I'm not able to use it.

[devgrp 1,233]

The bits I changed were:

 

 

My suggested changes in bold.  

 

This assumes only a yoke and the only button explicitly mapped is the AP Disengage which maps to the right hand button on a Saitek Yoke.  The pedals will still be dealt with by FSX (I haven't got my pedals to work, but will try again tonight).  If you find that the Elevator is inverted, remove the axis assignment from the above and use the following line which has a minus after the equals:

 

J0_Y=-FlightControls_->sensors.Elevator0_ADC

 

For me, my yoke worked fine as J0, but if you get stuck, in FSUIPC, go to axis assignment and click rescan.  Move your yoke and it should detect the axis.  Look at the joystick number (probably 0).  If it isn't 0, simply change J0 to J{Number shown in FSUIPC}.

 

That's as far as I've got, if I get my rudder working I'll report back.  They really need to make a config utility for this....

To get the rudder working use J2_Rz=FlightControls_->sensors.Rudder0_ADC

[Flying Penguin 44]

To get the rudder working use J2_Rz=FlightControls_->sensors.Rudder0_ADC

 

I'll give that a shot, thanks!  Think my Rudder is J1, based on FSUIPC, but it took so long to get anything to work (the aforementioned re-loading issue) that I gave up and went to bed....

[carlito777 712]

What is the advantage to configute the controls through the Q400 interface rather than FSUIPC? I have my Saitek Yoke setup in FSUIPC and it works fine with the Q400. So where is the benefit?

[devgrp 1,233]

What is the advantage to configute the controls through the Q400 interface rather than FSUIPC? I have my Saitek Yoke setup in FSUIPC and it works fine with the Q400. So where is the benefit?

The benefit is smoother controls because its by passing fsx's polling which operates at a lower frequency. I use the majestic control option for my ele, ail and rud. Everything else goes thru fsuipc

[Flying Penguin 44]

 

 

To get the rudder working use J2_Rz=FlightControls_->sensors.Rudder0_ADC

 

Thanks, a quick adjustment to J1 and that worked!

 

I really apreciate your time and skill on this but i am a pilot not that much into this ini.file configuration changes if you understand so i will properly leave the 4 x smoother experience out of the sales speech and wait for something user handy to come along. 

 

Thanks alot anyway  ,  :wink: 

 

Michael Moe

 

Michael,

 

Now that I've got a working file, I might as well post the whole thing here so you can try it if the instructions are a bit much. Bold and sizing are just so you can see what I edited, they won't be saved in the INI, so you could just copy and paste this into the file as a whole (backing it up first of course!)

 

Everything not in bold is default, so there should be no reason you can't just take the below.

 

 

 

[iNTERFACE]
; GENERAL SUPPORT OF THE INTERFACES
COCKPIT_INTERFACE=1
LABJACKUSB_INTERFACE=1
JOYSTICK_INTERFACE =1
ASN_INTERFACE=1


; UDP 0 CONNECTOR FOR THE SHARED COCKPIT
[uDP_CONNECTOR_0]
UDP_ENABLED=0
SEND_RATE_DIVIDER=0; // 128 times per second
UDP_BROADCAST_ALLOWED=1
UDP_BROADCAST_MASK=0.0.0.0:49200
UDP_RECEIVE_ALLOWED=1
UDP_RECEIVE_MASK=0.0.0.0:49210
ICP_TX_FILTER=6152
ICP_RX_FILTER=6152

; UDP 1 CONNECTOR FOR THE SHARED COCKPIT OBSERVER LINK
[uDP_CONNECTOR_1]
UDP_ENABLED=0
SEND_RATE_DIVIDER=0; // 128 times per second
UDP_BROADCAST_ALLOWED=0
UDP_BROADCAST_MASK=0.0.0.0:0
UDP_RECEIVE_ALLOWED=0
UDP_RECEIVE_MASK=0.0.0.0:49200
ICP_TX_FILTER=6152
ICP_RX_FILTER=6152


; UDP 2 CONNECTOR FOR THE SYSTEM PANEL
[uDP_CONNECTOR_2]
UDP_ENABLED=1
SEND_RATE_DIVIDER=16; // 8 times per second
UDP_BROADCAST_ALLOWED=1
UDP_BROADCAST_MASK=127.0.0.1:49230
UDP_RECEIVE_ALLOWED=1
UDP_RECEIVE_MASK=0.0.0.0:49240


[EFIS]
; 1 for KG, 0 for LBS
FUEL_KG_UNITS=0
; 1 for hPa, 0 for Inches
PRESSURE_HPA_UNITS=0
; 1 to syncronize pilot and copilot side altimeter settings
PFD_QNH_SYNC=1
AFCS_FSX_SYNC=1


[GRAPHICS]
Enable =1
SmoothingQuality=1
;VECTOR_RATE 0=1x, 1=1/2x, 2=1/4x, 3=1/8x
VECTOR_RATE=2
; Q400 will make sure the screen drawing thread always consumes power.
; If this option is enabled, recommend to set VECTOR_RATE to 0
LoadEqualization=0

[sYSTEM]
; timing source 0=Queue Timer, 1=Multimedia Timer
TimingSource=0
; disabling the FDE to FSX syncronization might be necessary if unlimited fps setting is used
disableFDEtoFSXSync=0
; by default Dash-8 will not load it's tasks onto the CPU core where the FSX process runs
disableFSXCPUBypass=0
; Here one can specify which CPU cores the certain function threads will prefer to run
; 1 bit per core. For example, 2=CPUid2, 4=CPUid3, 6=CPUid2+3 Only takes effect if disableFSXCPUBypass is not 0
systemThreadsCPUMask=0
graphicsThreadCPUMask=0




; All parameters generally from -1.0 to 1.0
;

[FLIGHTCONTROLS]
; this means, no real force feedback available
ElevatorInFSXmode = 1
; TillerInput = 0: tiller control is with mouse only
; TillerInput = 1: turning ailerons below 40kts will steer the plane
; TillerInput = 2: tiller is mapped to the spoiler axis
TillerInput =1


; Flight Controls positions from FSX
ElevatorsByFSX=0
AileronsByFSX=0
RuddersByFSX=0


; CENTER AND DEFLECTION ARE IN THE 0x0000-0xFFFF range

ELEVATOR0_CENTER =32768
ELEVATOR0_DEFLECTION =32768

AILERON0_CENTER =32768
AILERON0_DEFLECTION =32768

RUDDER0_CENTER =32768
RUDDER0_DEFLECTION =32768

BRAKEL0_OFF =1
BRAKEL0_ON =65535

BRAKER0_OFF =1
BRAKER0_ON =65535

ELEVATOR1_CENTER =32768
ELEVATOR1_DEFLECTION 0

AILERON1_CENTER =32768
AILERON1_DEFLECTION 0

RUDDER1_CENTER =32768
RUDDER1_DEFLECTION 0

BRAKEL1_OFF =1
BRAKEL1_ON =65535

BRAKER1_OFF =1
BRAKER1_ON =65535

TILLER_CENTER =32768
TILLER_DEFLECTION =32768

FORCEFEEDBACK_TWIST =0.00


YAW_DUE_TO_PROPWASH =1.0
TURBULENCE_FACTOR =0.75

ELEVATOR_EFFECTIVENESS =0.4
AILERONS_EFFECTIVENESS =0.5
RUDDERS_EFFECTIVENESS =0.5
PEDALS_STEERING_EFFECTIVENESS = 0.5
AUTO_RUDDER_FACTOR =1.0


[ENGINECONTROLS]
; PARAMETERS ARE WITHIN THE 0x0000-0xFFFF range
; now tuned to the noisy sim

PL1_REVERSE =-4096
PL1_DISC =0
PL1_FLTIDLE =18000
PL1_RATING =65535
PL1_MAX =65535

PL2_REVERSE =-4096
PL2_DISC =0
PL2_FLTIDLE =18000
PL2_RATING =65535
PL2_MAX =65535

CL1_FUELOFF =5000
CL1_START =23370
CL1_850 =38158
CL1_900 =53264
CL1_1020 =65152

CL2_FUELOFF =5000
CL2_START =23092
CL2_850 =39032
CL2_900 =53080
CL2_1020 =65280
AUTO_DIFFERENTIAL_THRUST_ON_TAXI =1



[VISION]
; This section is for the Flght Training Device Vision
LeftViewAngle = 0.04
LeftViewOffset = 0
RightViewAngle = -0.03
RightViewOffset = 0

[sOUND]
; global focus means, sounds will be played even when window inactive
GlobalFocus = 1
;Set the following to 1 if experiencing sound problems under Windows 7
Win7CompatibilityMode = 0
; Device on which all sounds in this section will be played. 0 Sound Mapper,
; 1..n is a device number as it appears in the "Default Device" list at the audio page of the windows sound settings.
MainPlaybackDeviceId = 0
; Device on which the headphone sounds will be played, can be the same as the MainPlaybackDeviceId
HPNPlaybackDeviceId = 0


; the next entries define to which speakers the respective sounds will be routed to. The map is created by adding the flags, corresponding to the particular sound

channels in a SB 9.1 standard, as follows:
; SOUND 3D -1
; SOUND INACTIVE 0
; SPEAKER_FRONT_LEFT 1
; SPEAKER_FRONT_RIGHT 2
; SPEAKER_FRONT_CENTER 4
; SPEAKER_LOW_FREQUENCY 8
; SPEAKER_REAR_LEFT 16 ( if you dont hear any sound from it, try SPEAKER_SIDE_LEFT instead)
; SPEAKER_REAR_RIGHT 32 ( if you dont hear any sound from it, try SPEAKER_SIDE_RIGHT instead)
; SPEAKER_SIDE_LEFT 64 ( microsoft would usually play it at REAR LEFT)
; SPEAKER_SIDE_RIGHT 128 ( microsoft would usually play it at REAR RIGHT)

; the XXXX_sound_level has 3 values in % (from 0..100), for cockpit, cabin and external views

; The map for left engine sounds. Engine sounds will also be played by subwoofer in anycase
left_engine_sounds_map = -1
left_engine_sound_level = 50,80,75

; The map for right engine sounds. Engine sounds will also be played by subwoofer in anycase
right_engine_sounds_map =-1
right_engine_sound_level = 50,80,75

; MAP for left side headphones navigation sounds.
leftpilot_hpn_sounds_map = 1
leftpilot_hpn_sound_level = 75,0,0

; MAP for left side speaker navigation sounds.
leftpilot_spkr_sounds_map = -1
leftpilot_spkr_sound_level = 75,0,0

; MAP for right side headphones navigation sounds.
rightpilot_hpn_sounds_map = 2
rightpilot_hpn_sound_level = 75,0,0

; MAP for right side speaker navigation sounds.
rightpilot_spkr_sounds_map = -1
rightpilot_spkr_sound_level = 75,0,0

; MAP for observer navigation sounds.
observer_sounds_map = -1
observer_sound_level =75,0,0

; MAP for synthetic warnings (same for left/right side). was 48
synthetic_warnings_map = -1
synthetic_warnings_sound_level = 75,0,0

; avionics fan
avionics_fan_map = -1
avionics_fan_sound_level = 75,0,0

; sounds, coming from the cabin
cabin_sounds_map = -1
cabin_sounds_level = 110,100,0

; clicks from the switches and knobs (is it possible to do this dynamically)
switch_clicks_map = -1
switch_clicks_sound_level = 100

; Nose Gear sound
NoseGear_sound_map = -1
NoseGear_sound_level = 100,100,100

; Sound for left langing gear
LeftLandingGear_sound_map = -1
LeftLandingGear_sound_level = 75,75,100

; Sound for right langing gear
RightLandingGear_sound_map = -1
RightLandingGear_sound_level = 75,75,100

; Ambient wind sound, left side of windshield
LeftAmbientWindSound_map = -1
LeftAmbientWindSound_level = 50,50,50

; Ambient wind sound, right side of windshield
RightAmbientWindSound_map = -1
RightAmbientWindSound_level = 50,50,50

; Sound when aircraft rolls
GroundRollSound_map = -1
GroundRollSound_level = 75,75,75

; APU/GPU sound
APUSound_level = 0,0,100
GPUSound_level = 35,0,100


; passenger entertainment settings
; flag to enable/disable all announcements of flight attendant
entertainment_FA_announcements_enabled = 1
; flag to enable/disable all announcements from flight deck
entertainment_FC_announcements_enabled = 1
; flag to enable/disable music
entertainment_music_enabled = 1
; if set to 1, announcements will be played according to the announcements script.
; if set to 0, the announcements still can be played manually using FMS
entertainment_auto_announcements = 1



[JOYSTICK_INTERFACE_ASSIGNMENTS]
; See SpecialFeatures.pdf Joystick Connector section for description
; Ailerons
J0_X=FlightControls_->sensors.Aileron0_ADC
; Elevators
J0_Y=FlightControls_->sensors.Elevator0_ADC
; Rudder
J1_Rz=FlightControls_->sensors.Rudder0_ADC
; AP DISC
J0_b1=AFCS_->inputs.AP_disengage


[CONFIGURATION]
cockpitConfigScript=
; Maintenance Deprecation Factor specifies how much faster the aircraft is weared off compare to the real life
WearOffFactor=10.0
; Pause the sim when FMS1 Top Of Descend is reached
PAUSE_ON_TOD=0

 

The above was for the following hardware

• Saitek Yoke & Quadrant (J0 in the INI)
• Saitek Rudder Pedal (J1 in the INI)

In theory it should work for any yoke/pedal combination, though you may need to work out the ID number of the joystick.  To do this either:

• Look in the "USB Game Controllers" page in Control Panel and 0 will be the top controller in the list, then 1, 2, 3 etc.. (the way the manual says)
• Open up the paid version of FSUIPC and click on "Axis Assignment".  Click on "Rescan" and move the yoke, the controller number will appear in the box labelled Joy#.  Click rescan and repeat for the rudder

 

Hope the above is useful for someone!

[Michael Moe 495]

 

 

 

 

Thanks, a quick adjustment to J1 and that worked!

 

 

Michael,

 

Now that I've got a working file, I might as well post the whole thing here so you can try it if the instructions are a bit much. Bold and sizing are just so you can see what I edited, they won't be saved in the INI, so you could just copy and paste this into the file as a whole (backing it up first of course!)

 

Everything not in bold is default, so there should be no reason you can't just take the below.

 

 

The above was for the following hardware

• Saitek Yoke & Quadrant (J0 in the INI)
• Saitek Rudder Pedal (J1 in the INI)

In theory it should work for any yoke/pedal combination, though you may need to work out the ID number of the joystick.  To do this either:

• Look in the "USB Game Controllers" page in Control Panel and 0 will be the top controller in the list, then 1, 2, 3 etc.. (the way the manual says)
• Open up the paid version of FSUIPC and click on "Axis Assignment".  Click on "Rescan" and move the yoke, the controller number will appear in the box labelled Joy#.  Click rescan and repeat for the rudder

 

Hope the above is useful for someone!

 

Thanks alot  :wink:

 

 

But i cannot get the rudder to work . Its jammed to the right . Any ideer ? :wink: I have it set as Z because RZ does not work . The control panel seems ok under rudder settings

 

 

Update : its from a saved flight . Maybe this is causing rudder to behave bad

 

Its 26 click to left on the pedestal and it does not react to commands with A/P off or on

 

 

Update 2 ; nope does not move with a normal flight as well

Michael Moe

[Flying Penguin 44]

Thanks alot  :wink:

 

 

But i cannot get the rudder to work . Its jammed to the right . Any ideer ? :wink: I have it set as Z because RZ does not work . The control panel seems ok under rudder settings

 

 

Update : its from a saved flight . Maybe this is causing rudder to behave bad

 

Its 26 click to left on the pedestal and it does not react to commands with A/P off or on

 

 

Update 2 ; nope does not move with a normal flight as well

Michael Moe

 

Ok, so if it's the rudder only, we are dealing with the following line in the INI:

J1_Rz=FlightControls_->sensors.Rudder0_ADC 

A few possibilities spring to mind.

 

1.  Another controller is in position 1, possibly a throttle quadrant?  This seems likely as by assigning another axis you get a response (even if it's not the one you want). With your current version, try moving your other axes in turn (including throttle quadrant and brake axis).  If you find that any of the axes that aren't on the pedals give a response on the rudder (or if you get no response at all), try the following:

J2_Rz=FlightControls_->sensors.Rudder0_ADC 

2.  If you get a response from an axis on the rudder pedals, there is also the possibility that your rudder axis is not Rz (though this is less likely).  The possible values (from the manual) are listed below, you just have to try them one after another (re-loading the whole shebang each time unfortunately, or you are likely to find that nothing at all works)

X
Y
Z
Rx
Ry
Rz
Ax
Ay
Az
ARx
ARy
ARz
Fx
Fy
Fz
FRx
FRy
FRz
Vx
Vy
Vz
VRx
VRy
VRz
Slider1
Slider2
ASlider1
ASlider2
VSlider1
VSlider2
FSlider1
FSlider2

3. If all that fails, use my original file and find the following line:

RuddersByFSX=0

 

and replace it with

RuddersByFSX=1

That will restore your previous rudder settings, so at least you can fly it with the yoke set up, until Majestic (hopefully!) come out with a config tool...

 

[Olmba 27]

Amazing work , thanks a lot..

 

When you use your twist on your joystick as rudder remember to set the same number as the Elevator and Aileron, in my case it will be like this ;

 

J0_Rz=FlightControls_->sensors.Rudder0_ADC

 

Have done some adjustment to the engine control (IDLE & DETENT) and removed the AP disengage button (J0_b1=AFCS_->inputs.AP_disengage) The Ap disengage button is mapped with the FSUPIC 

 

Here is my INI optimized for use with Saitek X52 Pro:

 

Edit: Update with new engine control setting.

 

 

[iNTERFACE]

; GENERAL SUPPORT OF THE INTERFACES

COCKPIT_INTERFACE=1

LABJACKUSB_INTERFACE=1

JOYSTICK_INTERFACE =1

ASN_INTERFACE=1

 

 

; UDP 0 CONNECTOR FOR THE SHARED COCKPIT

[uDP_CONNECTOR_0]

UDP_ENABLED=0

SEND_RATE_DIVIDER=0; // 128 times per second

UDP_BROADCAST_ALLOWED=1

UDP_BROADCAST_MASK=0.0.0.0:49200

UDP_RECEIVE_ALLOWED=1

UDP_RECEIVE_MASK=0.0.0.0:49210

ICP_TX_FILTER=6152

ICP_RX_FILTER=6152

 

; UDP 1 CONNECTOR FOR THE SHARED COCKPIT OBSERVER LINK

[uDP_CONNECTOR_1]

UDP_ENABLED=0

SEND_RATE_DIVIDER=0; // 128 times per second

UDP_BROADCAST_ALLOWED=0

UDP_BROADCAST_MASK=0.0.0.0:0

UDP_RECEIVE_ALLOWED=0

UDP_RECEIVE_MASK=0.0.0.0:49200

ICP_TX_FILTER=6152

ICP_RX_FILTER=6152

 

 

; UDP 2 CONNECTOR FOR THE SYSTEM PANEL

[uDP_CONNECTOR_2]

UDP_ENABLED=1

SEND_RATE_DIVIDER=16; // 8 times per second

UDP_BROADCAST_ALLOWED=1

UDP_BROADCAST_MASK=127.0.0.1:49230

UDP_RECEIVE_ALLOWED=1

UDP_RECEIVE_MASK=0.0.0.0:49240

 

 

[EFIS]

; 1 for KG, 0 for LBS

FUEL_KG_UNITS=1

; 1 for hPa, 0 for Inches

PRESSURE_HPA_UNITS=1

; 1 to syncronize pilot and copilot side altimeter settings

PFD_QNH_SYNC=1

AFCS_FSX_SYNC=1

 

 

[GRAPHICS]

Enable =1

SmoothingQuality=1

;VECTOR_RATE 0=1x, 1=1/2x, 2=1/4x, 3=1/8x

VECTOR_RATE=2

; Q400 will make sure the screen drawing thread always consumes power.

; If this option is enabled, recommend to set VECTOR_RATE to 0

LoadEqualization=0

 

[sYSTEM]

; timing source 0=Queue Timer, 1=Multimedia Timer

TimingSource=0

; disabling the FDE to FSX syncronization might be necessary if unlimited fps setting is used

disableFDEtoFSXSync=0

; by default Dash-8 will not load it's tasks onto the CPU core where the FSX process runs

disableFSXCPUBypass=0

; Here one can specify which CPU cores the certain function threads will prefer to run

; 1 bit per core. For example, 2=CPUid2, 4=CPUid3, 6=CPUid2+3 Only takes effect if disableFSXCPUBypass is not 0

systemThreadsCPUMask=0

graphicsThreadCPUMask=0

 

 

 

 

; All parameters generally from -1.0 to 1.0

;

 

[FLIGHTCONTROLS]

; this means, no real force feedback available

ElevatorInFSXmode = 1

; TillerInput = 0: tiller control is with mouse only

; TillerInput = 1: turning ailerons below 40kts will steer the plane

; TillerInput = 2: tiller is mapped to the spoiler axis

TillerInput =1

 

 

; Flight Controls positions from FSX

ElevatorsByFSX=0

AileronsByFSX=0

RuddersByFSX=0

 

 

; CENTER AND DEFLECTION ARE IN THE 0x0000-0xFFFF range

 

ELEVATOR0_CENTER =32768

ELEVATOR0_DEFLECTION =32768

 

AILERON0_CENTER =32768

AILERON0_DEFLECTION =32768

 

RUDDER0_CENTER =32768

RUDDER0_DEFLECTION =32768

 

BRAKEL0_OFF =1

BRAKEL0_ON =65535

 

BRAKER0_OFF =1

BRAKER0_ON =65535

 

ELEVATOR1_CENTER =32768

ELEVATOR1_DEFLECTION =0

 

AILERON1_CENTER =32768

AILERON1_DEFLECTION =0

 

RUDDER1_CENTER =32768

RUDDER1_DEFLECTION =32768

 

BRAKEL1_OFF =1

BRAKEL1_ON =65535

 

BRAKER1_OFF =1

BRAKER1_ON =65535

 

TILLER_CENTER =32768

TILLER_DEFLECTION =32768

 

FORCEFEEDBACK_TWIST =0.00

 

 

YAW_DUE_TO_PROPWASH =1.0

TURBULENCE_FACTOR =0.75

 

ELEVATOR_EFFECTIVENESS =0.4

AILERONS_EFFECTIVENESS =0.5

RUDDERS_EFFECTIVENESS =0.5

PEDALS_STEERING_EFFECTIVENESS = 0.5

AUTO_RUDDER_FACTOR =1.0

 

 

[ENGINECONTROLS]

; PARAMETERS ARE WITHIN THE 0x0000-0xFFFF range

; now tuned to the noisy sim

 

PL1_REVERSE =-4096

PL1_DISC =0

PL1_FLTIDLE =18000

PL1_RATING =52224

PL1_MAX =65535

 

PL2_REVERSE =-4096

PL2_DISC =0

PL2_FLTIDLE =18000

PL2_RATING =52224

PL2_MAX =65535

 

CL1_FUELOFF =5000

CL1_START =23370

CL1_850 =38158

CL1_900 =53264

CL1_1020 =65152

 

CL2_FUELOFF =5000

CL2_START =23092

CL2_850 =39032

CL2_900 =53080

CL2_1020 =65280

AUTO_DIFFERENTIAL_THRUST_ON_TAXI =1

 

 

 

[VISION]

; This section is for the Flght Training Device Vision

LeftViewAngle = 0.04

LeftViewOffset = 0

RightViewAngle = -0.03

RightViewOffset = 0

 

[sOUND]

; global focus means, sounds will be played even when window inactive

GlobalFocus = 1

;Set the following to 1 if experiencing sound problems under Windows 7

Win7CompatibilityMode = 0

; Device on which all sounds in this section will be played. 0 Sound Mapper,

; 1..n is a device number as it appears in the "Default Device" list at the audio page of the windows sound settings.

MainPlaybackDeviceId = 0

; Device on which the headphone sounds will be played, can be the same as the MainPlaybackDeviceId

HPNPlaybackDeviceId = 0

 

 

; the next entries define to which speakers the respective sounds will be routed to. The map is created by adding the flags, corresponding to the particular sound

 

channels in a SB 9.1 standard, as follows:

; SOUND 3D -1

; SOUND INACTIVE 0

; SPEAKER_FRONT_LEFT 1

; SPEAKER_FRONT_RIGHT 2

; SPEAKER_FRONT_CENTER 4

; SPEAKER_LOW_FREQUENCY 8

; SPEAKER_REAR_LEFT 16 ( if you dont hear any sound from it, try SPEAKER_SIDE_LEFT instead)

; SPEAKER_REAR_RIGHT 32 ( if you dont hear any sound from it, try SPEAKER_SIDE_RIGHT instead)

; SPEAKER_SIDE_LEFT 64 ( microsoft would usually play it at REAR LEFT)

; SPEAKER_SIDE_RIGHT 128 ( microsoft would usually play it at REAR RIGHT)

 

; the XXXX_sound_level has 3 values in % (from 0..100), for cockpit, cabin and external views

 

; The map for left engine sounds. Engine sounds will also be played by subwoofer in anycase

left_engine_sounds_map = -1

left_engine_sound_level = 50,80,75

 

; The map for right engine sounds. Engine sounds will also be played by subwoofer in anycase

right_engine_sounds_map =-1

right_engine_sound_level = 50,80,75

 

; MAP for left side headphones navigation sounds.

leftpilot_hpn_sounds_map = 1

leftpilot_hpn_sound_level = 75,0,0

 

; MAP for left side speaker navigation sounds.

leftpilot_spkr_sounds_map = -1

leftpilot_spkr_sound_level = 75,0,0

 

; MAP for right side headphones navigation sounds.

rightpilot_hpn_sounds_map = 2

rightpilot_hpn_sound_level = 75,0,0

 

; MAP for right side speaker navigation sounds.

rightpilot_spkr_sounds_map = -1

rightpilot_spkr_sound_level = 75,0,0

 

; MAP for observer navigation sounds.

observer_sounds_map = -1

observer_sound_level =75,0,0

 

; MAP for synthetic warnings (same for left/right side). was 48

synthetic_warnings_map = -1

synthetic_warnings_sound_level = 75,0,0

 

; avionics fan

avionics_fan_map = -1

avionics_fan_sound_level = 75,0,0

 

; sounds, coming from the cabin

cabin_sounds_map = -1

cabin_sounds_level = 110,100,0

 

; clicks from the switches and knobs (is it possible to do this dynamically)

switch_clicks_map = -1

switch_clicks_sound_level = 100

 

; Nose Gear sound

NoseGear_sound_map = -1

NoseGear_sound_level = 100,100,100

 

; Sound for left langing gear

LeftLandingGear_sound_map = -1

LeftLandingGear_sound_level = 75,75,100

 

; Sound for right langing gear

RightLandingGear_sound_map = -1

RightLandingGear_sound_level = 75,75,100

 

; Ambient wind sound, left side of windshield

LeftAmbientWindSound_map = -1

LeftAmbientWindSound_level = 50,50,50

 

; Ambient wind sound, right side of windshield

RightAmbientWindSound_map = -1

RightAmbientWindSound_level = 50,50,50

 

; Sound when aircraft rolls

GroundRollSound_map = -1

GroundRollSound_level = 75,75,75

 

; APU/GPU sound

APUSound_level = 0,0,100

GPUSound_level = 35,0,100

 

 

; passenger entertainment settings

; flag to enable/disable all announcements of flight attendant

entertainment_FA_announcements_enabled = 1

; flag to enable/disable all announcements from flight deck

entertainment_FC_announcements_enabled = 1

; flag to enable/disable music

entertainment_music_enabled = 1

; if set to 1, announcements will be played according to the announcements script.

; if set to 0, the announcements still can be played manually using FMS

entertainment_auto_announcements = 1

 

 

 

[JOYSTICK_INTERFACE_ASSIGNMENTS]

; See SpecialFeatures.pdf Joystick Connector section for description

; Ailerons

J0_X=FlightControls_->sensors.Aileron0_ADC

; Elevators

J0_Y=FlightControls_->sensors.Elevator0_ADC

; Rudder

J0_Rz=FlightControls_->sensors.Rudder0_ADC

; AP DISC

J0_b1=AFCS_->

J0_b2=AFCS_->

 

 

[CONFIGURATION]

cockpitConfigScript=ccReadyForTakeoff

; Maintenance Deprecation Factor specifies how much faster the aircraft is weared off compare to the real life

WearOffFactor=10.0

; Pause the sim when FMS1 Top Of Descend is reached

PAUSE_ON_TOD=0

 

 

Edited November 21, 2015 by Olmba

[carlito777 712]

One quick question: Axis assignments in both P3D itself and FSUIPC have to be deleted (for aileron, elevator and rudder) if I want to use that Q400's own control interface as described above, right?

[Olmba 27]

One quick question: Axis assignments in both P3D itself and FSUIPC have to be deleted (for aileron, elevator and rudder) if I want to use that Q400's own control interface as described above, right?

 

Yes correct..

[Michael Moe 495]

Yes correct..

 

I havent deleted the FSUIPC axis. They dont seem to conflict. Its so much smoother now. Thanks alot everyone.

 

Michael Moe

[SquadronLeader 61]

Hi

 

I am using P3DV3 and have just downloaded and installed the Dash 8 pro to my main P3D root file.

 

I then went to follow the P3DV3 beta patch, as shown here

 

2.  Very Critical Step!!!
There is an alternate .dll (mjc84_main.dll.p3dv3beta) which has been supplied for the Beta testing purposes specifically for users of P3D v3 which is located in your PANEL Folder.  Please ensure to re-name the default/original .dll to something like mjc84_main.dll.original, and re-name the supplied .dll to mjc84_main.dll.

 

 

but I cannot find the PANEL folder, and when I search for the .dll, nothing comes up.

 

What am I doing wrong and where should I be looking for the PANEL folder?