Jump to content

Recommended Posts

Not sure if this has been discovered or known yet. Fresh install of Windows 10 64, fresh install of Prepar3d V4.2, NO mod tweaks, stock .cfg's, fresh install PMDG QOTSII. Everytime I exit Prepar3d V4.2, I get a BEX64 CTD, ONLY in the QOTSII.  

Edited by davidzill
typo

Share this post


Link to post
Share on other sites
7 hours ago, davidzill said:

Not sure if this has been discovered or known yet. Fresh install of Windows 10 64, fresh install of Prepar3d V4.2, NO mod tweaks, stock .cfg's, fresh install PMDG QOTSII. Everytime I exit Prepar3d V4.2, I get a BEX64 CTD, ONLY in the QOTSII.  

Moreover, LM has identified that the issue is (well..."issues are") actually on their end, though we had alleviated one of the other issues that crept in that affected the 744 and a few other add-ons as well.

Share this post


Link to post
Share on other sites

Kyle, 

Is this something that we will have to wait for LM to fix on their end or are you guys still looking for solutions?

Thanks!

Share this post


Link to post
Share on other sites
36 minutes ago, gstreet said:

Is this something that we will have to wait for LM to fix on their end or are you guys still looking for solutions?

As mentioned earlier LM identified the issue is on their end. As we do not have access to their source code, it would follow that we are dependent on them.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...