Do your graphics freeze in places? Post here

[Uthgaard]

5IfoiCJFViY

For certain players, specific locations will cause the display to stop updating even though the game continues to play. This can be corrected by resetting the display, although sometimes this will cause a ResetDeviceFailed() crash. See demonstration above (skyshrine steps are notorious for this, as are OT docks)

Trying to track down this issue. If you've ever had this happen, post below with a breakdown of your OS, graphics card, any eq specific things you are running (i.e. wineq2, dgvoodoo, etc), whether you're using any FPS modifications, and any other relevant information.

[cdfurry]

I have had this issue.

Primarily at OT/SF tunnel, Skyshrine, and randomly in other locations.

Asus Rog laptop with Nvidia 1650 and Asus Rog with 2060 both have same issue.

Installing DGVoodoo 100% fixed it on both though - or at least it has not reoccurred in the 4-5 weeks since I did that.

[Kenshi235]

I crash almost 100% of the time in Wakening Lands near the eastern entrance to geonids. Anywhere between: (-3000, -1500) to (-2000, -1000). I've talked to many people who crash around here as well. The crash is a screen freeze exactly as you describe. I can still hear sounds, type to group, and cast spells, but I am essentially blind until I /quit and restart.

Specs:
OS: Windows 10,
Video Card: Nvidia GeForce GTX 1660 TI

I am not running wineq2 or dgvoodoo. I am using DuxaUI.
I've done any recommendation under the sun for updating eqclient.ini and reinstalling P99.

Just installed DGVoodoo. Will report back if that fixes my screen freeze.

[Uthgaard]

I have had this issue.

Primarily at OT/SF tunnel, Skyshrine, and randomly in other locations.

Asus Rog laptop with Nvidia 1650 and Asus Rog with 2060 both have same issue.

Installing DGVoodoo 100% fixed it on both though - or at least it has not reoccurred in the 4-5 weeks since I did that.

Send me a DM on discord, I'd like to take a look at your dgvoodoo2 configuration vs mine and see if there's a difference that jumps out. Dgvoodoo2 fixed zone crashes for me but not this.

[Gamadon]

Crashing at OT/SF zoneline in OT, SS coming around the corner and down the ramp from Lararith, and WL Geos tunnel just inside eastside entrance.

OS: Windows 11
Video Card: NVidia GeForce RTX 3060
Used WinEQ2 and dgvoodoo2, neither of which helped the ResetDeviceFailed errors.

[dk0]

I can try to gather details on my changes later, but might be in a good position to help diagnose.

This issue used to happen fairly regularly after I started playing again in ~2016. Around 2018 and beyond, I combed through threads and did practically everything except WinEQ2:


Altered .bat for CPU affinity 1
Altered .bat to /wait to keep cmd window alive
Set eqgame.exe compatibility to WinXP SP2
Installed dgvoodoo2
Forced use of nvidia card
Altered nvidia settings, tinkered with a lot here
Probably some others I can't remember


Hard to nail down what specifically helped, but this problem went away for years.

After another p99 break, I started up again about a month ago. More out of curiosity than anything, I was tinkering with some settings and ended up with a slightly new setup. This freezing problem has now happened twice in the past month. It seems fairly rare, but it's not something I've seen in a very long time.

High level recent changes:


No longer using .bat to launch
No CPU Affinity 1
No /wait for cmd shell persistence
Altered some nvidia settings, returned a lot to defaults (notably removing vsync)
Altered registry to enable Large Address Awareness for eqgame.exe
Updated version of dgvoodoo2
Altered dgvoodoo2 config (used GUI this time, previously would edit config file directly)
Possibly other changes, can review in more detail later


I likely (hopefully!) have a backup of my previous setup (minus the nvidia settings) so can compare this evening. My hunch was undoing CPU Affinity 1 being the leading culprit, but that likely conflicts with many players who do not have this issue and also have not set CPU affinity.

Have you (or anyone) been able to determine what triggers this issue? Locations, parameters, etc. that could be used for some relatively controlled testing?

[Dhax]

I Also have this issue. While it does tend to be more common in specific areas as stated in this thread, I feel like it also just randomly occurs sometimes no matter where I am.

Not sure if this is related or a different issue but if I log out of one account and then into a different account and then alt tab my game it will give the reset device error 100% of the time. I have not heard of anyone else having this issue.

OS: win 11
video card: Nvidia GeForce GTX 1660 super
Trying dgvoodoo2 now but doesn't seem like its helping

[Kemadin]

Have you ever had this issue occur while using a UI that was not the default P99 UI?

I used to encounter this issue in East Freeport while camping guards, specifically at 187 -203 -52 while medding near the lamp post in the corner by the Trader's Holiday building. Occasionally when I would go to move/engage a guard the video would freeze as shown in your video. Repro on this issue would take about 1.5-2 hours of remaining in the same zone, but it was ALWAYS reproduced in the exact same location.

I have since resolved this issue, though it is not clear how. I have upgraded to Windows 11 since last seeing the issue and did a full reinstall of the Titanium client from the discs. I do not use any custom files (aside from those distributed by P99) and I do not use dgvoodoo2 or WinEQ. I usually use DuxaUI and can only recall ever seeing this occur with the P99 default UI.

OS: Win 11
GPU: AMD RX 6900XT
CPU: AMD Ryzen 9 5900X
RAM: 32GB @3200 MHz

