[Gtkradiant] Gtkradiant broken after system and drivers upgrade
Forest `LordHavoc` Hale
lordhavoc at ghdigital.com
Mon Oct 29 10:32:21 CDT 2007
I have to concur, the DRI drivers haven't had a very good track record.
I can tell you exactly what that driver error means however:
older Radeon cards have only the ability to address up to 4096 vertices at a time (an arbitrary number of triangles, but only that many vertices - probably some kind of on-chip vertex transform cache
is responsible for this limit), GTKRadiant is issuing more than this many vertices in one call.
The hardware however has configurable base address for vertex arrays, and configurable index bias, this allows it to issue the large draw operation as several smaller ones that do not violate the
limits of the hardware.
That error indicates the code for splitting the operations into smaller ones, is broken.
Report this to the DRI team, it's not a GTKRadiant problem.
(All other drivers have to deal with this sort of hardware limitation transparently as well, it's not an application error)
Timothee Besset wrote:
> Stick to ATI's official fglrx drivers. That error is clearly a driver
> Jose Rodriguez wrote:
>> I previously sent this from another mail account by mistake so it
>> got stuck somewhere. My mistake.
>> My Gtkradiant broke after I upgraded from the stable to the
>> testing branch of Debian. At the same time, I switched from the ATI
>> proprietary driver to the open source one, so I'm unsure about
>> which one of these two changes is the culprit for Gtkradiant not
>> I can fire the program up, and even load maps with
>> textures in them as long as I don't have the three ortographic
>> vews visible. Otherwise it just crashes. With only one of those
>> views it stands a bit more before closing itself. I played with the
>> options but they didn't make any differece. In the program console
>> I can read the following:
>> Lighting mode requires OpenGL features not supported by your
>> graphics drivers: GL_ARB_shader_objects
>> And after it crashes this is what appears in the terminal:
>> radiant.x86: vbo/vbo_split_inplace.c:97: flush_vertex: Assertion
>> `max_index >= min_index' failed. Aborted
>> Could somebody provide some information about how to find out
>> what's going on? I'd really like to stay with the open source
>> drivers. If there was an issue with them, would it be possible
>> somehow to do the missing OpenGL bits via software rendering? As a
>> side note, only two days ago somebody I know experienced something
>> similar after upgrading to the latest Ubuntu release, but I'm not
>> sure about his hardware/drivers whatsoever.
>> PS. I use Gtkradiant to map for Open Arena, if that is of any
>> Gtkradiant mailing list
>> Gtkradiant at zerowing.idsoftware.com
> Gtkradiant mailing list
> Gtkradiant at zerowing.idsoftware.com
Author of DarkPlaces Quake1 engine and mod
"War does not prove who is right, it proves who is left." - Unknown
"Any sufficiently advanced technology is indistinguishable from a rigged demo." - James Klass
More information about the Gtkradiant