Posts made by fxDreema

Maybe input parameters are cached and you think that the value is 1, but it is 3?

https://fxdreema.com/shared/hxkG9bOBc
http://docs.mql4.com/trading/orderprofit

http://prntscr.com/47u09p

Spread matters. By default the last known spread is used for backtesting, and while backtesting it remains constant. But the spread can be manually set, then the results should be the same (if the same history data is used).

"unmatched data error" errors are produced before the EA starts to work, so these are MT4 errors

Aaaaaaah, these errors, how can I forget about them These are not because of the EA. Bad history data - this is what they mean. There is some ticks data missing somewhere in timeframes, but this is "normal", it always happen. You can delete the existing data and download it again only to get missing data somewhere else This is unfortunately well known problem for MT4, and also very old problem

What mismatch errors do you get? This project looks simple... I mean, it does not use custom indicators and fancy stuff, the result should be something or nothing, but without errors. Show me these errors

I think I fixed the problem, here is what I used to work with it: https://fxdreema.com/shared/iXmqBbmAc

I don't remember why I decided to set SL to it's minimum size in AlignStopLoss() while working with virtual stops. Maybe because I wanted the same EA tested with normal or virtual stops to give the same results in backtest. Now I make it the way you want it and I hope that there will be no problem to come out of this

I will try to fix the other things as well.

What can I say

First candle (the current candle) has ID = 0. The previous one has ID = 1. The next previous has ID = 2. And so on... Just like in the first picture here: https://fxdreema.com/documentation/gett ... indicators
Notice that these are candles from the history, not from the future. So you check something from the history when you are in present time.

Am I wrong, or you want to do something at 00:00 and then in 00:45?

Time filter, Hours filter... then Once per candle, Once a day...

"Sell now" is used to sell, this block creates a new trade every time it runs. Run this block 10 times and you will get 10 trades. Run this blok 1 time and you will get 1 trade. Don't run this block at all and you will get nothing.

There is a block called "Condition" which is used to compare two values. When the comparison is true - it's orange output becomes active and the next block is run. Otherwise it's yellow output is active.

In the same block under "Market properties" you can find Ask and Bid. These are basically the current price. Yes, there are 2 current prices actually. Or Candle -> Candle Close.

Define some Constant (because you can choose it's name, the way it will appear in inputs) and then use it in Condition.

http://prntscr.com/45o7j5

Well, I'm mixing boolean with numeric a little bit, but boolean 0 or 1 (false or true) which are basically numbers. You can place that constant at Value -> Boolean on the left side in Condition, but there is some visual bug that I need to inspect and that's why I'm using numeric.

And you can use numeric values where 1 can mean something, 2 - something else, 3 - different thing...

Buffer 0 is the uptrend line, buffer 1 is for downtrend. Swap those buffers 2 and 3 are ok.

But I don't have this indicator to check it

Ok, here are very simple things to do. It's important to do these when needed.

1. To know when and where some block passes, use Draw Arrow. Connect this after some block, let's say block X, and you will know when block X passes. There is even a special block I created for this - Logic points tester. It does not draw arrows, it draws some lines.... a line is the time period where block X was passing. But I found myself using Draw arrow anyway.

2. To know what is the value of something. Use "Comment on chart" for multiple values, or "Indicator tester" for a single value.

3. Keep an eye on the error logs. If something goes wrong this is the first place to look at.

For MT5 make sure that you run fresh EA. There was a problem before, but I'm almost sure that I fixed it

______Then it's something with the strategy.
I have no email, write PM to me here[/quote:3le8zgni]
well there is no strategy related with the lot size just fixed lot. the code is there I can not see any issue on that but you are better than me[/quote:3le8zgni]

I have teamviewer installed what should I send you?[/quote:3le8zgni]

These: http://prntscr.com/45bb8y
But I think the error is obvious, at least for MT4

By the way at the moment you have this: http://prntscr.com/45b84m

And also by the way, this Risk % value should be something like 100%, not 1%. This option % of Equity Lots, when set to 100%, means that if you have equity of 10000 dollars, it will take 0.1 lot, because 0.1 lot is 10000 and 100% of 100000 is 10000 => 0.1 lots. Maybe not very correct MM, but something that I wanted to have at the very beginning
1% will give you something really really small and the minimum lot will be taken.

Otherwise there are other options, some especially for Risk when the lot size depends on the SL. And other options "Freeze" where the lot size is calcylated in a way so you freeze certain amount of money which cannot be used for trading until you close the trade (this depends on some broker options)

Then it's something with the strategy.
I have no email, write PM to me here

Wow, this video is so old, if it is the one I know.

MAs are easy, PSAR is a little bit tricky when you search for the moment where it turns, because you need to compare it's value to the current price. Look at some examples here: https://fxdreema.com/examples

Actually looking at this log I don't know what is wrong - the way trades are handled or that strange dates - 1977 and then jump to 1999. But I don't feel good when some problem happens for long time, so let's check it now