found it!!!
i think... looks like it was my particle generator...
i was checking to a see if the particle life was =0 before i deleted it, but my algorithm for generating and aging the particles could sometimes result in the life being a fractional value... and it could conceivably never equal 0, but go right past it to -.025, or something like that...
sort of a programmed in memory leak :) i would say... boy, i can be so stooooopid sometimes...
but hey, if we had a proper debugger (not much chance of that now eh :) ) this might've made itself apparent much sooner (gatta blame the system right :) )...
i eventually had to put up a textline to see how many particles was being generated, and how many remained after the sub stopped and no new particles were being created (they should've all died off eventually)...
if your particle code is based on the ole 'party' generator code then you might wanna change the line that checks to see if p\ent=0 to if p\ent<1... just to be sure :)
***Added***
now after saying all that about Blitz needing a good debugger, i have to say, that on the other hand, i'm really impressed with how fast Blitz3D handles this stuff... man i must have a million loops spinning around in here, and before i tracked down the bug, the particle count went up to near 900 before i started noticing any slowdown... impressive thing, this Blitz3D...
Mark... if you're out there, i just wanna THANK you for creating this thing the way you did... and i'm sold on the next B'Max version for sure...
(now this is not an attempt to kiss up or try to get an advanced copy of B'Max3D... i mean, not unless you want to, that is :) )
--Mike
i think... looks like it was my particle generator...
i was checking to a see if the particle life was =0 before i deleted it, but my algorithm for generating and aging the particles could sometimes result in the life being a fractional value... and it could conceivably never equal 0, but go right past it to -.025, or something like that...
sort of a programmed in memory leak :) i would say... boy, i can be so stooooopid sometimes...
but hey, if we had a proper debugger (not much chance of that now eh :) ) this might've made itself apparent much sooner (gatta blame the system right :) )...
i eventually had to put up a textline to see how many particles was being generated, and how many remained after the sub stopped and no new particles were being created (they should've all died off eventually)...
if your particle code is based on the ole 'party' generator code then you might wanna change the line that checks to see if p\ent=0 to if p\ent<1... just to be sure :)
***Added***
now after saying all that about Blitz needing a good debugger, i have to say, that on the other hand, i'm really impressed with how fast Blitz3D handles this stuff... man i must have a million loops spinning around in here, and before i tracked down the bug, the particle count went up to near 900 before i started noticing any slowdown... impressive thing, this Blitz3D...
Mark... if you're out there, i just wanna THANK you for creating this thing the way you did... and i'm sold on the next B'Max version for sure...
(now this is not an attempt to kiss up or try to get an advanced copy of B'Max3D... i mean, not unless you want to, that is :) )
--Mike