[RESOLVED kinda] edgeDetectP.hlsl warning X3550

#1 I'll take a look when I get home if nobody else has done it.

If you are feeling intrepid you could open the shader file in notepad++ and see what's on line 30.

#2 This warning is telling you that shader code, which would otherwise be a dynamic loop, is being unrolled.

So, this means that, instead of something like this:

for(int i = 0; i < 4; i++)
   foo[i] += bar;

Turns into...

foo[0] += bar;
foo[1] += bar;
foo[2] += bar;
foo[3] += bar;

And the compiler is just warning you about why this is happening.

#3 @Joshua - actually I did have a peek, and it seems to be exactly the same file as in Beta4, which didn't flag a warning, so I reckoned it was because of something else.

#4 Oh.. yeah I haven't seen that file. Loop unrolling is usually an optimization but I guess it's saying it can't address the memory at run-time. I'll be interested to look at this file to see how that array is being passed to the shader.

#5 Yea... whenever you use array indexing via [] in a loop it spits out that warning. Its sort of annoying... not sure if there is a way to code it better or disable that one warning in that case.

#6 @Steve:
I recall seeing this warning before - might have been a Beta other than 4 though - can't remember.

@Tom:
I wonder if there is a difference about how the two blocks would count against the maximum command count for the actual shader model. If there's no difference, then I think the warning should be suppressed.

#7 There is a difference. Unrolling the loop means it will duplicate the instructions.

#8 @Konrad - Here's where I've seen it before - when I was getting the cartoon Outlining shader to work. linky And you did do a resource along those lines.

#9 @Steve: You're right, that's why it was familiar. :)

@Pat: Thank you for the info! That's very useful to know!

#10 Just on a clean up.
Not resolved in Release, but not really a bug - see post 5 - so moved to resolved.