[SOLVED]Critical error : Unable to initialize render device [only with 64 bit executable]
Saraya
✭✭
UPDATE: Looks like ESO does not like SweetFX anymore (or at least my version). As soon as I renamed the Dxgi.dll, it launched the 64bit.
========================================================================================================================
Had ESO running fine on my SSD/Windows 10 64bit. Had to move the SSD away for a bit and using HDD in it's place. Got ESO up onto the HDD but everytime I try to run the client I get an immediate Crital Error : 'Unable to initialize render device'
This problem has come up quite a bit in the past several years though often it's due to some type of Direct X issue, lack of a properly installed graphics driver and/or use of Windows Vista - none of which applies to me.
However if I run the standard ESO executable(have to do it from within the game folder, as the launcher automatically points to the 64 bit version), it works fine.
So I am at a loss of why a simple hard drive change would make any difference to this as it was working before.
Anyone else having this?
Edited by Saraya on April 14, 2017 6:28PM ========================================================================================================================
Had ESO running fine on my SSD/Windows 10 64bit. Had to move the SSD away for a bit and using HDD in it's place. Got ESO up onto the HDD but everytime I try to run the client I get an immediate Crital Error : 'Unable to initialize render device'
This problem has come up quite a bit in the past several years though often it's due to some type of Direct X issue, lack of a properly installed graphics driver and/or use of Windows Vista - none of which applies to me.
However if I run the standard ESO executable(have to do it from within the game folder, as the launcher automatically points to the 64 bit version), it works fine.
So I am at a loss of why a simple hard drive change would make any difference to this as it was working before.
Anyone else having this?
0
-
Edda✭✭No idea about your other issues but I think you MAY be able to make the launcher point to the 32 but version by clicking the cog in the UPPER RIGHT of the launcher. I have a check mark on 64 bit client there.“The truth may be out there, but the lies are inside your head.” [Terry Pratchett in Hogfather]0 -
ashenb14_ESO✭✭DELETE AL RESHADE.ME/SWEETFX FILES, EXCEPT PRESETS, RUN LAUCHER REPAIR, THEN REINSTALL THE RESHADE FILES.
i had to do this a couple times, mostly with the latest preview build of windows and latest nvidia drivers...something in the whole mess broke reshade..i got it working again though
1 -
Saraya✭✭ashenb14_ESO wrote: »DELETE AL RESHADE.ME/SWEETFX FILES, EXCEPT PRESETS, RUN LAUCHER REPAIR, THEN REINSTALL THE RESHADE FILES.
i had to do this a couple times, mostly with the latest preview build of windows and latest nvidia drivers...something in the whole mess broke reshade..i got it working again though
This is actually an extremely important post. This last version and the one before had problems with reshade/sweetfx.
While there is an underlying issue of increased delay when joining servers or loading surrounding world objects, that is a separate problem.
0