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'm trying to work through a bug using eMini-Watch Better Momentum.
I've been using eMini-Watch Better Momentum, Sine Wave, and ProAm for a couple years now on Tradestation 9.1 update 29 with no problems. I also created custom indicators that do exactly what the indicators do except I have more control with alerts, printing and such. These custom indicators just access the functions behind the canned indicators so they work in exactly the same way.
Now the problem... I upgraded to TS 9.5 U11 on another PC and restored a backup or 9.1 to it. While verifying everything works I noticed the Better Momentum indicator doesn't look right. On 9.1 everything works exactly as it should between the canned and my custom indicators. On 9.5 only Better Momentum is off. It seems that the functions are returning the same value for all for all of the signals. Interestingly, the canned indicators all work correctly on 9.5 which is why this has me puzzled. I'm trying to figure out the difference between calling the functions vs. using the canned indicators. If anyone has run into this situation I'd appreciate it if you could let me know.
Below is a piece of test code that shows the problem on 9.5. I've replaced my software code with <YOUR CODE> so if you have the indicators just pop in your code from emini-watch.
{********************************************************************
{SETTINGS:
Max num bars study will reference - Auto
Update value intrabar - No
Load additional data for accumulative calc - None
Alerts on/off - off}
*******************************************************************************}
//print the codes
If vPrintDebug then print(Bardatetime.Value, " | Print the BM Signals ***");
If vPrintDebug then print(Bardatetime.Value, " | vMom ",vMom );
If vPrintDebug then print(Bardatetime.Value, " | vFirstDiv ",vFirstDiv );
If vPrintDebug then print(Bardatetime.Value, " | vDiv ",vDiv );
If vPrintDebug then print(Bardatetime.Value, " | vExh ",vExh );
If vPrintDebug then print(Bardatetime.Value, " | vExhPrev ",vExhPrev );
If vPrintDebug then print(Bardatetime.Value, " | vFlush ",vFlush );
If vPrintDebug then print(Bardatetime.Value, " | vPSE ",vPSE );
Plot1(last);
Can you help answer these questions from other members on NexusFi?
Sorry missed that in my post. Yes I emailed him 3-4 times with no response. I found another user who experienced the same problem on the TS forum but want to cast a wider net and see if any one else can replicate the problem and maybe find out if there is any new info about this.
Thanks for testing the code ChrisTinaBruce.
So if you view the printlog you'll see the problem. Check out the annotated image attached
He still hasn't addressed this problem.
I would be happy to help. My system is still working as usual. I tried to find the print log and could not. I even opened Easy Language and still could not see where to open print log to help.