Correct shader table strides when preparing DispatchRays descriptors

[jaladreips]

It's more correct, probably won't have any functional effect.

I've ran into this when I was increasing the number of miss shaders in the triangle sample.

[jaladreips]

@microsoft-github-policy-service agree

[alecardoso-tech]

This change is incorrect.
The DispatchRays function is initializing dispatchDesc members. If you assign dispatchDesc->HitGroupTable.StrideInBytes to itself, you're not updating the value to the correct stride.

Plus, consider the comment at the beginning of the function: Since each shader table has only one shader record, the stride is same as the size. This explains why they use the SizeInBytes member.

[jaladreips]

You're right, my change is incorrect.

However, having the stride equal to SizeInBytes makes the sample break as soon as someone modifies it and adds an additional table entry. That's what happened to me.