@Dizi, no that is not wat we get. We get one line (nothing optimises) with the fixed value from the first column (regardless whether Fixed is ticked). But even then, these fixed values work out to always the same value anyway.
It looks like the value taken is always 1 for each of the parameters.

@Nicolas, I said something along these lines before. I recall I received a response from you similar to “Peter, it just works fine”. I think you should really look into this. It does not work at all, and vendors can’t see this; they see it normally working. I am not even sure whether the vendor can mimic the mode “we” as the customers get to see; then it would be readily clear to them and will start asking questions.

The simplest way to test this is with YOURLOSS because that is not subject to the Indicator code. So already that does nothing, no matter the (fixed) value you fill in the parameters. As Wim said, only setting it in the code itself to a value,  will influence the in this case %LOSS.

Regards,
Peter

image_2022-12-10_065642744.png image_2022-12-10_065820372.png

I started from the DAX30T trade manager and took the indicator and included a filter.
Here is the backtest in 200K
spread=5

Capture-decran-468.png Capture-decran-469.png

Dizi wrote:

The latest version of the script is available. I have attached the screenshot with backtest and my live acc

I think I already have the latest version – I downloaded this just prior to my post.
And if there is a newer, I don’t know (yet) how to upgrade.

The snippet you showed with the ONCE declarations in there, is the one which would NOT work, right ? (I say this can’t work). But this is not in the script I downloaded. So *not* having that in there would be the way do t it, but something just does not want to cooperate with the backtesting.
It would work in Demo or Live, but then with the filled values at handing to ProOrder.

image_2022-12-10_102132284.png