Blackbird Sims / Milviz Forum Archive

Good day,

I am coming here in the forum to report that I could hardly use the 732 since today, because I have got consistent crashes while using th MCP of the sp177+FMS version.

I am sorry to report that I cannot define a clear pattern of sequencial actions that woul lead to the CTD. However, it happens often when I hit the LVL CHG button. This is persistant enough to have labelled the LVL CHG button "INOP" on my MCP.


It happens often in descent, but also sometime in climb. The issue is similar as the issue reported here :
http://www.milviz.com/forum/viewtopic.php?f=85&t=4174

In this thread the issue was not solved, suspecting an implication of the V. 8 of windows and of the v2.2 of P3D.

However, I do have the issue on Windows 7, P3D 2.5, MV_B737-200_P3Dv2_v2.140621 (and 4GB RAM).

Best regards,
Zed

Things are a bit hectic at the moment but it will be investigated.

Thanks !

I apologise I cannot get the topic addressing my issues well. The SP177 is malfunctioning: 1. level change works only upwards not in descend 2. Auto throttle does not function without clicking speed twice of thrice, then the speed continues to increase or decrease past set speed 3. When I click t at the right speed again twice or thrice it then remains there but will not change automatically when I adjust speed up or down. 3. Airplane turns opposite the FMS path at every turn and then only after a few minutes in the wrong direction comes back. All these problems were not there before the latest update.

P3D 2.5, win 7 64 bit.

I was finally able to replicate this in P3D. It seems LM has broken a few things regarding AP functions. We are in contact with them for this and most likely it will be resolved in the next build of P3D v3.

In fsx Acc., pressing LVL CHG button causes CTD. Any solution?

Can you post the error report please?

Dear JB:

I apologize for the fact that I don't know how to retrieve and post Error Report. Kindly help.

Haseen.

Run the sim and let it crash. Go to Control Panel->Administrative Tools->Event Viewer->Windows Logs->Application and find the error and post the details here.