1 person found this helpful
It's simple: Your wild mix of cards only ever works with specifically adapted code and drivers via CUDA or OpenCL. AE being a dumb nut in this department it simply locks on to the primary GPU in the system and in your case that may simply not be compatible. Ergo the answer would have to be to fiddel with your driver settings. Not that it should matter much - even the GPU accelerated effects are severely limited in AE and you probably won't see much difference between CPU vs. GPU.
HI Mylenium, thanks for answer.
Hmm, but it worked fine with 2*TitanX+2*GTX 1080 since CC2014, CC2015 and early CC2017, now with latest update on CC2017 and now when i removed one TitanX and added 2*1080ti and it got confused to the level that it won't even start properly. Not sure what i can do to fix it now.
That ASpeed GPU is on chip/motherboard GPU on this Asus Z10 MB i can't remove it 'coz MB is dumb to go to BIOS only with that GPU (D-sub connector) so evne if i disable it in BIOS i'd have problem go into BIOS next time and i'd need to reset BIOS battery to get it back to default.
BUT that Aspeed was fine when i had 2*TitanX+2*1080 in system. Only thing i can think of now is to move TitanX from Slot 7 to slot 1 and hope AE will pickup somehow when PCI number changes ?
I don't really need GPU acceleration much in AE but i can't even start it 9/10 times 'coz GPU sniffer is never finishing it's job so it's stalled on splash screen. Is there way to kill GPU sniffer somehow to prevent that loong booting time ?
Are you still facing this problem with your GPU? If not, let us know how you solved it. If so, please let us know so we can assist you further.