Recommended Posts

The 747 for P3D v4 is loading up dead with no activation window. I tried installing the Simconnect as explained on the website, but nothing is working. I'm now repairing P3D hoping that will fix it. Please help! :) Thank  you.

  • Upvote 1

Share this post


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

8 minutes ago, godimaginedme said:

The 747 for P3D v4 is loading up dead with no activation window. I tried installing the Simconnect as explained on the website, but nothing is working. I'm now repairing P3D hoping that will fix it. Please help! :) Thank  you.

Did you install FSUIPC5? If so, remove it.

  • Upvote 1

Share this post


Link to post
Share on other sites
1 minute ago, godimaginedme said:

Thanks, Kyle. That did it. Can I use FSUIPC now that it's activated?

If it works, sure, but there have been several reports of FSUIPC causing issues here on the forum. There may be a few workarounds in those threads. I'd avoid using it if at all possible.

  • Upvote 1

Share this post


Link to post
Share on other sites

Does that mean you are not looking into this issue? How am i supposed to set up my thrust reverse levers without FSUIPC. :mellow: 

  • Upvote 1

Share this post


Link to post
Share on other sites

This issue is mentioned in the 747 forum known issues thread, and that was posted before 747 for Prepar3d v4 was released.

 

Share this post


Link to post
Share on other sites
4 hours ago, scandinavian13 said:

Did you install FSUIPC5? If so, remove it.

Stupid but I have to ask this: How do I uninstall it correctly? Just removing the files from MODULES folder?

Share this post


Link to post
Share on other sites
10 minutes ago, LH747fan said:

Stupid but I have to ask this: How do I uninstall it correctly? Just removing the files from MODULES folder?

Run the installer and select - REMOVE.

Share this post


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

Run the installer and select - REMOVE.

I have the same problem and this does not work for me. FSUIPC5 not registered version. 

 

Edit: Simply deleting everything related to FSUIPC inside the Modules folder in the P3Dv4 root, solves it.

Share this post


Link to post
Share on other sites
6 hours ago, Floeffel91 said:

Edit: Simply deleting everything related to FSUIPC inside the Modules folder in the P3Dv4 root, solves it.

Or you can just rename the FSUIPC5.dll file

Share this post


Link to post
Share on other sites
9 hours ago, Heffron said:

Does that mean you are not looking into this issue? How am i supposed to set up my thrust reverse levers without FSUIPC. :mellow: 

I do not want to be rude, but I do not understand your logic. Clearly 747 works in P3D. As soon as you install FSUIPC, it does not work. When you remove FSUIPC it works again. It is obvious that FSUIPC has some issues. Why would PMDG look into it? They do not have the code. Ask Mr Dowson to address this issue.

Share this post


Link to post
Share on other sites
20 hours ago, scandinavian13 said:

Did you install FSUIPC5? If so, remove it.

That can't be a solution to cut an arm to keep a leg?

Best Regards

Jens 

Share this post


Link to post
Share on other sites
7 hours ago, hasse29 said:

I do not want to be rude, but I do not understand your logic. Clearly 747 works in P3D. As soon as you install FSUIPC, it does not work. When you remove FSUIPC it works again. It is obvious that FSUIPC has some issues. Why would PMDG look into it? They do not have the code. Ask Mr Dowson to address this issue.

I believe the developer of FSUIPC has looked into it and concluded that it is a PMDG issue, although more correctly a L-M issue that needs to be addressed by LM.  He speculated that it was similar to another issue he had with FSUIPC and Windows10 and that LM helped him out with a fix.

Share this post


Link to post
Share on other sites
3 minutes ago, Julean said:

That can't be a solution to cut an arm to keep a leg?

 

At the moment it seems the way to resolve the issue. Keep in mind that p3dV4 developments are still ongoing and that a fix for this will probably come sooner than later. Be it from PMDG or from Pete Dowson or LM as mentioned in the post from Mark just above mine.

  • Upvote 2

Share this post


Link to post
Share on other sites
5 minutes ago, LH747fan said:

