FS2Crew not starting

[blazer05 15]

Okay, here is what I have done:

1 - reinstall - no joy

2 - make sure FS2Crew is enabled - Yes - but no joy on FS2C starting with the FSLabs A320 loaded and at the gate.

3 - make sure Auto Feather is assigned to "U" as all my FS2C are.

4 - FS2C works with all my other aircraft

OK - FSLabs A320 is loaded at the gate running on GPU and parking brake is set.  Then I press U to open FS2C and nothing.  I also have UGCX and it continues to work with FSLabs.

OK - I am probably missing something simple but I am at a wall here.

Your help is appreciated as always.  I love FS2C.

Franklin Duncan

[byork 2,258]

Hi Frank,

The FS2Crew entries are probably not on your panel.cfg for some reason.

The test is to try to open the FS2Crew Main Panel via the VEHICLES -> INSTRUMENT PANEL menu in P3D.

If you don't see the FS2Crew in the list of panel "windows", then you know FS2Crew is not on your panel.cfg file.

You can also open the Airbus's panel.cfg file with notepad and physically check if FS2Crew entries are on it.

 

[blazer05 15]

Thanks Bryan - I am not at my PC but I will check this tonight.  Your support of your product is among the best in the flight sim community.

Franklin Duncan

 

[blazer05 15]

Under VEHICLES - INSTRUMENT PANEL - saw no mention of FS2Crew.

Now what?

 

[byork 2,258]

1 hour ago, blazer05 said:

Under VEHICLES - INSTRUMENT PANEL - saw no mention of FS2Crew.

Now what?

 

That means FS2Crew is not on your panel.cfg.

Are you sure you 'enabled' FS2Crew via the FS2Crew FSLabs Config Manager as per the manual?

Make sure you run things with Admin rights to avoid write permission issues.

 

Edited March 1, 2022 by byork

[blazer05 15]

I will go back and check to ensure I enabled FS2C per the manual.

I always run with Admin rights - it solves so many issues.

Franklin Duncan

[byork 2,258]

Also, when you installed the FS Labs, did you try installing it to a custom location?

That can sometimes mess things up if the FS2Crew Config Manager is unable to locate the panel.cfg file.

[blazer05 15]

I used the address for one of my SSDs.  But when installing your program found the location without issue.

Franklin Duncan

[blazer05 15]

Reinstalled and no joy.

Can I manually add the correct entries to the panel.cfg?

 

[byork 2,258]

39 minutes ago, blazer05 said:

I used the address for one of my SSDs.  But when installing your program found the location without issue.

Franklin Duncan

That's the problem.

In some cases, this can trip things up and things can get messy when everyone starts using their own custom paths.

Can you reinstall the FS Labs aircraft, but don't use custom paths option.

That'll be much simpler than trying to hand edit multiple panel.cfg files.

 

 

[blazer05 15]

Where would I expect to find the FS2crew files?

Wouldn't they be in the same group of folders as the FSLabs aircraft?

[byork 2,258]

The problem is not the FS2Crew files.  The problem is the FS2Crew's config manager ability to write to your panel.cfg file.

When you installed FS2Crew, the installer correctly auto detected the location of your P3D folder, right?

You didn't manually try to install it to some other location, right?

[blazer05 15]

Yes it installed to my P3d folder - so my understanding is that is correct.

Tell me if this is my issue.

P3d is on my E drive (an SSD card) but FSLabs A320 is in the Documents/Prepar3D V5 Addons folder

This is on my C drive = C then Users/name/Documents/Prepar3D V5 Add-ons/FSLabs/SimObjects/Airplanes - then folders for all my FSLabs aircraft.

Sorry to be so slow to realize this is probably the problem.

[byork 2,258]

Hi Frank,

Please take a close look at this thread:

 

Edited March 2, 2022 by byork

[blazer05 15]

That looks like a solution.

I also want to ensure that my posts do not appear to be critical of your product at all.

I knew it was something you could figure out and get me corrected.

Will report back and let you know if this solves my issue.