@ontradingx 
This indicator has 4 buffers, but when placing it on the chart it does not display the constants so we can choose and customize how many periods, or deviations, we want it to be configured.
Does anyone here have the knowledge to modify it to the point of letting it display the settings?
@slimmz @biztet
I'm in a similar project but for Metatrader 5, I need help to publish the buffers and constants of this indicator, I believe it's the same as our friend here who opened the topic needs but only in mt5 format.
0_1640346446481_Support_and_Resistance.mq5
@slimmz Can you check if this one would be the indicator?
@slimmz you don't have the source code file of this indicator?
@slimmz Hello friend, I would like to help you but the indicator file is no longer available.
Can you make it available?
@uriel-0 You are right.
I am following an EA of a Brazilian that he operates in the Brazilian market and is performing excellently, I had access to perform backtests and I realized that the results in (each tick and each real tick) are identical, and the EA actually replicates the same entries and exits from the real market in the backtest, but for the programmer to be able to make this almost miracle happen, he created his own historical database.
I will try to follow this same line of reasoning with my EA's.
Friends, would this rule meet what I'm trying to say?
@fxdreema
Just to close this matter.
I managed to get around the problem by doing the following:
@fxdreema, I'm sure this worked before, all this work I've done wouldn't be necessary but it's because something that worked before just stopped working.
@l-andorrà Sorry, actually I misspell, the correct is 45 seconds and not minutes.
When there are 15 seconds left for the current candle to close.
But I believe I managed to do it, the "time filter" block didn't solve my problem, so I had to use the blocks, once per bar, set flag true or false and once per seconds.
Thanks a lot for the help.
@pacificnet-lk Did not work.
I think maybe I explained it wrong.
Imagine that a candle has just opened in m1 at 09:00
From this moment on when it is 9:45 am I want to open a trade.
Hi, can you please help me understand what the rule would be so that I could make an entry in the final 15 seconds of a 1 minute candlestick?
Here is my example project.
https://fxdreema.com/shared/DsOuQH1lb
@jstap Nice observation, I've also been doing this, the OHLC being faster makes it possible to verify this.
Hi friends, I opened this thread to get your opinions about backtest results vs real market.
Developing EA's I could see that many times there are very good results from backtests, but when the EA is put into real account we really know if it works or not.
Based on this I started looking to develop strategies where the entries really happen (equal) in the backtest and in the real account.
For this I always run a backtest of the day before to find out if the result that happened in the real account happens similar in the backtest.
When I see that there is similarity (entries and exits, with close prices) I understand that I can trust the results of that backtest.
But here's the question, should I believe in a Backtest done in the format (OHLC or EVERY TICK), I've heard from many developers, one DEPENDS.
Many say the following:
If the Target is too short, always use (EVERY TICK)
If Target is too long, always use(OHLC)
Today I always try to use both modes, but I prefer the results (EVERY TICK), because I realize that in fact it is the closest to the real market result regardless of whether the targets are long or short.
What is your opinion on this?
@piptheripper
Try 2.0 to buy and 1.0 to sell.
Why does it work well with "grid"?
What is the difference in the calculation?
@fxdreema
I know Fxdreema doesn't round up.
But at some point he should open orders 0.02, 0.03 and this is not happening.
I put an example of what should happen and is not happening.
If there was a change from 120% to 155% it works perfectly.
I also tried to create a formula to multiply by 1.20 and it doesn't work.
Tested on FBS, ICMARKETS, FTMO, ACTIVE TRADES.
@fxdreema
It saddens me that you say it's not a bug.
I used this normally, so you mean I'm lying?
This "Add Volume" block worked correctly with initial volume of 0.01
I even have "Grid" resources with 120% and it works perfectly.
I considered it a bug because it was something that worked perfectly before, but stopped working without warning.
@l-andorrà I don't know if you noticed but, I first created a question in "questions and answer" where there really was an answer, but after my tests it didn't work, so after numerous tests I understood that it may be a possible problem existing in the tool.
So, believing that this is a problem in the tool, I created a new topic in "bug reports" which I believe is something just to deal with problems with the tool and not with doubts.
I believe that the best way to avoid duplication would be for the developer to have some mechanism to transform topics that were "issues" into "problems", thus avoiding duplication of topics.
