Dynamic zone indicators ... - page 72

New comment
 
mrtools:
Dynamic range mtf with jurik smoothed!

Dynamic double zone range - new mql compatible : dynamic_double_zone_range_nmc.mq4

 
mrtools:
Dynamic double zone stoch kase smoothed, its the bottom indicator in sub windoe.

Dynamic double zone Kase permission stochastic (smoothed version) made new mql compatible : dynamic_double_zone_kase_permission_stochastic_smoothed_nmc.mq4

 

dz kase stoch smoothed

Dynamic double zone stoch kase smoothed, its the bottom indicator in sub windoe.

Updated version posted here : https://www.mql5.com/en/forum/general

 
mladen:
biddick

You are right : a adjustable precision dynamic zone calculation should be used for non-lag ATR (whenever the values are tending towards very small values an adjustable pre3cision must be used otherwise you get those results)

Here is a corrected one (it is the same dll from the first post of this thread, so no need to change or additional download of an dll, just the function that is called is the different one and it has one extra parameter at the end : the required precision of calculation)

regards

Mladen

Correct dynamic double zone nonlag ATR : dynamic_double_zone_non_lag_atr_-_adjusted_nmc.mq4

 

biddick

You are right : a adjustable precision dynamic zone calculation should be used for non-lag ATR (whenever the values are tending towards very small values an adjustable pre3cision must be used otherwise you get those results)

Here is a corrected one (it is the same dll from the first post of this thread, so no need to change or additional download of an dll, just the function that is called is the different one and it has one extra parameter at the end : the required precision of calculation)

regards

Mladen

Updated version posted here : https://www.mql5.com/en/forum/general

 
mrtools:
Dynamic double range on oma on picture jurik range alongside oma range.

Updated version compatible with the new mql : dynamic_double_zone_range_on_oma_nmc.mq4

 
mladen:
odysseus

Sorry

The error in that indicator is purely my mistake and is of the kind that makes me ashamed. Line 149 of the indicator goes like this :
limit=MathMax(Bars-counted_bars,Bars-1);[/php]
and it should go like this :
[php]limit=MathMin(Bars-counted_bars,Bars-1);
So, the only change is to use minimum of the 2 values not the maximum as it stands in the wrong one. The way it was posted it recalculated all the bars all the time. Here is the corrected one (no more CPU killer) But, also while at it decided to make one that uses jurik smooth for smoothing and not the usual moving average (it additionally lightens CPU usage since it avoids one instance of indicator usage) Here is the comparison of the 2 with default parameters :

regards

Mladen

Dynamic zone inverse fisher transform of rsi smoothed made new mql compatible : dynamic_zone_-_inverse_fisher_transform_of_rsi_smoothed_nmc.mq4

 

dz rsx 3 oma - lines 1.01_mtf from here: https://www.mql5.com/en/forum/general made to be compatible with new mt4 builds.

 
Walter Fordham:
Is the indicator available as MTF(multi-timeframe)? dz_rsx_3_oma_-_lines_1.01.mq4

Walter Fordham,

Couldn't find one so made this version.

updated version posted here: https://www.mql5.com/en/forum/general

 

The "regular" version of dynamic zone inverse fisher transform of RSI new mql compatible : dynamic_zone_-_inverse_fisher_transform_of_rsi_nmc.mq4

1...656667686970717273747576777879...159
New comment