Well... It doesn't work for me either. I dont even need it, but I tried it.
Hardware:
i5 3570k
Asus dc2o gtx660
2x4gb 1600mhz ddr3
Win 7 ulti 64bit.
Just play fair, it's way more fun! :)
Advertisement
r_primitives
#12
Posted 30 January 2013 - 10:42 PM
i knew it doesn't do much on nvidia cards, i've used ati/amd too but never thought of putting this value up to 3.
this might be a glitch working only on intel integrated graphics and i'd say those suffer so much on performance that i'd be supprised someone wouldnt use this knowing about this glitch.
but it's gotten fixed at 4.2 so... well just quit using this outdated 4.1.1 if you don't like bugs as this one. i suppose.
this might be a glitch working only on intel integrated graphics and i'd say those suffer so much on performance that i'd be supprised someone wouldnt use this knowing about this glitch.
but it's gotten fixed at 4.2 so... well just quit using this outdated 4.1.1 if you don't like bugs as this one. i suppose.
<sXe>
#13
Posted 01 February 2013 - 06:03 PM
jfyi:
r_primitives (variable)
syntax: r_primitives [value] default: 0
Sets rendering method.
Valid settings:
-1=skips drawing
0=uses glDrawelements if compiled vertex arrays are present, or strips of glArrayElement if not.
1=forces strips
2=forces drawElements
well, just give me decent animations and fix ugly bugs in 4.2 than I'll quit playing 4.1.1
r_primitives (variable)
syntax: r_primitives [value] default: 0
Sets rendering method.
Valid settings:
-1=skips drawing
0=uses glDrawelements if compiled vertex arrays are present, or strips of glArrayElement if not.
1=forces strips
2=forces drawElements
n1n, on 30 January 2013 - 10:42 PM, said:
but it's gotten fixed at 4.2 so... well just quit using this outdated 4.1.1 if you don't like bugs as this one. i suppose.
well, just give me decent animations and fix ugly bugs in 4.2 than I'll quit playing 4.1.1
Advertisement
1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Advertisement