TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
Well now it is working. I did not change a thing so why it failed before and now it is working I have no idea.
Last edited:
Official GranTracker Thread
- Thread starter GrumpyOldMan
- 423 comments
- 36,405 views
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
I hate when that happens. I mean, I'm glad it's working, but "it's a mystery" isn't a good feeling. Let me know if it stops working again.
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
@TheNormsk A while back we were talking about representing DR points more accurately on the chart. I did a little playing around, and here's what it ended up looking like:
I can, of course, leave out the lower and higher letter ranges that have no associated data, but honestly, I don't think this will help much.
What do you think?
I can, of course, leave out the lower and higher letter ranges that have no associated data, but honestly, I don't think this will help much.
What do you think?
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
I think it looks good. Now if you can limit the upper and lower bounds to the range of data presented, then that would be ideal. Otherwise, the line may look sort of flat. Do you think that’s possible?
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
Depending on which version of graph it shows either:
By %
By DR points
Question: what does DR Constrained do in the enter race details line?
So what is still on the to-do list?
- Graph update
- Add the fastest lap flag
- Center the DR Points column label.
Last edited:
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
Sounds good - thanks.
It's to handle this situation:
- 12:22 - I'm almost at DR A, but my SR is B.
- 14:25 - I improve to DR A level, but the game constrains it to B because of my SR. It looks like I lost 98 points.
- 15:42 - Got my SR down to A, so the game gave me DR A. It looks like I gained 109 points.
So for 14:25 and 15:22, I turn on "Constrained", and it looks like this:
It shows DR at A, but colored red to show it's been constrained. And here's the chart:
The red stars indicate they were constrained. If you hover the cursor over a star, it displays this:
Does that make sense?
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
Excellent explanation and clever solution. Thank you.
Last edited:
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
- 71
- Los Angeles
Decided to really make a push to get into DR A and GranTracker has been awesome.
I’ve been doing a ton of Race B this week which has been a great DR booster for me and then today I saw a familiar name in a lobby and wondered if it was the man himself. When the race ended I caught the exit message promoting grantracker.com!
I’ve been doing a ton of Race B this week which has been a great DR booster for me and then today I saw a familiar name in a lobby and wondered if it was the man himself. When the race ended I caught the exit message promoting grantracker.com!
Attachments
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
Got this.
I was importing a screenshot from March while the chart was filtered on the current week.
I also got this one.
I was adjusting back the time to the original time (past midnight) for those races that crossed the week start. One worked fine. The other threw this error.
How is the time zone set now?
Mine should change at 2am but this threw my updated time into next week.
Formatting reminder. Should header text be left aligned or center aligned? I vote for center.
Code:
App Version: 1.3.2
message: Uncaught TypeError: console.logWarn is not a function
at file:///Applications/GranTracker.app/Contents/Resources/app/src/renderer/ui/tabs/userRaces/userRacesTableController.js:444:12
Stack Trace:
at file:///Applications/GranTracker.app/Contents/Resources/app/src/renderer/ui/tabs/userRaces/userRacesTableController.js:444:12I was importing a screenshot from March while the chart was filtered on the current week.
I also got this one.
Code:
App Version: 1.3.2
message: Uncaught TypeError: console.logWarn is not a function
at file:///Applications/GranTracker.app/Contents/Resources/app/src/renderer/ui/tabs/userRaces/userRacesTableController.js:444:12
Stack Trace:
at file:///Applications/GranTracker.app/Contents/Resources/app/src/renderer/ui/tabs/userRaces/userRacesTableController.js:444:12I was adjusting back the time to the original time (past midnight) for those races that crossed the week start. One worked fine. The other threw this error.
How is the time zone set now?
Mine should change at 2am but this threw my updated time into next week.
Formatting reminder. Should header text be left aligned or center aligned? I vote for center.
Last edited:
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
Awesome! Glad you like it, and I wish I'd known who you were in the race. At least now I know.
This is already fixed for the next version, which I haven't released yet. The new version will remove filters when you edit something, or add a new record.
The time zone stuff should happen automatically, unless I missed some code, because it's all based on UTC. I'll take a look at it.I was adjusting back the time to the original time (past midnight) for those races that crossed the week start. One worked fine. The other threw this error.
How is the time zone set now?
Mine should change at 2am but this threw my updated time into next week.
Agreed.Formatting reminder. Should header text be left aligned or center aligned? I vote for center.
EDIT: I believe the time zone thing is correct. According to Google, Wisconsin in January is UTC-6. The races change at 07:00 UTC-7, which makes it 01:00 your time.
Last edited:
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
Got this today, opening the app.
Upon reopening, it worked.
Before 2am Mar 12, 2023 we were on standard time when CST is UTC-6. After that it is UTC-5, so my error was against standard time when the week changed at 2am and not daylight savings (or summer time) when it changes at 1am. So on January 23 it was:
Tonight will be:
So if daily races change at 7am UTC (1am CST) how did I record a race at 1:42am CST that was the prior week? Weird.
Don't you just love time zones?
Code:
App Version: 1.3.2
Cannot read properties of null (reading 'verticalFillMode')
Stack Trace:
at RowManager.adjustTableSize (file:///Applications/GranTracker.app/Contents/Resources/app/node_modules/tabulator-tables/dist/js/tabulator_esm.js:23428:20)
at RowManager._wipeElements (file:///Applications/GranTracker.app/Contents/Resources/app/node_modules/tabulator-tables/dist/js/tabulator_esm.js:22660:8)
at RowManager._setDataActual (file:///Applications/GranTracker.app/Contents/Resources/app/node_modules/tabulator-tables/dist/js/tabulator_esm.js:22632:8)
at file:///Applications/GranTracker.app/Contents/Resources/app/node_modules/tabulator-tables/dist/js/tabulator_esm.js:22622:10
at new Promise ()
at RowManager.setData (file:///Applications/GranTracker.app/Contents/Resources/app/node_modules/tabulator-tables/dist/js/tabulator_esm.js:22607:10)
at DataLoader.load (file:///Applications/GranTracker.app/Contents/Resources/app/node_modules/tabulator-tables/dist/js/tabulator_esm.js:24047:26)
at TabulatorFull.replaceData (file:///Applications/GranTracker.app/Contents/Resources/app/node_modules/tabulator-tables/dist/js/tabulator_esm.js:25567:26)
at UserRacesTableController.createOrUpdateTable (file:///Applications/GranTracker.app/Contents/Resources/app/src/renderer/ui/tabs/userRaces/userRacesTableController.js:356:16)
at UserRacesTabPage.refresh (file:///Applications/GranTracker.app/Contents/Resources/app/src/renderer/index.js:1410:29)Upon reopening, it worked.
Before 2am Mar 12, 2023 we were on standard time when CST is UTC-6. After that it is UTC-5, so my error was against standard time when the week changed at 2am and not daylight savings (or summer time) when it changes at 1am. So on January 23 it was:
Tonight will be:
So if daily races change at 7am UTC (1am CST) how did I record a race at 1:42am CST that was the prior week? Weird.
Don't you just love time zones?
Last edited:
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
I had this happen once too. I have no idea what's wrong. I suspect it's a timing issue of some kind, but it's hard to debug when I can't repeat the error.
As far as the timezone thing is concerned, no, I don't love timezones.
And I have no idea what happened with your race. I'm reasonably sure it's working the way it should work. But honestly, my head's about to explode, so who knows for sure.EDIT: For some reason I missed these comments from you:
Dangit! I forgot about #2, which I could have added in the version I just released (1.3.3). #3 is fixed, though.
I'm working on #1, and it's looking good so far, fingers crossed.
Yeah right, then I'll be done. Here's a couple of things that keep me up at night (figuratively speaking):Anything missing? That's all I can think off and then you'll be done!
1. I combined Car Category and Car Type, because I didn't realize they're different. I need to separate them. And I'm not sure how to find the car types for all cars, unless you own them, and there's no way I'm gonna try to buy all the cars. Although probably nobody cares, it bugs me to have something like that wrong.
2. This is the big one: Distributing new Cars, Tracks and Maps.
Cars aren't that big a deal - you can add them yourself.
Same with Tracks, except for when I want to issue new maps. If you enter a new track yourself, and I have new maps for it, I'm not sure how to sync that up. But I'll figure something out.
Last edited:
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
GranTracker v1.3.3 has just been released.
New Feature
- Exposed a “Zoom” dropdown for changing the zoom factor on tables. It’s in the bottom status bar. It’s mostly for sharing screenshots on social media, to help make screenshots of the tables not quite as wide, but you may want to use it just for readability reasons.
Quality of Life
- Date Range selection process modified so there’s never an invalid date range. In other words, you can’t have a “from date” later than the “to date”.
- In previous versions, if you had an invalid date range, the chart would just paint itself empty, which was confusing (to me, anyway).
- Now if you change one of the date range values to something that would create an invalid date range, the other date value is automatically modified so the range is valid.
Bug Fixes
- Fixed bug introduced in last version where the race timestamps might not have been saved in UTC format. This may have introduced a boundary issue for races on or around the weekly track change.
- The next time you save changes to your races, the file will be fixed so that the timestamps are saved in UTC format.
- So if you think you have an issue with timezones at the start of a race week, modify your race data (for example, double-click a race then click “OK”), then check the timestamp and correct it if needed.
- And in case it’s not obvious, you can change a race’s timestamp by double-clicking the race to edit it, then clicking into the timestamp field and changing it.
- Fixed a bug where under certain situations, you could get an error saying something about “console.logWarn” not being defined.
- Some cosmetic and alignment fixes.
- 2,026
- Bristol, UK
- OJBrit
Adding GTWS to the roster. At the moment I sub in race A as I don't do those but it means I have to try and be creative if there is 2 GTWS in a week.Depending on which version of graph it shows either:
By %
By DR points
Question: what does DR Constrained do in the enter race details line?
So what is still on the to-do list?
Anything missing? That's all I can think off and then you'll be done!
- Graph update
- Add the fastest lap flag
- Center the DR Points column label.
Allowing Jpegs. As the app pumps out the pictures in this mode it means I have to use Photoshop to make them jpgs. Not that time consuming but annoying.
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
I own every car. Perhaps I’ll work it out for you.
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
You can do that now. See https://www.grantracker.com/doc_tips.html.
That was added in v1.3.0. What else you got?
That would be nice, thanks, however, no rush. Everytime I start working on that, I end up stopping because it just isn't used anymore. They used it in some of the early daily races, but they haven't used it in a really long time.
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
Last edited:
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
- 2,026
- Bristol, UK
- OJBrit
Ah I was on too old a version. Thanks.You can do that now. See https://www.grantracker.com/doc_tips.html.
That was added in v1.3.0. What else you got?
That would be nice, thanks, however, no rush. Everytime I start working on that, I end up stopping because it just isn't used anymore. They used it in some of the early daily races, but they haven't used it in a really long time.
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
TheNormsk
Premium
- 2,224
- Wisconsin
- Normsk_VR
Mine does.
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
- 2,026
- Bristol, UK
- OJBrit
Probably. I may have made the decision that I didn't need the upgrade at the time as everything was working o.k.
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
- 1,019
- Italy
@GrumpyOldMan sorry for the late feedback. I just wanted to tell you that I downloaded the very last release, added weekly races and imported results.
Everything was very smooth and effective!
Couple of comments / food for thinking:
Last week I moved from Rate C to D then back to C. I've got the feeling that the game kind of overlaps the grades, meaning that if you are on C and do bad, you lose points but keep staying C, until you continue to do bad, and you get demoted to D mid range. I'm not sure I've seen the same sort of grey area going in the opposite direction.
It's probably impossible to capture this (assuming that it's true) from the progress bar, but I just wanted to mention it.
I value the race# information a lot. Usually take pictures after each race but then move to the usb and to your application days later.
Last week it was exceptional for me with 8 races, which problaly average player does in a day.
I put notes on paper after each race referencing the race#, and I assure to have the race# in the picture I take
I understand that capturing race# may be tricky because involves the willing of having the info shown in the picture, but would be an interesting info also added manually in a specific column
Finally:
it took very short to get used to reference your app as the go-to one. The distance between yours and Kudos is morroless the one between a top 10 Time Trial time and my time, so, yours in an 👽 app
Everything was very smooth and effective!
Couple of comments / food for thinking:
Last week I moved from Rate C to D then back to C. I've got the feeling that the game kind of overlaps the grades, meaning that if you are on C and do bad, you lose points but keep staying C, until you continue to do bad, and you get demoted to D mid range. I'm not sure I've seen the same sort of grey area going in the opposite direction.
It's probably impossible to capture this (assuming that it's true) from the progress bar, but I just wanted to mention it.
I value the race# information a lot. Usually take pictures after each race but then move to the usb and to your application days later.
Last week it was exceptional for me with 8 races, which problaly average player does in a day.
I put notes on paper after each race referencing the race#, and I assure to have the race# in the picture I take
I understand that capturing race# may be tricky because involves the willing of having the info shown in the picture, but would be an interesting info also added manually in a specific column
Finally:
it took very short to get used to reference your app as the go-to one. The distance between yours and Kudos is morroless the one between a top 10 Time Trial time and my time, so
, yours in an 👽 app
GrumpyOldMan
Premium
- 2,004
- Southern California
- dagware
Thanks, I appreciate all the kind words!it took very short to get used to reference your app as the go-to one. The distance between yours and Kudos is morroless the one between a top 10 Time Trial time and my time, so
I actually have an option for this (that is hidden right now), but I didn't like how it looked. But I'll turn it back on for the next release, and you can see if you like it,
I think it would be too hard for me to get the race # out of the picture, because of language differences. But I've been toying with the idea of allowing you to define custom columns, so at least you could have a column for the information. I'll think about it.
Thanks for the feedback! I really appreciate it - keep it coming!
Similar threads
