Ah, found it after all.
For your fun and good mood :
Left is IB, right is IG. I was porting backtesting from IB to IG. Nothing – just nothing worked because what I call a short- vs long moving average was no way the same in both. But so drastically that it was unworkable.
You will be able to recognise the short vs the long moving average and you can see that the crossings in comparison don’t make sense at all. I spent a couple of days finding the culprit (which I blamed IG for, not IB) but all to no avail. In the end I made the MA myself (add and divide) and that helped.
One of the conclusions I drew at that time was that IG makes up trades. That is, in comparison with IB. You can best see that on the for IB more horizontal (no price change) lines. In the 2nd attachment the part of IB – compare that with IG.
If you run into such differences now between the SB and CFD account, then ditch all your (optimised) Strategies, because the one really won’t work in the other (but use them in the account where they were developed, of course).
It seriously is for a reason that I have 814 outgoing emails to PRT support (local and France together).
For the not-destructive mood, here an excerpt from what I received this morning (from France). I deliberately tug it away, hidden from its original topic which is also in here (PRC).
If you don’t like the way a sell trailing stop order linked to a long position with a buy limit order not linked to the position set above the sell trailing stop order work, I invite you to send us a suggestion for a change to the way it currently works.
I can then forward your message to our Level II support team and if the suggestion is considered relevant and workable, we would then implement the suggested change in the ProRealTime platform.
I show this, in order to let know that our moods may be down the drain regularly because of our “helplessness”, but as I told more often, for me and behind the scenes my mood hardly is ever bad because I really have good contacts and ever so much helping support. It is only that looking back, the efforts to make things clear are huge, and the efficiency on the return (the result) is close to zero. And would I write out bug or issue #395 today, then you can bet that they are all of the caliber like you just experienced. So one of these issues would be “Hey PRT, I just spent a full year on a strategy developed under PRT-IB, but under PRT-IG it does not perform AT ALL”.
So this is ONE issue and I think all together I spent something like 300-400 hours to make PRT-IG suitable for what I do with my Strategies. Nobody at PRT will intuitively understand this and nobody thus takes care of it. And the saddest perhaps of all : while I spend a lot of effort on improving PRT in general (not with suggestions like the above italics imply, but by describing plain money-losing bugs), this not solved and thus everybody will un into it eventually, while no storm of community support helps us (you and me).
🙂