Posts made by roar

@miguel-0 Ok, that makes the error. Copying blocks normally works, but it doesn't include variable declarations.. Search the forum to learn those

@miguel-0 Yes it should work on mt5. Do you have the necessary constants and variables

@specialfx I think the "price of the last deal" is actually not what you want. It doesn't refer to your trades, but instead all of the market. Actually it doesn't seem to work at all, at least on demo account - the value is always 0.

It doesn't open buys, because 0 is never above MA.
It does open sells, because 0 is always below MA.

It's just a help-button, click it.

You could just calculate the average entry price:
https://fxdreema.com/shared/ij7Qn3Mfd

When you have the average, just add the extra pips

Sounds like a cooking recipe lol

@ggtrader Hi!
https://fxdreema.com/shared/FE3VNtfH
^This animal uses two loops, first finds the low and second finds the prior high.
Download the .mq4 and then import it to your builder to get the constants and variables set up.

Never 100% sure, but I can't think of a possible reason why it wouldn't be the same.. It's just volume

@caesarcrypto
I changed the logic once more, apparently the ELSE-output from cross conditions don't work as expected, better avoid using that.

https://fxdreema.com/shared/jqvCgqYT
This build provides that secondary sell signal on eurusd 2013.08.29, although I think it is lagging 1 bar compared to your intended logic...

@sli1-0 You must take into account that the fractal indicator has a value on every candle, even if there are no fractal visible. In that case, the value is just 0. So make a condition: fractal up/dn is NOT 0 before any other condition.

@caesarcrypto Ah, for the two slightly different entry conditions. Anyway, I would use a more conjoined structure, so there is more hierarchy (and less risk of some weird misunderstanding in logic flow)

https://fxdreema.com/shared/rgZ96qppc

I can't test this because I don't have those fancy custom indicators. Have you tried replacing your custom indicators with some standard ones, just to check the logic? Does the same problem appear?

@caesarcrypto I don't understand the structure here. Why there are 2 logic flows doing buy trades? Why not combine them to one? You are using same indicators in both flows?

I mashed my project into atoms and solved the issue - I had a variable called "size" and this apparently has some other meaning in the mql5 as well

How do you troubleshoot this? A method:

• break your structure into smaller pieces, as small as possible
• test the logical passes piece by piece
• use visual testing and some visual object to check: "comment"-block or "draw vertical line" are my favourites
• if you get the visual confirmation from one piece of your project, modify the visual pointing to some other piece, and repeat
  -> at some point you must find what block / combination of blocks makes the error

@dan-2 Yes, copy-paste works. Remember to declare the variables and constants too.
And I don't know what function you use to make that line - make sure it is named as my constant "allstop"

Edit: wtf did I think you wrote... well, have you tried just refreshing the page?

@l-andorrà Just to activate the connection.. could as well be a pass-block

This mess of blocks seems working for some reason: https://fxdreema.com/shared/JYbZWfZnd
A variable to track the horizontal level changes:

Object name must be in this constant:

Note that this works tick-by-tick, so there might be some seconds delay after moving the line, if market is quiet.

@dan-2 Ah, I see! Let me think a minute

@dan-2 How do you define that "quick motion"? A button? Fxdreema can't really alter the metatrader interface, just add-on elements.

Finding the proper lot amount is easy done with a loop.
Or, if you want a permanent solution, switch to mt5 netting account..

This should do it: https://fxdreema.com/shared/NBisvtvOd