@bagheria said in Close trade when MAX DD is reached:

fter close immediately....Abs
that's because the MAX DD as described in the snippet bot is static. once that value is true, it's always true until you stop the bot and re-run it. rather look into profit unrealized block and use that with for-each trade to accomplish the closing of positions once there is a certain amount of drawdown or loss on those trades. a stop loss would roughly accomplish the same.

This indicator needs color buffers to map the values to the different signal colors... I saw from the posts here from as far as 2 years ago needing this done but it's still the same even now. Can the author please update this.

If there is someone who knows the value mappings kindly post so I can implement it manually while we wait and see if this indicator will be updated.

Does anyone know how to round off numbers like (Account -> Equity) as they spring from something like 56.8 to 59.345335 and I just can't find a way to keep them displaying in 2 decimal places like how real money should ideally be displayed.

I'm showing that info via the comment block but it's annoying how it can't be tamed

@tipsywisdom analyze this output vs the ea and determine if you think it's timing the trades correctly.

if you look at all the buy trades, they are well in the middle of the bars and never if ever at the beginning of the bars. therefore, if you were to take profits here you'd be missing the points/pips left behind at the bottom before the trades are placed vs an ea which would correctly place the trades at the very beginning so that there is maximum take profits, especially for scalping expert advisors which take profits as little as $0.10 sometimes.

EA setup

Results (just test with $100000 to see the timing issue before it runs out of cash. I purposely avoided any more LOGIC to show that it's delaying even with minimum basic blocks).

Look at where all those buy trades are placed... it gets worse with a complete ea with all the moving average checks and other embedded logic. You'd see the trades planted in the air well above the bars and actually outside the bar components (low, high, open, close).

I know we all love fxd, but let's admit where there's problems.

Its failing to time trades correctly with the minimum logic states required to buy or sell on a new bar!
Its set on every tick to place a buy and sell trade, but on testing it just aptly places trades in the middle of the bars, more noticeably bullish bars than bearish bars and it gets worse if id place any calculations before finally saying on a new bar, buy or sell. That would place the trades right above the bars on the tips of the highs, which is ridiculous.

I do create ea programs with other applications using exactly the same logic and ALL the trades are placed correctly at the beginning of the new bars.

Once the fxd site starts working again I’ll show you the 5 blocks its chocking on

I can't say for sure but I suspect this all comes from the delay placing trades by fxd. It's difficult to get it to place trades at the very beginning of bars correctly. Most just miss the mark.

compared to other ea builder

Someone needs to debug the core fxd web application... I hope the owner is still actively doing so.

This is some sort of coding issue / optimization or lack of that on the backend of fxd. It just can't time trades well. This leads to huge accumulative losses.

See how much of the beginning of the bar is missed!

This following clip is from another ea creator application. See how exact it times the beginning of the bar to get maximum profit if trade goes in favor. Note that I'm not using fixed TPs or SLs. Everything in my EAs is dynamic, such as is the market.

.

If I have free time to kill, I will attempt to debug the actual mql4 code produced to find out why there is this huge delay getting things done... or perhaps one of you knows how to get a perfect (new bar open trade placed like the later using fxd)?

@luckytrader-0 my experience exactly... it seems to rendering from some cached bits instead of taking each render as a new thing. you can change parameters and entire blocks but still get the old stuff

Fx Dreema has some quirks. It's rendering things that are not in my blocks. It renders the output from some cache on its servers and doesn't see the new blocks (even after deleting all blocks and creating new ones, it will render the old robot that was there).

This is a problem even with changing variables or block links and values... you'd think it updated, but still get the old robot exactly as it was output, making one test for hours not seeing any difference. For example you may delete the 'sell now' block but still see it in full glory also making sells with only a 'buy now' block and 'no trade' block on the actual screen!

Surely there are huge server issues. Lately it wasn't working at all and would not even open the actual site. Now its back but doesn't work properly. I have made nearly 150 iterations and am still getting the same robot output. I tried deleting all my cache, restarting my computer and so on, and I even reinstalled MT4, but the issues lie with fxdreema.

Another problem is the inability to place trades at the bottom or open price level, it will rather put a buy trade on the very top of the wick even if the trade is actioned by a previous bar with no special additives ( e.g. if bull candle ID 1 then sell candle ID 0) it will sell at the very bottom of the wick of candle 0, instead of placing the trade exactly on the opening of the next candle). This becomes worse if you're using continuous signals because it will leave hanging trades that are left at the tips and even in the air above or air below the candle it was trading on. Clearly something wrong with the code blocks.)

The comment block also sometimes doesn't get rendered or gets corrupted and need to be redone. Sometimes TPs and SLs lose some digits e.g. TP 5000 would become TP4999 for absolutely no reason. Someone needs to debug the blocks and allow us to place trades on open price of next candle and not to trade all the way to the tip of the candle when on continuous mode (a percentage must be made available to stop placing extra trades say at 80 up the candle or to stop placing additional trades by using a count variable (say no more than 2 per candle etc.))…

We also need candle pattern implementations... building our own patterns would fill a dozen screenfuls of complex branching and hard to describe candle situations/patterns. The available indicators are also way too few and mostly inaccurate. (like the impulse up and impulse down)... how about resistance and support and pivot levels, the things used in everyday trading. I never heard of impulse up & down and time bombs that can't be tested in the strategy tester due to the fake/missing time element...