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 answer and asking the clarifying question by "what do I mean". Well, at first I meant (and still do) what is the math behind the indicator? I'm very analytical by nature, a math graduate at one time long ago, a programmer after that, etc. Any indicator I use I make sure I understand what it is doing, why and if possible I then tune it.
However as soon as you say it works great for you, you pique my curiosity. Would you share with me (I won't tell anyone else :-) how it works great for you?
Thanks for any answers.
Can you help answer these questions from other members on NexusFi?
Let me know if you can import this. I got rid of the RSqueezeUtility Namespace that may have been causing the problems. I don't know why that was in there at all.
I also got rid of a lot of ridiculous plot switcheroo code that was being used to change the colors of plots à la Ninjatrader 6.5 because somebody did not know how to use the PlotColors method.
I further optimized it by eliminating any usage of external instances of several indicators that are now calculated inside the OnBarUpdate() method.
If you can manage to import this, you may be shocked at how quickly it loads.
Hi. Thank you. It loads fine. I just noticed if you draw the BB and KB bands with default settings ((as in your squeeze indicator), the squeeze areas on chart do not match the squeeze dots on indicator's zero line. I know you mentioned no support, but Just an observation.
Alligator " noticed if you draw the BB and KB bands with default settings ((as in your squeeze indicator), the squeeze areas on chart do not match the squeeze dots on indicator's zero line."
Yeah, I noticed that the dots are not correct in the BBSqueeze mode.
However overall it does seem to give decent signals.
I don't know where the version that I optimized came from. I do know that it was a resource hog because of the way it was coded. My version uses a small fraction of the CPU resources of the original, and will work fine on COBC false.
The code for this indicator is in a dll, so you won't find it in your Indicators folder.
the code from the edit ninjascript drop down to see If I could figure that out. I could not find the code for the optimized version. The display with the same settings is quite different from the "original".
that the pbfsqueeze displayed on my charts is repainting. Is anyone else aware of how/why this could occur. It looks like the price bars are a little different as well. I called the broker and of course it is a NT issue. I emailed NT and of course I am waiting.
changed to
price bars look different just before 10:00 and the green/pink dots seem to have repainted.
@wldman: If you add a free copy of a commercial indicator to your chart and this indicator has coding errors, then you can neither blame your broker nor NinjaTrader.
The RSqueeze has been coded for NT 6.5, and the author has left it with a minor bug, which only occurs, if you set the indicator to CalculateOnBarClose = false. In CalculateOnBarClose = true the indicator works without problems.
That said,
-> The indicator does not repaint - repainting means changing values of prior bars after the fact.
-> It calculates all values in real-time correctly. The author has used two DataSeries to differentiate between the colors, and for those bars that change color intra-bar, he simply forgot to remove the inactive color (bug).
The issue can be easily fixed. But I am currently fixing something different, so I won't fix it today.