subject:"\[Bug 33172\] \[r600g\] ingame rendering broken \(black screen\) in ut2003"

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-02-01 Thread bugzilla-daemon

https://bugs.freedesktop.org/show_bug.cgi?id=33172 Tobias Jakobi changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-02-01 Thread bugzilla-dae...@freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=33172 Tobias Jakobi changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-27 Thread bugzilla-daemon

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #5 from Tobias Jakobi 2011-01-27 07:49:02 PST --- (In reply to comment #4) > That's 64-bit ut2004, right? Yes. > Probably, but it's certainly not going to make it any faster. That's a given. And it didn't work anyway, since it looks

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-27 Thread bugzilla-dae...@freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #5 from Tobias Jakobi 2011-01-27 07:49:02 PST --- (In reply to comment #4) > That's 64-bit ut2004, right? Yes. > Probably, but it's certainly not going to make it any faster. That's a given. And it didn't work anyway, since it looks

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-27 Thread bugzilla-daemon

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #4 from Henri Verbeet 2011-01-27 07:28:26 PST --- (In reply to comment #3) > Monitoring ut2004-bin with htop showed that during peak times the process has > more than 50GiB virtual mem (VIRT) allocated. So there's clearly a mem leak

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-27 Thread bugzilla-dae...@freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #4 from Henri Verbeet 2011-01-27 07:28:26 PST --- (In reply to comment #3) > Monitoring ut2004-bin with htop showed that during peak times the process has > more than 50GiB virtual mem (VIRT) allocated. So there's clearly a mem leak

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-26 Thread bugzilla-daemon

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #3 from Tobias Jakobi 2011-01-26 11:46:00 PST --- New tests on my system with ut2004. UseVBO is disabled, so I only get a black screen ingame. I can still play though (by ear so to speak) and while doing this I watched memory consum

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-26 Thread bugzilla-dae...@freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #3 from Tobias Jakobi 2011-01-26 11:46:00 PST --- New tests on my system with ut2004. UseVBO is disabled, so I only get a black screen ingame. I can still play though (by ear so to speak) and while doing this I watched memory consum

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-19 Thread bugzilla-daemon

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #2 from Tobias Jakobi 2011-01-19 14:35:02 PST --- We (Jan and me) did some tests today and found out that the issue is probably related to the use of VBOs (or more specifically: not using them). In ut2004 there is a option called 'U

[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003

2011-01-19 Thread bugzilla-dae...@freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=33172 --- Comment #2 from Tobias Jakobi 2011-01-19 14:35:02 PST --- We (Jan and me) did some tests today and found out that the issue is probably related to the use of VBOs (or more specifically: not using them). In ut2004 there is a option called 'U