@roar said in Restricting optimization of parameters to matching values:

@tonyramirez If you want matching values, use the same constant for both MAs

In case constants are new to you, you can declare them in Constants (Inputs) menu and then insert to any field by right-clicking

Thanks for that! Until now I hadn't got round to using variable and constants.

Hi, I've designed a simple project to test Check Profit (Average). So far it seems to be closing positions correctly when total profit is n pips as specified...but also when profit reaches -n pips!

I'll play around with it some more to see if my logic is flawed or it's a bug.

I haven't been able to get this to work 'as advertised'. More importantly I haven't found an alternative that would work for you. I'm going to post the problem to see if anyone can find a flaw in my logic. Otherwise it's a bug.

Thats a fairly complex project. I think if you share just the relevant section, you'll have more chance of getting feedback.

Must have been temporary server error. Now magically it's fine.

Don't know what I'm doing wrong. When I import a custom indicator, the input parameters and buffers are imported but when I click update, the values are not added to the block.

Thats a fairly complex project. I think if you share just the relevant section, you'll have more chance of getting feedback.

It's working properly now I think. I've attached the working version. For visual clarity it buys a maximum 2 positions and waits 5 bars after buying one position before opening another.

Note, for it to work the way you wanted, you have to change the default settings on the Check profit (unrealized) block as shown in the picture.

https://fxdreema.com/shared/9Fge6c36e

@roar said in Check profit (average) and check profit (unrealised) not working? (MT5):

@tonyramirez your EA has an SL of 50 pips, thats closing the trade. Not the profit checking block.

Thanks for checking it. That default 50 pip stop/TP has caught me out more than once!!

I will test again to make sure there no bug.

UPDATE *** There is no bug, this was my error. I forgot the buy and sell blocks have a default SL and TP of 50 pips. Warning to everyone - this can really catch you out!

I have tried both and while the blocks pass when the profit target n pips/$ is met, they also pass for -n!.

Below is a simple project to test this. To make it easier to visualise the results, I only allowed one trade at a time, which should still work.

https://fxdreema.com/shared/PqMeukc4b

Yes, I see that.

Since nobody has given any explanation for the -n result I'm reporting this as yet another bug.

@l-andorrà said in auto tp:

@tonyramirez You inserted a link to your thread asking for help here.

It's completely normal and efficient to post relevant links from one post in another!

You're having the problem because your trades are executing once every tick. Insert the once per candle or once per n candles block in your project. I also recommend you read the how to and instructions sections before attempting to create any projects.

I'm not sure I understand your questions.

1. Highs and lows are not absolute, they are always relative to something. If you were trying to find a relative high for an oscillator you could create 2 condition blocks where the first checks to see if the RSI 2 candles ago was less than 1 candle ago, and then another condition to check if the RSI 1 candle ago was was greater than at the current candle. That would detect a relative high in the RSI I think.

2. Currently with Fxdreema you need to import a custom indicator if you want one indicator to use another indicator's data. I haven't looked into how to do this. My coding abilities in MT5 are almost non-existent.