So the only clue I could find by googling was something like an interpretation of a value of different type? The problem I have is beyond my ability to comprehend, my description of what is happening is: read float array data and write to float array in a loop, print out the value of the array I copied into and its allright, after loop print out same value in same array I copied into and the first couple of elements have value 1.4013e-044, after that the following elements are ok... HOW CAN THAT HAPPEN? Nothing happens after the loop that neither reads or writes the array, its texture coordinates and I saw the error visually in my program first, and traced it back to the loading function were it reads the coordinates from file into an array, and then copies data from that array into a new one to get a different order. Ive used same code in the past and never encountered this before, does anyone know anything about the 1.4013e-044 corruption and can have a guess at something that could happen? I thaught mayby something happened in the loop to get back to first elements by mistake and mess with the data, but I checked carefully, its literally all ok inside of loop and next line after loop the data is corrupted. --- Double Post Merged, Sep 1, 2016, Original Post Date: Sep 1, 2016 --- If I offset the use of the array, like add 30 to the elements xxx[x+30] then it works, its a few elements in the beginning of array that gets autocorrupted after a loop has finnished writing to them, theyre ok inside of loop but directly after it theyre nolonger ok, and nothing happens inbetween... This just drives me insane, and how could I trust it not to happen worse in the future?