I'm aware of that right now. I'm currently trying some backup procedures on the server, but the system become overloaded and things are happening slowly. Plus, there is a 10 seconds timeout for the compiling requests, so the builder just stops waiting and nothing more happens.

First i will remove that timeout, because unfortunately even if something is fine, metaeditor.exe (which is also the compiler) always starts very slow, with at least 2 seconds delay, which makes all compilations 2+ seconds slow. Very bad, I tried to find a way to resolve this, but no success.

@fxDreema I tested it now and it worked. It was very good.

We all make mistakes 🙂

@fxDreema Thank you so much! It's working now.. all projects there 👍

@ndt113 It's already fixed! the custom indicators load up correctly now, thanks to the admin:simple_smile:

@webstarsfx For Stop-Loss mode first select "Fixed pips" and then load the Constant

ok thank you

Very strange, I see this for the first time. Somehow this appears in the code:

void iCustom() { //---- Read value from trend and signal buffer int start() { // Read values double trend = iCustom(Symbol(), Period(), "PZ_LopezTrend_LICENSENUM", 5, 1); double signal = iCustom(Symbol(), Period(), "PZ_LopezTrend_LICENCESUM", 6, 1); // Do something if(trend == OP_BUY) { /* Your code if trend is currently bullish */ } if(trend == OP_SELL) { /* Your code if trend is currently bearish */ } if(signal == OP_BUY) { /* Your code for bullish trend change */ } if(signal == OP_SELL) { /* Your code for bearish trend change */ } // Exit return(0); } return; }

.. but I don't recognize this code and I can't see how it's injected into the code. Do you have some idea?

Outputs are not defined there. Outputs are defined here with ~next~ and ~inext~ http://i.prntscr.com/925dfd57926e46abb2 ... a47a1e.png

Fixed

MetaQuotes sometimes change their format and older .ex4 files can't work anymore, but now I don't think that this is the problem now. On the server I use compilers that are month or two old and everything works on my MetaTrader build 1012. Note that there are many other people working with fxDreema every day as well. Even the desktop version, which is from 2015 still works for me 😕

But in the "shared" project there are no blocks with such IDs.

You know, you can give IDs that are not numbers. I will suggest exactly this. It is more convenient to control blocks with IDs who have certain meaning instead of some weird numbers. But better use one word IDs, something simple.

I think there is a bug now in MT5. Before, there were only these filling options I believe:

ORDER_FILLING_FOK (which is 0)
ORDER_FILLING_IOC (which is 1)
ORDER_FILLING_RETURN (which is 2)

Now few more appear:

SYMBOL_FILLING_FOK (which is 1, not 0)
SYMBOL_FILLING_IOC (which is 2, not 1

And they wrote a function IsFillingTypeAllowed() to check the allowed filling mode right here: https://www.mql5.com/en/docs/constants/ ... oconstants

But it seems that this function works correctly with SYMBOL_ constants, while ORDER_ appears to be the correct constants when opening positions. I finally found that, made some changes and now I hope that it works.

For .mq4/.mq5 files you need MetaEditor. I believe that when you start MetaTrader, it finds all .mq* files without .ex* and compiles them automatically.
fxDreema outputs .mq* or .ex* files. If you choose to output .ex* file, it is compiled on the server. If you are using the desktop version... I think it uses embedded compiler, which is kinda old now.

Ok. Thanks fxDreema.

The difference between 1.15878 and 1.1548 is 40 pips, pretty large number.

Do you know how this block works? Because it reads the trades, calculates their average lot size and average open price using some formula (imagine that the result is one single position) and sets SL of all trades to a particular level behind that invisible "open price". Of course, each trade is still individual, each one still have its type (Buy or Sell) and depending on the current price you are able to set SL at certain level for some of the trdes, but not for others.

Imagine you have Sell trade that is on profit. You can't put the SL level below the current price.
Imagine you have Buy trade that is on loss. You can't put the SL level above the current price.

When you have mix of Sells and Buys, it depends, some of them might be out of the game.

The price is Bid. Normally on the chart we see candles based on Bid price and indicators based on those candles

Ok, but technically what are you trying to do and it doesn't work?

Use "Close Trades" instead of this "close" block. Also, in those blue blocks there are few filters, so you can make them work only for Buys or only for Sells. Now the problem is most probably that a trade is created and then immediately closed.

I would to close the buy EURUSD and the buy USDCHF when the profit average is positif.
I would to close the sell EURUSD and the sell USDCHF when the profit average is positif.
I must specify the lot and the symbole of each position.