I have a weird problem with the newly released Prepar3d V4, which is the first venture into being totally 64bit for Prepar3d.
When using the latest stable driver released (5/17/17), I get the following from launching P3D:
Invalid Hardware or Driver Detected
Prepar3D was unable to initialize the rendering system and will shut down. Please make sure this system has a video card that supports DirectX 11 and that the drivers are up to date.
The card I'm using is a Sapphire Dual-X Radeon R9 280, GDDR5, 3GB. According to AMD's own specs, Sapphire's specs, and GPU-Z, this card supports DirectX11 and DirectX 12. The rest of my setup:
Intel Core i5 3570K (not overclocked)
8GB DDR3 PC16000 Memory
Windows 7 64bit
Sapphire Dual-X Radeon R9 280, GDDR5 3GB
OCZ 120GB SSD (OS)
Samsung 850 EVO 500GB SSD (P3D)
WD 500GB SATA HDD (non-simming applications)
WD 2TB SATA6 HDD (storage)
Reverting to the previous driver I had (Catalyst 14.12) caused P3D V4 to crash with the following:
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 22.214.171.12468
Application Timestamp: 59279be2
Fault Module Name: atidxx64.dll
Fault Module Version: 126.96.36.1991
Fault Module Timestamp: 546e9ecc
Exception Code: c0000005
Exception Offset: 000000000059b3da
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: ce0b
Additional Information 2: ce0bfa972b4bffe98e6830e87165821a
Additional Information 3: 3d4e
Additional Information 4: 3d4e379af8047de47ec968f5a5aa0621
When using the Catalyst driver with Prepar3d V2, it works fine, and Prepar3D V2 has the same DirectX requirement as Prepar3D V4.
The P3D support team recommended that I report this to AMD and revert back to the Catalyst driver, but the Catalyst driver crashes the entire sim, while the latest driver gives the error above and exits normally. Again, this card is supposed to support DirectX 12, and V4 requires DirectX11, so this should support it. Any ideas as to what is happening?
Additionally, I can confirm that Prepar3d V4 does work with the 17.2.1 driver from 2/28/17, while it fails on the 17.5.2 driver from 5/7/17. So for now, I have reverted back to the 17.2.1 driver. The driver that gave me the atidxx64.dll crash also in the above post was the Catalyst 14.15 driver.
But for now, I'm good with 17.2.1, though this will need to be addressed with Prepar3D on any new driver.