RDSS Testing: Bug Reports
 

This topic is for RDSS Testers to reports bugs or unexpected or goofy behaviour. Please be as detailed as possible about what was happening in the RDSS software (i.e. which screens, which race, if pertinent), and what other software was running at the time.

It is always useful to first attempt to duplicate the problem behaviour. If you can duplicate it, and can explain it, then I can duplicate it too and fix it.

I have all of your computer system specs, so no need to report that.

If you encounter a Windows System error message (i.e. inviting you to send information to Microsoft), as opposed to an internal RDSS software error screen, no need to post the Windows error message - just report that you hit one.

Please post any questions about how to use the software, installation, navigation, where to find things, suggestions, etc in the RDSS Testers Questions & Answers Topic.

Many, many thanks for everyone's help!

Ted


Here is a list of known bugs for Version 0.97.1 and the solutions or workarounds, if any, effective the 'Last edited' date shown below.

www.ArtofPace.com/rdss/bugs/RDSS_Bug_List.pdf

Hi Ted,

Not a bug exactly but a minor thing. When RDSS program screen is minimized, it cannot be maximized again by left clicking the mouse at the bottom of screen on RDSS. To open again, I had to right click and choose maximize. Not a biggie and apologies if you already knew of that.

Jim

me too
 

Hi Ted
I'm getting the same thing :rolleyes:

Noted, and thanks! Please check the posted Bug list from time to time in Post #1 of this thread.

Ted

Ted,

When I'm converting files from my Aqu files and I hit F12, I cannot convert any other track. I'm presuming this is because there are multiple Aqu being converted. So F12 is only an option if your doing single conversios ?

Ken

Hi Ted

I get this error message often.

passrace

Passrace,

I have one other report of an intermittent Windows System error like you show.

Are you able to actually calculate and display Past Performances of ANY races, ever? Or does this happen only occasionally? Note that I have posted in the Bug List (Post #1 link) that for now you should avoid loading multiple race cards, or unfortunately even multiple races on the same card. Just close the card before re-opening for the next race.

If you follow that (limited) scenario, do the Windows System errors persist?

Thanks,

Ted

I observe the behaviour you describe, when multiple cards start converting. After the conversion begins (automatically in the case of multiple cards), hit F12 to return to the RDSS Desktop and click Convert Data again, choosing another Track. If you choose multiple cards for that 2nd track, conversion will also commence automatically. However, if you choose 1 card, sometimes, I observe you are returned to the Desktop without being able to click Update to start that second card going (though sometimes not...)

The solution is, if you can't use F12 to get back to that previous Convert window (while another conversion is running), just use the standard Windows Ctrl-F6 key to cycle among the open sheets (windows) until the convert window for the card needing Updating shows. Then click Update to get it going. And then cycle back to the Desktop to start another, if you wish. Also, you can always use the Windows menu at the top of the application to select an open sheet, and go directly there.

It does work once you get the hang. I often start 7 or 8 cards converting, then go for breakfast.

As I mentioned, this Conversion module (and the Download module) will be rewritten. Soon, this download (PP and Charts)/database conversion/race calculation process (and spot play identification, etc) should happen automatically overnight for you. For now we must work with their warts.

Hope this helps,

Ted

Dear Ted:

Some good news. I use Windows VISTA and RDSS will effectively minimize and maximize without a problem. The same is not true for XP users.

Gary

This too is not a bug per se but I have no way to scroll the screen with pps etc within the main window on a widescreen moniter thus I cant see all the horses at the bottom of the screen. Could a vertical scrowlbar be added?

Doug,

Could you post a screenshot of what you see.

Ted

Ted,
Today I converted my 2/28 files, I then had to leave the program and re-enter to see the Race Cards. The only cards that appeared were those that I converted more then one day. Aqu did not appear since I only did 2/28 but Lrl did since I did 2/28 + 3/1. I went back and did Aqu 2/25 + 2/28 and Aqu appeared.

Ken

Ken,

Well, doing the same cards and groupings as you, I got something even weirder (cards misfiled by date). As you point out, it all corrects itself if you exit and reload. I'll try to clean that up if it's simple, but the Database Conversion and Download modules are being rewritten so this will all look rather different. If we can limp along with how it works now, that would be great.

Thanks for pointing this out, and the workaround.

Ted

Hi Ted

I have the same problem as Ken.

Update on previous post.
I have only one card open at once.
If I close the card after EACH race the
problem goes away!

Al

Foreign Running Lines missing
 

might be able to but i dont have a screenshot program on this laptop and im sure id have to shrink it before uploading it also

I dont have a screenshot program On this laptop Ted, also if I did Id have too have something to shrink it before uploading. All it is is the bottom of the handicapping screen that doesnt show up you can only see around 3 entrees, a prgrammer friend of mine last night said it just needs a vertical scrollbar added to that window for the fix.
Doug

Doug, Wow, I must be dense, but I can't quite nail down (without that picture) what 'handicapping' screen you might be referring to - ALL the screens are handicapping screens! And if you say you only see 3 entries, I don't see how you can be referring to the so-called Entries Screen, as that must occupy only the top quarter of ANY resolution monitor. Maybe you could use your other computer, take a screenshot and describe at what vertical point the screen stops on your widescreen laptop. Or try another description...

I thrive on specifics :~)

