I am marking this post as resolved as I have realised the issue is local.
I decided to test the same EA on another terminal/broker, and to my surprise it worked fine. Hence I reinstalled the terminal on which I initially experienced the issue, and that resolved the issue.
Best posts made by oseiwe
-
RE: Candle position is lost when using a multi-symbol EA on MT5posted in Bug Reports
-
Set Current Timeframe For Next Blocks Not Workingposted in Bug Reports
It's taken me hours of troubleshooting to realise that the "Set Current Timeframe..." block does not work properly. In the below link, I have added two "Draw Line" blocks - both drawing trend lines. However one derives (or is supposed to derive) its timeframe from the "Set Timeframe..." block, while the other has it manually set to "H1".
If you run the EA on a 1min chart, you will notice that the two lines drawn are different. The manually set one is correct while the other isn't.
-
RE: Set Current Timeframe For Next Blocks Not Workingposted in Bug Reports
@roar Precisely. I think what's happening is that it only works on fields named "Timeframe" and nothing else. So even fields named "Candle Timeframe" will not work.
One could argue that it is working according to specification


Latest posts made by oseiwe
-
RE: Set Current Timeframe For Next Blocks Not Workingposted in Bug Reports
@roar Precisely. I think what's happening is that it only works on fields named "Timeframe" and nothing else. So even fields named "Candle Timeframe" will not work.
One could argue that it is working according to specification


-
Set Current Timeframe For Next Blocks Not Workingposted in Bug Reports
It's taken me hours of troubleshooting to realise that the "Set Current Timeframe..." block does not work properly. In the below link, I have added two "Draw Line" blocks - both drawing trend lines. However one derives (or is supposed to derive) its timeframe from the "Set Timeframe..." block, while the other has it manually set to "H1".
If you run the EA on a 1min chart, you will notice that the two lines drawn are different. The manually set one is correct while the other isn't.
-
RE: Candle position is lost when using a multi-symbol EA on MT5posted in Bug Reports
I am marking this post as resolved as I have realised the issue is local.
I decided to test the same EA on another terminal/broker, and to my surprise it worked fine. Hence I reinstalled the terminal on which I initially experienced the issue, and that resolved the issue. -
RE: Candle position is lost when using a multi-symbol EA on MT5posted in Bug Reports
Ok great. Thanks @l-andorrĂ ...was beginning to think I was seeing things
-
Candle position is lost when using a multi-symbol EA on MT5posted in Bug Reports
I've been battling to make this work...until I realised it might be a bug...
I have attached an example project to demonstrate the issue.
Steps:- Ensure GBPUSD, EURUSD, AUDUSD and GBPJPY are present in the Marketwatch window
- Ensure the strategy tester window has the 1hr TF selected
- Ensure the attached EA is selected
- Ensure the symbol selected is GBPUSD
- Run the EA and let it run for a few bars (4 bars or more should suffice)
- Pause the EA
- Compare the hour displayed in the comment (on the top left of the window) with candle time of the current candle that has just been created. You will notice that the hours are different. The one in the comment lags behind
I have noticed that for every 2nd and 4th symbol in the Set "Current Market" for next blocks block, the candle id position lags behind by 1 candle. Hence it lags behind when symbol in the Condition block (block 3) is set to either EURUSD (which is the 2nd on the list) or GBPJPY (which is the 4th on the list)
This issue makes it near-impossible to backtest multiple symbols if the logic utilises candle id positions (eg check that candle ID 1 closed above candle ID 2)
-
RE: Modify Level of an already drawn fibonacciposted in Questions & Answers
Not to worry. Worked it out. Just needed to write the level of the already drawn object's 100 level to a variable and leave it unchanged in the "Move" block...while the O level keeps updating with the current bar
-
Modify Level of an already drawn fibonacciposted in Questions & Answers
Hi,
Hope someone can help with this...
I am trying to modify the 0 level price of an already drawn fib to always be the high of the current bar (where the 0 level is the highest level). That way, the fib will keep adjusting as price goes higher. But I can't see anywhere that the fib level prices can be modified...there is no "Modify Object" or "Modify fib properties" block.For clarity, I know how to check for the conditions (by the way, I am using the "loop" option so I don't have to specify a name for the fib. This works on other object types such as trend lines). The issue I am having is changing just one level without having to move the actual fib (hence the "move" block does not do the job).
Even if I save the 0 lovel price to a variable, how do I write that variable into the fib level?
Hope that makes sense.
Any ideas?
-
RE: Trendline (Chart object) False Trigger Alertsposted in Questions & Answers
I was finally able to work out the cause of the issue. I realised the problem only occurred at the end of a trendline. Hence one bar after the trendline has ended, it seems to evaluate the value of the trendline as 0. Hence, since my condition says "Trigger when BID is greater than Trendline price value" it would trigger at that point.
So now, I simply make my trendlines longer.
-
Trendline (Chart object) False Trigger Alertsposted in Questions & Answers
Hi,
I created a trendline alert EA that alerts me when price touches a trendline that I have drawn on the chart. 80% of the time, it works well. However at other times, it triggers without even reaching the trendline.
Does anyone know what could be wrong? I have looked through the blocks over and over again without any luck.
By the way (in case anyone is wondering) I used '<=' and '>=' rather than '<x' and '>x' intentionally.
Here a link to the EA: shared/DNUCf7I6d
It is a simple one.Regards
Ose -
RE: Compilation Errors: template parameter ambiguous, could be 'double' or 'int'posted in Bug Reports
Thanks!
It's now working.
Regards