Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I was hoping that all that hardware would cure a problem I've been having... I've made an indicator which is a
Bollinger% B3 of t4tcum. (Boll%B3 was published here in one of Gabryele's threads).
If set for cobc false, ninja crashes... I thought more computer power and more memory would cure that.
What do you think?
Can you help answer these questions from other members on NexusFi?
my "old" t4tCUM... have little problemsto give permanentvalid values to the external data series... when COBC = "false", then its give during the internal sync state moments with invalid and not accessable values...
-> many indicators dont check/validate the current array values...
I have this now corrected by continue using the "old" values from last bar as start value of any new bar, when COBC = false. This give everytime accessable in combination valid values and if "insync" all tickvalues well be used for correct new tickbased calculations.
=> for using other indicators its very important the use of a only one time on StartUp initialized variable!
-> in my t4tCUM thread i have published a demo source(with a update of t4tCumUD->v15) for a indicator with external using the t4tCumUD15... this show this coding style and work better as t4tCumUD13...
-> t4tCumUD2 well come this month
