Thanks Saver0, this is very helpful  

You can’t backtest any cluster indicator (like this one) because in backtests MT Terminal will only load price series of one pair at a time. This specific indicator permanently needs price series of 28 pairs to work.

It’s a limitation of MT4, not a bug or repainting issue of this indicator.

Regards, simplex

You can’t backtest any cluster indicator (like this one) because in backtests MT Terminal will only load price series of one pair at a time. This specific indicator permanantly needs price series of 28 pairs to work.

It’s a limitation of MT4, not a bug or repainting issue of this indicator.

Regards, simplex

You can’t backtest any cluster indicator (like this one) because MT Terminal will only load price series of one pair at a time. This specific indicator permanantly needs price series of 28 pairs to work.

It’s a limitation of MT4, not a bug or repainting issue of this indicator.

Regards, simplex

Hmmm – did you never observe similar spikes of this indicator when no relevant news are about to happen?

My guess is: sheer coincidence.

Thanks for the link – didn’t know them yet.

When it comes to EA generators, I’m very reluctant. Seen way too much rubbish in the past. At least it should be worth a closer look. Do you have any personal experience with their service?

Ok – great music here! Now I found something different which is nice for a little break.

Non-Coders: the link provided is not for you! It may reveal too much about how coders do think about their users, hehe!

Coders:

Are you experiencing weird error messages from time to time when coding?
Are your indicators forcing MT to terminate from time…[Read more]

Hey Kiads,

This looks interesting! Can you provide a link to the origin on those indicators to find some more background information?

Cheers, simplex

Compiled from another thread:

One thought related to debugging: I found it to be very useful to place

#property strict

in your code. It requires a bit (really only a bit) more discipline while coding to avoid compiling errors, but what you’ll get as a reward is much more detailed runtime errors, especially popular ‘array out of ran…[Read more]

Compiled from another thread:

One thought related to debugging: I found it to be very useful to place

#property strict

in your code. It requires a bit (really only a bit) more discipline while coding to avoid compiling errors, but what you’ll get as a reward is much more detailed runtime errors, especially popular ‘array out of ran…[Read more]

Compiled from another thread:

One thought related to debugging: I found it to be very useful to place

#property strict

in your code. It requires a bit (really only a bit) more discipline while coding to avoid compiling errors, but what you’ll get as a reward is much more detailed runtime errors, especially popular ‘array out of ran…[Read more]

Compiled from another thread:

One thought related to debugging: I found it to be very useful to place

#property strict

in your code. It requires a bit (really only a bit) more discipline while coding to avoid compiling errors, but what you’ll get as a reward is much more detailed runtime errors, especially popular ‘array out of ran…[Read more]

Compiled from another thread:

One thought related to debugging: I found it to be very useful to place

#property strict

in your code. It requires a bit (really only a bit) more discipline while coding to avoid compiling errors, but what you’ll get as a reward is much more detailed runtime errors, especially popular ‘array out of ran…[Read more]

Compiled from another thread:

One thought related to debugging: I found it to be very useful to place

#property strict

in your code. It requires a bit (really only a bit) more discipline while coding to avoid compiling errors, but what you’ll get as a reward is much more detailed runtime errors, especially popular ‘array out of ran…[Read more]

Compiled from another thread:

One thought related to debugging: I found it to be very useful to place

#property strict

in your code. It requires a bit (really only a bit) more discipline while coding to avoid compiling errors, but what you’ll get as a reward is much more detailed runtime errors, especially popular ‘array out of ran…[Read more]