Using phase run while quartz flask'd -> client crash

Hi, I posted a thread awhile back about a character I had that was receiving frequent client crashes and I couldn't figure out what part of my build was causing it.(https://www.pathofexile.com/forum/view-thread/1973180)

After going back to him after a couple patches to see if whatever issue was fixed, unfortunately I was disappointed to see it wasn't but I did come to realize what the issue is.


That character uses a quartz flask as well as a cwdt phase run setup. I noticed that the crashes I was seeing were happening in situations where both were active recently. After some testing, I noticed that if phase run triggered while i was already phased from a quartz flask, soon afterwords I would wind up crashing. Sometimes it seemed to happen right as the cwdt triggered (my immortal call being attached made it easy to tell), sometimes it took a few seconds after the triggers, but eventually it would crash in those circumstances, while if i avoided using my quartz flask or unsocketed my phase run their was no problem. Didn't matter whether phase run was triggered or used manually, either way it'd happen.


It seems to be tied to a graphical bug that's been happening for a long time now. For months if you used phase run while already phasing, your character would be turned nearly invisisible, persisting even after the phasing effects are gone. I've experienced this firsthand before, and as recently as a week before 3.0 it was never causing a client crash for me (i used the exact same cwdt setup and flask combination in a build late in legacy). It seems something in 3.0 has caused this graphical bug to take a turn for the worse.

I also experienced this with D3D11. I think it's related to the bug that makes your character permanently invisible with quartz + phasing. But for me 3.0.1d stopped issues, but that might be also related to the fact that I removed [DISPLAY] section from production_Config.ini file and removed shader cache and minimap files (I did that before 3.0.1d, but didn't help). The only notable change that I noticed after configuring again is that these 2 rows:

"

max_PS_shader_model=ps_3_0
max_VS_shader_model=vs_3_0

Were replaced with these:

"

max_PS_shader_model=ps_4_0
max_VS_shader_model=vs_4_0

Well, my config's already got the latter two lines. Tried deleting my shader cache and minimap too for the hell of it, didn't work.

At least it's something i can work around, i can just not use my cwdt-phase run... it is a shame though, since it's a great defense mech for my build that worked just fine before 3.0 (aside from the harmless perma-transparency graphic).

gear and mtxs don't make a difference, happens with a completely naked character with just an unset ring with phase run socketed, with no other buffs either ofc. My original problem character was a shadow, just tested again on a marauder for the same results.


It doesn't seem to happen when i'm in my hideout, only in hostile instances. Usually with enemies within active distance... while testing, doing it at the waypoint in the grain gate (act 8) didn't seem to do anything at first but then i traveled a bit into the area and it crashed.

It's probably related to my graphics driver too, idk, but if i alt-tab out instead of closing the frozen window i get a little taskbar bubble telling me my graphics driver stopped working and recovered. I have a Radeon r9 270x, using windows 7 64bit.

I get a windows error popup when it happens, the info it gives is:



Hope that helps.

I have the same issue with (codt+phase run)+(phasing). Seems to me its any phaseing, flask or passive buff, and phase run (gem). When they both proc my game crashes. I also use ic+codt but I notice the game crashes before the ic procs so I doubt thats the cause. I took off my phase flask and phase run gem and mo more crashes. Also I play on xbox so its probably just a conflict of coding. Hope any of that helps.

Current movement/auto procs

Phase run lv 4 + codt lv 2 + inc duration lv 9 + frost wall lv 11

Ic lv 7 + inc duration lv 12 + codt lv 5

Shield charge lv 12 + stun sup lv 17 + ecoms lv 15 + fort sup lv 13

Just wanted to pop back in here and say: since 3.0.2, my issue seems to be fixed, i tried doing the same thing that caused crashes before and everything's fine, and I've since been using a quartz flask with cwdt-phase run regularly and no client crashes at all. (still get the whole invisible character thing, but that isn't much of an problem now that it's not causing crashes).

Just wanted to point it out for any others that may not have realized it (since this wasn't something explicitly stated as being fixed in the patch notes) and say thanks for the fix. I can finally run my saboteurs the way i like to run them again, feels good.