Hi,

 

I am having an SDK error with the PMDG 600/700 expansion package. I am able to run FS2Crew in NGX 800 without a problem, however expansion package gives me hard time. My NGX expansion package is SP 1.c (1.00.3219). I did couple of times uninstall/installs with NGX and FS2Crew but no luck. I also deleted the livery .ini's in PMDG/Aircraft folder. But again it did not sort out, I am out of options and any help will be appreciated.

 

Cheers,

Hi,

 

From the on-line manual:

 

Problem:  The FO is acting strange and I'm getting an audio "SDK Warning" alert when I open the FS2Crew Main Panel.  For example, the beacon was on, yet during the checklist he said "Are you sure"? during the beacon challenge.

Solution:

1. You need to ensure you have installed SP1C or later.  SP1B is not sufficient.  SP1C is currently available via the PMDG Support Forum only.  Re-install it if in doubt.
2. The PMDG NGX uses Simconnect for their SDK.  The SDK allows other programs to interface with the NGX.  Simconnect can sometimes be a bit funky.  If the NGX is not loaded properly, the SDK will not connect properly.
3. In some cases, certain 3rd party NGX liveries can interfere with the SDK.
4. Open the file below with Notepad.

Microsoft Flight Simulator X\PMDG\PMDG 737 NGX\

737NGX_Options.ini

Add these two lines if they are not present in that file:

[sDK]
EnableDataBroadcast=1

Note:  IF YOU'VE INSTALLED FSX INTO THE DEFAULT 'PROGRAM FILES' FOLDER, WINDOWS WILL OFTEN 

BLOCK OTHER PROGRAMS, LIKE FS2CREW, FROM WRITING TO FILES LOCATED IN PROGRAM FILES

.  THIS IS WHY IT'S ALWAYS RECOMMENDED TO INSTALL FSX INTO A LOCATION OTHER THAN THE DEFAULT ''PROGRAM FILES' FOLDER TO AVOID THESE KINDS OF 'WRITE' PROBLEMS.

          5. Ensure the default Trike is the default aircraft visible in the FSX 'Free Flight' menu, not another aircraft.

 

6. You need to ensure that the NGX loads by default into the 

2D cockpit

, never the VC, via the FSX setting shown below here:

I have the same problem. I have sp1c installed and everything worked fine with fs2crew untill I purchased the 600-700. Now the 800 allso gives sdk error and can not start the engines properly.

Default Trike trick solved my problem, thanks!!

Installed SP1c, although it had already been installed. Now FS2Crew is gone. Now what?

Now FS2Crew is gone. Now what?

 

Re-enable Button Control via the FS2Crew NGX Config Manger. You may have to 'cycle' the enable button.

 

When you (re)installed SP1c, it probably wiped the FS2Crew entries off the NGX's panel.cfg file (resulting in FS2Crew no longer loading).

 

You can check to see if FS2Crew is attached to your NGX's panel.cfg by opening the panel.cfg file with notepad.

 

Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG 737-800NGX\panel\panel.cfg

 

 

 

You should see FS2Crew entries on it.

This stuff is gonna drive me to an early grave! I re-booted, ran everything again, and - Lo & Behold! - no SDK error. Fine, let's fly. And I did, for about a week. Last night, I once again launched FSX the "proper" way - boot into the trike, make sure the 737 loads in 2-D mode, cold & dark - set my location at Gate E3 at KFLL (Dreamteam airport), called GSX to start servicing the A/C. Opened the doors, moved the jetway over, and opened the FS2Crew panel.

 

:mellow: :huh: :angry:  In that order!!! SDK error again! #####??? I just continued on with the crew after ignoring the error and everything seemed to work, but I'm getting ready to uninstall this app and trash it. I have done everything I am supposed to do. Made sure the SP's were installed AGAIN, per the instructions. The system WAS working, and nothing else has been installed. You know, it used to be fun to open FSX, click on Load, open my favorite aircraft, and fly it. Now I have to load a freakin' hang glider at Friday Harbor on a clear day, on days starting with W, after fasting for 12 hours, then carefully load an airplane with the 2-D panel and wait till a count-down timer decides that I have spent entirely too long sitting and staring at my monitor, and maybe, MAYBE I will see what I thought I was supposed to load. Or then again, I might get a dreaded SDK error, and have to un-install MS Office and Angry Birds and my entire A2A collection and re-install as admin with my anti-virus in "silent" mode.

 

Train Sim! That's it!

I wish PMDG didn't use Simconnect for their SDK as it can be finicky, but there's not much I can do about that!

 

You don't need to "load" the trike.

 

Just have the Trike on the Main Screen.

 

In other words, don't use saved start up files.

 

 

If you want, I can help you via a Remote Desktop.

 

PM me.

 

Cheers,

I wish PMDG didn't use Simconnect for their SDK as it can be finicky, but there's not much I can do about that!

 

You don't need to "load" the trike.

 

