ok try this bit of code out...
sync on
sync rate 0
global count as integer
count=0
func()
function func()
cls
inc count
print count
sync
func()
endfunction
now i know and you know this is a stupid thing to do cause ya can NEVER get out of the function caling itself (there is method to my madness..) so why would i do such a thing, well, im glad you asked! i have written some code which does sort of the same thing except after its achieved its goal, it will exit the function no worries at all....
except for if it runs for too long it locks up/bombs out/crashes etc take ya pick! so i whipped this up to test if it was me or something else, and interestingly enough this snippet up here will freeze every time it hits 37034 on the count, which seems like plenty of 'loops' to get things done but sadly as i have found out its insufficient for my program when it needs to do more than that!!! if im checking an array of say 200*200 elements (and yes it is necessary for it to check internally!) thats comes to 40000, so as ya can work out for yaself 37034 is a wee bit too small for this!
ARGH!!!! is it just my machine that does this?? can someone check and see if it dies for them at this mystical 37034??? is this a problem with a memory leak with functions?? losing its place or something???
i have DB pro patch 4, DX9, and 288mb ram.
oh should warn ya, if it does hit 37034 and stop counting ya pc might do REALLY weird things, reboot if ya have too! lol
So Rich, Lee anyone!! is this fixable???
optic blast! megablast! have a blast!!