search

Resike / Z-Perl

World of Warcaft unitframe addon
https://www.curseforge.com/wow/addons/zperl
GNU General Public License v3.0
23 stars 21 forks source link

zPerl bugging out water effects in wow classic #188

Open cokesplash opened 2 weeks ago

cokesplash commented 2 weeks ago

zPerl is bugging out water effects in-game. When "Liquid Detail" under "Graphics settings" are set to "Good" or "High", the water edges flicker constantly. When Zperl is disabled, the flickering effect stops.

cokesplash commented 1 week ago

I have narrowed the problem down to the 3D player portrait. If you uncheck 3D portrait on the player tab, the water issues immediately stop.

Resike commented 1 week ago

Are you on MAC? Have you tried to exit the game and delete your World of Warcraft\WOWFLAVOR\Cache folder?

cokesplash commented 1 week ago

I'm on windows. I deleted the cache folder (playing classic era) and it had no effect on the bug.

Resike commented 1 week ago

Yeah you gonna have to report this issue to Blizzard then, including your DirectX and OS info.

cokesplash commented 1 week ago

I have 3 computers all with different graphics cards that are all having the same issue with zPerl and many others in my guild are having the same problem. What makes you think this is a Blizzard problem? Considering when I disable the 3D portrait in zperl, I can tell you exactly what they will say if I report it to them.

Fieora commented 4 days ago

I have 3 computers all with different graphics cards that are all having the same issue with zPerl and many others in my guild are having the same problem. What makes you think this is a Blizzard problem? Considering when I disable the 3D portrait in zperl, I can tell you exactly what they will say if I report it to them.

While it may be Zperl interacting with the render pipeline causing the issue, it doesn't mean it's a problem with what Zperl is doing. An addon can't interact with textures or objects in the 3D world, only the interface layer. So if loading a 3d model in the interface layer causes this behavior, it points to a problem in the render pipeline in WOW, not the addon.

If I remember correctly this started after the sunken temple phase started (before Zperl updated), If I had to guess, they were experimenting with some new glow or particle effects and never caught this problem.