April 18, 201610 yr Commercial Member You can run the sim with an AM=3 and it wouldn't do those things. Processes don't conflict via use of cores, they are protected by the way the CPU works. Steve Waite: Engineer at codelegend.com
April 18, 201610 yr Not really a conflict but an error on the first core as someone else described. Either that or conflicting AMs set outside of P3D. I really don't see how else it could be AM related. To OP, can you reproduce this again with the same AM or different AMs? Shanan ASUS Z170 PRO, I7 6700K @ 4.85ghz (HT ON), ZOTAC AMP EXTREME 1080TI GTX (OC), 16 GB DDR4 G.SKILL TRIDENTZ RGB @ 3230MHZ CL 16-17-17-33 (OC) 4X SSDS : WIN 10 (NVME 960 EVO) + P3D + OTHER GAMES, 2X WD BLACKS RAID 0 + 1 SEAGATE BARRACUDA, CORSAIR AX860i PSU, CORSAIR 760T CASE (BLACK), 27 INCH IPS PREDATOR GSYNC 165HZ 1440p + 24 INCH IPS DELL 1080p, THRUSTMASTER HOTAS FCS THROTTLE + FCS16000M CORSAIR K95 RGB + CORSAIR M65 RGB + CORSAIR MM800 POLARIS RGB, CORSAIR H115i v2, CREATIVE GIGAWORKS 7.1 + ASUS D2X XONAR
Create an account or sign in to comment