ResetDevice() failed!

[andrewbshifflett]

https://i.imgur.com/TPu9lhi.jpg

This issue has plagued people across many games for many years (I've seen posts as early as 2005).

Specifically in EverQuest p99 (Titanium client), this error usually means there was a problem with querying your display adapter and the reason for the query by the game is, for whatever reason, it has detected a change to/from windowed or full screen mode.

There's a variety of things that I've noticed cause EQ to want to switch between windowed/full screen mode.. generally, it's always a consequence of another application that's actively running and taking advantage of hardware acceleration (i.e. using your gpu).

many productivity apps (by default) have hardware acceleration turned on.. including windows desktop manager (i.e. alt-tabbing, minimizing windows, 3d generated thumbnails with windows peek, etc), google chrome (by default chrome continues to run in the background, even when you close it), discord, fan/lights/motherboard/gpu/peripherals like keyboard/mouse software (razer synapse, eVGA Precision, Corsair iCUE, ASUS Armory Crate, Steam, Battle.net, Zoom, the list goes on...)

Here's the steps I took to fix the issue:

https://i.imgur.com/VGFbA2Y.png

If this works for you, please report back in a few days if you don't experience errors any more. The best place to test is on Skyfire ramp area as you are running to/from Skyfire zoneline in The Overthere.

Another great place to test is in The Hole, especially in The Slabs area.

Usually strafing and turning your camera (holding right click and dragging it around to see around you) will trigger the error to occur.

I've even had it so bad that certain areas I crash and I log back in 6x+ in a row and I immediately get the error.. the fact that it's repeatable in specific locations at different times tells me once certain conditions are met, that it's definitely not random and it's certainly possible to reproducie it and even diagnose and resolve it entirely.

Let's use this thread to try and fix this problem once and for all!

P.S. here's my graphics card: https://www.evga.com/products/product.aspx?pn=10G-P5-3897-KR

[andrewbshifflett]

Here's the corresponding windows event viewer log for this EQ error:

Log Name: Application
Source: Windows Error Reporting
Date: 5/22/2021 12:17:32 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: PC-Andrew
Description:
Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 4094e84e-f282-4eff-94d1-70c9b51af2fd

Problem signature:
P1: 141
P2: ffffaa0c76903460
P3: fffff80799da6f64
P4: 0
P5: 3004
P6: 10_0_19043
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210522-1217.dmp
\\?\C:\Windows\TEMP\WER-187638156-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A56.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A57.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A65.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A76.tmp.txt
\\?\C:\Windows\Temp\WER47C2.tmp.WERDataCollectionS tatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArc hive\Kernel_141_937c6ed2ba8a37f2ead56de6e1ca3ee022 6eaa_00000000_cab_0d638916-fb49-47ba-9ad0-e252c04b69f6

Analysis symbol:
Rechecking for solution: 0
Report Id: 0d638916-fb49-47ba-9ad0-e252c04b69f6
Report Status: 268435456
Hashed bucket:
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-05-22T17:17:32.7812107Z" />
<EventRecordID>27311</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>PC-Andrew</Computer>
<Security />
</System>
<EventData>
<Data>LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys</Data>
<Data>0</Data>
<Data>LiveKernelEvent</Data>
<Data>Not available</Data>
<Data>4094e84e-f282-4eff-94d1-70c9b51af2fd</Data>
<Data>141</Data>
<Data>ffffaa0c76903460</Data>
<Data>fffff80799da6f64</Data>
<Data>0</Data>
<Data>3004</Data>
<Data>10_0_19043</Data>
<Data>0_0</Data>
<Data>256_1</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210522-1217.dmp
\\?\C:\Windows\TEMP\WER-187638156-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A56.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A57.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A65.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2 A76.tmp.txt
\\?\C:\Windows\Temp\WER47C2.tmp.WERDataCollectionS tatus.txt</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArc hive\Kernel_141_937c6ed2ba8a37f2ead56de6e1ca3ee022 6eaa_00000000_cab_0d638916-fb49-47ba-9ad0-e252c04b69f6</Data>
<Data>
</Data>
<Data>0</Data>
<Data>0d638916-fb49-47ba-9ad0-e252c04b69f6</Data>
<Data>268435456</Data>
<Data>
</Data>
<Data>0</Data>
</EventData>
</Event>

[andrewbshifflett]

More resources:

http://www.carrona.org/bsodindx.html#0x00000141

http://www.carrona.org/VideoTDR.html

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/157586/tdr-registry-settings/

Warning: backup your registry before loading new registry entries into your system or changing existing/adding new registry entries.

Cheers!

[koala]

I have a very similar card (EVGA 2070 Super) and I used to be plagued by similar issues. I haven't tried any of the registry fixes you mentioned, but what I can share is that I was able to 100% eliminate my ResetDevice crashes with the following combination:

1. Install dgVoodoo in the EQ folder.
2. Do NOT use WinEQ2 (this is incompatible with dgVoodoo).
3. Do NOT run eqgame.exe under Compatibility Mode (contrary to much advice on the forums, this actually causes an increase in zoning crashing for me under this combo).
4. Run eqgame.exe as Administrator.

With those 4 things in place, I can run at max settings and I never experience an in-game crash. The only time my client will ever crash is when camping, which I have just come to accept and I always /camp desktop anyway. This is a much better situation overall than random crashes while actually playing the game.

My theory is this has to do with DX9 and the Nvidia driver. There are messages in the Windows Event Viewer whenever this error occurred saying that the driver failed and recovered. dgVoodoo seems to fix (or go around) that issue, and the other pieces are basically just required to make that solution function properly.

[Cecel__Soulhealer]

So, something I found in my never ending search to prevent crashing was from a Dev on Day Break's forum, https://forums.daybreakgames.com/eq/...failed.253742/ It was one of the two changes I made, the other being I set my game to run off of one core at random as the wiki suggest.

Please add this line to your eqclient.ini:
GraphicsDLL9=EQGraphicsDX9.DLL

That is something I did to prevent mine. dg_Voodoo seemed to have prevented it but I didn't like running another program and instead did that. Also did single core processor to run it and I may take that out.

I do still have freezes in Overthere going to Skyfire and going into the city of FV. Just alt + enter twice and back at it.

https://wiki.project1999.com/Players:Technical/Affinity This is a link to the single core processor file I use, selects it at random.

I have a Geforce RTX 2080 Ti.

[Polixa]

Nothing brilliant to add to this thread, except to say I regularly have this crash at the Cabilis guards in LoIO. Heading past them into Cab, or after exiting Cab and heading out.

Workaround for me is to pan down to look at the floor as I run past them. Haven't ever crashed doing that.

[andrewbshifflett]

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.

[koala]

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]