Ted

Ill get back to you on this one Ted, Promice I wont be so generic also:)) I should in all truth get more familar with the program before opening my mouth. Busy last 2 days here with the markets taking a big burp, I should never try to multitask. More later:))

Thanks, Doug

I think I know the problem, you need to increase the size of the bottom panel.

Drag window up until you see all the entries

Dumptruk (great handle!),

This is only circumstantially a solution, but correct none-the-less, a solution for now. The splitbars which are dragable were an experiment in fitting everything into limited vertical space and will likely have some role in the final outcome, but are implemented imperfectly right now. I was thinking that the lower splitbar would not even be visible (and thus not grabable) in 1024x768 resolution screens - the user must go to the main Analysis screen. An alternative is a button or key (or automatically) resizing the visible panels (i.e. 2 or 3) according to how many pacelines exist. If there are the maximum 10 lines, on 768 height screens likely only 2 panels will ever be visible (and workable).

For now, drag the splitbars if you wish, but I think this will be frustrating. I'll try to get my hands on a widescreen aspect video display and do some 'resize' coding so that at least 2 full panels show up on it.

Thanks for the tip, Dumptruk - you hit the ground running!

Ted

Dumptuk,

AHA! I should have looked at your 1st screenshot first! Now that I know who you are (!) and know that you have the same widescreen as Doug (900 pixels high), I now see what he was referring to as only seeing 3 horses (3 entries) in the 3rd panel Analysis screen while looking at a horse's Past Performances (a picture was worth all those words!). At 768 pixels high, you don't see that 3rd panel at all - at 900 pixels high, you see about 3 horses worth. :)

Now that I understand that, I can do some useful coding when RDSS detects 768 versus 900 versus 1024 height pixels. Let me try some candidate solutions for the next update for the widescreen aspect users.

Thank you.

Ted

Thanks Dump!! problem solved:)) Now since this is my first time using this how do I close a race card to avoid having too many open and getting a system crash? Yep I had 3 cards done and went to open the 4th and lost the screen emuation.

Sorry to ask a basic question:)) Many thanks once again, Doug

Doug,

Even if you crashed, you should not lose any data, as paceline selections are stored to the database with each keystroke and mouse-click.

To close a race card (and for now, better do this after each race), just click on the little button at the lower-right named (oddly enough) 'Close'. :)

Ted

Thanks Ted, You know what they say, "When all else fails read (or look) at the instructions:))))

I was wondering here if...instead of havingto close the entire race card and reload it to avoid the system crash, is there to anyones knowlege another way to do this? Could you say unclick all the running lines and then go on to the next race on the card? Also Ted found a very minor bug here, when I minimaize the program I have to left click the icon to bring it back up using the restore. No biggie but try to pay attention to detail here:)) Doug

