apphangb1 prepar3d.exe? V3.1

[Manny 1,293]

OK... I installed V3.1 client successfully yesterday...tested it for a bit flew the 777 end to end and was very happy.

 

a) I saved a restore point.

 

Then I did the following

 

1) Ran the update for the ASNext for 3.1

2). Installed the KDEN flightbeam

3) Installed the new Addonamanger from SFDT

 

Flew Honolulu and it seemed good with ASNext weather 

 

Then I reinstalled the VAInterface for the PMDG 777 FMC on my samsung note poad since that was not working.

 

I noticed I had micro stutters and searched for a solution for that.. and read to increase the Water slider all the way to the right. which I did...then the machine hung

 

I tried loading several fllght and my sim was hanging...with this message 

 

apphangb1 prepar3d.exe? V3.1

 

 

What could be the problem?

=======================================

 

I went to safe mode and restored my system and brought itback to step a)

 

and it flies ok now. Note to self: Enjoy the two weeks off and just fly..enjoy what you have...until the new year!

 

Not sure which is the offending app or setting now

 

Now, I am  gun shy to install anything.. LOL

[Richard Sennett 2,499]

OK... I installed V3.1 client successfully yesterday...tested it for a bit flew the 777 end to end and was very happy.

 

I have seen some posts lately with KDEN in the posts that are having issues I would uninstall all of it (KDEN and manager) and see if your sim settles down if so there you go - always remember if possible what you installed before having problems

[Jim Young 2,356]

Hi Manny,

 

It is not KDEN as that issue was fixed (as you have proven with your flight to Honolulu with ASN).  It appears to be an issue with the Virtual Airlines Interface with the PMDG 777 FMC.  It could be a simconnect issue.  Raising your water slider to the max should not be the cause.  Check to see if the issue reappears by disabling the VA Interface (do not know how to do that).

 

An AppHang B1 freeze is extremely common and very difficult to diagnose as it does not show the faulting module to give one a clue as to the cause.  So you have to investigate the scene of the crime yourself by doing things like disabling the VA Interface, then enabling it again to see if you can replicate the freeze.  Perhaps the VA Interface is not compatible with P3D3.1 yet (some products are not compatible yet like the Object Flow dll in Orbx). 

 

Men with all their gadgets....

 

Rich is correct (as usual) to remember what you installed the last before having issues.  It is most likely the problem.

 

Best regards,