I just received ResetDevice() failed! error in Paineel... so my proposed fixes did not resolve the issue.

here's my windows event log:

Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: ddfa2cf1-e2c6-40f7-90d8-9f1a19de93c7

Problem signature:
P1: 141
P2: ffffaa0c76e0a010
P3: fffff80799da6f64
P4: 0
P5: 2a9c
P6: 10_0_19043
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210524-1146.dmp
\\?\C:\Windows\TEMP\WER-358609968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF EA0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF EA1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF EA0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF EB1.tmp.txt
\\?\C:\Windows\Temp\WER3DBD.tmp.WERDataCollectionS tatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArc hive\Kernel_141_2e54e8e2dd6595730c9c9deeb8b129b944 50ee_00000000_cab_39645470-7ae0-4d95-9962-e8c887381919

Analysis symbol:
Rechecking for solution: 0
Report Id: 39645470-7ae0-4d95-9962-e8c887381919
Report Status: 268435456
Hashed bucket:
Cab Guid: 0

[andrewbshifflett]

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.

[andrewbshifflett]

Based on koala's suggestion.. I've been looking into d3d wrappers. From what I can tell, this error occurs due to incompatibilities between older directx/d3d (d3d/direct3d is the 3d engine and is a subset under directx) APIs and new gfx card drivers.

So, piggybacking off of linux and wine (windows emulated environment run on linux to support windows games and applications being utilized successfully on linux distributions), someone has ported the directx/d3d part of this emulated environment over to Windows to help provide relief to older games that are plagued by driver incompatibility issues that prevent players from going back to play old games (like Everquest).

here's a few options that I'm currently testing. my goal is to find one that will (hopefully) work with WinEQ2.. I suspect only the developer of WinEQ2 can really make the necessary changes because WinEQ2 uses it's own d3d7/d3d8/d3d9 dll injection and the below directx/d3d dll's either don't work with WinEQ2, or WinEQ2 doesn't work with them or both:

