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)
There are still some questions arround the ADXVMA included in .zip-files of new indicator-versions.
Here are to postings about this from the ninja-forum :
ok folks,
here is a fixed ADXVMA in the way it is written in the postings from ninja-forum - see above.
make tests and if its the "good" one -- please also change it in your further DMA.zips etc.
max-td
**file deleted for a while **
>> up again -- at your own risk -- should work ok! <<
Please report if not !!
Also, I think the ADXVMA=1 issue can still be solved (when inside DMA) by setting COBC to false, instead of leaving it unstated. I do not know the reasons as to why, but that is the difference between the "old" ADXVMA and the "new" one.
Hey Mike, I just tried again as this one has the rev. info in it.
I don't know why but it still gives problems when in my DMAPaint at ADXVMA1. No flatline at top but one long ADXVMA line through middle.
I hope it is just for me.
But in case anyone else has that problem, the one I use at the moment is the one from inside JMAPaint. Just import the zip and only accept ADXVMA.
The COBC is different but that is not the problem. As mentioned before my good ADXVMA gets problematic by just opening the indicator editor and then compiling (without any changes).
I just compared your ADXVMA with my good ADXVMA. Next to the COBC and version stuff I found a difference in the NT generated code.
It is the same difference that I also find (as only difference) after opening and closing my good ADXVMA that turns bad after opening&recompiling.
To be sure I replicated it again as follows:
I loaded again the good ADXVMA via ZIP from JPaint (and copied it to my desktop... it is the version in right top in the pic) and I checked that it worked with ADXVMA at 1 in the DMA.
I then opened this working ADXVMA indicator with the editor and closed without editing .... again I got a flatlline. I then opened this recompiled ADCVMA file in DiffDoc (left top of panel)
DiffDoc found a difference in the NT generated code. It is the only difference it found.
To me it looks again that NT itself is the culprit.