Edit: one other change since seeing this issue disappear was moving from an ultra-wide monitor with a 3440x2160 native resolution back to a standard 1920x1080 monitor. I ran the game windowed (without WinEQ) in both instances but only ever encountered this freeze with the widescreen resolution.

[FaeSeeker]

Same thing has been happening to be since I came back to p99 a couple weeks ago. Maybe 3 times total.. Twice in Crushbone and once in LFay.

I started researching it all over and have seen multiple people post that hitting alt-enter (switching to full screen) fixes the issue while it’s happening without having to camp. I haven’t had it happen recently to be able to test this, but wondering if any of you have tried this short-term fix?

[Ooloo]

I started researching it all over and have seen multiple people post that hitting alt-enter (switching to full screen) fixes the issue while it’s happening without having to camp.

I don't play on win10 or 11, I actually still play on a really old winxp machine, but I will encounter a somewhat similar problem where if I lock the screen by hitting windowskey+L, and then come back and unlock the screen, the EQ window will be totally black but I can still hear game sounds and my character clearly hasn't actually crashed. Alt-enter to fullscreen fixes it, although sometimes the transition to fullscreen crashes the client instead, but pretty rarely.

[dk0]

I have spent a lot of time troubleshooting this over the past week, and I may have solved this for myself, though it's difficult to prove a negative. I found a location in Skyshrine where I could do some testing, where I was able to reproduce the issue within 5-10 minutes every time I made some changes to see if something worked. It's now been a day and a half of regularly trying in the same location and zero freezes. Still hard to say 100% solved, but definitely major improvements for me. Hoping I'm not jumping the gun here with only 1.5 days of freedom, but wanted to provide some info.

What worked for me is using the 32-bit dgvoodoo2 wrapper instead of the 64-bit. I incorrectly assumed the target architecture was intended for the OS, not the application. There are also user-written guides, forum posts, etc. out there that incorrectly recommend the same. But per the developer's own documentation: "D3D9 has both 32 and 64 bit versions. Always use the proper one, depending on the application type (not the OS type)." This also points to why some people have had dgvoodoo2 resolve this issue, while others have not.

As a bonus, this change also resolved a strange framerate issue I had been having for a very long time.

Would be interested in learning if this helps others. If not, happy to share some of my diagnostic experience this week and see if we can at least point to something.

[cdfurry]

What worked for me is using the 32-bit dgvoodoo2 wrapper instead of the 64-bit.

Yes this part is important as well and was the version I loaded too that seemed resolve it. I did not try the 64 bit but I would expect it doesn't work and should be evidenced by the lack of watermark on the first launch but I could be mistaken.

And to answer a prior question on this thread. When this issue occurs, Alt + Enter to force out of full screen and back does resolve it. (Wife and I play in full screen exclusively).

[dk0]

I did not try the 64 bit but I would expect it doesn't work and should be evidenced by the lack of watermark on the first launch but I could be mistaken..

As far as anybody could reasonably tell, the 64-bit version works flawlessly. I have been using it for years to solve every issue dgvoodoo2 is intended is used to solve, have been able to configure watermark, etc.

Given this, there would be no reason for users to suspect dgvoodoo2 would be related to this issue. And given that most guidance I've seen on how to actually install dgvoodoo2 re: p99 advises the 64-bit version, I suspect that a lot of users are in the same situation I was.

Glad to hear another report supporting this being the issue, would be great to put this longstanding problem to rest once and for all.

[cdfurry]

Aha my mistake on the 64 bit assumption then. Sorry for any confusion.

[branamil]

I have spent a lot of time troubleshooting this over the past week, and I may have solved this for myself, though it's difficult to prove a negative. I found a location in Skyshrine where I could do some testing, where I was able to reproduce the issue within 5-10 minutes every time I made some changes to see if something worked. It's now been a day and a half of regularly trying in the same location and zero freezes. Still hard to say 100% solved, but definitely major improvements for me. Hoping I'm not jumping the gun here with only 1.5 days of freedom, but wanted to provide some info.

What worked for me is using the 32-bit dgvoodoo2 wrapper instead of the 64-bit. I incorrectly assumed the target architecture was intended for the OS, not the application. There are also user-written guides, forum posts, etc. out there that incorrectly recommend the same. But per the developer's own documentation: "D3D9 has both 32 and 64 bit versions. Always use the proper one, depending on the application type (not the OS type)." This also points to why some people have had dgvoodoo2 resolve this issue, while others have not.

As a bonus, this change also resolved a strange framerate issue I had been having for a very long time.

Would be interested in learning if this helps others. If not, happy to share some of my diagnostic experience this week and see if we can at least point to something.

I stopped crashing since D3D9.dll, been a few days

[FaeSeeker]

Hi friends, I’m sorry I’m definitely not as skilled technically as I wish I was. How do I select the 32 bit wrapper of dgvoodoo2? I’m not sure what that means. I went through the full dgvoodoo2 install and have it up and running, not seeing an option for 32 bit..

Thanks!

[dk0]

I stopped crashing since D3D9.dll, been a few days

Right on, but the whole point here is that there are 2 versions of D3D9.dll, and you definitely want the 32 bit version.

How do I select the 32 bit wrapper of dgvoodoo2?

Copy it from the x86 folder instead of the x64 folder.