Bugs List!
 

Here is a list of known Bugs which are pending being fixed. Please report any new bugs in this Thread. A Bug is an error message or some kind of mis-behaviour - something which really should not happen in reasonable use. First check to see if the potential Bug is already listed here. I will list which bugs have been corrected in subsequent updates.

If you find a new Bug, please describe it in as much detail as you can, including context such as what you were doing, what you were trying to accomplish, etc.

If its not a Bug but rather a behaviour or feature you would like to see, please submit this instead in the Suggestions Thread! I'll see what I can do, prioritize the important ones, and comment as best I can :)

The Bug List will be continually updated in Post #2 below.


Ted

Listing of Known Bugs (or mis-behaviours ;) ).

1. When you first install RDSS 2.1 and enter your TrackMaster UID/PWD in the Registration screen then click Update Registration Info and receive a success message (i.e. you entered a valid TrackMaster UID/PWD) - even VALID UID/PWDs are not recognized at first when you go to Download in the Data Centre. Instead -- you must first restart RDSS.

2. RDSS freezes/crashes after assembling more than 1 card of races (sometimes between 2 and 3 cards, depending on total number of horses across all races). Essentially, it runs out of memory :(.

Workaround: assemble each card in a separate instance of RDSS. While the first card is assembling, right-click on the Windows Taskbar icon for Rdss2.1 and open another instance. Assemble the next card in the new running instance. And on and on. You should be able to get about 5 copies of RDSS running, all assembling different cards at the same time.

3. Horses displayed in Analysis screens switch around by themselves! When running with a toteboard connection and one races is declared official and moves to the next race, the race you may be watching shows the horses from that new race (as prompted by the toteboard's moving to the next race). This does not happen if you are NOT connected to the Supertote toteboard.

Workaround: Per Mick's observation - simply just refresh the Analysis screen you're looking at by switching away then switching back.

4. When you open a race from the MyRaces Card Summary display, particularly (possibly) when you have engaged the filter tools to get a subset of all available races - the race you click on in either the Sidebar or the main (right-side) race listing sometimes does not open up the correct race.

Warning: when opening up a race this way, double-check the race header to be sure you got the race you were expecting.

5. The 'dominant Early horse' marker (red underline and right-triangle marker on Original and Segments screens for positionally Early horse - F / E / EP - who owns the 0.0 on F1 and 2nd Call Segments) - does not always work correctly.

Refer to: http://paceandcap.com/forums/showpos...45&postcount=1

6. Sometimes the Data Centre Convert process toes not completely or correctly complete the Convert of the raw downloaded Trackmaster data ZIP file to the RDSS database. For example, sometimes a horse's pacelines are all missing, sometimes designating them as FTS, or other goofy displays which are obviously incorrect. I will add an internal check for things I can check before calling the Convert process complete and successful (e.g. and automatically re-do the Convert to see if that helps).

Note: you CAN reliably create such an incomplete, screwed up Convert yourself -- just interrupt the Convert process for a card while it is running (and ignore the warning message that the card was likely not completely and properly Converted, and please UNCHECK Don't Duplicate and try it again ... ). Conversely, if this does happen to you - just follow that advice!

Refer to: http://paceandcap.com/forums/showpos...9&postcount=17

7. Entries Screen: shifts right-ward by certain unwanted keystrokes, leaving some of the left-side of the screen hidden.
Workaround: click on another Race-level Tab, then click back on the Entries Tab.

Refer to: http://paceandcap.com/forums/showpos...9&postcount=19

8. Data Centre error messages: Some of the TrackMaster related error messages which RDSS fails to interpret properly (per this long-standing bug FAQ: http://paceandcap.com/forums/showpos...7&postcount=17) still persist. Example: when you specify an incorrect TrackMaster UID/PWD, or your credit card is expired. (I thought I had fixed all those ... :()

Workaround: make sure you have the correct UID/PWD, and that your credit card info is up to date! Otherwise, refer to the complete discussion in the above FAQ.

Program freezing
 

Hi, Ted. We've discussed this before but I'll add it to the list and make it "official." :)

When assembling multiple cards, the program will freeze. I can usually get through two cards before it freezes on the third card. There have been occasions when playing 2-3 tracks that it's exhibited the same behavior. Then I have to open Task Master, shut RDSS down and bring it back up again. (Fortunately, it retains the BRIS Supertote and TwinSpires ProfitLine connections.)

mick

Horses change suddenly
 

This occurs when I'm playing multiple tracks, e.g. Saratoga and Finger Lakes. I'm looking at the horses for Saratoga and they are suddenly replaced by the horses running in the next race at Finger Lakes.

The work-around is easy - just click on an Analysis tab and I'm back to the Saratoga horses that I was looking at. A minor bug.

mick

Race Card sort issue:
 

Example:
Saratoga 8/28/16

Ted, I was playing around with the sort feature on the race card screen, I generated a sort for CL, MC, MS only. The 1st race was a CL_6.5F but when I looked at the PP I got the 2nd race PP, when I looked at the 2nd race I had the 5th race PP. The 6th 7th 8th and 11th were correct
.
When I did a refresh on the 1st and 2nd I get the correct PP’s.

Depending on the sort It look to me that it’s trying to keep some semblance of order?


Mike

Race Card sort issue:
 

Race Card sort issue:

Example:
Saratoga 8/28/16

Ted, I was playing around with the sort feature on the race card screen, I generated a sort for CL, MC, MS only. The 1st race was a CL_6.5F but when I looked at the PP I got the 2nd race PP, when I looked at the 2nd race I had the 5th race PP. The 6th 7th 8th and 11th were correct.

When I did a refresh on the 1st and 2nd I get the correct PP’s.

Depending on the sort It look to me that it’s trying to keep some semblance of order?

Mike

Ted, this is another example from tomorrows Woodbine Card.
Sort 8F and 8.5F
Race 7 has Race 2 enters
Thanks, Mike

Mike,

1. From your screens, I don't understand the SEQUENCE of events which lead you to clicking on one race in the Sidebar, yet getting a different race in the right-side window. I have tried to duplicate both the example you show, and a number of other tests where I filtered the initial set of races to a subset, then clicked on members of that subset in the left Sidebar. Everything worked as advertised. Which makes it difficult to correct errors (i.e. if everything works fine).

2. I only suggested comparing a FUTURE Race Cards by Date Sidebar which looks kind of like the existing MyRaces Sidebar for Pook to get a flavour of where I was heading. However, there are a number of issues and enhancements to that mechanism which I need to flesh out. For APPEARANCE, and ease of navigation without that bottom row of removed race tabs - this mechanism is where we're headed.

3. When I start to flesh out the Sidebar, if it still misbehaves for you, we can connect computers for you to show me. it could be a sequence of actions which I do not use which results in the problem.

4. Meanwhile - I suggest you use the MyRaces filter to FIND the races you are interested in, then switch back to Race Cards by Date to actually open them. (And certainly, to Assemble All - per Bug #2 - MyRaces will crash pretty quickly after Assembling more than about 15 or so races at once).

Ted

Ted, most of the time but not always, when going to a new race the race is laid out as shown below. Half the screen to the left of the BLBL column is hidden whether I am displaying the bar on the left or not. I mentioned this once before and you said the way to correct this is to click on the screen and arrow left. The screen does move to the right and all is well.

What I don't understand is why I have to keep correcting. This happens in both versions of RDSS 2. It is an extra annoying step when I am in a hurry. Maybe there is a configuration I haven't set up properly?

Pook

When importing information with the Profitline button and the Mutuel Prices button after the days races, all changes to the races are made except changes to surface and (if necessary distance) when an off track. You have to watch for that and make the updates manually.

Pook

Correct. Surface and distance changes are not part of the ProfitLine data, thus they don't affect those changes. V2.1.048 addresses full cad scratch and change info.

ProfitLine was always just about getting the PL numbers, and a convenient by-product was updated Scratches.

Ted

Password Security in 2.1
 

Not sure if this is a bug but I notice that the password under the Registration and the Configure tabs are not the typical ******* but display the actual password.

Consistent Error Message
 

As I am eliminating horses from the Win Contender window as I do in the process of handicapping each race, after a number of horses the following error message appears:Attachment 41855.
I can work around this by clicking "OK" which causes the "Exit/Restart/Start Another dialog box to appear, by selecting "Cancel". This will make the Analysis>Original Screen go blank but by selecting any other tab and then selecting Original again I will see the screen as intended with the horse now down in the ITM section. As I do multiple horses I will have to repeat this process each time usually for 3 or 4 horses and then it will operate correctly.
Something that can be lived with but wastes time when there is time pressure to finish a race.

Buzz, it was a choice on my part to show the password. As often as not, in support requests, some of the problems had to do with not knowing what the password was. For example, sometimes people change their TrackMaster Password but forget to change it in RDSS. You can look up the Password in the Configuration file, but I thought it better to just display it. Perhaps a check-box which asks to display or not display the password, so folks can still get it if they need it.

Thanks!

Ted

Mark, if we can prevent the error message from occurring in the first place, your subsequent attempts to recover from the problem will be eliminated, of course.

I could not duplicate the error just now (or ever). You say you you are 'eliminating horses from the Win Contender window'. From your screenshot, I'm guess in you mean that you start with all horses having a paceline selected somehow. Then you look at each horse and remove the check from the Win Checkbox in the horse header section (the top section of the screenshot you show). This means that THIS horse is in the Non-contender group.

Did I understand that right?

Then you go to each next horse, sometimes doing the same thing. After a number of times doing this, you get the error message you show. is that right?

If so, I just did several several tests - with no problem - as follows. I selected the last paceline for every horse. Then I went to each horse in turn and removed the check from the Win Contender box in the horse header until I had removed them all. No errors.

Can you duplicate this problem at will? If so, can you describe your process in more detail, and show how it's different from what I described?

Thanks!

Ted

(BTW - I moved your post from the previous, general RDSS Users private forum to this Forum and Bugs List for V2.1)

Error Message
 

I'm not dreaming here and I know Alyosha has had the same problem as well.
I select the last line for all horses. I look at each horse beginning with the program generated E horses. Typically, when I have reviewed all horses, confirmed or reassigned a R/S and chosen a paceline, from the Analysis>Original screen I will move horses with P or SP or S from the Win Contender section to the ITM/Secondary Contenders section. That is when I begin to see the error message. I love the sort on R/S on these several screens because I have the horses listed in Win Contender section as E, EP and ITM section P. SP and S. Lastly I will cull runners out into the Non-contender section that will not meet the variegation or are just slow horses. But it doesn't give me that error as I remember when I do that. It appears to only want to accept so many horses in the SecondaryContenders/ITM section and then after a few more are moved down with the work around, the problem goes away.

I may have missed something, but I thought that installing 2.1 would put a second RDSS icon on the desktop. I did a straight install and RDSS 2.1 "took over" the existing RDSS 2 icon. I click on that icon and Ver. 2.1 opens.

No big deal for me, since I have yet to want to go back to 2.0, and it is easy enough to do it through the start menu.

I am using Win 10, and the RDSS version is 2.1.033.

Thanks Mike, I'll fix that.

Meanwhile, you can get 2 separate Desktop Icons, one for each version of RDSS (your previous one and the new testing version 2.1), by going to the folder where RDSS is installed (i.e. RDSS2 and RDSS2.1), right-clicking on the Application file RDSS2.EXE and choosing from the popup menu: Sent To / Desktop (create shortcut).

You already have a Desktop Icon for RDSS 2.1 (the icon V2.1 'took over') so all you need to do is go to your old RDSS (on folder RDSS2) and do the same thing to get a 2nd Desktop Icon which points to the old RDSS.

I am working on getting a new Icon for RDSS 2.1 so you can distinguish between old and new Shortcuts (RDSS horse pointing the other way ... 'a new direction ...' ;) )

Hope that helps! Thanks for the feedback!

Ted

Regarding ProfitLine ranks - differences in TwinSpires readouts versus RDSS: you will notice that in the column labeled ProfitLine, showing an Odds number, the #3 and #5 have the same ProfitLine Odds = 9/2. In fact, there is an underlying probability number in the ProfitLine screen display (e.g. .1537) for each horse which translates into Odds (i.e. thats where the Odds come from). Thus, horses with the same Odds should be ranked the same, which is precisely what RDSS does. It does not look at PL Ranks, it looks at the probability number (or Odds).

I looked at hundreds of ProfitLine screens in adapting that number for display in RDSS. Whenever I saw tied PL Odds yet separate rankings - as best I could determine, the difference was ALWAYS that the tied PL Odds horse with the better ML rank was given the higher PL rank. Thus, for tied PL Odds, this becomes a composite ranking (PL + ML ranks). In RDSS, we already have ML ranks as a separate observation, so I wanted to keep them independent, especially since we are already giving both PL and ML (and other factors) weighting in coming up with the various Rx flavours.

So - that's the method: if tied PL Odds, then tied RDSS PL ranks. As Tim points out, it doesn't often happen, but better to treat those horses as equals rather than assume one is better, though NOT based on whatever goes into the ProfitLine rating.

Ted

Tim, sorry I did not look at PRX yesterday so did not download ProfitLine. If I had, I could comment on your observations. I have PRX for today: any problems with that?

Usually, I download ProfitLine everyday for all tracks (via the MyRaces ProfitLine button) - so going forward I can respond to any observed anomalies with how RDSS ranks PL. But check my explanation above to see if that covers it.

Ted

For those who have not seen the Brisnet Profit Line sheet when it comes to entries they not only show the original ranks and ml odds but to the right of the horses name in parenthesis they show the odds the horse will be in the event 1 half of the entry scratches.
A very nice feature.
Tim G

I have a minor problem with the PPs for Turf Paradise for tomorrow, 2/14/17. The Card Summary correctly shows one FTS in the 1st race. When I click on that race, RDSS opens the list of entries for the race and shows 2 horses with a red block "FTS" and a black block "U" under running style after their names, the 6 and the 7.

The 7 horse is a real FTS, but the 6 horse, "Trojan", is also identified as such. Clicking on the tab for the 6 horse shows no races in its history, although it has had one race.

That race may be what is screwing up the process, because it was a 3 1/2 F at NP back in September. RDSS does show workouts for the horse, but nothing else in its history.

Not that its race was anything to be proud of, running 7th in a 7 horse field, 25 lengths back in a 3 1/2 F race. :D

I have a problem with PPs for Delta Downs today, March 11. I don't know if this is a 2.1 problem or a general RDSS problem or a TrackMaster problem.

For races 5 and 6, when I open the race, no pace lines are selected even after clicking again on the "last line" or on "best of last 3" pace line tool. Also, there are no check boxes on the far left of each pace line. If I go through the PPs of each horse and double click on a pace line, that line then appears on the bottom panel, but again with no check box on the left. While the Original tab on the Contender screen shows each pace line, all of the other tabs (BL, Rx, Energy, etc.) are empty.

I'm guessing the problem may involve the length of the races. Race 5 is at 1 mile and 9/16, and race 6 is 2.5f.

Mike, you answered the question in your last paragraph. RDSS - any version - does not do > 12f races, or less than 4.5f races. These distances are not susceptible to pace analysis.

What you CAN do for distances > 12f though, if there are usable pacelines, is change the distance of the race to 12f or less. On the Card Summary screen, simply right-click on the distance or surface column, then select a new distance or surface.

Ted

Mike, I checked that race and I see what you mean. I don't know why that 3.5f race from Northlands Park did not show up in the PPs. ALL races, no matter how weird are supposed to show up.

Any chance you still have the PPs from another source for that race (other than the RDSS TrackMaster data file)? If so, could you email them to me? I can also examine the internal contents of the TrackMaster data file. You never know what pops up!

Thanks,

Ted

Thanks Dick. With this version (.033) RDSS still runs out of memory after loading about 15 races or so, depending on how many horses and how many pacelines. If you ran into that limit, RDSS stops. I also notice it stops after running a certain amount of races through the live toteboard. Same reason - memory.

Perhaps one or both of those scenarios happens to you. I have a plan ...

Ted

Ted,

For some reason the same old assembly problem has gotten worse. Today I am down to assembling individual races so it won't crash. The old version has always been more stable regarding this issue. Is this going to be addressed in an update? This should be a basic function of the software that can be relied on meaning you should be able to assemble a couple of tracks daily programs without restarting continually.

Pook

Mike, just to be clear -

I'm not quite sure which 'old version' you are referring to, since (from the RDSS server logs) you have not been using RDSS V2.1.xxx (.033 or .040) for anything for the past few months - rather, using the 'old' public version 2.0-Beta2.6-02. Are you saying this old version (not V2.1) is more unstable than previously? If so, that's confusing - since of course that version (the one you're using) has not been updated in over 4 years ...

Regardless - if you are reporting that whenever you previously used V2.1.033 it appeared to crash more frequently (run out of memory) when assembling single cards, or when assembling MANY races from the MyRaces screen - than it previously did, well, I'm not following that either. I can't think of what external issues might cause the same program version to perform worse during assembly, given the same computer, same memory, same Windows version - all of which appear unchanged (per the RDSS server logs).

If your question is - when will the bulk Assembly crash problem be fixed (i.e. assemble ALL races = 100's of them at a time): the answer is - it is working its way to the upper regions of my To Do list! I have a plan, which requires some 'heavy lifting' of some code bits, but I don't see why that plan should fail if we can Assemble either Full Cards (which always seems to work, for me, several computers) or at worst individual races.

In the interim, I can only recommend that you use the OLD version (2.0-Beta2.6-02) to download, convert and Assemble. Of course, if you want to make use of the CR+ and ProfitLine and Rx ratings in V2.1 - you'll have to Assemble in V2.1.

I usually advise people: Assemble 1 track, restart the software and then handicap. Or, start Assembly of 1 track, then start another copy of RDSS and start Assembly of another track, then start another RDSS copy ... etc. The parallel Assembly trick appears (to me) to work up to about 5 simultaneous RDSS instances (also possibly dependent on total system memory and whether using 64 bit Windows such as Win10).

I absolutely agree that this Assemble problem has to be resolved, and I actually recently have a greater reason than before to get this working sooner than later (Assemble ALL races, ALL Tracks - e.g. overnight - to get more detailed knowledge about which races offer competitive betting and matchup-related opportunities).

If I didn't understand your concerns correctly, could you kindly restate them. However, I am surprised that in V2.1.033 (or .040) Assembly of entire cards of races (i.e. up to say 15 races at a time) ever fails, let alone behaves any differently now than it did a year ago.

Ted

Ted,

Maybe I wasn't clear on the problem I was having that day.

For whatever reason yesterday assembling races was better (not crashing every race). Maybe I had a bad file or something because everything else was the same. This assembling is done in 2.1.0.7 which has Profitline etc. It would be okay if I did it ahead of time like the night before but you need to wait for scratches to get the Profitline benefits. So I do it closer to post time. Also I may change tracks part way through the day and any time I have to restart software, the software starts to get in the way of itself. That is in 2.1.0.7.

You are correct that I use my older version 2.0.2.12 to download the files. This version is simpler and doesn't crash as much. This is the one I use for the Matchup because I don't need the bells and whistles of the newer one. I use the versions concurrently.

I have only ever had these two versions. Your version numbers are different. Am I using the latest update?

One other thing that I have mentioned before is screen shift. I am not sure but I think it happens in both. It is when you go to the entries screen and the information has shifted to the left partially off screen. To correct it you have to click on the screen and hit left arrow repeatedly to bring it back to the right. Hitting one of the tabs at the top will take you to that screen which is then correctly positioned. If you are not sure what I mean I can put up a screen shot next time it happens. It doesn't occur all the time but starts after I have been using RDSS for a while. I usually restart to get rid of it. Another restart:mad:

Anyways I hope that the soon to be released update addresses these two basic functions.

Thanks
Mike (Pook)

Mike, re versions: the 'old' (public) version is the one you get via the main 'Get RDSS' page, V2.0-Beta2.6-02: http://www.rdss2.com/how-to-obtain (and the one you use to download, per the RDSS server logs). The current RDSS 2.1 Testing version (the one we're discussing in this Testing Forum) is the one available on the Testing Forum Download page: http://www.paceandcap.com/forums/showthread.php?t=10573 -- Version 2.1.040. Some people (you?) use the older Testing Version 2.1.033. I recommend you update to .040 as that fixed a ProfitLine Bug described elsewhere in this Bug List.

I think the Entries screen offset problem was fixed long ago and does not occur in V2.1. If you can demonstrate it in the new version, I would appreciate knowing!

I'll address the efficiency of Assembling many races at once as soon as I can, and take this reporting as encouragement to address it sooner than later: I want you to be happy! (And, I have plans for things the RDSS cloud server can do for all users if it had all races Assembled for a day, which it can't do now, unattended).

Thanks Mike,

Ted

Ted I just downloaded the new version and almost immediately encountered the screen shift issue again as shown.

Mike

Pook, well, right you are :o:eek:. The little bugger. Back on the hit list you go ... :(

Workaround: I do notice that simply hitting the keyboard left-arrow moves the Entries screen back to its left-most side whenever this happens.

Ted

Oops another bug report. Sometimes there is difficulty selecting more than one pace line for an entry. After selecting a 2nd pace line when you move the cursor away it un-selects. You have to do it a few times for it to stick. (The weird part is not always)

Today I got this error message three times in a row when after getting my multiple selections to stick, I attempted to go back to the Analysis screen. It then crashed. Hopefully this system error means something to you.

Pook

Thanks Mike, let me look into that one! (And, thanks for your on-the-job reports! Making our software better.)

Ted

New error for me when trying to select a projected pace. This happened so often today along with the error screen already reported above that I have had to abandon this version and go back to the version from years ago for stability. It has a couple of quirks like screen shift but doesn't crash (at least not nearly as often). I will wait until you officially release the new hopefully bug free one.

Pook

Wow, that's weird! I'll take a look Mike.

Ted

New bug
 

When going through the following tabs in a horse's PPs (Adjusted, Velocity POH, Velocity POR, Energy, PMTR, Primary and Trip), the "zoom" setting (font size) is much smaller (and for someone who wears glasses, hard to see! :) ).

My screen resolution is 1980x1080 and my default RDSS "zoom" is 120%, which has always worked for all screens - PPs and Analysis. I have changed this setting up and down to see if it "cures" the issue, but to no avail. The font size for those aforementioned tabs remains the same.

My config settings:
Attachment 45792

Regular PPs at 120%:
Attachment 45793

The "bug":
Attachment 45794

Tim,

Although my own eyes are not what they once were, I am struggling to see the difference between your 2 screenshots - though I accept that YOU see a difference!

I cut and pasted sections side by side of what you labeled 'regular' and 'the bug' versions of the same horse, same readout. At least from what you posted - they are identical size.

Attachment 45795

So your example doesn't illustrate (at least to my eyes ...). I myself have not observed any difference in text size from previous versions, when set to the same settings as you, same 1920 x 1080 screen res and that code has not changed in years.

Are these before and after installing the current version on the same computer, or did you preserve the previous version and are running it simultaneous to the new version?

At the moment, I don't know what I would fix: I cannot see any problem. Can you develop and explain this observation further?

Also - it is odd that you say changing the Zoom setting has NO effect on text size. If you switch to another race (or restart), you should see the font size change. Are you saying NOTHING you can do has an effect on Font Size?

I do suspect something peculiar to your particular computer. A useful test would be to install the previous version you have from one of your downloaded Install files. Preserve the new 2.1.048 by simply renaming the RDSS2.1 folder to, say, RDSS2.1.048. Then reinstall a previous version (say 2.1.045 or whatever). Open each and compare screens side by side. That process should give useful info.

Ted

(Also - if you can keep your screenshots to 1000 pixels wide max, it will keep the browser screen from blowing up with too large an image).

In window panes 1 and 2, click on either the Adjusted, Velocity POH, Velocity POR, Energy, PMTR, Primary or Trip tabs. This is where the difference in font size shows for me.

I downloaded and selected Update rather than a clean copy.

OK, got it, and I see it - thanks! :confused::confused: On the list for sure, pronto.

Attachment 45798

Ted