2 hours ago, Fervex said:

All the errors encountered appear to be related to the non-uninstalling of the previous P3D V3.4 (with the directories cleaning, registry with ccleaner etc) and the new PMDG installer which check the two versions at the same time. Make your choice and no more problem with FSUIPC 5 or this beautiful 747 !

Run all "install folder\Prepar3D v4\redist\Interface\" (FSX-RTM\retail\lib, FSX-SP1\retail\lib, FSX-SP2-XPACK\retail\lib to see gear, etc..

I am tending to agree. I removed my complete P3Dv3 along with everything else include the Ops Center. Installed P3Dv4, Queen, FSUIPC (registered) - all worked OK.

2 hours ago, Fervex said:

All the errors encountered appear to be related to the non-uninstalling of the previous P3D V3.4 (with the directories cleaning, registry with ccleaner etc) and the new PMDG installer which check the two versions at the same time. Make your choice and no more problem with FSUIPC 5 or this beautiful 747 !

Run all "install folder\Prepar3D v4\redist\Interface\" (FSX-RTM\retail\lib, FSX-SP1\retail\lib, FSX-SP2-XPACK\retail\lib to see gear, etc..

Not in my case. The issue occurs on a newly-built computer that never had P3D or any PMDG aircraft installed previously.

It does have Win 7 Home Premium 64, which also seems to be a common thread - Win 10 appears to be less affected.

9 hours ago, JRBarrett said:

Not in my case. The issue occurs on a newly-built computer that never had P3D or any PMDG aircraft installed previously.

Not my case as well. I uninstalled the v3 version, then installed both v3 and v4, as suggested. Anyway now the problem seems gone (without me doing anything) if I load the default F22 first.

Have any of you tried loading a saved flight?  It's completely buggered for me although I never have a problem with initially loading the 747.  

Has there been any update on this issue?Been experiencing the same issue and indeed,it seems to be a problem with FSUIPC5.If i disable this,the 747 loads up fine.But sad to have no custom controls then.

Keeping an eye on this topic!

Regards,

Steven Ghion

13 hours ago, Fervex said:

All the errors encountered appear to be related to the non-uninstalling of the previous P3D V3.4 (with the directories cleaning, registry with ccleaner etc) and the new PMDG installer which check the two versions at the same time. Make your choice and no more problem with FSUIPC 5 or this beautiful 747 !

Run all "install folder\Prepar3D v4\redist\Interface\" (FSX-RTM\retail\lib, FSX-SP1\retail\lib, FSX-SP2-XPACK\retail\lib to see gear, etc..

Not in my case either... I've moved from FSX directly to P3D v4 and so far I can only get the 747 to work with FSUIPC5 when I load a default aircraft first then load the 747 on top of it. (Naturally the 747 works just fine with FSUIPC5 removed)

I'm also on Windows 7 which seems to fit the trend.

Problem is back, I'm the OP.

Even without Chase Plane installed, I uninstalled it, and I uninstalled AS4, I get black screens, no gear, no click spots and no initialization.

Could it have been a simconnect AS4 installed?  I even uninstalled it and same.

I have FSUIPC5 but it is not registered.

So again, I have no 747.  Huge disappointment.

In the FSUIPC forum Pete Dowson (developer of FSUIPC) has mentioned something about PMDG discovering some interaction with legacy FSUIPC code, and although the latest update to FSUIPC, 5.101k, hasn't fixed the problem (and in fact for me the workaround stopped working when I installed 5.101k), it does sound like there is an interaction between PMDG 747 and FSUIPC which might just be the cause of our grief. Watch this space, I'd say.

3 minutes ago, cathay808 said:

In the FSUIPC forum Pete Dowson (developer of FSUIPC) has mentioned something about PMDG discovering some interaction with legacy FSUIPC code, and although the latest update to FSUIPC, 5.101k, hasn't fixed the problem (and in fact for me the workaround stopped working when I installed 5.101k), it does sound like there is an interaction between PMDG 747 and FSUIPC which might just be the cause of our grief. Watch this space, I'd say.

If the FSUIPC's are installed separately, one (3.4) and registered and the other (V4) not registered, and only one 747 installed, in V4, I'm curious how PMDG can interact with 3.4's FSUIPC.

 

Just now, Jack_Sawyer said:

If the FSUIPC's are installed separately, one (3.4) and registered and the other (V4) not registered, and only one 747 installed, in V4, I'm curious how PMDG can interact with 3.4's FSUIPC.

 

No no, I meant that the 747 is trying to interact with FSUIPC 5 (in P3D v4) using old code. I'll quote Pete Dowson's post from the FSUIPC forum below:

11 hours ago, Pete Dowson said:

