Ray-caster: drop outdated performance comment
The size of the internal fragment arrays is what really matters, as discussed in the "Display" page on the wiki.
This commit is contained in:
parent
f47be08d98
commit
7cb01bab82
@ -13,8 +13,7 @@ struct vecInv {
|
||||
|
||||
// --- uniforms ---
|
||||
|
||||
// construction. the SPHERE_MAX array size seems to affect frame rate a lot,
|
||||
// even though we should only be using the first few elements of each array
|
||||
// construction
|
||||
const int SPHERE_MAX = 200;
|
||||
uniform int sphere_cnt;
|
||||
uniform vecInv sphere_list[SPHERE_MAX];
|
||||
|
@ -13,8 +13,7 @@ struct vecInv {
|
||||
|
||||
// --- uniforms ---
|
||||
|
||||
// construction. the SPHERE_MAX array size seems to affect frame rate a lot,
|
||||
// even though we should only be using the first few elements of each array
|
||||
// construction
|
||||
const int SPHERE_MAX = 200;
|
||||
uniform int sphere_cnt;
|
||||
uniform vecInv sphere_list[SPHERE_MAX];
|
||||
|
Loading…
Reference in New Issue
Block a user