Posts made by OntradingX

@OntradingX

Note that the EA was never in mql4 format, always in mql5 format.
I've been stirring it many times practically every day and this happened.....

I notice slowdowns in the middle of project development, crashes that last for seconds and then I have to refresh the browser screen for the project to work again.
Currently I got a problem where I was in an mql5 project and it simply turned into mql4 without prior notice, even with small and unreadable blocks.
Notice in the picture, my project is not MQL4, I never made it in MQL4.
And now how to solve this in such a big project??

@l-andorrà
The reason I want more than 2 lines on the chart is because the market can often make one (Big Candle), and as I will always use the Trailing Stop on the previous line, imagine if the Candle crosses 2 or 3 lines simultaneously.
Note: Trailling stop movement will happen only if the candle crosses and closes above the last line being moved to the previous line.

I'm trying to get the EA to draw new lines on top of each other.
Can you help me understand if this logic is starting to get right?

My project https://fxdreema.com/shared/zEdvY0fD

What I wanted exactly is to create a way for the EA to identify if candle 0 is above the current line, that it draws a new line 100 points above this current line and does this consecutively.
Every time the current candlestick is (above) the (current) line a new line should be drawn above this line it crossed.
Let's say the current candlestick got bigger, so it draws a new line 100 points above the last line, but if the candle doesn't (closes above the last line that was drawn) this last line should be deleted.
Does anyone have an idea how to do this?

I cannot share this project with you, I already mentioned above. I already shared the entire project with the admin who owns fxdreema.
I'm waiting for his answers.

@l-andorrà
I really believe that the problem is in mq5 of fxdreema, because I asked a colleague to do exactly the same as I did in fxdreema but in pure mql and he did it, the result was that in pure MQL, it worked. In Fxdreema, however, it doesn't work, so I believe that the admin should thoroughly check each of these blocks, after what happened with the hacker attack, I realize that a lot of things were out of order, it's very sad to have no answers or solutions.
I'm about to give up using the tool.

I don't know if it's Fxdreema, but I had a problem with my projects that had these functions, stay tuned.

@fxDreema I have some projects in progress that are being greatly impaired when they are running on real accounts at different brokerages. I can't share it here but if you call me in the chat I can share the project with you.
These blocks that are in the image are currently showing the reported problems.

This " Position created " block should only execute 1x everything below it whenever any order is opened.
His flashing is:

1. Sometimes it is not executed when the order is opened.
2. When it is executed, it doesn't execute that one time, it happens 2 or more times, it happened 17 times, so as a rule of thumb I put it for him every time he opens a BUY HE hangs a sell on the opposite side, but it's only 1, he then opens a BUY and hangs sometimes 17 sales or 3 sales, it's random, every hour something happens with this block.
   

The " loop pass n times " block should, according to the description of the block, do (execute the number of times that the next block is filled in), I have pending sales orders in the next block, so I consider that if it is defined in this block the number 50, he should then place 50 sell orders at the price I set.
In some moments it does it correctly and in other moments it doesn't, it doesn't matter the number of orders, it can be 50, 1 or 10 orders, it does what it wants, I'm using a formula to calculate the number of orders following times that should be placed pending, this variable is linked to this block, but this block is not consistently respecting it, at some point it fails and places more orders at a time, and at another time less orders, and there are times when it places the requested quantity.

The " Trailling Stop" block was working perfectly, I always put it in "ontick" but I noticed that it is also having an intermittent behavior, it is triggering with a delay, or else at points where it was not requested to trigger.
Today I took a case that I set.
Trailling start to trigger at 1700 points
Moving stop loss to 200 points i.e. would have 1500 points of profit.
Walk every 100 points.
Unfortunately he was triggered with 4260 points.
I didn't understand the reason for this behavior, because the brokerage was normal, with ticks happening, no problem I detected on the brokerage side.

@ambrogio
I don't have a slippage filter enabled, because I believe there isn't one that works, the fxdreema one I've seen in several posts that the admin mentioned doesn't work.

About slippage, I believe that it does not fit this problem, as you agree that slippage would not influence (do not allow opening the order) and yes it would influence improving or worsening the price of the order but (opening) the orders?

@ambrogio I understood what you meant.
But I insist on saying and I will give one more very important detail.
This (the) orders that generated this error (were already hanging) were just waiting to be triggered.
The basic principle is that if the order was launched, let's say as it was in the case 1 minute before, then the broker already knew that there was an order there at the price.
Example of how my robot works.

1. It had sell orders hanging at price 1000, so the market went over there and triggered sell orders at price 1000, all orders were triggered, and at the exact moment these sell orders were triggered, the robot hung others (purchase orders) at price 1300.
   The market then went against the sell orders leaving them negative and then he arrived with the ask price at 1300.

In view of all this logic, when the (ask) price reached 1300, he should trigger these orders, correct?