I think PMDG may have located the problem. It seems they DO use FSUIPC, and have used the old ModuleUser.lib code which dates back about 17 years and which is not compatible with a 64-bit prrocess like P3D4.

They've only just told me they use this, and it really surprised me.

I will temporarily make FSUIPC ignore module user calls until I work out a 64-bit implementation. That change will be in FSUIPC 5.101k, later today.

Pete

 

 

The change Pete mentioned, 5.101k, actually made mine stop loading altogether - previously I could still load the 747 by loading a default aircraft first, but now that wouldn't work either. This is fascinating as it's the first time we've seen that a change to FSUIPC could predictably alter whether the 747 would load.

What I JUST discovered after restoring my system to a save the other day with Aconis is this.

First, let me rewind, yesterday I installed AS4 beta, ran V4 with Chase Plane as I always do.

Went to KDEN, loaded up the default plane.

Loaded up the 747, it initialized and all was right with the world.

Shut down the sim and got some lunch.

Came back 30 minutes later all ready to finally make the tutorial flight from KDEN to KSFO.

Same procedure as above but now the 747 wouldn't initialize!  WHAT!?!?!

So I quit the sim.

Ran Chase Plane and told it to NOT start with V4.

Ran V4 and loaded the default then the 747.

It worked!

Okay, so there's a problem with Chase Plane right?  Wrong.

Shut down the PC for dinner.

Booted it and now I CANNOT get the 747 to initialize.  WHAT????!!?!?!

So I uninstalled AS4 and the simconnect it installed.

No help.

Went to bed.

Now back to the Acronis recovery I just made.

Same problem.

Thought it was Chase Plane.

Nope.

Then I read about your post so I thought why not move all the FSUIPC stuff out of the folder and lo and behold it works.

I can now load the default plane then the 747 initializes WITH Chase Plane.

Since I don't have the registered version for V4, and since I don't use it for flight controls, I use the Saitek SST, I know but it works.

So I KNOW for 100% certain it HAS to be FSUIPC5 as I can duplicate this all day.

Hope this long boring screed helps someone.

Now, if FSUIPC for 3.4 somehow manages to develop its own AI and weasels its way into V4 I'll be bumfuzzled.

 

31 minutes ago, Jack_Sawyer said:

Then I read about your post so I thought why not move all the FSUIPC stuff out of the folder and lo and behold it works.

I can now load the default plane then the 747 initializes WITH Chase Plane.

Oh... I hadn't thought to mention that because in page 2 of this thread we had established that if you remove FSUIPC5 it all works flawlessly.

Now try loading the 747 directly (rather than default plane first) - that works for me when I don't have FSUIPC5 installed.

(But being that I fly with FTG and the FTG ACARS requires FSUIPC, removing FSUIPC isn't a desirable fix for me - hence I've been pursuing the matter.)

1 minute ago, cathay808 said:

Oh... I hadn't thought to mention that because in page 2 of this thread we had established that if you remove FSUIPC5 it all works flawlessly.

Now try loading the 747 directly (rather than default plane first) - that works for me when I don't have FSUIPC5 installed.

(But being that I fly with FTG and the FTG ACARS requires FSUIPC, removing FSUIPC isn't a desirable fix for me - hence I've been pursuing the matter.)

I have read it, I'm the OP.

I had it working perfectly with FSUIPC installed all along.  I never registered it.

So what caused it to suddenly become messed up?

Was it installing AS4 and the simconnect it installed?

I'm making another Acronis as I type this on my Mac.  Then I'll add in AS4.  Perhaps the simconnect did it?

I never ran all the sim connects msi's like a lot of people do because Elaine (@Poppet) said I didn't need to, and I don't think there's anyone on this Earth in the sim community I trust more.

So could it have been that simconnect that ASN installed?  Or could it have been the AS4 simconnect somehow interacting with FSUIPC?

I don't know one millionth of this stuff like others do.  So I'm trying to be cautious.

I'm just very curious as to what caused it all of a sudden.

And yes, as soon as it's backed up in 30 minutes I'll try loading just the 747 without loading a default plane first.

Best regards.

Jack

Pete just hinted that a patch from PMDG is imminent.  I just checked the Ops Center but nothing yet.  As I like to predict things here goes.  747 Patch to fix this by Saturday June 10th and 777 released same day as I am sure this issue affects it as well.  

4 minutes ago, MarkW said:

Pete just hinted that a patch from PMDG is imminent.  I just checked the Ops Center but nothing yet.  As I like to predict things here goes.  747 Patch to fix this by Saturday June 10th and 777 released same day as I am sure this issue affects it as well.  

Thanks, but in my above post, can you make a guess why this might have happened all of a sudden?

Could it have been AS4 beta related with the simconnect?  Did that not play well with FSUIPC?