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 checked just now. The difference is that version has CalculateOnBarClose forced to true, where my version has no setting.
When you try your ADXVMA 1 setting, are you using COBC true or false within DoubleMA?
The proper way is to not force the COBC setting inside of the ADXVMA.cs, which is the method mine uses. I will have to explore more, but please tell me if you are using DMA setting of COBC true or false.
Mike I was updating my 2nd PC. Did the advised procedure of ChannelThis, delete, etc. and installed the new package.
After editing my local ADXVMA to pricesupported is true .... I got flatlines with ADXVMA=1 (both with DMA and DMAPaintbar in both COBC true and false) while being not connected.
- put the pricesupported code in ADXVMA back on false and restarted NT -> flatline
Overwriting with JayMAPaintbar solved the problem as mentioned above.
In the following tests I started everytime with a working ADXVMA=1 by overwriting with the ADXVMA in JayPaintbar
- changed ADXVMA code to COBC false -> flatline
- commented the whole COBC line out -> flatline
Now the interesting one....
1. overwriting with the JayPaint ADXVMA -> no flatline
2. opened ADXVMA with the editor and compiled without any changes -> flatline
3. load new ADXVMA from JayPaint -> no flatline
Looks more and more to me that it is an NT bug.
BTW I am on NT .10
Will see toninght what happens while being connected to data.
BTW, looks like we might need another 'new' package with COBC forced to false on ADXVMA to fix this. NT advises the indicators to not force a COBC either way, which is what I did... but you guys are still experiencing issues.... so we can just force it back to false.
It may not be clear from my text but I tried editing COBC to =false ... it did not work for me.
NT needed a newADXVMA to work.
As mentioned:
I started with a good/new ADXVMA from JayPaint and a chart without flatline. Then I did a 'strange' test.
I opened the ADXVMA indicator as if I wanted to edit, but I compiled directly after opening without making any changes (so I did not tough COBC=false). This open/compile only action resulted in a flatline.
If the value would have been cached, then the cached value should have been false.... but still I got the flatline.
That is why it doesn't make sense to me.
What is different after open/compile without any editing?
he peter you take the old version of adxvma (the first one without changes) with the recompiling you clear out ... and good is. i had the same problem for two weeks ... then i take my first version of adxvma
all runs fine at the moment with the JayPaint ADXVMA. Probably it would also run fine with the 'very old' ADXVMA. Didn't test that yet, but I've had it with testing for the moment.
I don't really have a problem at the moment.... with DMAPaint anyway..., , but I wrote the info above down to inform others on what I found.
And confirm a way to solve the ADXVMA issue.
The thing that bugs me is that I can't explain it....
I downloaded the latestest version of MA Paint and i am having problem with ADXVMA when I used setting with 1 I am getting a st horizontal line when changed to value 2 it is working
Any suggestion what to do because there is huge difference with ADXVMA value 1 and 2
Open the file, add the line under the Initialize section:
CalculateOnBarClose = false;
Save/Compile. Remove the indicator from your chart. Exit Ninja. Re-open Ninja. Re-add indicator to your chart. (extra steps due to reported bug by Peter).
, , but I wrote the info above down to inform others on what I found.