Just have the Trike on the Main Screen.

 

In other words, don't use saved start up files.

 

 

If you want, I can help you via a Remote Desktop.

 

PM me.

 

Cheers,

Thanks, Byork. I'll probably take you up on that. However, I think you misunderstood (or I wasn't that clear, which is probably the case): I don't LOAD the trike. It is the default A/C, along with User-Defined Weather, Time of Day (System clock) and Friday Harbor. When I launch FSX, that's what appears. I then choose (usually in this order) KFLL, Gate E3, and then the PMDG 737NGX 800 Winglet, and choose Fly Now.

 

The sim launches the 737 in 2-D cockpit mode. I can pull up the FS2Crew from the panel hot-spot or a button on my X52. Most of the time, it comes up normally, but now it's starting to come up with the SDK error. Let me play with it a bit more, and then I'll get back to you about the remote help.

It sounds like you're doing everything right.

 

It could be a bad livery... I've seen that a couple times.

 

Try with a PMDG livery.

 

Also check that "enable sdk" is on your PMDG options ini.

 

Cheers,

I only use the liveries from PMDG - no 3rd-party as of yet. I am using the American Airlines 800 Winglet model currently. And (I hate all of these files - they're buried all over the place, and it took me several minutes to locate this one) here's my 737NGX_Options.ini file:

 

[iRS.0]
LastPosValid=1
[iRS.1]
LastPosValid=1
[iRS]
IRS_QuickAlign=1
IRS_UseLastPos=1
[Pushback]
PushbackUnitsFeet=1
PushbackCommsType=0
[AFS]
ThrottleATOverride=0
AutotuneOBSinLOC=1
AP_EngageRealistic=1
[userOptions]
FOCallouts=1
PauseAtTOD=0
SyncAltimeters=1
SyncStbyAltimeters=0
ShowThrustLeverPosition=0
ShowPilots=1
ServiceBasedFailures=0
TABforCDUinput=1
FOCalloutV1=0
FOCalloutVR=0
FOCalloutV2=0
[PerformanceOptions]
FPSlimit_PFD_EFIS_2D=15
FPSlimit_PFD_EFIS_VC=15
FPSlimit_ND_MAP_2D=15
FPSlimit_ND_MAP_VC=15
FPSlimit_Engine_2D=15
FPSlimit_Engine_VC=15
FPSlimit_HUD_2D=15
FPSlimit_HUD_VC=15
disableSide=2
[Aircraft Config]
FixedConfig=N1146GB
[Panel State]
StartupPanelState=NGX CLDDRK
[sDK]
EnableDataBroadcast=1
[sound]
PlaySoundsInExtView=1
SoundDevice=Speakers (High Definition Audio Device)
SoundMasterVolume=0.50
SoundGroupValue.0=1.00
SoundGroupValue.1=1.00
SoundGroupValue.2=1.00
SoundGroupValue.3=1.00
SoundGroupValue.4=1.00
SoundGroupValue.5=1.00
[FMC]
LastPosLatLon=N2604.4W08008.8

 

Note that the SDK is on. I'm going to try to load the generic 737-800 and see if that works. Back at ya in a short! Again, thanks!

Strange things happening...I just launched FSX, and got a box asking me to accept new gauges. Huh? Anyway, I left everything else alone (time, location, weather) and just loaded the AA 737NGX. Got the count-down timer in the 2-D cockpit, and then opened FS2Crew...with no errors! Moved my A/C to FLL, and turned on FS2C, and went through all of the check-lists, right up through take-off, with no problems. So far, so good...

 

Quick question: I use FSDT GSX, and so I choose (in the 737 and in FS2C) ground power. I don't choose the ground start unit in the 737 or GSX, just ground AC. I'm noticing that if I do that in FS2C, the check-list puts in a ground start, which I don't want. I usually start the APU at the gate, and then disconnect ground power. So which is the best way to use ground power, yet do the APU start route? I just cursored past the ground start in FS2C.

Glad you seem to have resolved your SDK issues.

 

For the other issue, check Option # 3 here:

 

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

 

 

Maybe that's what you're looking for.

Well, right now I'm using the button mode, but this is good advice, since I'd like to switch to voice operations shortly. For the time being, I'll just set FS2C for EXT power, and let the crew set me up that way. When I'm ready for push-back, I'll manually start the APU, and if the manual is right, when I switch to APU bleed, FS2C should automatically revert to APU power.

Addendum: the SDK issues continue to pop up. I can start the sim as directed, wait for the count-down, and open the FS2Crew panel with no problems. But flying enroute (everything worked up through take-off and climb-out, next menu item, Descent, was cued up), panel was hidden, and then I open it and get the SDK error. And after that, nothing works. This app is so iffy as to be not reliable at this point. I never know if it will work or not.

 

I hope you have some work-around, or I'm going to have to un-install it. I was looking forward to the voice version, now I don't know.