xiando Lv 1
I have been noticing an odd occurrence, in which freeze appears to be acting within the confines of the global wiggle environment.
My understanding was that wiggle is supposed to function right "through" a frozen area, yet I am seeing clear occurrences of it behaving somewhat more like isolated wiggle.
it may be that under some threshold of perturbation, freeze is dominating, I don't know, but my understanding was that term was zeroed, (ie suspended DURING wiggle) prior to initiation of the wiggle function until AFTER the wiggle is completed (specifically, a stop command is issued)
In the attached composite picture, not that the two situations used the same initial condition, except for one variable, namely the frozen section. images were reduced in size and extraneous screen image has been removed to reduce upload size.
Would someone from the development team, ie, Seth, Adrien, Zoran, or someone with similar detailed understanding of the inner workings of the program please respond to this issue in a timely fashion. It is alarming to say the least, in light of explicit statements to the contrary made by several of you during the initial stages of the beta release.