If LM would have given the chance to PMDG,.. to test the products for a week... :(

I'm pretty sure that PMDG (and all other major third party devs) have had their hands on V4 since the beginning of this year... There are just so many different add ons that things are bound to conflict at some point.

Edited by harvester21

Share this post


Link to post
Share on other sites
14 minutes ago, Julean said:

That can't be a solution to cut an arm to keep a leg?

I can see where you're coming from, kind of, but let's look at this logically:

  • P3Dv3 with 744 and No FSUIPC: Works
  • P3Dv3 with 744 and FSUIPC: Works
  • P3Dv4 with 744 and No FSUIPC: Works
  • P3Dv4 with 744 and FSUIPC: Doesn't work

FSUIPC has had a long history of doing some pretty awesome things, but it also has had a long history of doing some very weird things. We're looking into it, but, for now, FSUIPC is clearly causing an issue.

Share this post


Link to post
Share on other sites

 

1 hour ago, harvester21 said:

At the moment it seems the way to resolve the issue. Keep in mind that p3dV4 developments are still ongoing and that a fix for this will probably come sooner than later. Be it from PMDG or from Pete Dowson or LM as mentioned in the post from Mark just above mine.

I see. Thank you for the answer.

Because I have Radar Contact, the best working ATC I can get to manage, and therefore I have FSUIPC 5 registred. 
Which I also need by the way to get X-55 Rhino to work with the throttles.

So when i Load the 747: I load default F-22 and then 747 and back to F-22 and back...An after kicking and shaking the bird. ..Then she is ready...:rolleyes:

Until I corrupted the scenery.cfg with a Drzewiecky Baku X that when I tried to follow the procedure for reinstalling the scenery.cfg which I found different places.. Everything went into crisis:wacko:

http://www.prepar3d.com/forum/viewtopic.php?f=6322&t=125046

All with these half sloppy adresse · %LOCALAPPDATA%\Lockheed Martin\Prepar3D v4 :marah:

Where one dont know what one is deleting.

That sent my whole computer inte selfrepair mode.:huh:

Quote

These days: I have created an add-on folder  to put the Drzewiecky sceneries in I guess... I mean quite a change I use to have 850 scenery layers in FSX, And wonder where the Aerosoft sceneries are? Proberly externally now. Then to add FT Global meshes. And i see the Flightbeam and FSDreamteam sceneries push themselve now on top all the time in the scenerylist. ... MyTraffic; I at this time cant gett to work. And with the new codes for scenery.cfg, I dont dare to touch it either.

And then its to get FTX central from the Orbx sceneries, to arranges everything correctly.

So everyone is working high pitch in making this awesome simulator is really looks like becomming to work nicely.

 

All the best

 

Jens 

Share this post


Link to post
Share on other sites
38 minutes ago, MarkW said:

I believe the developer of FSUIPC has looked into it and concluded that it is a PMDG issue, although more correctly a L-M issue that needs to be addressed by LM.  He speculated that it was similar to another issue he had with FSUIPC and Windows10 and that LM helped him out with a fix.

That is something I am tired of. One developer blaming others when it is clear within what area the problem is. There are many out there who do that.

Share this post


Link to post
Share on other sites

Guy's.....

This was a know issue in P3Dv3 earlier too and Julian/Jens adressed the issue in the right way.

The work around is to reload the same B744 situation again when it doesn't come alive, most of the times the B744 comes alive then.

When not, just alway's start P3Dv4 in a default a/c and start that default a/c situation, then load the situation with the B744 or select the B744 a/c and it wil come alive.

In the past...that work around eats VAS, but we do not have to worry about this that much anymore. So for now we can do with that (cant we?)

Hope that helps....everybody is working hard to attach their product to the new P3Dv4, wich Simulator is indeed awesome in many way's.

Kind regards,

Ben

  • Upvote 1

Share this post


Link to post
Share on other sites

By my own trial and error I've also discovered that workaround. I'd set up a scenario with the desired time, airport, and gate and with a default aircraft (I just stay with the F-22), then once the scenario has started up I'd change to the PMDG 747. In this way I can usually get the PMDG 747 and FSUIPC 5 (unregistered - I only use FSUIPC to run FTG ACARS to fly with FTG) working together.

EDIT: I've re-read the "known issues" thread more carefully and found the entry "Issues where the aircraft loads into the simulator with the screens dead and no landing gear. (failure of dll initialization)", so I do apologize for a bit of ranting which I have now removed from this post, and shall wait for a fix.

Share this post


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

That is something I am tired of. One developer blaming others when it is clear within what area the problem is. There are many out there who do that.

But how would you know from your armchair.  I don't think there was blame but rather trying to be helpful to reach a solution.

Share this post


Link to post
Share on other sites

I too was suffering from this problem. I need FSUIPC to control all my hardware.

There were too many variables to contemplate while searching for a fix and didn't want to load another aircraft first to get eventually to the queen which, while it worked as a workaround for me, was ultimately an undesired compromise.

I decided to wipe everything - clean install W10Pro (from W764pro), P3Dv4, FSUIPC5 (register), PMDG 747 (activate). In that order. Problem solved.

Share this post


Link to post
Share on other sites
6 hours ago, Orbitandy said:

I too was suffering from this problem. I need FSUIPC to control all my hardware.

There were too many variables to contemplate while searching for a fix and didn't want to load another aircraft first to get eventually to the queen which, while it worked as a workaround for me, was ultimately an undesired compromise.

I decided to wipe everything - clean install W10Pro (from W764pro), P3Dv4, FSUIPC5 (register), PMDG 747 (activate). In that order. Problem solved.

I actually wonder if getting Windows 10 was the thing that fixed it - there seems to be a trend that Windows 10 users were able to get everything working together perfectly whereas Windows 7 users such as myself are doing the same thing but getting stuck.

Share this post


Link to post
Share on other sites
26 minutes ago, cathay808 said:

I actually wonder if getting Windows 10 was the thing that fixed it - there seems to be a trend that Windows 10 users were able to get everything working together perfectly whereas Windows 7 users such as myself are doing the same thing but getting stuck.

Can't say for sure. I would have rather stayed with W7 but the both the sim and OS platforms are moving on and as such, so will I...

 

Share this post


Link to post
Share on other sites

I removed all traces of v3 and the v4 Queen starts normally with registered FSUIPC. Win7 Pro.

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