v11 bugs
Forums › ProRealTime English forum › ProRealTime platform support › v11 bugs
- This topic has 108 replies, 13 voices, and was last updated 1 year ago by GraHal.
-
-
01/20/2021 at 4:42 PM #158700
I could then abbreviate in column to PP, PO and PB ?
Done – column I added as you suggested, thanks
01/20/2021 at 6:39 PM #158719That seems to be all the recent posts from the English speaking forum updated on the Wants & Bugs Log, although anything not titled with V11 or so old it’s already been patched will have been left out.
Not sure how we would go about adding in other languages we’d probably need a separate sheet as even if I translate at top of page the description and link would still need to be in the original language.
Next challenge how do we make it visible enough so all forum users know to check there first before logging a V11 Want or Bug and also to get people to update it after posting a unique entry?
01/20/2021 at 6:59 PM #158720Next challenge how do we make it visible enough so all forum users know to check there first before logging a V11 Want or Bug and also to get people to update it after posting a unique entry?
I agree … big challenge! Website Moderators have difficulty getting some members to adhere to Forum Rules that are in a big yellow box directly above the Submit button.
Where do we go from here? I could raise a dedicated Topic under Platform Support where we introduce the 3 x Logs and ask members to use them?
It would be great if the PRT Suggestions Form were submitted for the Wants you have recorded and the PRT Contact Form for the Bugs you have recorded.
Let’s sleep on it … you’ve done enough for one day! Thank You!
1 user thanked author for this post.
01/21/2021 at 7:55 AM #158764Yes please raise the dedicated topic in Platform Support I think a fresh post with your links at the very beginning should help get it kickstarted.
I’m happy to keep an eye on forum for any new V11 issues and update the Wants and Bugs log until more people get used to using it.
In an ideal world it would be great if forum users checked there before raising a ticket and adding an entry in the PRT Improvements or PRT Problem log and if they already have the issue listed in Wants and Bugs, update the thread with the resolution once discovered but hey ho.
I’ve noticed a few users marking threads with Best Answers which when sifting through posts makes it easier to spot the fixes although I’m ashamed to say I don’t know how to do that. lol
Also if you could please mention that any V11 issues should have V11 at the beginning of the title so I can track them easier, even if there logged in the wrong part of the forum I can categorise them right on the spreadsheet as long as I can find them.
Thanks again for all your help getting this moving.
01/21/2021 at 8:34 AM #158765v11 is a powerful tool and it is wonderful to have it after such a long wait. There are some issues to be aware of though:
1. it fails to save changes. This was already an issue with 10.3 but now much worse. My work flow now includes exporting EVERY time I close the algo I’m working on, then importing it when I restart PRT. The changes eventually register but always seems to be a day behind.
2. exporting often causes it to crash! A half dozen times already I have got 2 dialogue boxes, one says ‘Export was successful’, plus a smaller one that says ‘Export in progress’ that never goes away. Then I have to close PRT via Task Manager and restart.
3. big discrepancy between a straight backtest and an optimization that includes those same values. For example, I had trailing stop settings of 0.29 % with a step of 0.028%. I ran an optimization with a range of values above and below that. It returned 0.31% with a step of 0.03%, but gave worse performance than what I started with. When I clicked the 0.29 / 0.028 line in the optimization box, I got a completely different (worse) result than the original backtest. TBT checked in both cases.
I have passed all this on to PRT, just posting here for others to be aware. Anyone else getting similar or different problems?
Hi nonetheless I’ve added these into the Wants & Bugs log.
https://docs.google.com/spreadsheets/d/1kuJH-FWuhjuT-krvFCyyyrrDdhRTvMM7VKy3dH0k6G4/edit#gid=0
01/21/2021 at 8:57 AM #15876601/21/2021 at 9:00 AM #15876801/21/2021 at 9:10 AM #158770Dear People, @GraHal,
This does not work at all like how this is now. You can’t just copy-paste forum topics in a “bugs” list and hope someone takes the time to work through it. Impossible !
I just peeked into the first few, and no, those are no bugs. Of course, this is what happens when someone like @Kovit does his stinkin’ best to fill that list, but it really should be
a. Bugs which remain that and which have not been worked out to solutions via the forum;
b. The most concrete possible (and brief with that).IOW, if you send this out to PRT, it will be counterproductive. Really.
Additionally, do we really think it will be for the better if we mix such a list with “wants” ?
Lastly, and have three similar logs on top of it ?So now what.
I think that a first thing for self-structuring would be that we don’t have a “Brief Description” but a Full Description. A forum topic or post could be a reference but should not be leading.
The self-structuring kind of implies that “we” fill out our issues ourselves. And yes GraHal, I read you – people won’t do that. OK, indeed some of us could pick that up. But only if they understand the problem themselves.I don’t know if I tell you that I am on software (development) support myself. I-have-no-time-to-work-out-what-someone-means. OK ?
I need to understand the problem and I need to instantly agree that there could be a problem indeed. Or else it is simple : please clarify better, make larger screenshots, give relevant data, etc. No deal (yet).A well meant 2c, and I guess you saw that I wanted to start something like this myself. But the format ain’t easy …
01/21/2021 at 9:12 AM #158776Since today no correct display high-low lines, the daily lines are missing but those of the previous days are displayed although not selected at all!
And randomly posting problems in a general topic (though about problems) isn’t going to help in the first place.
🙂 🙂01/21/2021 at 9:17 AM #158780@GraHal, something else … Your given contact links are not the correct ones (never mind you posted them a dozen times by now). But I am not sure what to do with that. … I wrote a full topic about it the other day but I am reluctant to post. So for now this is a kind of small reminder.
I will try to work out something which is approved in advance (where to send to). But no guarantee that I can really work it out.
01/21/2021 at 9:22 AM #15878101/21/2021 at 9:44 AM #158783Dear People, @GraHal,
This does not work at all like how this is now. You can’t just copy-paste forum topics in a “bugs” list and hope someone takes the time to work through it. Impossible !
I just peeked into the first few, and no, those are no bugs. Of course, this is what happens when someone like @Kovit does his stinkin’ best to fill that list, but it really should be
a. Bugs which remain that and which have not been worked out to solutions via the forum;
b. The most concrete possible (and brief with that).
IOW, if you send this out to PRT, it will be counterproductive. Really.
Additionally, do we really think it will be for the better if we mix such a list with “wants” ?
Lastly, and have three similar logs on top of it ?
So now what.
I think that a first thing for self-structuring would be that we don’t have a “Brief Description” but a Full Description. A forum topic or post could be a reference but should not be leading.
The self-structuring kind of implies that “we” fill out our issues ourselves. And yes GraHal, I read you – people won’t do that. OK, indeed some of us could pick that up. But only if they understand the problem themselves.
I don’t know if I tell you that I am on software (development) support myself. I-have-no-time-to-work-out-what-someone-means. OK ?
I need to understand the problem and I need to instantly agree that there could be a problem indeed. Or else it is simple : please clarify better, make larger screenshots, give relevant data, etc. No deal (yet).
A well meant 2c, and I guess you saw that I wanted to start something like this myself. But the format ain’t easy …
Dude i’ve got about 25 years in the IT industry 7 of which as a 3rd line Senior Systems Analyst for a County Council supporting about 30,000 users but cheers for flinging shit without anything to base it on.
Also my view is anyone that would rather just post in a thread than checking a spreadsheet where all issues are listed by category and whether they are ongoing or resolved is just lazy.
Feel free to add your input to GraHal I’m sure he’ll be happy to remove the Wants from the Wants and Bugs, maybe the new thread he’s going to open will create a discussion on what is most ideal for everyone.
01/21/2021 at 9:55 AM #15878401/21/2021 at 10:00 AM #158788but cheers for flinging shit without anything to base it on.
I suppose you shouldn’t post when in a bad mood.
But yeah, you’re welcome.
How many issues did you got through to PRT Development so far ?
Be nice please. 🙂01/21/2021 at 10:12 AM #158792Errors are gone again, something annoying and costing money. We have waited so long for version 11, then it should work without errors, after all, this is also about money. 😉
What happened is :
- PRT V11 was made available to the public in an environment where no AutoTrading is possible (PRT-IB);
- June 2020 it was given to IG who laid it aside until December 2020.
And thus nobody could really test it for the AutoTrading environment.
Kind of official standpoint of PRT is that IG is to be blamed, with “kind of” between quotes. This is because it may be so all right, but *still* it costs money (indeed) and IMHO PRT is responsible for it.
Even if I filed a 100+++ bugs, there are still so many small ones which will never get attention because at PRT development they say “oh well”. Small example for our (not so much fun) : have a cross under in a list (see attachment) while at some stage it because virtually impossible to grab the edge of a list to drag it larger/smaller. Try it. When this fails (grab the edge) you have two chances : 1. you’re under the list and clicked in a chart (like my example), or you could accidentally click that red cross and lose your position (like my example again and this really happened).
The formal response : Yes Peter, you hgave “1-Click” activated, so …” (so you better had not). Meanwhile the real issue is that you can’t grab the edges anymore.
a. No-one is going to solve that in the midst of seemingly larger issues;
b. It indeed can cost you money. And a lot at it. -
AuthorPosts
Find exclusive trading pro-tools on