Raphael_Chacon

[09MAR19] FS2C not working after PMDG 747 Update

Recommended Posts

Hello,

Did someone else experience some problems about thew PMDG Updates?    My FS2Crew is not working after that...

Txs

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Posted (edited)

Nope. Updated this morning, flying this evening with FS2Crew. Not one single issue.

P3Dv4 Win10.

Edited by vc10man

Share this post


Link to post
Share on other sites

Even the RAAS is not working....  Also noticed that products seemed to be deactivated(747 and 737 products), so i just enabled em booth again, but is not working inside the sim.   After actual flight in reinstalling everything and see what happen.

Share this post


Link to post
Share on other sites

How did you carry out the Update just released?

Did not need de-activation at all, and the 737NGX which has not been touched by the 747 Update does also not require de-activation. Don't really know what other inherent issues you may be having.

Share this post


Link to post
Share on other sites

I just went through the PMDG OC....

After that and going to the flight, i noticed no FS2C product was working (747/RAAS).   Then opened the FS2C enabling application and noticed that 747 and 737 were deactivated....  so i just clicked on it again but..i guess i got to restart sim, which i will do after current flight.   

  Hope the info is useful, im going to test in few hours and report back.

Share this post


Link to post
Share on other sites
1 hour ago, Raphael_Chacon said:

got to restart sim,

Precisely

 

1 hour ago, Raphael_Chacon said:

info is useful,

1 hour ago, Raphael_Chacon said:

PMDG OC

Yes, and was the correct way to Update.Well Done,

Share this post


Link to post
Share on other sites

The PMDG update "may" have over-written the panel.cfg with a fresh version.

In that case, you simply need to "re-enable" FS2Crew via the FS2Crew Config Manager to get the FS2Crew entries back on the panel.cfg file.

 

Share this post


Link to post
Share on other sites

Affirmative, Thanks,

Just did that after my long haul.... everything seems normal after that.

Happy flying!

Share this post


Link to post
Share on other sites
Posted (edited)

Hi Bryan,

it seems they changed something in the SDK regarding the flaps. During the before and after takeoff checklist the flaps reported by the FO are incorrect and so are the flaps callouts when the flaps reach the commanded positions. I asked PMDG regarding the flaps and Chris Markis said they haven't changed anything reagring the flaps themselves, but probably sth in the SDK. 

here is the link:

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/pmdg-747-queen-of-the-skies-ii-forum/5391-takeoff-checklist-issue-with-fs2crew-since-update

Both the 744 and 748 are affected.

thanks

Marc

Edited by Ephedrin

Share this post


Link to post
Share on other sites

Marc,

Thanks for bringing this to my attention.

Send me a Support Ticket...  If able maybe you can help me test the fix.

 

Share this post


Link to post
Share on other sites
8 hours ago, Ephedrin said:

Hi Bryan,

it seems they changed something in the SDK regarding the flaps. During the before and after takeoff checklist the flaps reported by the FO are incorrect and so are the flaps callouts when the flaps reach the commanded positions. I asked PMDG regarding the flaps and Chris Markis said they haven't changed anything reagring the flaps themselves, but probably sth in the SDK. 

here is the link:

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/pmdg-747-queen-of-the-skies-ii-forum/5391-takeoff-checklist-issue-with-fs2crew-since-update

Both the 744 and 748 are affected.

thanks

Marc

 

Are you sure about this?

Because I just installed the latest PMDG updates, checked all the numbers and tried to reproduce your issue.

The flap callouts are working fine for me.

Let me know.  

 

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, byork said:

 

Are you sure about this?

Because I just installed the latest PMDG updates, checked all the numbers and tried to reproduce your issue.

The flap callouts are working fine for me.

Let me know.  

 

Hi Bryan,

yes I'm sure, on my 747. But I'm on an approach right now with the -400 and am experiencing some very strange flight characterisitcs regarding drag and lift (and a violent nose down dive) after a FS2C flaps extension. I will try a flight without FS2C to make sure and if it's still the same behaviour I will uninstall the 747 and reinstall the latest download from the PMDG site. If this won't help I will come back to you and PMDG. 

Thank you for checking it on you side. 😃

 

Edit: the latest "thing" was that I've just called for Flaps 30 (coming from Flaps 20) and she said "Speed checked green flaps 30" exactly as I am writing here, while the flaps were still travelling. 

 

Edit 2: during the landing my armed spoilers didn't deploy (which is obviously nothing FS2C gets access to) and after my FO cleaned up the Flaps retracted and when they passed around the Flaps 10 indication she called "Flaps 10 green"

 

Maybe you can read something out of these edits but I will check for the issue in my installation anyway. 

Edited by Ephedrin

Share this post


Link to post
Share on other sites

Violent nose down:  That's not FS2Crew.  FS2Crew can press buttons in the cockpit, but can't alter anything "internal" in the aircraft.

I checked the SDK and it's returning the same expected values as before.

PMDG didn't change anything.

 

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
5 hours ago, byork said:

Violent nose down:  That's not FS2Crew.  FS2Crew can press buttons in the cockpit, but can't alter anything "internal" in the aircraft.

I checked the SDK and it's returning the same expected values as before.

PMDG didn't change anything.

 

Okay, thanks for your effort, I‘ll try a reinstallation of the 747 and FS2C as soon as I‘m back home. 

Why I told you about the nose down: I‘ve had this once in the 737 before I had FS2C and when the flaps were assigned via an FSUIPC axis. Something got messed up and the airplane internally extended the flaps to position 40 but only displayed them at 5. I solved this with a new FSUIPC.ini file. Now all my flaps are controlled by FS2C. However after your latest reply I am pretty confident that it‘s an issue on my side.

Edited by Ephedrin

Share this post


Link to post
Share on other sites

Hi Bryan,

to let you know, after investigating on my system and reading some older posts in the PMDG forum I remembered that I have used a custom saved panel state which I had saved using P3Dv4.3 and the old version of the 747. After deleting this panel state and using a new one everything has been working fine.

Thanks,

Marc

Share this post


Link to post
Share on other sites

Cool, glad you got it sorted 🙂

We generally recommend not using custom panel states, or saved situation files.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now