Regarding Repulse, I finally reproduced the crash on Pro, but unfortunately I'm out of wits, old on older works without problems, new on Pro just doesn't like to be optimized... Maybe I'll figure this out someday, but for now it's trash bin material, sorry. I removed Repulse from every location I knew of, advise to do the same on your ends.

Thanks, Dave!

After I raise my hands and state my failure, I go a bit mental and come back with anger - a sign of madness? Anyhow, that's what happened, gloves off and all I used an axe instead of a knife, so to speak. Now it works. It's something about how Pro optimizer uses data. Long story short -  for this version if there are less than 3500 bars, indicator fails. Silently. That's the plan anyway. No crashes or errors on my end. Make some noise if something is still off.

3500 bars may pose a problem for trading though... Bear that in mind.

Hey Zezo,

Those indis are available at repository. Since Pro version came out there was new indi standard introduced. Every indi got converted. LINK

I should remove those indis from the first post and provide only the list and the link, shouldn't I. Confusion is bad.

Thanks!

hello footon
regarding to your indicator linear regression line iam trying to add shift function by any means but failed
kindly may you help adding the shift function
thanks in advance

bar shift

thanks footon thumps up

Hey Footon love your work and appreciate how you help out.

I downloaded your Spud Fibo v3 indi, but there is no MQL code provided. Any chance of getting that coded up for use with FXSB Pro?

Just a curious q is there a reason as to why some custom indi's have both C# and MQL while others don't? Is a matter of work load or something?

Thanks again for your contributions.

Thanks for the response. I am in the "process" of learning C# and MQL so hopefully I can contribute one day.

Thanks again, appreciated!

Hey footon, didn't want to open a new thread for this.
Is there a way to realize an opening-range-breakout system that has a multiple of the opening range as TP or SL? Let's say I use "Hourly High Low" for the Opening Point. The only way I could imagine to set the TP at twice the opening range, is if there was a version of the "Hourly High Low" with a "Multiplier" parameter. So if I had an opening range of 40 pips, I could use Hourly High Low with a Multiplier of 3 as a closing point. This would be 60 pips away from the middle of the opening range and therefore 40 pips away from the opening of the position. Here's what I mean:

Also, this would allow one to use a multiple of the range as TP and at the same time the lower bound of the original range as SL. That would be:
Closing Point -> Bar Closing
Closing Condition -> Hourly High Low "The bar closes below the hourly low" Multiplier = 1
Closing Condition -> Hourly High Low "The bar closes above the hourly high" Multiplier = 3

Unfortunately it is still not possible to use "Hourly High Low" as a Closing Point with additional Closing Conditions, though .

Exactly what I needed. Thanks.

EDIT: I think there's a bug. With short positions, the criteria are not inverted.
So if I have a lower multiplier of 1 and an upper of 3, long positions close correctly at the lower bound and one added range on the upper side. But when a short position is opened at the lower bound, it is immediately closed (it should be closed at the upper bound)

EDIT 2: I'm not sure what the bug is.. but something is off.

Yeah, I thought about it over the night and it is not doing what it is supposed to do. The main problem is that indis don't get position info in FSB. But I thought about a couple of workarounds, I'll try them later in the day and see if those correct the behaviour.