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, too had trouble getting MACDBBlinesV2 to work properly in NT7. Changing the default from "TwoHundredFifty" for Maximum Bars Lookback period to "Infinite" seems to have solved the problem, for me, in NT7. Give it a try.
After all, it's what you learn AFTER you know it all, that counts!
Can you help answer these questions from other members on NexusFi?
Exported using NT Version 7.0.1000.10
This is a fast version of the MACD BB Lines indicator. The MACD settings and the band period, the multiplier for the standard deviation, the dotsize and all colors can be selected.
Different colors can be …
Richard has tuned it a bit, so today I replaced it with an even faster version.
Sometimes it is the draw elements. If it is not, it is something else.
So the procedure is always the same:
Step 1: Try to import the indicator. If the import fails, check the trace file. Often the trace file tells you what to do. If the trace file does not help, then copy old indicator into directory Own Documents -> NinjaTrader 7 -> bin -> Custom -> Indicator. Start NT 7 and edit the indicator. Check for code breaking changes and try to compile. Now it is the compiler messages that will help you.
Using this approach, you can usually convert any NT 6.5 indicator to NT 7.0.
The only problems I have encountered so far are custom plots. ChartControl is not properly documented, so it takes a long time to try to figure out what might have changed. Usually I am giving up at this stage, or I prefer using a different custom plot or coding a new one.
For the MACDBBLines I have scrapped the entire custom plot, because it was unnecessary.
Step 2: The indicator needs to be tested. Even if it works on NT 7.0, it is not sure that it will produce the correct results and work under all circumstances. Again the problem here are custom plots. With the multi-series charting of NT 7.0 a non-equidistant bar spacing has been introduced, and many custom plots cannot cope with that.
Yes the absence of documentation on ChartControl is one of the biggest pains going.
Don't mind it not being supported but even just a list of methods,properties,etc would be nice.
Ditto trying to get hold of BarIndex nos via Mouse Clicks- NT seem to have made this positively difficult to discover- and yet it's the one feature that made me move over from TradeStation.
Anyway that is flogging the old so moving on....
OnStartUp is a definite improvement on initialize - I found my Toggle buttons work but work incorrectly in 6.5 due to the lack of the OnStartUp method.
In NT7 this indicator does not produce the ZERO line colours as predicted. i.e. the crossover of whether the MACD line is above or below the average line and the overall trend is up or down.
Updated version of ZeroLag MACD with some enhanced visual flare, zero line is colored based on whether the MACD line is above or below the average line and the overall trend is up or down.
COMPATIBILITY:
NinjaTrader 6.5: YES
NinjaTrader 7.0: NOT TESTED …
Is anyone else having an NT7 issue with NoGapRangeBars not updating consistently? I loaded the NT7 version last Thursday. Friday's session seemed to work OK, but neither Sunday's nor today's session price bars are updating. I loaded a basic price chart today with no indicators to verify and it only showed prices through Friday's close.
Better Renko and minute bars are fine. If there isn't a known issue, is there anything else I can look at to determine what's going on? thx
so moving on....
