OK, for me “bug” is a term i use very generally describe some sort of unwanted behavior of a program. Maybe I speak of “a problem” in the future if this is better.
And you are surely right, it is a difficult situation to create a “fool-proof” platform with all that functions so I will try to be more positive and be happy for all the many things that work great and not focusing on the problems so much. 🙂
I will try to be more positive and be happy for all the many things that work great and not focusing on the problems so much.
Good! It would help me enormously to maintain the cohesion of our site of almost 10.000 members 🙂 and besides it is soon ~*~ Xmas! ~*~
I’ve not logged-in to the site for 4 months as I felt I was getting somewhat negative also (not negative to this PRC website but to PRT). I sympathise with you Despair … like you, I feel I have a love / hate relationship with PRT!:)
For me, I find it demoralising to spend time writing up ideas for improvements only to then feel like I am sending them into a ‘black hole never to see the light of day’ again! I’d rather see / be told that my suggestion has been listed as No 500 on a list of 1,000 than – as currently – no system to even see what I have previously submitted. A lot, I find myself thinking … did I tell PRT about this or not?
It would be so good to have a few improvements every month or two and be able to see a ChangeLog? For example my Platform shows a Last Update on 23 Nov 17 … anybody know what the update was?
I know there are Changelogs for Version changes (https://www.prorealtime.com/en/trading-system-programming-changelog) but a bit of Agile / regular fixes of the small ‘recurrent frustrations’ on the Platform would be very encouraging?
Anyway I was going to ‘come out of hibernation’ when 10.4 arrived (another 12 months yet!?) … maybe I’d best get back in my burrow again until Spring is here? 🙂
Prosperous Christmas to All
GraHal
Good to read from you Grahal. I was already wondering what might have happened to you. 🙂
I started also being more and more negative but then I said to myself that it was stupid to sit here and complain about this and that. There is nobody that forces us to use PRT. Every platform we can use has advantages and limitations. I therefore started using matlab for the things that I can’t do with PRT what at the same time made me happier when using PRT. I use it for all the things that it is great for and if there is a limitation I try to solve it myself instead of complaining. 🙂
Hey Grahal welcome back, we missed you! Hope you’ll stay around!
OMG Grahal is back! Welcome again, we were talking about you this morning with Noobywan. Hope you are well 🙂
I’ve had strategies stopped on entry for the same reasons (27th Nov and 12th Dec). The issue for me appears to be between the times 18.00 EST Sunday and 1.00 EST Monday. My strategies entering the market after 1.00 AM on Mondays were successful. There were no trades triggered on Monday 4th December before 1.00 AM so no info either way for that day.
I have not had any problems with the other days so it may not be the strategy code although I suspect the trailing stop function could be aggravating a data issue originating from one or more of the service providers. It has been suggested it could be associated with margin adjustments occurring during this time period. Has anyone using MT4 had the same problem on Mondays?
Regarding stopping strategies without reason…. I have not noticed anything unusual until last night.
Technically this is not a stopped strategy but I had identical strategies running on both live and demo. The one on demo opened a position and then almost immediately closed it for a 0.6 pip loss. The one on the live account is still running now. I am assuming this is something to do with the differences in the live data accuracy compared to the demo data but have not fully investigated yet (more important boat jobs that need doing!)
One thing that you might have overlooked is that if your SL is variable dependant it might be too close to your entryprice. Say if you for instance use a MA as SL and it’s only a couple of pips away it might be too close to current price to be able to use as a stop loss. I always code in the minimum SL amount given by IG as a safeguard and I never encounter this problem.
I’m aware of this problem and take care of it in my strategies. This was’t the case here for the stopped strategies in this case. They were stopped because they are supposed to have requested a SL too far away (several hundred pips), but this is not possible from my code. Both strategies had a fixed SL so it was obviously something else going wrong.