1) DXVK: https://github.com/doitsujin/dxvk/releases/tag/v1.8.1
2) dgVoodoo2: http://dege.fw.hu/dgVoodoo2/ (koala's suggested directx/d3d wrapper)
3) WineD3D for Windows: https://fdossena.com/?p=wined3d/index.frag

I'll keep you updated on which of these (if any) work with WinEQ2.

Alternatively, if anyone knows a way to make the game go full-screen (and actually look fullscreen, no window border, no window application title, etc) then let me know how and I'll toss WinEQ2 to the side.

Cheers!

[gkmarino]

Thanks for starting this post I hope I can work towards a resolution as well. Yeah this really sucks, I'm posting here so I have a link back to this post. I've died multiple times, and even had a group wipe due to this problem. I'm using a RTX 3060ti & Ryzen 7 2700x. I noticed that potentially turning my DPI down on my mouse may have reduced how often it happens.. a theory, i'm an avid mouse turner and keyboard strafer.

Places this has happened to me on Green..

The Hole
1. Slabs area second doorway connecting to Dock's first building area.
2. Golem Tower court yard pool area.

Paineel
1. The doorway connecting to the Darkglow Palace.

[andrewbshifflett]

gkmarino.. same exact areas for me.

Following up on koala's advice.. he's got it down.. trying his solution now and ditching WinEQ2 (since it doesn't work with the dgVoodoo2 wrapper).

I've uploaded all files you need to make this work, make sure you remove any explicit mention of what directx dll to use (double-check your eqconfig.ini file and remove if it's there, make sure you run notepad as admin so your changed take effect).

then download the files below and put them into your everquest folder:

https://drive.google.com/drive/folders/1y9mYC97lDRZK9uJWs6SHWWoJTL6HG1fj?usp=sharing

you may need to run dgVoodooCpl.exe and change the adapter to specifically be set to yours (and not mine, not sure if it updates automatically or not).

ensure eqgame.exe and dgVoodooCpl.exe are both set to run as administrator (for all groups and users).

here's screenshots of my settings for dgVoodooCpl.exe and the borderless gaming app (this will replace WinEQ2, if you're using it):

Borderless Gaming
Global Settings: https://i.imgur.com/Ppb5GK6.png
Game Settings: https://i.imgur.com/TTdsPHF.png

dgVoodoo2
General Settings: https://i.imgur.com/vyZ8Mjk.png
DirectX Settings: https://i.imgur.com/ld2u2qv.png

The shortcut on drive is a shortcut to the launch_titanium.bat batch file that's set to automatically be run as an administrator.

So the flow to open the game is to open Borderless Gaming app, it'll go to the tray area. Then use the EverQuest shortcut that I supplied, double-click to open the game.. it will open in windowed mode.

Log into the server, then select your character. Once you're in the game, go to your tray area and right-click on the Borderless Gaming application icon, then go to Game Settings, click apply/save. It should maximize your game, making it appear to be borderless (with no windowed border or application menu/title bar).

A bit more manual than WinEQ2.. I'll let you all know how it turns out.

FYI -- I also went into the Nvidia Control Panel (right-click desktop -> Nvidia Control Panel) and chose "Use the advanced 3d image settings" clicked "Add" and located eqgame.exe and customized better graphics preferences (16x anistropic, windowed+fullscreen gsync under gsync settings, scaling set to be handled by GPU (not the display), and overriding eqgame.exe's anti-aliasing settings to 8x supersample, as well as turning off vsync, high quality textures, etc).

Not sure how much the above helps, but now that this wrapper is talking to d3d9 better then maybe the above will make my game look nice and all the other stuff will provide relief for the ResetDevice(); failed! error.

I'll report back if I experience the error again.

Big thanks to koala for the great recommendation.

Cheers!

[Immok]

Do you get crashes if you exit the GeForce Experience app?

[andrewbshifflett]

Do you get crashes if you exit the GeForce Experience app?

I don't install Geforce Experience. that's optional. I'd just do a clean install of latest drivers and reinstall physx engine, sound and then the driver itself.

[Zekayy]

This Happens to me too! everytime I switch toons or go in full screen!

[Va1entines]

Ive never been able to switch between fullscreen/windowed consistantly without getting this error. Never heard for dgVoodoo, downloaded it and been swapping it back and forth for hours with no crashes. Would reccommend.

[Va1entines]

Had another error, didnt completely fix.

[Handsonsight]

I get this in the basement of Howling Stones, in the north and south Wings. Just as you're walking in to the outpost in the Overthere. I played on blue yeaaaars ago and it wasn't an issue then - but now on green it is. I've done all sorts of suggestions like the ones in this thread and no dice.

[andrewbshifflett]

gkmarino.. same exact areas for me.

Following up on koala's advice.. he's got it down.. trying his solution now and ditching WinEQ2 (since it doesn't work with the dgVoodoo2 wrapper).

I've uploaded all files you need to make this work, make sure you remove any explicit mention of what directx dll to use (double-check your eqconfig.ini file and remove if it's there, make sure you run notepad as admin so your changed take effect).

then download the files below and put them into your everquest folder:

https://drive.google.com/drive/folders/1y9mYC97lDRZK9uJWs6SHWWoJTL6HG1fj?usp=sharing

you may need to run dgVoodooCpl.exe and change the adapter to specifically be set to yours (and not mine, not sure if it updates automatically or not).

ensure eqgame.exe and dgVoodooCpl.exe are both set to run as administrator (for all groups and users).

here's screenshots of my settings for dgVoodooCpl.exe and the borderless gaming app (this will replace WinEQ2, if you're using it):

