JeffG

Not sure what is happening but it doesn't appear that FS2crew is reading my aircraft data correctly. I am get V-speed callouts way below my actual speeds. Maybe a corrupt panel.cfg or sdk issue? I have the most current version of FS2crew and am running this on p3dv5.

Similar to the thread here: https://www.avsim.com/forums/topic/555675-takeoff-calls-have-stopped/

The Dash 8 is the only aircraft I fly since I upgraded to P3D V4, I've done some 55 flights and FS2Crew has worked perfectly on all of them but now there is no V1, Rotate or gear up callout.

The check power callout is still working though, I have no idea. Every single flight I have always done the exact same procedures and my last two flights this has happened which has left me rather confused.

I don't use nor LINDA or FSiPanel, if I can provide any more info please let me know!

Kind Regards,

Matthew

since Updated to the latest 3.3, i have lost my female first officer. i would like to have the lady back.

since updated, i got back the troubles with transition, when descend.
i can not use transition while descending before the descend checklist start.
the old (was repaired) problem is back now: when i descend, and press transition, the
copilot did say double say  "set crosscheck, set crosscheck".
and also after transition Only while descend, the co begins the descend checklist again...

 

There are several voice control vids on youtube, but no luck yet with a button one.

Any ideas?

Thanks.

The Majestic is installed under C:\programs on my FSX Steam machine and is my main FSX simulator now. I do have UAC turned off and no issues with other programs with permission problems. I have 

It must be a key assignment problem, because I can open the FS2Crew Main Panel via the VIEWS -> INSTRUMENTS PANEL menu. Also, when I click the button on my joystick, an action cycles though the information window and the FO responds. So, my issue is getting the process to talk to the key assignment...I will post this, but in the mean time, I will remove and reinstall FS2Crew to see if this helps.

Before I start removing FSX-SE and re-installing outside of the C:\programs, I wanted to know what should appear in the panel.cfg for the Majestic for FS2Crew to be happy? I did notice these changes to the panel.cfg, which appear ok. All windows open manually.

Window21=FS2Crew Main Panel
Window22=FS2Crew Marshaller Panel
Window23=FS2Crew PA Panel
Window24=FS2Crew Briefing Panel

and then at the bottom of the entries, below the [Vcockpit00] color, and default view was the 4 FS2Crew Windows.

[Window21]
size_mm=959, 56
pixel_size=959, 56
position=3
visible=0
ident=1000
zorder=100
Sizeable=0
gauge00=FS2Crew2010\Versions\MJCQ400\Gauges\FS2CrewQ400Voice!FS2Crew_MainPanel, 0,0,959,56
gauge01=FS2Crew2010\Versions\MJCQ400\Gauges\FS2CrewQ400Voice!FS2Crew_Audio, 20,20,5,5
gauge02=FS2Crew2010\Versions\MJCQ400\Gauges\FS2CrewQ400Voice!FS2Crew_VoiceMain, 10,10,5,5
[Window22]
size_mm=600, 110
pixel_size=600, 110
position=6
visible=0
ident=2777
zorder=102
Sizeable=0
gauge00=FS2Crew2010\Versions\MJCQ400\Gauges\FS2CrewQ400Voice!FS2Crew_Marshaller, 0,0,600,110
[Window23]
size_mm=256, 458
pixel_size=256, 458
position=6
visible=0
ident=1003
zorder=103
Sizeable=0
gauge00=FS2Crew2010\Versions\MJCQ400\Gauges\FS2CrewQ400Voice!FS2Crew_PAPanel, 0,0,256,458
[Window24]
size_mm=400, 800
pixel_size=400, 800
position=3
visible=0
ident=1005
zorder=104
Sizeable=0
gauge00=FS2Crew2010\Versions\MJCQ400\Gauges\FS2CrewQ400Voice!FS2Crew_BriefPanel, 0,0,400,800

When I bring up the configuration manager, how do I minimise it again? I presume if I X out at the top right, kills the session?

Regards

Geoff

When I use the arrow for exemple with a saved scenario to go "before start chk" I don't hear any sound from the FO.

When I start FS2Crew for DashQ8-400 the message appears to update my program to version 3.3.

But when I go to my shop and download the program it still is version 3.1 on my configmanager.

Any idea how to get this right?

Frans van Zantbeek

I tried assigning different keys and buttons via P3D Version 3.4 such as C, N, and joystick keys to Alt static source, and nothing works. When it did work the very first time I tried it, I got the main menu bar, the voice announcements, check lists and everything. Now it just won't start again. P3D is also running with admin permissions. 

[Vcockpit01]
//file=prev_$vc2q400.bmp
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024, 1024
texture=$vc2q400

gauge00=mjc84_main!VC_sheet2_gauges,  0,0,1024,1024

