Posts made by fxDreema

I'm bad with C/C++ as well. This is not fxDreema error, this is from the software that I use to generate fxdreema.exe. FxDreema itself is not C/C++, it's only packed into this .exe in order to work like a normal program. Unfortunately on their forum there is no information about this error and what setting can cause it. But as you can skip it, I think fxDreema can work.

Later I will install XP on other PC. The fact is that me and those around me, we all quit from XP

If you want to try it, make a backup - "fxDreema/Data" is where important things are (the database of projects), so you can backup this at any time.

Note that after build 038 I changed

The software that I use to generate fxdreema.exe is the same, but I don't remember what settings I changed. In their forum there is nothing about this error message.

What about build 40?

You are with windows XP?

And when is this errors shows up - when starting the program? Is there the loading screen at least?

MetaTrader 4 cannot backtest multiple symbols, it can only backtest the Current one.

History trades are already closed trades, not the running ones. You really want to check already closed trades, not those who are still running?

At 12:00 do you really need to check for past crossover or just MA1>MA2? Because the crossover is valid for a single candle somewhere.

When you wonder if/when some block passes, place "Draw arrow" below that block and you will see many arrows on the chart where the block passes. There is also a block named "Logic points tester" which is designed to do the same - to check what is happening somewhere in the project, but it draws a line instead of multiple arrows.

Can you write the strategy step by step? Something like...

at 12:00 - check condition A and if it's true remember that event A happened.
at 12:30 - check condition B and if it's true remember that event B happened.
at 13:00 - if event A and event B -> do C. If event A, but not event B -> do D. If event B but not event A -> do E.

Doing this is actually constructing the strategy. Knowing what steps must be taken you will know what blocks are needed. And knowing what blocks are needed you can ask me "Where can I find a block that can do this?".

And by the way, do you know what are the history trades?

Now there is a single #define constant named POINT_FORMAT for the whole EA, not for certain markets. The function above makes the difference between different market types, but it can be incorrect for non-currency markets. Everything is fine with EURUSD, USDJPY and so on... Which market uses wrong point format now?

Be extremely suspicious if the EA has small SL/TP, uses trailing stop (or similar) with small SL or calculates pips distance traveled in certain seconds. Why? Because the backtester is not 100% correct in M1, and by using some kinds of trailing stop the EA can produce amazing results by exploiting the backtester's disadvantages.

Close each trade (in MQL4) or Close each position (in MQL5), it's a blue block.

Indicators are related to the candles, and the candles itseld. Trades and orders are not, they are not some naked price levels, but they have other attributes like the time when they are opened (open time). You can check the if the trade is older than X minutes for example. This functionality is located in one of the pink blocks, and I think you will get it - I can see you already use loops.

You have single "Time filter" block, which passes all the time between 12:00 and 16:00. By the way, it's logically better to put that block on the top.

But on the closing side... at any time if MA33 is lower than MA10 you close everything. Note that this is not a crossover, it's a simple condition - something is lower than something else at this moment.

Here is a little bit more about crossover for indicators: http://fxdreema.com/documentation/proje ... er%20works

In "Condition" in "More settings" there is an option "Candle ID" for most of the instruments, you can use it for the indicators if it's needed. If you put Candle ID to 100 for Moving Average, this operand will get the value of the 100th candle in the past. By defaut Candle ID is 0, which means Now.

Indicators are based on candles - each point of the indicator belongs to a certain candle, and candles are based on time. So for example, in 13:00 you can analyze something happened in 08:00. It's by taking a value from the indicator from the N-th candle on a certain timeframe.
In other words, to analyze indicator/candle data we look from the present to the past.

If we want to look from the present to the future, we have to save some data now an use it later. For example, in 10:00 we remember that event "A" happened, and in 12:00 we check whether the event "A" was happened. For this... well, there are many ways to remember something and use it later in fxDreema - Flags (there is a category of blocks named like this), Variables (basically the same thing - set variable and assign value to it), and Formula block (practically the same as Variables).

I recommend to use the first method if possible - analyze past data.

Options -> Current project options -> Point format

fxDreema picks this automatically, but there are differences between brokers when it comes to instruments other than currencies. This option is for currency pairs basically, but you can test it.

This is the function that makes those simple calculations: http://fxdreema.com/documentation/colle ... 4/pipvalue
POINT_FORMAT is a global constant, it is what comes from "Point format" option

Yes, it is from the broker.

This can be workaround, under "on Tick":
Start pending orders loop > (in loop) Check trade/order age > (in loop) Delete pending order

In most cases there is a broker limit for the expiration time, I think it is 10 minutes. I will probably add artifical expiration time in future in case it is set below this limit.

I can download and install it. Maybe you can try to download it again...

It works for me with Firefox and Chrome. What browser do you use?

You can see "Adjust" on many places (Condition block and Condition-like parameters in other blocks). Write there something like "+0.0001" or even "+1pips", and it will add this to the value (for example, it will add 0.0001 to the Close(0)).

http://fxdreema.com/desktop

More details? Just "It doesn't work" don't tell me nothing.

There was the same report days ago... I'm not sure what is it and what cause it to appear.This comes from the phpBB3 forum... it's maybe something with the cookies (weeks ago I have made some cookies changes). What if you delete them?