Jump to content

Moving main P3D window causes Left MCDU to lock up.


Dazzlercee

Recommended Posts

Hi,

I run P3Dv2.4 in windowed mode, and I have found that moving (and maybe resizing) the main window causes the left MCDU to lose all flight plan data and lock up.

Reloading the aircraft resets the MCDU but obviously the aircraft then returns to default state, which is not helpful during cruise.

I think this is the same problem described here:

http://forum.aerosoft.com/index.php?/topic/86880-left-cdu-lock-up-with-11-and-also-prior/

Regards,

Daz

Link to comment
Share on other sites

Now i am no longer the only one with this issue. Going from alt tab fullscreen to windowed mode and then moving the window resilts exactly what Daz described.nany chance to get this solved Mathijs ?

Thanks, Carsten

Link to comment
Share on other sites

  • Aerosoft

Now i am no longer the only one with this issue. Going from alt tab fullscreen to windowed mode and then moving the window resilts exactly what Daz described.nany chance to get this solved Mathijs ?

Thanks, Carsten

I doubt it as it is such a rare isssue. But do this: http://forum.aerosoft.com/index.php?/topic/85493-a318319-crashing-on-exit-combination-topic/?p=624856 and we'll sure give it a try.

Link to comment
Share on other sites

  • 2 weeks later...

I doubt it as it is such a rare isssue. But do this: http://forum.aerosoft.com/index.php?/topic/85493-a318319-crashing-on-exit-combination-topic/?p=624856 and we'll sure give it a try.

P3D does not lock up, close or present an error message when the left MCDU becomes unresponsive. The rest of the aircraft still functions you just lose access to the left MCDU - it's as though it has lost focus.

Would a mini dump still be useful when this happens, even though there are no errors?

Regards,

Daz

Link to comment
Share on other sites

Sure we can try!

I tried to create the mini dump but when asked to save the .dmp file Process Explorer gave the following error:

"Error writing dump file. Only part of a ReadProcessMemory or WriteProcessMemory was completed."

Could you please test this on one of your systems:

Put P3D into windowed mode.

Load the A319.

Move the window slightly across the desktop.

Once the window has refreshed and the graphics have redrawn test the left MCDU for functionality.

For me, 100% of the time the left MCDU does not then respond to mouse interaction - everything else in the cockpit is fine.

I would be grateful if you could try this, it should only take a couple of minutes.

Regards,

Daz

Link to comment
Share on other sites

  • Aerosoft

I tried to create the mini dump but when asked to save the .dmp file Process Explorer gave the following error:

"Error writing dump file. Only part of a ReadProcessMemory or WriteProcessMemory was completed."

Could you please test this on one of your systems:

Put P3D into windowed mode.

Load the A319.

Move the window slightly across the desktop.

Once the window has refreshed and the graphics have redrawn test the left MCDU for functionality.

For me, 100% of the time the left MCDU does not then respond to mouse interaction - everything else in the cockpit is fine.

I would be grateful if you could try this, it should only take a couple of minutes.

Regards,

Daz

We are unable to recreate this issue on any of our internal test machines and none of the 50 testers has reported it. There has to be a local element in this issue that we are not aware of. I doubt there is anything we do about it. As the A320/A321 shares so much of the code it is most likely to behave the same way on the affected machines.

For the Airbus Extended we had three customers with the same issues. In the end all three did a clean install of Windows and in all three cases this solved the issues. Not advising you to do so, just stating the fact.

Link to comment
Share on other sites

We are unable to recreate this issue on any of our internal test machines and none of the 50 testers has reported it. There has to be a local element in this issue that we are not aware of. I doubt there is anything we do about it. As the A320/A321 shares so much of the code it is most likely to behave the same way on the affected machines.

For the Airbus Extended we had three customers with the same issues. In the end all three did a clean install of Windows and in all three cases this solved the issues. Not advising you to do so, just stating the fact.

Fair enough, knowing the cause of the issue means I can avoid it.

It is just really strange that it is only one module within a single product that this affects. If the whole sim, or the whole aircraft became unresponsive then yes, I would consider a windows/sim re-installation, but not at this point.

By the way, setting a new aircraft state does not resolve the issue, but reloading the aircraft does.

It is not a show stopper by any means, and there may only be an isolated case or two reported, but I am sure that this will crop up for other users eventually.

Anyway, great product overall.

Regards,

Daz

Link to comment
Share on other sites

It happened to me last night. And it happened before sp1 where the whole system locked and I lost all the flight info including route. Then on my right fmc I could not hit return and the only solution was selecting the vehicle again.

Link to comment
Share on other sites

  • 2 weeks later...

I just tried using the new A321 on the system that has shown issues with the A318.

I installed the A321 into FSX as FSX is also there but in a completely different install directory/disk.

The A321 in FSX is not affected by any Window movements.

When I try the same action with P3D V2.4 A321 the spinner happens and the left MCDU locks up.

Something is obviously not happy but how can it be found? The install of P3D is a clean install with the latest build.

Link to comment
Share on other sites

that seems to be a fully different topic, please make a new topic about that.

Seems the same to me, moving the main window locks up the left MCDU in P3D. Not sure what is meant by "the spinner happens".

Link to comment
Share on other sites

Hi,

I tried a change last night. I removed A320, P3D completely and made sure that my Windows 7 64 bit system is up to date and has the most recent video drivers from nVidia.

I made a clean install of P3D V2.4 on my default C: SSD drive and let it get stable.

I then installed the A320 V 1.10.

Once again when I am in a windowed mode with P3D and move the application window the spinner goes and the MCDU locks up.

If I start with a windowed mode and simply make it max there is no problem. I can change back and forth from max to wherever the window is without issue but if I grab and move the window the spinner goes and the MCDU locks up.

Reloading the aircraft makes it work again.

The rule for me now is to run P3D in max window mode when using the airbus.

AMD AX88PRO BIOS AMI 1301, A10-6800K 4.4GHz, 8Gb 1600 RAM, EVGA GTX570, MS Windows 7 Pro 6.1.7601 SP1

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use