_{I think Mic but not sure.}

Bryan,  does FS2Crew use a COMM port?  My VRInsight is setup on COMM3 so just wondering if there is a conflict here?

FS2Crew doesn't use any comm ports.

 

I suspect what's happening is that that your MCP hardware is somehow corrupting the Majestic volume setting when it scans the aircraft.

 

This is why your problem only occurs with the Majestic Dash 8, and not the PMDG 737 NGX version of FS2Crew (which uses the exact same audio system).

Bryan,

 

Is your recommendation to contact the Majestic or LINDA developers to request a fix.  I am sure this is happening to a very small segment of their customers so not sure anyone will do anything but its worth a try.

Update for those of you using MCPLL/Linda.

 

After testing, it appears that Linda/MCPLL is, for some weird, reason forcing the Capt's Service Interphone knob value to 0 when it should be a 1.

 

This results in the FS2Crew crew volume value going to 0 (this is by design, because if the interphone knob value is 0, it simulates the audio mute function).

 

A work around is easy to create, but we're going to see if we can stop Linda/MCPLL from writing to that variable, but in the meantime if it happens to you just try cycling the Interphone Knob to force it back to 1.

HI

do you mean turning the knob back and forth between  serv/int and PA. It doesnt seem to help. please clarify

thx Lee

After further tests, the problem appears to be that LInda and the MCPLL hardware are not reading variables out of the Majestic Dash 8 in accordance with the Dash8's SDK, thus creating a conflict.

 

However, to help users get around this issue, I create a custom version which I just sent to MarkW.

 

Basically it removes the Service Interphone Knob as a link to Crew Volume.

 

Cheers,

Byork

your efforts and customer care are fantastic. I am anxiously waiting to be able to download your fix.

Thx Lee

Byork

your efforts and customer care are fantastic. I am anxiously waiting to be able to download your fix.

Thx Lee

 

 

your efforts and customer care are fantastic. I am anxiously waiting to be able to download your fix.

 

I'm afraid there is nothing I can fix.

 

It's something Linda is going to have to address; they do not appear to be using the Majestic SDK conventions.

Thanks for the amazing efforts Bryan.  Considering that probably a handful at most of your total customer base would be affected by this issue it is fantastic that you took the time to try and resolve this issue.  It certainly makes me pleased to be an FS2Crew customer (LDS767, PMDG737 & MajesticQ400) and looking forward to buying the 777.   In the meantime, I will have to fly the Q400 without the MCPii panel just like 98% of the rest of your customers for this product.

Have just come back to this problem after viewing all the posts. I am also using Linda and the mcp11 panel but have just tried without linda and the panel, and the problem still persists.

Have just come back to this problem after viewing all the posts. I am also using Linda and the mcp11 panel but have just tried without linda and the panel, and the problem still persists.

 

I have had this happen as well.  It is very important that the MCPII panel is shut off during FSX Startup and that the linda modules are turned off before you load up the aircraft.  If you do this then the problem will not be there (at least it has not been for me).

Thanks Mark. Will check those points.

Today I bought the FS2Crew Q400 add-on, as I also have the NGX version and am very pleased with it. I'm also suffering from the problem described above and came across this topic. Is this custom version you refer to still around, Bryan? If so, I'd be very happy, because I can't miss both LINDA and the MCP II while flying any aircraft in FSX.