Sorry your browser is not supported!

I just fixed a bug in my program that related to the use of arrays and I can't replicate it again but here is what was happening:

I dimensioned 2 arrays PathX(x,y) and PathZ(x,y)

Then I saved a set of values to PathX(num,all values here) and PathZ(num,all values here). Then if I printed the all the values in the arrays, I could see that if num was even, then the values of PathX(x,all values here) and PathZ(x,all values here) would be equal to PathX(num,all values here) and PathZ(num,all values here) for all even numbers x. And vice-versa for odd values of x.

I hope that makes sense, but has anyone heard of this happening before? I know it sounds strange but am 100% sure it was not an error I made and the only things I changed to fix it were the ways the arrays PathX() and PathZ() were dimensioned.

Hi luke - never seen a problem like this before - often I think I've found a new bug in DBC or experience some crazy behaviour like you describe, but for me it always turns out i've made a typing error somewhere.

Remember in your case the problem may be with the code that fills the the arrays with data - it's pretty easy to get an x and z mixed up, or something along those lines.

I though it might have been a strange for next loop, so I removed all the loops and tried again, it still happened. The changes I made to the code to fix it were only in the way the arrays were defined. They were previously based on a value inserted into another array from a function that set the value of said array, and I changed it from that and it went away. I tried replicating it but I can't remember exactly what I changed. I'm going to try again tonight.