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.

 

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...

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

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

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

Where one dont know what one is deleting.

That sent my whole computer inte selfrepair mode.

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 

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.

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

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.

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.

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.

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.

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...

 

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

Strange things happen ... FSUIPC freshly installed and did a 10:30hrs flight from AMS to SFO today without a problem.

YEAH.... i do not understand how it will be FSUIPC problem if the two codes are not compatible, etc. For people who fly for VA, FSUIPC is a must need for some ACARS. so can we please just all get along. Find the issue, resolve it so we dont have this problem for the 777, and the 737, and the 748i, and you get the point...

10 hours ago, MarkW said:

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.

In this case it is quite clear. I gave the logical solution above. No need special education for that. If you are a developer, you can even more easily see the cause. It is a sad thing, but it is way to common. Worse is that there is only one developer who apologized and admitted doing wrong.

This is causing valuable time and money for other companies. People report this as an error. It will cost companies a lot of money to do error search. When they say that the fault is in the other end, it will also cost in badwill. This is a more serious issue than you might believe.

Just now, hasse29 said:

In this case it is quite clear. I gave the logical solution above. No need special education for that. If you are a developer, you can even more easily see the cause. It is a sad thing, but it is way to common. Worse is that there is only one developer who apologized and admitted doing wrong.

This is causing valuable time and money for other companies. People report this as an error. It will cost companies a lot of money to do error search. When they say that the fault is in the other end, it will also cost in badwill. This is a more serious issue than you might believe.

Well I think you need to consider the source.  Pete Dowson is one of the most respected developers in our community and would go out of his way to help if he could.  If he says that FSUIPC is not the cause I tend to believe him.  I am not saying PMDG is not highly regarded but until RSR makes a statement I think we can believe Pete.  Anyway enough on this topic, I am certain a solution will be forthcoming.

36 minutes ago, MarkW said:

Well I think you need to consider the source.  Pete Dowson is one of the most respected developers in our community and would go out of his way to help if he could.  If he says that FSUIPC is not the cause I tend to believe him.  I am not saying PMDG is not highly regarded but until RSR makes a statement I think we can believe Pete.  Anyway enough on this topic, I am certain a solution will be forthcoming.

I think it's quite possible that this may not the "fault" of either PMDG or FSUIPC, but rather a problem in P3D V4. It is, after all, the sim itself which is responsible for loading various DLLs listed in dll.xml, allocating resources for each etc. The problem may be there.

Let us not forget that this is the very first iteration of the new P3D... for all intents "version 1.0.0" of the public release of V4, and the first to use 64 bit code.

Few if any programs this complex are launched without bugs. Though PMDG worked closely with LM during the pre-release phase of P3D V4, FSUIPC was not yet ready until after P3D V4 hit the streets.