Borderless Gaming
Global Settings: https://i.imgur.com/Ppb5GK6.png
Game Settings: https://i.imgur.com/TTdsPHF.png

dgVoodoo2
General Settings: https://i.imgur.com/vyZ8Mjk.png
DirectX Settings: https://i.imgur.com/ld2u2qv.png

The shortcut on drive is a shortcut to the launch_titanium.bat batch file that's set to automatically be run as an administrator.

So the flow to open the game is to open Borderless Gaming app, it'll go to the tray area. Then use the EverQuest shortcut that I supplied, double-click to open the game.. it will open in windowed mode.

Log into the server, then select your character. Once you're in the game, go to your tray area and right-click on the Borderless Gaming application icon, then go to Game Settings, click apply/save. It should maximize your game, making it appear to be borderless (with no windowed border or application menu/title bar).

A bit more manual than WinEQ2.. I'll let you all know how it turns out.

FYI -- I also went into the Nvidia Control Panel (right-click desktop -> Nvidia Control Panel) and chose "Use the advanced 3d image settings" clicked "Add" and located eqgame.exe and customized better graphics preferences (16x anistropic, windowed+fullscreen gsync under gsync settings, scaling set to be handled by GPU (not the display), and overriding eqgame.exe's anti-aliasing settings to 8x supersample, as well as turning off vsync, high quality textures, etc).

Not sure how much the above helps, but now that this wrapper is talking to d3d9 better then maybe the above will make my game look nice and all the other stuff will provide relief for the ResetDevice(); failed! error.

I'll report back if I experience the error again.

Big thanks to koala for the great recommendation.

Cheers!

Update. This works! 100% resolved. No errors since doing this.

Borderless gaming is a little funky. if you need help getting it to work properly, let me know I can post a guide. It's not as nice as WinEQ2 but it has its advantages... one being, you don't have to pay or log in to use fullscreen mode for the game.

This means, as long as you have the app then you're good... WinEQ2, if the developer ever shut it down or it went offline, you'd be stuck and couldn't log into EQ to access borderless.

Use Borderless and DgVoodoo2.. if you need help with settings, let me know but I did post screenshots above!

100% FIXED! Big thanks to koala!

[Handsonsight]

Can confirm also, I've been using the suggestion above with dgVoodoo and have not received a single error for the past week +

[Brockna]

Update. This works! 100% resolved. No errors since doing this.

Borderless gaming is a little funky. if you need help getting it to work properly, let me know I can post a guide. It's not as nice as WinEQ2 but it has its advantages... one being, you don't have to pay or log in to use fullscreen mode for the game.

This means, as long as you have the app then you're good... WinEQ2, if the developer ever shut it down or it went offline, you'd be stuck and couldn't log into EQ to access borderless.

Use Borderless and DgVoodoo2.. if you need help with settings, let me know but I did post screenshots above!

100% FIXED! Big thanks to koala!

Fixed for me as well. Haven't had any issues since.

[Cecel__Soulhealer]

I get this in the basement of Howling Stones, in the north and south Wings. Just as you're walking in to the outpost in the Overthere. I played on blue yeaaaars ago and it wasn't an issue then - but now on green it is. I've done all sorts of suggestions like the ones in this thread and no dice.

Try GraphicsDLL9=EQGraphicsDX9.DLL into your eqclient.ini. A daybreak dev had it on a forum from awhile back citing the Titanium Client is the only one with this issue. Did you recently upgrade hardware/new PC?

The above is something I may switch to anyways. I had 6 crashes in West Wing of HS and finally died on the 6th because my cleric was LOM and couldn't root them back. Almost deleted my damn characters over it. dgVooDoo was recommended, but it seems GraphicsDLL9=EQGraphicsDX9.DLL works great for me. I use Borderless Gaming to get the full screen effect and don't touch WinEQ anymore. Also, I have my game file opening by the notepad to do it off of a single core and it selects the core at random.

Try the DLL added in and see what happens. There is also a file you can add with a /wait in it. My game stopped crashing, then I'd go full screen then windowed and my crashes heavily went down off of that.

[Handsonsight]

Try GraphicsDLL9=EQGraphicsDX9.DLL into your eqclient.ini. A daybreak dev had it on a forum from awhile back citing the Titanium Client is the only one with this issue. Did you recently upgrade hardware/new PC?


I tried this previously and was still getting crashes. But I removed that from the .ini when I started using voodoo and works solid for me now.

[Cecel__Soulhealer]

I tried this previously and was still getting crashes. But I removed that from the .ini when I started using voodoo and works solid for me now.

Oh hell I think I mis-read the stuff up the chain! I thought I was at the end of the thread and was at the end of the page. Whoops!

[rahmani]

Why did you include a screenshot of the instructions so the text is now an image?

[andrewbshifflett]

Why did you include a screenshot of the instructions so the text is now an image?

Don't bother doing that first stuff. Just do the latest solution I quoted with dgVoodoo

[rionnecro01]

I made a webpage and a working EQ folder with dgVoodoo and Duxa Installer

https://rion400.wixsite.com/my-site

[Baler]

I made a webpage and a working EQ folder with dgVoodoo and Duxa Installer

https://rion400.wixsite.com/my-site

No offense but when someone comes back in a year and finds this post via the forum search feature. Will this still be online or link them to a WTS Website URL site like godaddy.

[rionnecro01]

I have no plans to delete it and I'm going to update it if more crashes are found

[roguep1999]

Try to open two EQ windows and close first one and use second one to log in solve my problem

[rionnecro01]

I deleted all that. You just download dgVoodoo by searching for it on Google. Extract all files into your EQ folder. Then also extract the files from dgVoodoo\MS\x86 into your EQ folder. You should see a dgVoodoo watermark at bottom right, if not it's not working.

[lituviel]

gkmarino.. same exact areas for me.


https://drive.google.com/drive/folders/1y9mYC97lDRZK9uJWs6SHWWoJTL6HG1fj?usp=sharing


Cheers!

FYI the link to Dl the files is not working anymore

[Robot]

cannot get borderless gaming app thing to work on eq client, idk

[mcoy]

I deleted all that. You just download dgVoodoo by searching for it on Google. Extract all files into your EQ folder. Then also extract the files from dgVoodoo\MS\x86 into your EQ folder. You should see a dgVoodoo watermark at bottom right, if not it's not working.

You can edit the ini, or run the config tool and disable the watermark if you don't want to see it.

-Mcoy

[Robot]

I have been suffering from the dreaded reset device error for years, DGvoodoo seems to have fixed it... So far.

It has caused a different problem which isnt as bad as crashing mid game/mid fight sometimes but still kind of annoying.

Since running dgvoodoo, now when I switch chars, or accounts, it crashes every single time resulting in about a 5 min wait at server select for the char to be kicked out.

I would take this trade any day, however, since the crashing in game was much worse and has gotten me killed a few times even.

[digush]

I have been suffering from the dreaded reset device error for years, DGvoodoo seems to have fixed it... So far.

It has caused a different problem which isnt as bad as crashing mid game/mid fight sometimes but still kind of annoying.

Since running dgvoodoo, now when I switch chars, or accounts, it crashes every single time resulting in about a 5 min wait at server select for the char to be kicked out.

I would take this trade any day, however, since the crashing in game was much worse and has gotten me killed a few times even.



try:
Right click on "eqgame.exe"
-> "Properties"
-> Go to "Compatibility" tab

then
1) Tic "Run this program in compatibility mode for:"
-> Select "Windows 98 / Windows Me"
••and••
2) Tic the box "Run this program as an administrator"


HTH
GL, HF