9X9 Super CSS Indicator

Post by **SteveHopwood** » Fri Aug 12, 2022 3:58 pm

Try running the 'brute force' historical data loading script that Thomas posted at https://www.stevehopwoodforex.com/phpBB ... 34#p173234 and see if that solves the problem.

Post by **WorldsEnd** » Fri Aug 12, 2022 5:59 pm

Thx for your quick response. Looks like the historical data is not the problem. Error message in the expert tab remains valid. Even after the brute force method linked by Steve.

This is what it says:

2022.08.12 17:53:09.909 9ofX_v2.3 AUDCAD,H1: array out of range in '9ofX_v2.3.mq4' (139,33)

The indicator window remains blank.

Post by **SteveHopwood** » Fri Aug 12, 2022 8:34 pm

WorldsEnd » Fri Aug 12, 2022 5:59 pm wrote:Thx for your quick response. Looks like the historical data is not the problem. Error message in the expert tab remains valid. Even after the brute force method linked by Steve.

This is what it says:

2022.08.12 17:53:09.909 9ofX_v2.3 AUDCAD,H1: array out of range in '9ofX_v2.3.mq4' (139,33)

The indicator window remains blank.

The error points us to the pair (ACAD), line (139) and character on the line (33) in the source code -which I do not have. Post it here if you are allowed to and I will have a look. I guarantee nothing because indi code baffles me, but you never know.

Post by **WorldsEnd** » Fri Aug 12, 2022 9:34 pm

SteveHopwood » 12 Aug 2022, 22:34 wrote:
WorldsEnd » Fri Aug 12, 2022 5:59 pm wrote:Thx for your quick response. Looks like the historical data is not the problem. Error message in the expert tab remains valid. Even after the brute force method linked by Steve.

This is what it says:

2022.08.12 17:53:09.909 9ofX_v2.3 AUDCAD,H1: array out of range in '9ofX_v2.3.mq4' (139,33)

The indicator window remains blank.
The error points us to the pair (ACAD), line (139) and character on the line (33) in the source code -which I do not have. Post it here if you are allowed to and I will have a look. I guarantee nothing because indi code baffles me, but you never know.

Thanks for your offer Steve. It‘s Dwains Indicator from page 39 of this thread. Version 2.3 just the page before this one

Post by **WorldsEnd** » Sat Aug 13, 2022 8:14 am

SteveHopwood » 12 Aug 2022, 17:58 wrote:Try running the 'brute force' historical data loading script that Thomas posted at https://www.stevehopwoodforex.com/phpBB ... 34#p173234 and see if that solves the problem.

Another thingie apart from my array error problem which might be worth mentioning ... the historical data "nuked" my VPS in terms of memory storage. The complete historical data for 28 fx pairs is more than 8GB (I am a GP customer). One should keep that in mind or request more disc space before starting the download

Post by **dap711** » Mon Aug 15, 2022 9:32 am

WorldsEnd » Fri Aug 12, 2022 3:34 pm wrote:
SteveHopwood » 12 Aug 2022, 22:34 wrote:
WorldsEnd » Fri Aug 12, 2022 5:59 pm wrote:Thx for your quick response. Looks like the historical data is not the problem. Error message in the expert tab remains valid. Even after the brute force method linked by Steve.

This is what it says:

2022.08.12 17:53:09.909 9ofX_v2.3 AUDCAD,H1: array out of range in '9ofX_v2.3.mq4' (139,33)

The indicator window remains blank.
The error points us to the pair (ACAD), line (139) and character on the line (33) in the source code -which I do not have. Post it here if you are allowed to and I will have a look. I guarantee nothing because indi code baffles me, but you never know.

Thanks for your offer Steve. It‘s Dwains Indicator from page 39 of this thread. Version 2.3 just the page before this one

I promise it's a history problem. Try using the indi with just one TF selected. The issue you are having is on the AUDCAD H1 chart.

Post by **dap711** » Mon Aug 15, 2022 9:32 am

WorldsEnd » Fri Aug 12, 2022 3:34 pm wrote:
SteveHopwood » 12 Aug 2022, 22:34 wrote:
WorldsEnd » Fri Aug 12, 2022 5:59 pm wrote:Thx for your quick response. Looks like the historical data is not the problem. Error message in the expert tab remains valid. Even after the brute force method linked by Steve.

This is what it says:

2022.08.12 17:53:09.909 9ofX_v2.3 AUDCAD,H1: array out of range in '9ofX_v2.3.mq4' (139,33)

The indicator window remains blank.
The error points us to the pair (ACAD), line (139) and character on the line (33) in the source code -which I do not have. Post it here if you are allowed to and I will have a look. I guarantee nothing because indi code baffles me, but you never know.

Thanks for your offer Steve. It‘s Dwains Indicator from page 39 of this thread. Version 2.3 just the page before this one

I promise it's a history problem. Try using the indi with just one TF selected. The issue you are having is on the AUDCAD H1 chart.

Post by **WorldsEnd** » Mon Aug 15, 2022 7:35 pm

dap711 » 15 Aug 2022, 11:32 wrote:
WorldsEnd » Fri Aug 12, 2022 3:34 pm wrote:
SteveHopwood » 12 Aug 2022, 22:34 wrote:
WorldsEnd » Fri Aug 12, 2022 5:59 pm wrote:Thx for your quick response. Looks like the historical data is not the problem. Error message in the expert tab remains valid. Even after the brute force method linked by Steve.

This is what it says:

2022.08.12 17:53:09.909 9ofX_v2.3 AUDCAD,H1: array out of range in '9ofX_v2.3.mq4' (139,33)

The indicator window remains blank.
The error points us to the pair (ACAD), line (139) and character on the line (33) in the source code -which I do not have. Post it here if you are allowed to and I will have a look. I guarantee nothing because indi code baffles me, but you never know.

Thanks for your offer Steve. It‘s Dwains Indicator from page 39 of this thread. Version 2.3 just the page before this one

I promise it's a history problem. Try using the indi with just one TF selected. The issue you are having is on the AUDCAD H1 chart.

Hi Dwain,
thx for answering

Well, I‘m pretty sure it was no history problem as I‘ve tried it with other pairs as well. It was no problem with your indi either. I don‘t know what caused my problems but when nothing worked out, history files filled my disc space with gigs of data and no terminal opened up due to insufficient memory I came to the conclusion that I need to do a complete reinstall of my Empty4 terminal. I saved all relevant data beforehand and started all over. I was lucky it happened over the weekend. Anyway, by now all is up and running again without problems. Sorry for troubleing you guys with my corrupt Empty4 terminal

Post by **SteveHopwood** » Mon Aug 15, 2022 8:41 pm

WorldsEnd » Mon Aug 15, 2022 7:35 pm wrote:
I came to the conclusion that I need to do a complete reinstall of my Empty4 terminal. I saved all relevant data beforehand and started all over. I was lucky it happened over the weekend. Anyway, by now all is up and running again without problems. Sorry for troubleing you guys with my corrupt Empty4 terminal

Something for us all to remember is that we deal a beating out to Empty4 that it was never designed to withstand. It is a much better platform than it was a decade ago, which means we can torture it even more. Sometimes it will break.

This is something to add to my emails to members on joining and occasionally to my wrup. Your travails have not been in vain.