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)
Active GeoKing - Triple Auto Swing Indicator for NT8
Yes the download is the latest V1004 but not by that name lol.
Toggle Off/On would be great as is the tiles cover over the "x" on the price axis to cancel pending orders if needs be, but no worries, it's enough already what you've done, thank you. The suggestions are just that, suggestions, if and when or ever or at all.
Many thanks
Can you help answer these questions from other members on NexusFi?
Thanks for the update. Yes, I had used the TrendLineColor somewhere else in the code which also had to be worked out when I removed it, forgot to mention that. It still doesn't make sense why the color was uninitiated in the indicator properties considering that the color was set in the OnStateChange. It should have worked the way you did it. Let's chalk it up in the "forever a mystery" category.
I didn't intend to do any more work on the Indi, but it's good to see folks getting some value out of it so I may do a little here and there.
Folks, as per @zt379 @MrTrader suggestions I have added toggle for the toolbar. This was previously in my NT7 version and always intended to add it at some stage so thanks for the impetus.
See the indicator download section for the updated version v1005.
I think you've nailed a number of VERY relevant/imperative factors to keep
track of before taking a position.. For me the most important part of the decision
is having a clear place to take the possible profit. That isn't this threads
subject.. but your indicator provides that information.
I don't know if any other users are running into this, but as I went about checking
resource usage for GeoKing I found a couple "NullReferenceException"(s) repeating:
Caught exception main GK NQ System.NullReferenceException: Object reference not set to an instance of an object.
at NinjaTrader.NinjaScript.Indicators.ActiveGeoKingV1005.CalcDailyLevels()
at NinjaTrader.NinjaScript.Indicators.ActiveGeoKingV1005.OnBarUpdate()
The WIERD part about it is that they're not showing up in the log ??
Are these due to something I'm not setting up properly perhaps ? I thought I'd
ask before I go messing with the code..
Thanks for your work, and your time answering.. My opinion is that GeoKing is on a very
short list of indicators that plots relevant S/R AND plots useful trendlines between
those values.. I find the fib values useful too..
Thanks for the kind words @Chof , the feedback is really appreciated! @zt379 mentioned the same exception coming up as well. I had never seen it before, although upon investigation I can see that it is the Bars.GetDailyBar() function not having an assigned value.
In reading the refence material at the below link, I can see that this function needs to be checked for initiation.
So, I imagine what is happening here is that you have a chart with less than 4 days loaded, which means that GK cant get the Daily bar 3 days ago to build the daily levels for the 3day balance.
I have upgraded the code on my side to avoid the exception and generate feedback to the output window, but I won't bother providing the updated version yet as the workaround is easy. Load a minimum of 5 days history into the chart if you are on Tick charts and you won't have an issue for now.
Regarding the logs, are you opening an output window to see GK's errors? When I loaded GK on NQ with only 2 days history, I saw the exceptions come up in the output window.
Please report back to confirm the additional days history fixes the issue for now, many thanks in advance.
V1006
Changes:
-Avoid exceptions when less than 4 days history on chart
-127 and 161 Fib extensions were mislabeled (swapped) by name as the default settings.
I set the Data Series to "Bars" rather than "Days" for all my charts (NT8 runs better from experience and other user comments)
Using latest V1006, if I set to "Days" then 3 days and greater I get this in Output Window:
Using less then 3 days (1 or 2 days) I get this:
Similarly if I use "Bars" rather than "Days" in Data Series I get the first image if greater than about 5000 bars on say a 200 tick chart and the second image if using less bars.
Hope this helps and thanks for the latest version.
Yes that fixed my 'Output Panel' errors. I was hoping it was something I didn't
set up properly.. as it was 'freezing' my chart.. I'll quote myself :
"Are these due to something I'm not setting up properly perhaps ? I thought I'd
ask before I go messing with the code.."
To go back to why I went there in the first place, I'm finding that 'GeoKing' burns
a lot of Total time (ms) in the Utilization Monitor.. That's not surprising when
you look at everything it plots and calculates.. Are there any tips you can give
to reduce that number ? I'm afraid this will 'kill' my NT when the volumes crank up.
You know, Mike did a major change to his 'Footprint V2' that stopped any resource
usage by calcs that weren't being plotted/checked off.. I think he did it by changing
how he called for data by each calculation (but I'm not sure).. It was a radical
change to resource use.. I'll probably never run without V2 going forward now.. You
may want to have a look - just saying..
Anyway thanks for the tip and I'll check back for your ideas on reducing the (ms).
The "Found ES" is an old debugging message, its not an error. Ill have to remove that.
The other message is reporting that the daily levels couldn't be pulled. The dailycalcs function isn't written properly, it needs to be updated with a daily data series added, this will improve resource usage significantly aswell.
Updates will fix all this. In the meanwhile, you can search the Print("FoundES!!"); in the code and comment it out. And also just add more bars on the chart until the other message stops will clean up your output window until I update again.
