Ok fair enough, yes i realize the code has "something" to do with it... what I mean is I have managed to narrow this down to a hardware issue of sorts... Something blitz is doing differently between machines that have an integrated videocard(such as failing at parts of the code that make no sense), and those that do not have an integrated card(works perfect).
I mean at this point it could be a million things. Without being able to physically see blitz's memory heap that it has allocated on the machines that fail, and create a stop on the machines that work and try to compare data or something. Regardless the only piece of the puzzle that is consistent is the fact that ALL machines with video cards execute the code flawlessly. And that makes absolutely zero sense to ol' boy Scott here.
I mean at this point it could be a million things. Without being able to physically see blitz's memory heap that it has allocated on the machines that fail, and create a stop on the machines that work and try to compare data or something. Regardless the only piece of the puzzle that is consistent is the fact that ALL machines with video cards execute the code flawlessly. And that makes absolutely zero sense to ol' boy Scott here.