From: Ben S. <dar...@ii...> - 2005-02-17 12:45:14
|
Jan Kreuzer wrote: >>nwn probably uses something which requires elts to be supported (ie. >>glDrawElements). >>The latest cvs snapshot has made a start on this, but more information >>is needed. I've >>had some success with ut2004 by putting the indices into the command >>buffer, but >>ultimately this is not how we want to do it. >> >> >As far as i could see from the cvs-logs the elts thing was added 17 hours ago, >however i tested nwn earlier and the screenshots looked the same. So it >seems that this change is not responsible for this weird looking. > > I wasn't saying that this change broke it, I meant that when completed, applications which use glDrawElements etc, should render correctly, rather than having some random polygons on the screen. I'm not even sure if this is the cause of the nwn rendering errors, it could be something else completely. But, it does look like the same type of problem which ut2004-demo has. Cheers, Ben Skeggs. >However i now can turn on reflection in neverball without an slowdown >(before i had an slowdown). > > >>>I dont get any lockups since about a week (which seems to be strange as many >>>others get lockups), however i do not use xorg-cvs, but ubuntus xorg-package >>>(seems to be the latest 6.8.2-beta) with the ati.patch from r300. >>> >>> >>> >>> >>Is this with vertex buffers turned on? If so, can you cause a lockup by >>moving a window >>over the top of the glxgears window? This is the only way I can cause a >>lockup with >>the vertex buffer code. I'm using xorg cvs from 1-2 days before the >>dlloader changes. >> >> > >Hmm i must test this with an earlier snapshot, then i will report back. > >Greetings Jan > > > > |