Elite indicators :) - page 950

Mladen Rakic
151617
Mladen Rakic  
Jaspersky:
Thank you for your fast reply, much appreciated ! I'm wondering if we have a version of uni cross that doesn't repaint ? Any suggestion ?

Jaspersky

Since that is a cross of two averages more or less, why not using cross of averages, for example?

I do not remember where the original request to combine centered TMA and T3 came, but if we leave out the centered TMA, oma (one more average) can simulate almost all other averages, so maybe you could use this one : https://www.mql5.com/en/forum/179662/page12 (with some "speed" combinations you could reach results very close to the uni cross indicator - just as a reminder : oma speed 2.5 is roughly equal to T3)

Fadi Feghali
12
Fadi Feghali  

Will do ! Thank you for your help ! have a good one

Mladen Rakic
151617
Mladen Rakic  

Sometimes it takes years ...

________________________

Today was checking some things in order to make some decisions about which average is "adaptable" and which is not, and noticed in the code of zero lag ma one strange thing. Not a big deal (that was a first thought) but then started checking and it turned out that it is a big deal.

In short : all the zero lag moving averages that are cruising around are biased towards even periods. What does it mean? For example : period 22 is "faster" than period 21, period 20 is "faster" than period 19, and so on and so on... It can easily be checked with comparison of existing zero lag emas on chart. The difference in "speed" can be significant. Checked also some independent (not coded by me) tradestation and metastock versions and all have that same error that I have inherited too

________________________

So, this one is the correct version that corrects that logic calculation error. It now behaves as any moving average should behave. Also, added to this version immediately multi time frame, alerts and % filter : zerolag_ma_nrp_amp_mtf__alerts_nmc.mq4

timmyhanke
541
timmyhanke  

Hi again ! and thanks for the trinity inpulse indicator that you added alerts on , the indicator is interesting and i got a very positive results from using it this past 2 days .

Is there any way possible to add 17-20 averages , and maby add the price options to it ( open,closed and so on )

Because i see that the indicator are using Lwma to calculate and has the price to price weighed.

Thanks again !

trinity-impulse-indicator_2.mq4

William Snyder
9496
William Snyder  
timmyhanke:
Hi again ! and thanks for the trinity inpulse indicator that you added alerts on , the indicator is interesting and i got a very positive results from using it this past 2 days .

Is there any way possible to add 17-20 averages , and maby add the price options to it ( open,closed and so on )

Because i see that the indicator are using Lwma to calculate and has the price to price weighed.

Thanks again !

trinity-impulse-indicator_2.mq4

Hi Timmyhanke, the indicator is using the built in mt4 Cci and the Force indicator, so made a version using Force of averages and added price options.

Mladen Rakic
151617
Mladen Rakic  

ZeroLag MACD using the new (correct) zero lag ema for macd calculation : zerolag_macd.mq4

Files:
timmyhanke
541
timmyhanke  

Can you add alerts to this indicator if its not a repainting one .

Yellow line over red line = buy

Red line over yellow line = sell

Thanks !

bttrendtrigger-indicator.mq4

Mladen Rakic
151617
Mladen Rakic  
timmyhanke:
Can you add alerts to this indicator if its not a repainting one .

Yellow line over red line = buy

Red line over yellow line = sell

Thanks !

bttrendtrigger-indicator.mq4

timmyhanke

Actually that version repaints

This one (for example) does not repaint : https://www.forex-tsd.com/forum/debates-discussions/116-something-interesting-please-post-here/page148#comment_545444

Or you can test this one (before adding alerts to any of the non repainting versions) : https://www.mql5.com/en/forum/general

timmyhanke
541
timmyhanke  
mladen:
timmyhanke

Actually that version repaints

This one (for example) does not repaint : https://www.forex-tsd.com/forum/debates-discussions/116-something-interesting-please-post-here/page148#comment_545444

Or you can test this one (before adding alerts to any of the non repainting versions) : https://www.mql5.com/en/forum/general

but if you change the:

ppor=1

mpor= 1

then the red line changes to a straight line , it seems very promesing if it trigger above and below the 0 line , i know that rsi have the same thing but i dont like that one .

Mladen Rakic
151617
Mladen Rakic  
timmyhanke:
but if you change the:

ppor=1

mpor= 1

then the red line changes to a straight line , it seems very promesing if it trigger above and below the 0 line , i know that rsi have the same thing but i dont like that one .

timmyhanke

It does not matter what values you use for ppor and mpor. They are not causing the problem.

The problem with that indicator is that it uses TTFbars future bars (and that is one of the causes for repainting - it does almost the same thing as super signal indicator). The other cause is in t3 calculation that inherits wrong data on new ticks and, after some time, the indicator does not "know" which data belong to which part of calculation.

When that usage of future bars is removed and when the T3 calculation is corrected, then it is exactly the same as "ttf new" indicator