Just to be sure... the script I provided, did you change the parameters in icustom to match the input parameters for the indicator? I notice that the parameters in the version of laguerre are different from the one I just down loaded from codebase.
I'm going to have to defer I'm afraid, I had a look at it and loaded it up, It may have something to do with referencing bar i for a different time frame, but I'm not that good with indicators so don't really know how you get around that. Hopefully someone more experienced will be along in a minute.
I'm going to have to defer I'm afraid, I had a look at it and loaded it up, It may have something to do with referencing bar i for a different time frame, but I'm not that good with indicators so don't really know how you get around that. Hopefully someone more experienced will be along in a minute.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
I repeat to keep things clear, The problem appears only when i call Laguerre value from H1.
otherwise without the RED line it works like a charm.
And your red line in OP has two parameters missing... have you changed that?
Just to be sure... the script I provided, did you change the parameters in icustom to match the input parameters for the indicator? I notice that the parameters in the version of laguerre are different from the one I just down loaded from codebase.
So does this still give the wrong result?
this one is OK
And your red line in OP has two parameters missing... have you changed that?
check this out it should never give such signals H1 was above 0.75:
I'm going to have to defer I'm afraid, I had a look at it and loaded it up, It may have something to do with referencing bar i for a different time frame, but I'm not that good with indicators so don't really know how you get around that. Hopefully someone more experienced will be along in a minute.
Sorry I couldn't help
V
I'm going to have to defer I'm afraid, I had a look at it and loaded it up, It may have something to do with referencing bar i for a different time frame, but I'm not that good with indicators so don't really know how you get around that. Hopefully someone more experienced will be along in a minute.
Sorry I couldn't help
V
thanx for trying
Calling an iCustom on a period higher than the current requires a few things :
- Storing the higher period values with the original shift to a buffer
- creating a 'transposed' shift from the higher TF to the smaller one; using Time[i] & iBarShift
- filling the values to another buffer with the 'transposed' shift
- .... then you can do a valid comparison.
hth