March 19, 20188 yr 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 March 19, 20188 yr by davidzill typo David J. Zill Core I7 8700K @ 5.3 Ghz / Liquid cooled (Kraken X62)/32GB DDR4 3200 RAM/EVGA 1080 Ti SC/ Acer X5280HK G-SYNC 4K Monitor/ ASUS Essence STX II Sound Card/ Samsung 960 Pro M.2 PCI-E SSD 2TB/ Windows 10 Professional 64/ Latest drivers
March 19, 20188 yr Commercial Member 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. Kyle Rodgers
March 19, 20188 yr 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! Geoff Street
March 19, 20188 yr Commercial Member 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. Kyle Rodgers
Archived
This topic is now archived and is closed to further replies.