Comment # 8
on bug 107694
from James B
All tests performed with same settings. - Rage 32-bit on Windows 10: Works perfect out of the box no performance issues, no issue with the virtual textures, no texture pop-in bug. I noticed the player shadow wasn't rendered correctly, but everything else is fine. Rage.exe RAM usage ~1,370MB on the Wasteland map. - Rage 32-bit on Ubuntu w/ 18.20 Pro drivers: I experience good performance out of the box but the virtual textures bug is present although very minor. Can be totally cured by setting "jobs_numThreads 1", texture pop in bug still persists. Rage.exe RAM usage ~780MB on the Wasteland map. - Rage 32-bit on Arch w/ latest mesa-git: Massive issue with virtual textures unless you set "jobs_numThreads 1" which reduces but doesn't fix the issue, frame rate dips to 30-40fps in certain areas of the wasteland and the "texture pop" is there regardless even if you enabled the texture cache, set the maxPPF etc. Rage.exe RAM usage ~730MB on the Wasteland map. http://renderingpipeline.com/2012/03/megatextures-in-rage/ Adding "+com_allowconsole 1" to the launch options using "toggle vt_showPageNumbers; vt_restart" you can see the wrong mipmap level and texture numbers are being loaded for some of the tiles. I'm wondering if somebody at AMD would have access to the changelogs for the proprietary drivers back when the Rage patches were first introduced, it would atleast point you in the right direction. Heres a video I made comparing 32/64-bit versions on my system: https://www.youtube.com/watch?v=EUwq4dbnFkA
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
