@abubakar I don't think fxdreema was designed to do so. However, if you have the source code of the indicator, you might use custom mql blocks to adopt some of the indicator's logic. But I wouldn't recommand doing so.
As an alternative you might check the integrated indicators in order to fit to your requirements.
@sirboyce Well, trailing is always a compromise as you will never hit the maximum possible profit.
However, as market conditions are changing you may want to give the trade more room to develop on volatile times and get tighter room on flat markets. I like to use ATR as a dynamic trailing approach.
On the other hand you may instead of trailing the entire position scale out the trade by partly closure.
Just keep in mind that doing so may interfere with your risk reward goals!
@cesardefez Does a buffer get a value if an arrow is drawn? In that case you may loop back and use indicator is visible block.
@markforysuccend Use the Trades count block.
@ambrogio Nevermind. The dropbox link contained the source code of the indicator.
@markforysuccend fxdreema comes with an integrated HA indicator. This you may use (haven't tested) like this
With your custom indicator it depends on the indicator itself. If you may upload it we might have a look.
@marianomartinez Is this a negative condition? If Bid > PSAR don't open trade? That may work for the current tick, but it doesn't mean it will be valid for the time when your order is filled.
Maybe better to have a max spread condition and avoid opening of trades if speads are to wide?!
@ambrogio said in NON GRAPHICAL buffers:
@trader-philipps said in NON GRAPHICAL buffers:
@gizmosz As you have the source code of the indicator it's easy.
Just create a file "OBV_vs_MA.mq4" in your indicator folder.
Now you ccan import it to fxdreema.@trader-philipps Please, could you kindly explain your response "Just create a "OBV_vs_MA.mq4" file"?
Thanks in advance
@ambrogio It's okay if @l-andorrà answers as long as it's correct.
I meant that you take the source code of from the txt file and put it to a text file with the ending .mq4
That file you could place in the indicator folder and you may open it in MetaEditor.
However, when you have a mq4 file, you can easily import it to fxdreema and it will recognize the available buffers.
With your indicator there might be an issue with the enum constant regarding MA method to use. I was not able to work around that even in MetaEditor. It really just seems to not work on tester and calculates only constants to the buffers per candle for whatever reason.
@sirboyce I think with only trailing block to achieve what you want is if trailing start and trailing distance are equal.
@gizmosz I took a look at it yesterday and it seems that on tester the indicator doesn't work. The values appear to be static. I haven't tried to debug it but it looks like the ma has an issue for some reason.
@marianomartinez I think the 9nly way to guarantee a maximum price for a trade is a limit order.
There will always be spread and/or slippage that will interfere hitting the desired price.
@thatashtonkid-0 It would help if you share your project and maybe indicator here to have a detailed answer for you.
However, there are 2 alternative solutions that I see, but both of them are not the 100% solution.
Alternative 1: Work with "No trade" or "If trade" blocks and specify buy or sell depending on your condition tree. Like this you could avoid having multiple trades opened in the same direction. Disadvantage, If one of the trades get closed for whatever reason, there might be a new trade on next signal in same direction of the closed trade.
Alternative 2: Use "Turn on" and "Turn off" blocks. So for instance once a buy signal was opened, you place a turn on block that turns on sell signals and another one that turns off buy block (usually you take the starting block). You do the same for Sell trades vice versa. Like this you ensure that a buy sell will only be opened after a the next sell trade. However, it might happen, that there is no sell signal after a buy signal for instance and in that case you might skip the next buy signal.
Does that help?
@l-andorrà said in NON GRAPHICAL buffers:
This is new to me. I never saw that. Could you please tell me where that window is on MT4?
Press <Ctrl>-D
How can you build strategies without?
@gizmosz As you have the source code of the indicator it's easy.
Just create a file "OBV_vs_MA.mq4" in your indicator folder.
Now you ccan import it to fxdreema.
The values of the 2 buffers you can see in the data window of your terminal when moving the mouse on the chart.
@gabrielebrignoli First the Block 211 yellow dot may not be your intention.
If you want to open a trade on each change of the indicator only, you'd have a condition block where you compare indicator value of candle ID2 with candle ID1 for instance.
If buy signal is "0", you'd check if ID2 was "1" and ID1 is "0" .. If it's really binary you could do like ID2 > ID1 for long trades. And vice-versa for short trades ID2 < ID1
Does that make sense?
@everjn17 Here you go. I just took some values - maybe default, don't know.
Kijun: 26 shift 0
KKS: 26, 0.3, 0.3
x> and x< width =2
On crossing there will be a line drawn. If KKS condition also valid, it draws a thumb up or down.
a) Short trade not taken on 2nd as KKS not confirmed
b) No Long signal on 3rd - Don't know why.
c) Long signal on 4th
d) short signal on 24th - not confirmed by KKS
e) short signal on 25th - confirmed by KKS
So the only thing that I have no clue about is that it didn't draw a line on 3rd. Maybe there is a hidden feature we don't know yet, as there was a cross down the candle before or maybe it's a bug!?!
Link to project.
0_1569935546475_cross_width_test.mq4 MQ4
Here are the indicators I used:
0_1569935569327_Kijun-Sen.mq4
0_1569935594811_Kuskus_Starlight.mq4
@everjn17 said in Help me with crossover price vs custom indicator:
Wait wait wait, so what do you mean is Width = 2 meaning the EA will check crossover on Candle +2 and still give a TRUE value for Candle +1 if it still above the baseline?
Okay, example:
Candle ID on condition block all set to 1 (I never use 0 for entry so it's easier for me.)
I can do the test as requested, but maybe need your indicator settings for kuskus and kijun in order to have comparable signals.
@abubakar The exact value of the cross will be hard to get. But as a workaround you may loop back in order to find the candle where cross happened and take the lower value (buy condition) of the emas.