Posts made by fxDreema

It's visible for me. Does it fail only for this EA or it fails for all EAs? I can suggest to try it with simple EA that contains say 2 simple blocks in "on Tick".

If you use some indicator in a block, no matter what the block is (Condition or something else) and that indicator exists in MetaTrader, then in backtester it will appear after the backtest ends, or in demo/real it will be used but it will not automatically appear on the chart.
So, in short, when you use an indicator and there is no error with it, it only appears in backtesting after the backtest ends, otherwise it's used but it's not visible. Even in visual backtesting if you want to see it you have to add it manually.

I can see it anyway. I think the problem is in the left side of block 6 where actually now you compare total size (something that results in value like10, 15, 20) with indicator value. Select Candle Close on the left, this will give you the current Bid price.

There is another problem after thiose Buy and Sell. Read about it here: http://fxdreema.com/demo/mt4-wrong-closing-rule

To check if any block passes, place "Draw Arrow" after it and you will see arrows where it passes or no arrows at all if something is not correct inside or above this block.
To check indicators or any other numeric values, use "Indicator tester" block like this: http://fxdreema.com/demo/mt4-indicator-tester

Also i can suggest the block "Once per bar", if needed. It adds different behaviour when it is placed before or after the conditions. You know, indicators seems very simple until you start to think how to add them into an EA You think there is only one way to use it and then you realize that there are more ways than you wanted Well, this is in case you work on the current candle.

Now I'm preparing few new blocks to work with the chart, I guess very soon.
What I can suggest is to check in the source code what is the timeframe that is selected, it should work. The problem is that names are shifted with one step, so H4 is actually H6, H6 is H8 and so on. When the fix comes it will not need any intervention, you can actually see on the project you posted that it now shows H6

Buffer 0 appears to be the value, no matter if the histogram is green or red
Buffer 1 is the value of the green histogram, and when the histogram is red the value is 0
Buffer 2 is the value of the red histogram, and when the histogram is green the value is 0

So the buffers looks fine and it depends on what is needed. If you want to detect the moment when the histogram turns into green, then something like this: http://fxdreema.com/shared/jjiYO4yBc

I think the rule is to have green>red>blue or green<red<blue, or maybe something like this: http://fxdreema.com/shared/XtQK7Fhwc

You are right, there is something wrong in this parameter - instead of H4, H6 is taken. I fixed that, thank you for this report.

Mmm this code comes from the indicator, I found it here: http://codebase.mql4.com/source/39163
Are you sure the problems is in the indicator, and if yes, are all the input parameters fine? By the way I'm not really good with custom indicators

Alligator is like multiple MAs and it's also integrated in MetaTrader. I think it will be similar, but with more Condition blocks depending on what crosses what.

Can you tell me what code is there on that line?

There is a better way to describe something technical:

1. This happens
2. This happens
3. This does not
   ...
   with less words as possible, the most important words.

And even better way - with screenshots! I can suggest this program: http://app.prntscr.com/

http://fxdreema.com/documentation/proje ... indicators

Instead of:

extern int  MA1period=1, MA2period=1;

try with:

extern int  MA1period=1;
extern int MA2period=1;

and if you don't need this it can be removed:

extern string expl01="0 u otro = (H+L)/2 = Precio Promedio";
extern string expl02="1 = Precio de Apertura";
extern string expl03="2 = Precio de Cierre";
extern string expl04="3 = High";
extern string expl05="4 = Low";
extern string expl06="5 = (H+L+C)/3";
extern string expl07="6 = (O+C+H+L)/4";
extern string expl08="7 = (O+C)/2";

Here is more: http://fxdreema.com/documentation/proje ... indicators

When you add an indicator in fxDreema it guesses what are the name of the buffers based on the source code, sometimes it can be wrong. Indicator buffers are these numbers - 0, 1, 2... and those names are just to have an idea what's behind the number. So Indicator tester is to understand what's behind 0, 1, 2...

It seems that some people get it well, others don't. Yes, no programming is needed, at least not in the sence of learning a programming language and writing text commands, but some aspects of programming are still needed - you must have good logic thinking. If you don't get it i see 2 options - find a programmer (with all the possible problems included) or find a ready-made EA, probably something that is paid (with all the possible problems included).

I think it's important to understand how custom indicators work in general. Here is a little information: http://fxdreema.com/documentation/getti ... indicators Here is a little bit more: http://fxdreema.com/documentation/proje ... indicators
After you read all this stuff (I hope you will also get it at some point) try this block called "Indicator tester". There is a little example of using it in the examples section.

Now for the color changing part... it depends on how that is made in the buffers. There is a group of blocks designed to work with buffers - see "Indicators" category, and if something does not fit with these blocks, "Condition" (or few of them) should be able to do it.

Well, all those MM are confusing to me as well, I'm really bad with mathematics. Try it and if it doesn't work as expected tell me to see if there is something wrong with it

EURUSD + USDJPY = EUR, USD and JPY = 3 currency pairs. We all know that MT4 has problems with ticks when we backtest only EURUSD (for example), so can we expect that it can work 100% correct when we add JPY into the game? I don't know, I never tested if this is correct or not, i don't even know how exactly it is working, by my feeling is that it is... less than 100% correct. But all depends, maybe there is no real need to be correct.

As i wrote above, AccountBalance() gives you the current balance value. It's a function, but you can imagine that it is a variable with () at the end. If the balance is 10000 then AccountBalance() will equal to 10000.

AccountBalance()*10/100 = 10% of balance.