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)
Thanks for the info. Do you have any idea on what settings the use at nexgen? I see a lot of people using ninja that have that but I cant seem to match it in TOS.. For instance in TOS my native macd is a 2 line macd with a macd line and an average line.. I can plot BB's on the average and it will look decent but if i try to plot them on the macd line they spread widely all over the place.
Yeah I coded the macd im using for this.. Just for thought I did try using price and it wouldnt even print right. I have it looking pretty good right now.. I just thought it was weird I having to base the bb's on the average and not the macd line.
I noticed that when you scroll your chart backwards in NT7, the dots separate from the BB Bands; you have to hit F5 on each page to get the right alignment. Can you fix this?
I've noticed SEVERAL weirdities in NT7 regarding indicators. Especially those that change color (blue = long / red = short), dots, lines, etc. Sometimes the indicator will be BOTH blue and red at the same time (one dot or line on top of another, slightly offset). I also noticed this with MACDBBLines - when you scroll back a day or so, the bb lines separate from the macd portion of the indy. F5 generally 'fixes' it, but not for long! I've seen this happening with other indicators, too. I don't think it's an indicator problem! I've mentioned several oddities to NT and they are always grateful and "will pass this on to the development team". I guess we'll just have to make do & wait until all the bugs are ironed out (sometime in 2014!).
After all, it's what you learn AFTER you know it all, that counts!
This is not a bug, just something that was automatically taken care of in NT6.5. If you have two dot plots that in NT6.5 would plot and show the appropriate color according to conditions, NT7 doesn't necessarily remove the one that doesn't apply anymore. Now you have to test for the condition as always but if it stops existing you need to reset the plot and make it disappear. Kind of like removing a draw object. The better way, which requires even more reworking, is to use one plot and do a color change if conditions change. This also saves memory that was used in the extra Data Series but you also have to add options for different colors since the user can't use the plot color option. Hope this helps.
It appears to be more sinister than just a plotting problem of the indicator, but I could be wrong. It would have been nice if there were a seamless way to migrate 6.5 indy's over to 7.0
I've attached some screenshots illustrating the MACDBBLines problem, when scrolling back several days.
After all, it's what you learn AFTER you know it all, that counts!
This is because when the bar went low there was a red segment drawn. When the bar went up and the green segment was plotted the red did not disappear for the reasons I stated in a previous post. You now need to test for conditions and reset the plot if the condition stops existing and you no longer need the plot. I don't know what is going on with TheWizards charts.
This is not big problem. It can easily removed by increasing look back period. Bydefault 256 bars look period in Ninja 7 indicators. If changed this to infinite, then problem gone and MacdBB working fine.