Topics created by 4xFatigue

It looks ok in the EA. Check if you have correct input values, I can see that you have these levels as input parameters. Also check if CCI on the chart is on Typical Price.

I had few trades on my MT4 and I put that EA to work. CCI is now between -100 and 100 and Nothing happened. I changed timeframes and when I reached M1 (CCI somewhere above 100) I got my two buys closed. So I don't know, I think it worked for me.

It means that it will trade 2 times per bar. Well, it's more accurate to say that the block will be able to pass twice in the same bar if you run it 2 or more times.

Just x<. It's not aware of indicator specifics

My fault, problem fixed

In the web version I actually can't re-open it after I close it. This is the problem I see, but it looks to be the opposite of what you are saying. Otherwise the descriptnion should automatically appear when the project is loaded.

Yes

Of course I know that Molanis exists and I was playing for a while with it before I started fxDreema, but I don't know its special features and I have no idea how they evolved in the last few years 🙂

"Condition" does not give single signals!!! It only compares two values and depending on that comparison one of the outputs is active. And if this block runs on every tick, then that output will be active once on every tick while the comparison between both values is true.

There is a whole category of blocks designed to work with indicators. They are in the category called "Indicators". Look at them. Or put "Once per bar" after (or before, it depends) "Condition".

😳
Um, yeah. That would be it...

Funny how that happened after the update.

Yes

Block numbers matter when you are on a road that splits into few paths. If block 22 is the only one to be run, then it will be run and that's it. Here is more: https://fxdreema.com/demo/blocks-execution-order

__If you don't mind my asking, who do you use?[/quote:1rksqrky]

I created my real accounts long time ago, before fxDreema. The first one I have is in a broker that does not use MetaTrader. The second one is in a broker where I used some Saxo platform and then I started using MetaTrader 4. It also offers MetaTrader 5, but I never used it.

I must say that I am not a trader, I was just playing few times with my real account and I was losing every time. I never traded automatically, only manually. Obviously I created this tool called fxDreema that many people are now using, but my job now is to make sure that it works properly and to answer to questions. I just don't deal with brokers and I have no professional opinion about them 🙂

Maybe the conditions to open a trade and then close it are the same. Crossover conditions can be true for many ticks while the candle closes. This is how the crossovers in "Condition" works: https://fxdreema.com/demo/mt4-crossover-indicators

Your blocks have wrong names 🙂

I think you want to do something like this: https://fxdreema.com/demo/mt4-buy-sell- ... conditions

Only if you use <, >, <=, >=, == or != you can yse the yellow output as a true "else". For block 2, one of it's outputs is active within some candles and the other output is active in different candles, but most of the time bith outputs are completely off. While there is no x< or x> both outputs in block 2 are completely off. This means that if you connect a block from these outputs, it will not run most of the time. This is how I did it in the beginning

If you want to check some condition and while it's not true to check other condition, use <, >, <=, >=, == or != for the first one.

Crossovers (x< and x>) are 2 in 1 conditions. And as I said, it was my initial decision to make the yellow output to work as the opposite crossover, but not "else".

I think that this is not hard to understand.

The orange output is active when the Condition is true and the yellow output is active otherwise. If one of the operands in Condition is EMPTY_VALUE (for example when indicator is used, but the indicator does not show something at the moment), none of the outputs are active If crossover is used (x> or x<), then the yellow output is active in case of the opposite case. If you have x>, then the yellow output works like x<. If you have x<, then the yellow output works like x>.

Use this:
C:\Users(my username)\AppData\Roaming\MetaQuotes\Terminal\CBC1E074A032EF0E6A1328D19FB1736E\

The left side is correct, the right is not. This is also explained here: https://fxdreema.com/demo/mt4-wrong-closing-rule