Graphical Issue in "No Refunds"

Ellisaria

Well-known member
Does anyone know what causes this graphical interference (flashing white screen) in No Refunds or (more importantly) how to stop it from happening? This happens to me every run across three different computer (all have up-to-date drivers, etc. as well). Any information or advice that stops this nausea-inducing problem (that tends to end my playing for the rest of the day) is greatly appreciated!

 

Gemini-Dragon

Well-known member
(just cross-posting my same post in this relavent thread too)
I can tell you that I've run that quest well over a few hundred times and only had it happen maybe a dozen or so times; I've never been able to reproduce it on purpose (and I've tried many times, my bug reports, info/testing I've done as a player is just pure RNG if I happen to ever have it happen). It's one of those, you zone in, take a couple steps forward, and the world starts going flashy like that. It's like there's a loose vertices or something that gets stuck on the character's eye if you hit it just right. My current specs is a Ryzen 5 3600 with GeForce RXT 2060 super; but it also happened on my prior computer too. And it's been a random event since the day Sharn was added to the game.

I haven't been recording right when it happens, but it's happens within seconds of moving after zoning in at this location in this video clip and sticks with you for the entire quest.
nvidia 1660. I get the graphics bug all the time as well. If I enter No Refunds and get the graphical glitch I go into adv graphics settings and disable stencil shadows. This stops the graphical flickering, you just need to remember to re-enable it after the quest.
 
Upvote 0

Kimbere

Well-known member
This has happened on an Intel and an AMD CPU system, it has happened on a 32GB memory Windows 10 pro system, to a 128GB memory Windows 11 Pro system, it has happened with Nvidia GPUs (RTX3060 12GB, RTX5090 32GB) and with AMD GPUs (RX580 8GB, RX7900XTX 24GB). So there is no "Aha, it's this GPU using this particular way of drawing this xyz that is the culprit."

Observations here include:

Multi Client
Client 1 to 6
Client 2 out of the 6 can be the one that experiences the issue, whilst the rest do not. Restarting the DDO Client will clear it for this client 2. Logging out and back in without restarting the client entirely (by logging out to the Desktop before logging back in) will leave this exactyl in place.

Theorised Stencil Shadows being associated with the issue is unsurprising, given observations I made saw that the triangles showed a scatter pattern from point sources and was roughly from where light sources are located in the map of the quest. Suggesting that it is something there that is used to draw those light sources that is not being loaded in with the rest of the quest assets and drawn that way instead. Or was unable to be loaded, resulting in what we see here.

The easiest way to replicate is to simply enter, see if there is a problem. Turn around, get back out. Reset quest and go in again. It was observed that this has happened in the middle of farming runs. So it didn't happen in the first run, didn't happen in the second, run, but it could happen at any point too, so first, second, third run, etc of the quest and it could happen to one of the clients.

J1NG
This.

I don't often encounter that specific bug in that quest but every once in a while I do so it is random/intermittent rather than consistently reproduceable.
 
Upvote 0

rabidfox

The People's Champion
The easiest way to replicate is to simply enter, see if there is a problem. Turn around, get back out. Reset quest and go in again. It was observed that this has happened in the middle of farming runs. So it didn't happen in the first run, didn't happen in the second, run, but it could happen at any point too, so first, second, third run, etc of the quest and it could happen to one of the clients.
I tried that once while recording in hopes to capture it in real time. After a few dozen recall/resets, I eventually stopped recording and went back to doing other stuff. The RNG factor for the bug occuring makes reproducing it a pain.
 
Upvote 0

J1NG

I can do things others can't...
I tried that once while recording in hopes to capture it in real time. After a few dozen recall/resets, I eventually stopped recording and went back to doing other stuff. The RNG factor for the bug occuring makes reproducing it a pain.
Agree. The highlighted part is the most important factor. Whilst I listed the easiest way to replicate it, it's still under the influence of some type of RNG to get to to appear.

J1NG
 
Upvote 0

Jaspar

Well-known member
My friends and I have all had this happen on rare occasions too. All have very different setups (new laptop, 10 year old laptop, new desktop, 5 year old desktop).

I doubt there would be any specs which are the same.
 
Upvote 0

Lazuli

Well-known member
As J1NG has said... It happened to me on my old PC with an i5 Intel processor, and it's happening on my new one with an AMD Ryzen 7 processor. Windows 10 Home or Windows 11 Pro, it happens on both. Low RAM or high RAM, it happens the same. With very different graphics cards (old GTX660 PCX3-0 DDR5 or new Sapphire Nitro+ Radeon RX 9060 XT 16GB GDDR6 FreeSync OC Tri-X) happens too. Heh, I've even had it on an old laptop (I have it at my other house now, so I can't mention its specs right now).

My brother has had it, my friends have had it. Everyone I know has had it at some point. It doesn't seem to be specific to any computer spec. Computers were very different.

This can happen when you're using a single account, or when you're multiboxing. If you're multiboxing, only one account will have the bug; the others won't at same time (in my experience, but I rarely multibox).

It's a relatively rare bug, but sometimes it's happened to me several times in a row. It's very annoying. I can only be grateful that it's relatively rare, but if you do Sharn often, someone in the group will eventually get this bug (you or others).

edit: It also happens whether you're alone on the quest or in a group.
 
Last edited:
Upvote 0

Mindos

CHAOTIC EVIL
Anyone ever try reporting this issue directly to amd and nvidia? Sometimes EVEN IF IT'S NOT A DRIVER BUG they can find something and make an adjustment or contact ssg for a workaround.
 
Upvote 0

Natashaelle

Time Bandit
It used to happan to me with some frequency, though it has become quite rare for me now.

AMD 6-core on an Aorus motherboard with RTX 2080 Ti, and Windows 11 25H2.

---

One workaround I've found is take the first barrier down before casting your buffs. Buffing very first thing you do after entering and before even moving did seem to trigger it more frequently.
 
Upvote 0

gringlebort

Well-known member
had it twice in all the time i been playing ever since sharn came out its been posted many time over the years i think it is a very rare glitch been in guildy runs and very rare some has it but no one else in group
 
Upvote 0

Alpha Tester

Well-known member
I had the same problem in this one. There is a feywild quest with the same issues but not I don't remmember the name but The Stone Crypt Chronicle to fix it is the third one. You are with your toon, with all PLs and with a top notch pc doing r10s with friends until you are a drag to the team because the game is not working.


I begged for them to fix it for YEARS and nothing. At least to me there should be not any new pack if they don't fix the old stuff.
And be warned: This bug may happen with any pc configuration: At one time and some quests a 750ti will work better than an rtx 3070 or 4070 because of BAD GAME OPTIMIZATION.

And this is DDO. Nothing we can do to fix it.
 
Upvote 0

Aeromach

The Best
Just ran into this for the first time today on Thrane, Heroic R1. (AMD Radeon graphics)
I tried adjusting in-game setting for awhile with no affect.





2026-04-13-DDO-No-Refunds-024022-0.jpg

(stopped frame Screenshot)

Maybe this will help get it fixed one day...
 
Upvote 0

Lazuli

Well-known member
No, it wasn't. I've had it twice since that patch. The first time I reset the quest, the second time I disabled stencil shadows, which also worked (thanks, Rabid, for pointing this out).
 
Upvote 0
Top