Interesting followup:
No setting I make in amdcccle allows the in-game selection of vsync/not-vsync to affect results. However, if I set amdcccle to force vsync on or off, it seems to work.
On further study, I'm pretty sure that the frame rate issues here are wine/opengl/WoW -- it appears that WoW has a single primary worker thread that does ALL of the rendering, and that in practice it consumes at most a tiny fraction past a single core's time, which means that as the amount of geometry work for it to do increases, it slows down quite a bit. There does not appear to be an obvious way to fix this, short of massive reworking of the opengl libraries or something comparable.
So my best bet will be to hope that wine's directx translation improves, since apparently that engine is better in WoW.
No setting I make in amdcccle allows the in-game selection of vsync/not-vsync to affect results. However, if I set amdcccle to force vsync on or off, it seems to work.
On further study, I'm pretty sure that the frame rate issues here are wine/opengl/WoW -- it appears that WoW has a single primary worker thread that does ALL of the rendering, and that in practice it consumes at most a tiny fraction past a single core's time, which means that as the amount of geometry work for it to do increases, it slows down quite a bit. There does not appear to be an obvious way to fix this, short of massive reworking of the opengl libraries or something comparable.
So my best bet will be to hope that wine's directx translation improves, since apparently that engine is better in WoW.
Comment