Hello,

i have the issue that the pilot monitoring does not turn on the batteries or connect the GPU during the pre-flight events. I use the cold and dark panel state, avail lights up on the external power button. I tried everything in the settings, but nothing works for me.

Maybe someone can help me.

Thank you!

Matthias

Edited July 15, 20196 yr by Gizzo82

Did you change your Transit / Crew change option on the Pre Flight events page?

That one needs to be set to No because connecting the GPU isn't done on a transit leg.

And did you manually start the APU or anything?

 

 

The crew change option is on no, and i leave anything how it is in the cockpit. I load in the cold and dark state and start the preflight event. At +30min the Copilot adjust the seat and the table and then nothing happens. The next thing what he perform in the cockpit is the APU firetest, but there is no power in the cockpit. I tried with an another liverie, on another airport, and with or without jetways...

Is the FO moving any switches?

Are you using the latest version of P3D v4?

You need the latest version.

The mouse macro ID's are based on the latest version of P3D v4.

If you're not using the latest version, you'd need to re-assign the mouse IDs.

 

I use the latest version of P3DV4. The first switch the FO moves is the APU firetest button. Lights working, flaps and so on. The only thing, when i didn't miss something, the FO don't set the autobreak to max during the afterstart/taxi flow. However, my only problem at the moment is the powering on the batteries and ground power... 

Autobrake:

Are you sure the PM's taxi flow was run?

He does his taxi flow right after he does his control check, and setting the Autobrake to max is part of that.

FS2Crew has a built in facility to test mouse macros.

Please do this:

Go to Config - Mouse Macro Setup.

Go to page 4.

"Right click" on the LSK associated with Autobrake Max.

Does the autobrake go to Max for you?  (toggles on/off).

If it does, we know you're mouse macros work fine.

If not, it means you're not using the latest version of P3D V4 and you'll need to re-assign your mouse IDs (takes about 4 minutes).

We have a large user base now and we tested the mouse macro system across many machines, and everyone's ID will be the same so long as you're on the same version of P3D V4.

 

Let me know about the Autobrake, and from there we can sort your GPU issue.

 

 

 

It´s definitely the newest version of prepar3d (4.5.12.30293), but yes, that was the issue also with the GPU and Batteries! I re-assign the mouse ID´s and now it works! I can not say why that was so...

I had tried everything, but I did not come up with the idea with possibly wrong mouse ID´s...

 

Now, as with almost all other versions, i can finally use fs2crew for FSLABS as it should. 

 

Thank you for the fast and kind support!!!

 

Glad you got it sorted 🙂