Auto Fib Retracement makes Chart Trader unusable!

[catinabag]

Hello there!

I put an auto Fib retracement drawing in an indicator that resets based on time of day. Well, it totally makes the screen gum up with jagged mouse movements.

Even if I put the calculation on "Bar Close" it still freezes things!

I have had a lot of trouble with Fib retracements on NT. Does this mean I should autodraw horizontal lines instead? Is there some extremely difficult custom-rendering solution that is really the only way to address this otherwise?

Please let me know! Thank you!

[NinjaTrader_Gaby]

Hello catinabag,

Thank you for your post.

Are you using a large amount drawing objects in your script? This could cause performance issues.

I am not seeing any performance issues with a simple Draw.FibonacciRetracements() call in an indicator script.

If your script is going to be utilizing a large amount of drawing objects, it may be more resource efficient to instead use custom rendering to improve performance.

Help Guide: NinjaScript > Educational Resources > Using SharpDX for Custom Rendering

SampleCustomRender included in NinjaTrader 8 demonstrates custom rendering from an indicator.

Please let me know if this doesn't guide you in the right direction.

[catinabag]

Thanks for getting back so quickly, Gaby!

I'm using this line in the code:
Draw.FibonacciRetracements(this, "Fibonacci", false, fibstart[0], fiblow[0], fibstart[0] + 1, fibhigh[0], false, "Template2");

where fibstart is defined as the bar number at 9:30AM Eastern time and the fiblow and fibhigh are static numbers from 9:30AM, also.

Thus, I think that's just 1 drawing object!

Nevertheless, it still gets gummy and jittery.

I will read up on the custom rendering, I suppose that's really the only solution other than hand drawing this!

If you have any further thoughts, please feel free to mention them. Thank you!

[NinjaTrader_Gaby]

Hello catinabag,

I wouldn't expect just 1 drawing object to cause this behavior.

I would text first by removing the Draw() method call and testing if the behavior persists. It would help to narrow down which section of the code is could be causing this behavior.