Posts made by trader.philipps

@marianomartinez In order to avoid unnecessary calculations you should put it as early as possible.

@everjn17 Okay, did a quick test on width of x>. I draw a line on candle ID:1 if condition is true.

Here the results:

Condition with width=2 for Closing Price x> Indicator value this means:

1. Condition valid if there was a cross-over and closing price was above indicator.

2. Condition stays valid if candle after closes still above indicator value.

3. If candle after cross candle closes below the indicator, the condition is not valid

So, I think that is exactly what you need, right?

@scottpapetti Well, first you need to be set with EA and settings. I don't see this, yet. Than you should do some long term back-tests over several years. If that is done you may think about forward testing on demo. And then sometimes use it on real account.

MT4 backtesting is not very reliable. I have tickdata from TDS2 which gives 90% quality, but it really depends how the EA works. With your EA I have some concerns about the different timeframes you use. M1 for exiting, M15 for most of the other stuff. Btw. what timeframe you intended it to run on? I chose M15 as most of the indicators use it.

Further I think you need to tweak the logic a bit. On flat market when EMAs are very close to each other trades get opened and closed directly after it.

Maybe you should include the opposite of your exit condition also as an entry condition?!

@scottpapetti Well, the signals I checked were all fine. All conditiones met by visual checking.
Do you have an example were it doesn't "listen" to you?

I did the ID change an also changed the Once per bar to the start of the flow.

Just for testing purposes I eleminated the AND block and lined all the conditions after each other. But results appear to be the same. Hence the AND block is not the issue.

Changed version

@scottpapetti May you share the indicator, please? I might take a look.

@l-andorrà Have eagle ears

@gsmtricks I think so.

@zooslinkis Getting better. You might think about a minimum distance between the lines maybe, Just saw this occurance in tester.

It seems like both lines have same price value.

@gsmtricks @miro1360 said that you have to compile in meta editor not in fxdreema.
So save your mq5 file to experts folder of your terminal and open it with metaedior (eg. refresh experts list and right click on your ea name and choose modify).
In Metaeditor press compule button and watch for errors on the bottom.

@scottpapetti Nice thread title .. Maybe you have to shout at it

One thing you may change is the candle IDs. You run your entry calculations once per bar (block). This candle usually just opened in the time the code is running and may not deliver reliable values.
Instead use candle ID1 where you use candle ID0 and shift all other occurances as well by 1.
For block 12 and following you might leave the ID0.

The trailing stop of 5000 pips is for securiry reasons only? Or do your trade non-forex symbols?

The rest looks fine assuming that the custom indicators you use do not repaint.

@zooslinkis Okay, understand. So I'd still say change for conditions block. And maybe share a version that is close to what you have right now. It's easier to work with.
Besides the blocks 15 and 27 I can't see a reason (yet) why once per par shouldn't work.

@everjn17 NNFX in da house :)) I can try to help you, but your project is a bit large to just overview it. Maybe we go one issue by another?

First you use candle ID 0 for the indicator checks. As indicators usually repaint on current candle, you may consider better to use candle ID:1 - btw. that i sthe definition by vp. Price has to close above / below baseline!

For the cross issue and the 1 candle after .. For instance on block KIJUN (593) you may specifiy the width to 2. That means the cross may have happen on the candle that is specified in the field candle ID or +1 candle.
In your case as candle ID is set to 0, the cross might have happened on candle ID 0 or 1.

Does that make sense?

@gsmtricks said in How to include library?:

data

Did you apply your test json to the data variable for testing?

@zooslinkis Okay, got you. So you intend always to open 2 orders? It's a bid confusing your project.
I understand that the upline and downline are calculated when a buy signal (arrow up) occurs.

From block numbering you let first open buy (4) and sell (5) order and after that calculate the upline (9) and draw the line to the chart (10). After that you do the same for the downline (8, 11).
If you get a down arrow close all trades from group 1 and 2 ?!?

So far so good.
The 15 and 27 blocks I don't really understand. What is Price Level 1 and Price Level 2 of your lines? I'd use a condition block if you intend to do what I think.

However, as you don't use SL and have moving targets for SL in particular, as it's recalculated probably each bar again, there might be a chance that you miss it when downline moved farer up and for EA there is no cross.
Further it looks like that for instance if upperline is broken, trade is closed immediately when there is a small pullback to the line. As you work on per tick level, there is a high chance that this will happen as prices moves up and down during a candle usually.

In short: I'd replace 15 and 27 with a condition block. Think about exits and redraw of downline.

@zooslinkis The indicator actually no need with fxdreema. You can do so with 1 Condotion block per direction and if you need the arrows a draw arrow block.
However, in blocks 15 and 27 you refer chart objects. Where do they come from? Do you draw them manually?

@michael-0 I have absolutely no experience with binary options as I believe it's not trading but gambling. However, I checked the MT2trading feature list and it seems to have a filter called "Minimum Payout Filter". So I'd expect that MT4 gives all the signals it generates to MT2trading and the Payout Filter will take only the "good" ones. Or am I totally wrong?

@gabrielebrignoli I think it would help if you could share your indicator in order to understand how the signals work. You probably need to find a way to identify the moment when it changes from no trade zone to trade zone. Then you'd only open a trade if that change condition is met.

@abubakar On buy trades you want the low before the cross or at the cross (candle) of red and green ma? Could you mark the SL in your screenshot, please?

@sirboyce Well, for MT4 EAs I use TDS2 for testing. There you can specify variable spreads, but they keep consistent if you configure it like that. So you can run your EA on exactly same conditions several times.
But I don't want to advertise here. There are probably other apps around that do a similar or better job.

However, the trade without SL, was that a sell trade? If so, than you should rethink the trailing logic. If spread is 4 pips, you have to make those 4 pips first in order to kick in trailing (as you specified open price). And on the other trades, there you have 5 pips spread which is 1/3 of your trailing step target. I think it's good to test with that high spread as you can see the flaws in the logic (not by fxdreema or MT4) better.

@miro1360 Okay, that's worth a try. Thanks for the information! I always compile in local Metaeditor. So that would be fine for me.