Doug,

The crash is unrelated to paceline selected, so deselecting pacelines doesn't help. I know what to do, and it's on the list. You probably want to keep all your paceline selections anyway, so they are there when you return to any given race. Sorry for this inconvenience :(.

Doug, per the Bug List Item #4, an outstanding issue with WinXP; Win Vista is OK. Thanks!

Ted

Thanks once again Ted, I just installed the program on my other machine here by the way:))

Doug

I updated the Bug List as of noon March 5, with all reported issues (I think) as of current. If you run into anything, have a look at the list to see if there is a workaround. Some of these will be addressed in the next update. If you run into anything else, please report it here!

Bug List (always linked on post #1, too): http://www.artofpace.com/rdss/bugs/RDSS_Bug_List.pdf

Many thankyous!

Ted

Error Message with Projected Pace
 

Hi Ted,
When I click on the Adjusted screen on 1st, 2nd call I get the attached error. It does not happen when I click on the Original screen on the calls. Just FYI.

Racer,

Thanks, added to Bug List. Workaround: don't click call times on the Adjusted screen (i.e. to attempt a Projected Pace). I would like to eventually make the Adjusted screen the place to manage Projected Pace, because all distances are equalized, but I must wait until I can add the 4 call time presentation (like Original) and add running position. Until then, use the Original screen to do Projected Pace.

Ted

crash
 

rdss crashes on the vista machine when you try to go back and forth, between results charts at bris and hcp in rdss.

tom

RDSS crash
 

ted,

Ijust installed the 1GB ram chip to this system and it is no longer crashing between the results charts and the hcp screens in rdss. maybe it was just the fact that this vista system is such a ram hog that was causing this. with the addition of the new chips in both systems the program is running faster and better.

tom

Can you describe what the crash looked like? Any error messages, what behaviour? I have a new Vista box, 512 Mb ram and will install soon.

Ted

rdss crash
 

crash might not be the right word, it would just shut the program down completely.
i would click on the icon to restart rdss and go through all the steps to get to the race just fine, until I clicked on a particular race, ie Aqu R# 8 or # 9, for 3/4/07, it just shut down.
tried this 4 times twice through rdss to bris results charts, twice connecting direct to bris results charts. with the addition of more ram works fine. don't know if this was what was wrong but ok now.

tom

Do any other Vista testers with only 512Mb memory experience what Tom describes? I would test as follows:

1. load RDSS to the Desktop only (i.e. no races); click the BRIS PDF charts weblink (i.e. loads the PDF browser plugin, some memory resources); any problems?

2. Load RDSS then load a race; return to Desktop via F12 then click the BRIS PDF link; any crash?

3. same as #2, but click Pace and Cap forum instead (no PDF plugin, less memory); any crash?

I'm trying to establish whether the memory demands of RDSS with a race loaded plus the demands of a browser with the PDF plugin loaded are too much for Vista and only 512Mb memory (doesn't make that much sense, but I have heard V is a memory hog...)

My own 512 Mb Vista box has to wait until I can do a few other things with it first.

Thanks,

Ted

Hi Ted, vista needs a MININUM of 1 gig of ram just to run, almost all new machines preloaded with it have 2gigs of ram. :)) Trust me on this one!

I ran it on Vista 1GB and no issues..when I had 512k DDRAM installed Vista would run slow even on a Dual Athlon 64 machine so 1Gb made it run a lot faster. Vista is still very, very buggy still..Ted if I were you I would wait on Vista until they release SP1 so that most of its bugs will be chased away. Otherwise time will be spent on fixes not knowing where the issues come from..is it Vista or RDSS? Also your idea to test it on a 512k RAM machine is excellent since most people probably run with that amount of ram. What is the rush anyway? Vista is Windows XP with another GUI..its features are not worth the upgrade IMHO. Unless you buy a new machine with it and you're stuck with it. Hope this helps a bit.

Software crashes when opening races over 12 furlongs. Workaround: don't open races over 12 furlongs :eek:

Ted