ResetDevice() failed!

[koala]

Originally Posted by andrewbshifflett [You must be logged in to view images. Log in or Register.]

All of these suggestions are great, what I'm hoping to get out of this thread are suggestions that have led to total resolution of the problem.

If you have experienced ZERO ResetDevice() failed! errors since making a specific change, please explain to everyone what exactly you changed.

Since making the changes in my original post (see: https://i.imgur.com/VGFbA2Y.png) I've had nO ResetDevice() failed! crashes.

If I do receive a crash, then I will follow-up here and let you know the solution does not work. Thus far, it's a success.

In the configuration I posted above, I used to receive ResetDevice all the time at the spots you mentioned -- and now I receive ZERO ResetDevice crashes. I still crash on camp, but it is not a ResetDevice error.

I also tried the DX9 item in the ini file as part of my months of searching for a solution to this, and it did not work for me. It's tricky because it is both seemingly random and not-so-random at the same time, so sometimes you have to test a "potential fix" over a span of weeks before you really know whether it did anything.

[andrewbshifflett]

Originally Posted by koala [You must be logged in to view images. Log in or Register.]

In the configuration I posted above, I used to receive ResetDevice all the time at the spots you mentioned -- and now I receive ZERO ResetDevice crashes. I still crash on camp, but it is not a ResetDevice error.

I also tried the DX9 item in the ini file as part of my months of searching for a solution to this, and it did not work for me. It's tricky because it is both seemingly random and not-so-random at the same time, so sometimes you have to test a "potential fix" over a span of weeks before you really know whether it did anything.

I'll try this now.. but, not being able to use wineq2 is something I don't want to do... is there no way to make wineq2 work with dgvoodo?

also.. do you know what dgvoodoo is / what it does?

[koala]

Yeah. dgVoodoo basically converts the DirectX 9 API into DirectX 12 API calls. So EQ thinks it's running DirectX 9 but in reality under the hood it's being powered by DirectX 12. For whatever reason, this seems to avoid the glitch that the Titanium client and Nvidia driver are encountering, so you don't end up with crashes.

WinEQ2 is impossible with dgVoodoo however. WinEQ2 hooks into EQ by relying on the DirectX 9 API, which EQ is no longer using in this setup.