Glad the tutorial helped, but looks like not quite enough ;)
If the display update rate is running at ~64, then the function isn't
bogging down due to performance. There must be some other problem. Hmmm...
Sounds like you have all the basis covered.
I'm assuming that the inputs actually "change" at 20Hz. Did you confirm that
too? Try dropping all the parameters into text objects and displaying them
as Hex (or whatever). Do their values also change at a fast rate or do they
change closer to .1 hz?
If they do change faster than 0.1Hz then it could possibly be a bug in the
derived engine. I have heard of a similar issue, but the input data wasn't
based on parameters (it was being simulated with GetValue functions).
Let me try to do some experiments and I'll attempt to reproduce.
Alternatively, if you can send me the data (privately jim at iads-soft dot
com) and your derived function project, I can step through the derived
engine code and see what's happening,
Jim
> --
> You received this message because you are subscribed to the Google Groups
> "IADS" group.
> To post to this group, send email to ia...@googlegroups.com.
> To unsubscribe from this group, send email to
> iads+uns...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/iads?hl=en.
>