gauge01=../Gauges/FSFX/Q400/fsfx_RealEffects_1!saturation, 0,0,1,1 //FSFX_Q400_Effect
gauge02=../Gauges/FSFX/Q400/fsfx_RealEffects_2!smoke, 0,0,1,1 //FSFX_Q400_Effect
gauge03=FS2CrewQ400Voice!FS2Crew_Icon, 10,10,10,10

//--------------------------------------------------------
[Vcockpit02]
//file=$vc3q400.bmp
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024, 1024
texture=$vc3q400
gauge00=mjc84_main!VC_sheet3_gauges,  0,0,1023,1043

//--------------------------------------------------------
[Vcockpit03]
//file=$vc4q400.bmp
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024, 1024
texture=$vc4q400
gauge00=mjc84_main!VC_sheet4_gauges,  0,0,1024,1024

Day=255,255,255
Night=87,86,75
Luminous=255,255,255

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=2600

[Window21]
Background_color=0,0,0
size_mm=937,390
ident=14403
gauge00=F1GTN!GTN650,  0,0,937,390,UNIT1.POP
window_pos= 0.660, 0.740
window_size= 0.340, 0.260
zorder=99
[Window22]
size_mm=255,800
Position= 0
window_size= 0.058, 0.243
visible=1
ident=14400
zorder=100
gauge00=F1GTN!GTNStack,  0,0,255,870
[Window23]
size_mm=959, 56
pixel_size=959, 56
position=3
visible=0
ident=1000
zorder=100
Sizeable=0
gauge00=FS2CrewQ400Voice!FS2Crew_MainPanel, 0,0,959,56
gauge01=FS2CrewQ400Voice!FS2Crew_Audio, 20,20,5,5
gauge02=FS2CrewQ400Voice!FS2Crew_VoiceMain, 10,10,5,5
[Window24]
size_mm=600, 110
pixel_size=600, 110
position=6
visible=0
ident=2777
zorder=102
Sizeable=0
gauge00=FS2CrewQ400Voice!FS2Crew_Marshaller, 0,0,600,110
[Window25]
size_mm=256, 458
pixel_size=256, 458
position=6
visible=0
ident=1003
zorder=103
Sizeable=0
gauge00=FS2CrewQ400Voice!FS2Crew_PAPanel, 0,0,256,458
[Window26]
size_mm=400, 800
pixel_size=400, 800
position=3
visible=0
ident=1005
zorder=104
Sizeable=0
gauge00=FS2CrewQ400Voice!FS2Crew_BriefPanel, 0,0,400,800
 

Uninstall and reinstall FS2Crew MJS pack

For button do I then start P3D3v2.3

(PS I installed only the Client and Control msi of the last update)

A. do I enable FS2, from the Config Panel, then select MJS (or is than done before enabling?), then make the button assignments

or do I select MJS and configure the 3 buttons, then enable FS2?

But is this all done in Full Screen, or Windowed mode?

Or any mix of the above.....

If after I press the main button and get nothing, I shall record my swear words and post them on this site.

This is just to describe an issue (a CTD) which occurred twice just after using the second button for TRANS ALT when climbing. I recently upgraded the Q400 from Pilot to Pro. I am using it with Spad Next and LINDA=YES in CFG. Without Spad Next things go on smoothly.

My rig is W7-Pro FSX

Best,

Seems the dash 8 does not do this for me, can't ever work out what is happening or what the first officer is doing if anything.

I get no flows like in the 737 like pre-start flow  I ask for him to start 2 and he acknowledges but nothing seems to happen upon watching youtube they seem to have START Engines I just have start engine 2 or 1 but nothing at all happens very

annoyingly. The dash 8 is not my fav plane and the fs2crew for it seems no better than the plane ATM.

I've tested the Q400 without FS2Crew and the issue didn't happen.

The problem is: as soon as I start FS2Crew on the Q400, I start to hear a voice saying "hello!" at random times. And after takeoff, the FO keep saying "a thousand to go, ALT SEL", during all the climb to cruise altitude.

Reading the forum I found some people with this problem but the discussion always goes to LINDA and I get lost.

Best,

Heron

I installed today the updated Q400 Bundle Pack version 3.1, which has the LINDA option. I hope this solves the irritating FO stuttering "1000 to go alt sel". But there is another problem I discovered still in version 3.0: during the ground checklists and when climbing, after passing transition level, both pilots say "altimeter zero-zero-zero-zero". When descending, after setting the destination pressure, they say the correct value.

Do you think this could be a LINDA's fault, a completely new problem, or the often culprit installed between my chair and the keyboard?

Best

Cheers Rod.

can not find in docunmentation.

how to set volume of sound in button version?

for me its too loud.

in briefing i have set T/O PWR to MTOP.

After startchecklist the MTOP is set, for any seconds,

but while taxi and takeoff procedure the FO set this alwasy back to NTOP 90%.

when i press the MTOP button in the Dash, the FO set it back to NTOP90%.