Hello !

 

this is the message  (and a vocal one) I get when I activate FS2Crew 777 for the first time.

 

As stated in the documentation I have already

 

[sDK]
EnableDataBroadcast=1

 

in my 777X_Options.ini file and FSX is on a local E:\Sims\FSX  disk with no windows ont it and FSX is running with admin right since quite a long time.

This is my 1st trouble with a Fs2crew product I must admit.

 

Please note that I've intalled the product with admin option.

 

With the 777 I've always started FSX with default Cesnna not the weird thing they call an ULM.

 

On another side CFG button works and audio test too, LK, Bright , BR, GND PA, FA all OK

 

Preflight button also works but when pushed and say "Hello captain!" nothing more happens.

 

 

 

 

 

 

 

 

 

I answer to myself after updating the PMDG 777 to SP1C, now it's working fine.

Sorry for convenience.

Regards

 

 

I answer to myself after updating the PMDG 777 to SP1C, now it's working fine.

 

Cheers!
 

I have the SDK error on starting the 777 what do i need to do to get it to work?

 

edt : Seems to be working now. Also what does the secondary button do?

Here's how to trouble shoot SDK warnings:

 

http://www.support.fs2crew.com/help/manuals/#pageid=troubleshooting5

 

 

The main culprit is using saved situation files... those are a no no.

 

 

Secondary button is used for Button Control.

 

Cheers,

"using saved situation files... those are a no no."

 

Does that mean I have to do all 777 flights using FS2Crew without interruptions?

I always get the SDK error when resuming a flight saved by RadarContact.

So far with other FS2Crew products (PMDG 747X and 737NGX) this never has been a problem.

Why now?

I always get the SDK error when resuming a flight saved by RadarContact.

 

 

The saved flight is the definitely problem.

 

However, you may be able to trick it by loading the saved flight "twice".

 

It seems the SDK loads properly on alternate load attempts.

 

The NGX and 777 both use Simconnect for the SDK, and Simconnect is sensitive to the way it's loaded.

Thanks for the tip. That may be the way to load a flight saved by RC4:

Close the FS2Crew window.

Save the flight by RC4 and immediately also save it in FSX.

Reloading it through RC4 will give a corrupted panel state, loading the FSX saved flight on top of it will correct that.

Then FS2Crew will work.

(At least it did once, I hope it stays that way.)