If the answer is yes, then I go further, the ask, bid prices are slowly surpassed at all times giving this mentioned error and (they did not open any orders, I had about 5 orders of 0.01 hanging, I also had enough balance, connection, ticks , everything perfect.
the price stopped there at 1500, that is, I lost 200 profit points because the orders were not triggered.

I wanted to understand why the orders were not triggered, I sent an email to the broker and so far I have not had any responses.

In my view, either it is a brokerage problem, or it is a Fxdreema problem (Bug), I can't understand anything about the robot's logic causing this type of error.
It is clear to me that if you have pending buy orders far from ask, as soon as ask reaches the same price as these orders it will trigger these orders, or am I wrong?

@ambrogio it is exactly in these tabs that these errors happen.
The question I want to know is if it could be a problem in some block.

@fxDreema you can help here, this is a BUG?

@sktsec
I didn't understand. What do I have to check? The orders were on the screen, the price went through the orders, they were buy orders so the price of (ask) should trigger them and it didn't trigger this error.
What do you mean by (check pending order price)???
If it is a pending order, then it means that it is already at a certain price on the chart and when the market price reaches it (it should be triggered and become an executed order) or am I wrong?

Hello friends, I've been trying to understand why my robot is showing this error in the forex market (demo) or (real) for weeks.

New pending order error: Invalid price (10015). Retrying in 5 seconds..
retry #1 of 10
OrderCheck() failed: Invalid price (10015)

I'm working with pending buy and sell orders and using the " loop pass "n" times " block to place the amount of orders I want when a certain rule is reached.

The problem I noticed happens when the robot tries to trigger some orders on one side, buy or sell, it generates this error, exceeds the order price (without triggering the order) and abandons the order.

Would this be a BUG????? If yes, broker, mt5 or Fxdreema?
Note: This project I cannot share.

Hello friends, I have been noticing that more and more brokers are offering bad (tick data) and the result is always:

1. Unreal backtests, profits, losses, numbers of operations (wrong).
2. Lack of candles on certain days.
3. Mid-day market gaps forming price gaps.
4. Change of trading session start and end times.

With that in mind, I want to develop a solution that can protect against these (brokers' scams).
Does anyone already have a project or part of a project ready that can help?

My logic would be that the EA, even before executing it, scans the symbol looking for these imperfections.
The EA would start as follows:

1. Mark the start of the Market whenever the 1st tick of the market occurs (ie the market makes the first tick movement). This would already solve the problem of starting the trading session, as the first tick of the market would identify the opening price of the 1st candle of the day in the current time frame, therefore the (real time that the market started).

2. I don't know if it's possible, but as it is a backtest environment, the EA will analyze after the item 1 command if there was a total number of candles on the day (This would detect the (lack of candles) on the market day. If there is no candle, there is no traded price and this can generate serious failures in the backtest, providing profits or losses (which should not happen).

3. Detect gaps between prices. I understand that these gaps can sometimes even exist, but they must not be continuous cases or very large gaps, this also causes damage to profits and losses, the difference between the closing of the previous bar can never be so great in relation to the opening of the current bar .

I haven't started the project yet, because I would like to have the opinion of those who want to contribute, so the initial idea would be to start the project and keep updating it, this project would have the purpose of being a kind of (market scanner) it would look for malfunctions and then (supposedly mark these breakpoints) so that strategies can skip those trading days that are faulty, or else adapt to these faults so that they can't have their backtest results fooled by the brokers' data.

@roar
I believe it is still not right according to what I wanted to say.
Notice my project, I am using a block of (once per day) and putting 1 hour ahead of the market start.
Then, as soon as this block is triggered, I identify which candle is (previous) so I put a condition?:

1. If the closing price of the candle was > than the opening price then it is a candlestick (green|bullish), otherwise it is a candlestick (red|bearish).
   Then I just plot arrows to guide which direction is the (first candle that happened at the market opening).

Your code from what I understand and tested it at certain times is confusing what is a candle (green | bullish) and what is a candle (red | bearish). Also place an arrow to observe this.

@roar Your code is identifying whether it is a bullish or bearish bar on the D1 timeframe.
What I needed is to identify if it's a bullish or bearish bar on the timeframe I'm using at the moment, it doesn't matter if it's m1, h1 or monthly.
He has to be able to look at the first bar and see, if it's green it's bullish if it's red it's bearish, and for that he needs to wait for this first bar to be closed to confirm.

Correct Project is here... https://fxdreema.com/shared/MgHR863pe

Explaining...
First I have to know what time the market starts, so I used (once a day).
Then I draw an arrow to identify that particular candle at the time the (market opens) on that particular asset.
And finally, I created a condition to identify whether the closing of the current candle is greater than the opening of the current candle, if so it is a green candle, if not it is a red candle.

@roar thanks... I got it but otherwise, follow the link.
https://fxdreema.com/shared/E8yo27G2c