It's not a question of CPU capacity, but of how to create the loop. I tried that on my shared project, but to no avail so far. Should the loop be positioned under the 'For each trade' block or above? I guess it should be below, so that open proces should be scanned case by case. However, mi initial configuration doesn't do that and I don't know why. 
If those SL are wrong then MS Excel is wrong because I got them there. 
Can you please tell me which one is the wrong one?
Yes, they are static from there on, but if I have three open traedes at the same time, there will be three different open prices to be considered on the same tick. This means that those numbers (0.04493 and 0.01123) are to be changed three times on the same tick. So I need three different static values. That is the problem.
@leonardo-1 said in HELP REALLY NEED WITH MT5 EA:
Just one more request if you may,may you please compile it for me,I have the basic version of fxdreema so I'm not able to compole it.Thank you very much
Really, man...:(
@roar said in HELP REALLY NEED WITH MT5 EA:
I'm curious about those 'Set current timeframe blocks'. If I understand it correctly, the one on top makes all those below it to work on TF M5 until those with number 3 and 11. Then all blocks below them will work on TF H4. Right?
If so, why not just using 'Once per bar' blocks with those same specified TF instead?
@juan-manuel-quiñonero said in The clock seconds do not count well.:
://fxdreema.com/shared/EG6Sy6uRd
What's the problem exactly? BTW, the first pass block on the 'On Tick' tab is not necessary.
Ok, I will detail a concrete example.
Initial conditions: TS trigger every 4% and TS step at 1% of open price. Both percentages are input parameters, so they can different every time the EA is run.
Sell trade at 1.12320
This means that 1.12320 x (4/100) = 0.04493. So when price hits the following levels:
a) 1.12320 - (0.04493 x 1) = 1.07827
b) 1.12320 - (0.04493 x 2) = 1.03334
c) 1.12320 - (0.04493 x 3) = 0.98842
d) 1.12320 - (0.04493 x 4) = 0.94349
e) ...and so on the TS is to be moved.
SL is moved according to the input parameter: 1.12320 x (1/100) = 0.01123. This means it is moved to the following price levels:
a) 1.12320 - (0.01123 x 1) = 1.07827
b) 1.12320 - (0.01123 x 2) = 1.03334
c) 1.12320 - (0.01123 x 3) = 0.98842
d) 1.12320 - (0.01123 x 4) = 0.94349
e) ...and so on.
And this is to be calculated for all open trades (up to 10 open trades at the same time).
I hope it is more clear now.
@roar said in Help on Trailing stop block appreciated:
@l-andorrà I have a feeling this is unnecessarily complicated approach
Why doesn't "% of profit" work as a solution?
What do you mean by "11% of open price", isn't that like EURUSD crashes to 0.1234 ?
That option doesn't work because that % is static on the block (something I want) but is linking the current price to the open price (something i do NOT want). Is that same option was available for the current SL level instead of the open price that would do the trick. Additionally it is calculated as money (profit), and not pips or price level. Why transforming the initial % into money first and then put them here? Double effort worthless, I'm afraid.
On the other hand, when I say '% of open price' I mean exactly that, an percentage applied to the open price that is added (for buys) or substracted (for sells) in order to get the trigger for the TS to move up/down to the trail step.
We'll be more than happy to help you. If you want to share your strategy we can lead you path to the right direction! 
@roar said in Help needed in modifying values in a sequence:
I guess that 'loses -2' text is the reason for that failure. I'm not sure, though. I would say this is not the correct way to write that variable there.
It is not the default way, but actually that works fine
Once more I learnt something new! 
Thank you.
@josecortesllobat Your suggestion is apparently very close to what I need. However, I see two problems. The first one is this formula
TrailStepPips = PipsToMoveStopLoss x TrailStepPercent = 1100 x (4/100) = 44
If you read my first post, the trailing step is a % of the ope price too. This means the formula should be:
TrailStepPips = OpenPrice x TrailStepPercent = 1.00000 x (4/100) = 0.04.
Then I don't understand the following one:
TrailStopLevel = StopLossLevel + TrailStepPips (as a price fraction). Is StopLossLevel the initial SL? And how TrailStepPips (as a price fraction) is affected by the new result 0.04?
The second problem is your loop. Those calculations before the 'For each trade' block will not be updated for all open trades, but on a tick on tick basis. If I have 3 open trades, all of them will have to have their specific TrailStopLevel value, for example. In your structure, if I understand it correctly, that cannot happen as those calculations will be applied before eavary trade is searched for.
@trader-philipps I tried as per your first post above and I confirm it doesn't work. For a reason I don't understand the stop moves before hitting the first level. Let me show my last backtest example. I tried GBPJPY qith a 4% trailing stop and a 1% trailing step.
The open price for a buy was 131.094. This means that:
a) Trailing stop = 131.094 x 1.04 = 136.338.
b) Once the previous price is hit the trailing step should move the stop to: 131.094 x 1.01 = 132.405.
Well, because of weird calculation made by the block, the stop moved when price reached 135.300, far before it should.
On your second suggestion, yes, I need static values. The problem is finding the equivalent of pips or price levels from the initial percentages and then 'translate' them into the trailing stop block.
I guess that 'loses -2' text is the reason for that failure. I'm not sure, though. I would say this is not the correct way to write that variable there.
Do not use any candle info on the left operand. Instead use Maket properties > Ask or Bid.
Six months is a too shot period to back test. Try at least 5 years and then we can begin to thing you found something. Please don't get me wrong. This is not a criticism, just my own experience. Believe me, I found tens of good systems that were great for a very shot time and then they destroyed the balance.
Thank you to both of you. Let me study your suggestions in detail and I will be back with my results.
Just curious. Is this grid defined by candle IDs in 'Time 1' and 'Time 2' operands?
I'm afraid I don't fully understand. The distance between a pending order price and what else?
I know bitcoin payment confirmations are slower than mainstream ones. Please contact the admin via the support page if you see no confirmation soon.
Do you mean the 'Constants' (input paraneters) or the 'Variables'? And which of them exactly?
