Posts made by jstap

Good luck, maybe another problem, I use Edge and never have this problem.

This is unusual, but sometimes it does seem to happen, from what others have said this is because of a problem with the browser you are using, is not fully compatible.

instead of variables use constants, this way they can be changed in your EA's inputs.

I rarely use no position nearby block, I have in the past but it rarely works as I would expect. As for 3rd risk of 1 I would set lot as % to 0.33 on each trade (100/3 = 33.3), then close all when profit reached, Check profit (period of time) but this would only look for profit in a given time.

I can help, but not sure exactly what you want, simple tree would be: no position block - condition block (to say reason for placing trade) - buy or sell block (set TP and SL inside)

That kind of makes no real sense, the comment shows the variable value, your condition checks the variable, which you visibly check, then passes to the check block onto the sell block. So everything should work as expected. The best thing to do now is enact a process of elimination, link out blocks until while backtesting you find the block that is causing the trouble. Sometimes (but rarely) you have to recreate the EA from scratch.

the code you have looks like it would almost work, does the number change in your comment when you change in the CSV?

No mate, but FX will only use one already created

You can do this on your PC platform, but not on FX Dreema, your only choice is finding a aftermarket indicator, to run on PC.

yes and in the EA inputs

This makes sense why error said "constant" expected

This is why I prefer working with MT4 not MT5, the problem is in your no position nearby block, the formula block is working correctly and multiplying the used pips, then you get that issue. You can try asking support why it's happening: https://fxdreema.com/support

Not sure what you mean? Magic number is in your inputs.

Principle is the same "if this = this do this", but if different timeframes mean different settings. You have the flags to allow/stop trades, now new trees that will set these, condition PSAR is < or > candle ID4, this means that as soon as the dot is on 4 (so when 3 closes) you can set the flag false.

Both these methods work in backtest

@Fireblade You are welcome

This should do it, you'll have have to add sells and change conditions to how you want:

https://fxdreema.com/shared/hp9rtLtNb

There is no once per signal, you have to create it with flags, once per bar may do it, but SAR will be the same on many candles,.

Set flags, if trade can be placed set flag to tree, if not leave a false, check with a check flag block, you can switch on/off as you like.

If created correctly they work the same on live as backtest, sometimes though they perform differently on backtest to a live environment.