Re: "tell a programmer" Index buffer
Posted by Nickelplate on
Fri Dec 31st 2004 at 3:24am
2770 posts
346 snarkmarks
Registered:
Nov 23rd 2004
Occupation: Prince of Pleasure
Location: US
I just got an error that says "too many indices for index buffer.. tell a programmer (33168>32768)" Literally that is what it says. Any hints?
Re: "tell a programmer" Index buffer
Posted by KungFuSquirrel on
Fri Dec 31st 2004 at 3:51am
751 posts
393 snarkmarks
Registered:
Aug 22nd 2001
Occupation: Game Design, LightBox Interactive
Location: Austin TX
Well... tell a programmer. :smile:
This is the sort of thing that they'd internally pass on to one of the programmers, who could probably track down the problem and help them fix it. Unfortunately this is one resource Valve hasn't made available. :smile: Is it causing an actual crash, or is it just a warning that shows up in your log?
Re: "tell a programmer" Index buffer
Posted by WatchDog on
Fri Dec 31st 2004 at 5:46am
43 posts
14 snarkmarks
Registered:
Dec 24th 2004
Location: Australia
Yea well all the mapper woudl be siting at valve and when they get this
error would probably walk past fat nwell to the programming department
and get one of em to help them.
Re: "tell a programmer" Index buffer
Posted by Forceflow on
Fri Dec 31st 2004 at 9:34am
2420 posts
451 snarkmarks
Registered:
Nov 6th 2003
Occupation: Engineering Student (CS)
Location: Belgium
I'd suggest you do the same. Happy flight !
No seriously, erh ... I don't think there's a way to solve this ... you could try mailing Valve or something.
Re: "tell a programmer" Index buffer
Posted by Livett on
Fri Dec 31st 2004 at 11:25am
Posted
2004-12-31 11:25am
164 posts
46 snarkmarks
Registered:
Dec 24th 2004
Occupation: Student
Location: England
Tbh... I doubt Valve would care.
Re: "tell a programmer" Index buffer
Posted by Myrk- on
Fri Dec 31st 2004 at 1:08pm
Myrk-
member
2299 posts
604 snarkmarks
Registered:
Feb 12th 2002
Occupation: CAD & Graphics Technician
Location: Plymouth, UK
I think they would tbh. If this problem occurs enough I'm sure they'll just patch the SDK in the next update.
Re: "tell a programmer" Index buffer
Posted by Foxpup on
Sun Jan 2nd 2005 at 3:35am
Foxpup
member
380 posts
38 snarkmarks
Registered:
Nov 26th 2004
Occupation: Student
Location: the Land of Oz
The first number is the number of indices and the second number is the maximum indices you can have. The fact that it's 32768 is interesting... A two byte unsigned integer (which is what you'd normally use for an index) goes up to 65535...
Tell the programmers at Valve to up the buffer size to 65535!
Re: "tell a programmer" Index buffer
Posted by Raeth on
Sun Jan 2nd 2005 at 4:06am
62 posts
16 snarkmarks
Registered:
Nov 24th 2004
Location: USA
I got one of these when I made a giant func_precipitation in my map and
then stood on top of a tower where I could see most of it. I
suppose it could be particle system related too.
Re: "tell a programmer" Index buffer
Posted by Leperous on
Sun Jan 2nd 2005 at 1:10pm
Leperous
Creator of SnarkPit!
member
3382 posts
1635 snarkmarks
Registered:
Aug 21st 2001
Occupation: Lazy student
Location: UK
Yeah, it sounds like there is too much of something- in Raeth's case, probably rain drops- or perhaps something is overflowing?
Re: "tell a programmer" Index buffer
Posted by khaosaxeman on
Fri Jul 4th 2008 at 5:25am
1 post
0 snarkmarks
Registered:
Jun 15th 2008
I also received the index buffer error. I believe it is because I have a lot of cydrilical brushes that have been hollowed out to appear as pipes. Hollowing a cylinder & deleting the end pieces creates new brushes equating to however many faces the original cylinder had. I opted against using props for the same as it seemed that props caused more problems than solid brush entities. I deleted many of the cyndrilical brushes & still encounter the same problem. I pose the following questions:
1. Is it possible to increase the number of allowable indicies?
2. Is using solid brushes more efficient than props?
3. Will reducing the number of faces on the cylinders solve the problem?
4. Will applying the nodraw texture to non-visible faces of the map help?
5. Will grouping similar brushes together help?
My map has also ALOT of displacement, along with blended textures (and subsequent alpha displacement). There is also a lot of texure scaling. For example, a 48X96X44 unit brush with the woodshelf texture. All sides are texture-scaled to make the entire brush look like a full bunk of lumber. I have deleted a few of these brushes to try to solve the problem, without compromising the theme of the map. I still get the same error. The compile log shows no errors, but when I run the map in-game, it crashes. Please help.
Yours,
?Khaos? axeman