lapcounter uses estimated time remaining when estimated is unchecked
Dustin Ollis wrote:That's... not what I was asking at all.
Make sure the dropdown at the top of the binding properties is set to automatic or laps...
I want it to show time remaining in the session using the lapcounter binding, however using time remaining shows estimated time remaining independent on whether "Use estimated" is checked or unchecked.
I will look into this, but it would help to know what kind of session you hosted in terms of race length. Was it decided by lap count or time limit, and which one would be reached first realistically? I believe there is logic in the estimation that checks:
- If you want to show time remaining
- but the race will be limited by the lapcount
- then show the estimated time remaining instead
Otherwise, you may have a session that is set up to take 2 hours, but only 4 laps. Then the time remaining would show 2 hours instead of only ~10 minutes which it takes to complete the 4 laps.
- If you want to show time remaining
- but the race will be limited by the lapcount
- then show the estimated time remaining instead
Otherwise, you may have a session that is set up to take 2 hours, but only 4 laps. Then the time remaining would show 2 hours instead of only ~10 minutes which it takes to complete the 4 laps.
Let's take a race that's both 30 minutes and 20 laps.
I default the ticker to show how many laps are left. However, if there's a lot of caution periods and it seems like we'll be close to hitting the time limit instead, I like to show the time remaining and laps remaining at the same time. I use two lapcounter bindings, one for lap x of y and laps to go, and one showing the time remaining in the race. The problem is ATVO shows estimated time remaining and not actual time remaining, even if you have "Use estimated" unchecked, so what I was showing wasn't actually accurate to what the server showed.
I know I can just use a timeremaining binding on its own, but I like being able to use the lapcounter binding because of the ability to customize what it shows.
I default the ticker to show how many laps are left. However, if there's a lot of caution periods and it seems like we'll be close to hitting the time limit instead, I like to show the time remaining and laps remaining at the same time. I use two lapcounter bindings, one for lap x of y and laps to go, and one showing the time remaining in the race. The problem is ATVO shows estimated time remaining and not actual time remaining, even if you have "Use estimated" unchecked, so what I was showing wasn't actually accurate to what the server showed.
I know I can just use a timeremaining binding on its own, but I like being able to use the lapcounter binding because of the ability to customize what it shows.
Edited (1 time)
In this situation you described, what is the difference between estimated time remaining and actual time remaining? If my calculations are correct, then ATVO should have figured out that you will not reach the lap limit, and instead "estimate" that the race will end by the time limit. In that case it should use the (actual) time limit. It will call it estimated because it's estimating that the lap limit will not be reached, and the race will instead end by the time limit.
Of course it's possible the calculation was off and it is showing something else, but I'm still a bit confused what the issue is now. If there are 5 minutes left in the race, and still 30 laps to go (just an example), both time remaining and estimated time remaining should be the same: 5 minutes.
I will check my code again, I built this a long time ago. Perhaps estimated time remaining is calculating first how many laps remaining (let's say: 6 laps in those 5 minutes), and then estimating again how much time that will take (let's say 5:16 instead of 5:00). Could be that this is happening...
Sorry, the reason I want to make it clear is because this code is intended to work for the most basic purposes and I think there was a good reason why it "forces" estimated time remaining in some cases. If you can convince me that that's wrong I will see how to fix it.
Of course it's possible the calculation was off and it is showing something else, but I'm still a bit confused what the issue is now. If there are 5 minutes left in the race, and still 30 laps to go (just an example), both time remaining and estimated time remaining should be the same: 5 minutes.
I will check my code again, I built this a long time ago. Perhaps estimated time remaining is calculating first how many laps remaining (let's say: 6 laps in those 5 minutes), and then estimating again how much time that will take (let's say 5:16 instead of 5:00). Could be that this is happening...
Sorry, the reason I want to make it clear is because this code is intended to work for the most basic purposes and I think there was a good reason why it "forces" estimated time remaining in some cases. If you can convince me that that's wrong I will see how to fix it.
https://youtu.be/Z0jUPLbiqpg?t=2616
Here's a specific example and what triggered this topic.
Race was set to 50 minutes and 40 laps. I admittedly forgot it was 50 minutes and was thinking it was 40 instead, so I was checking the time shown on the ticker and thought there was 10 minutes left as it said, but halfway through the backstretch it set itself back to 10:59, which shows that it was actually on estimated time instead of actual server time. I believe there was actually about 20 minutes left in the session at this time.
Here's a specific example and what triggered this topic.
Race was set to 50 minutes and 40 laps. I admittedly forgot it was 50 minutes and was thinking it was 40 instead, so I was checking the time shown on the ticker and thought there was 10 minutes left as it said, but halfway through the backstretch it set itself back to 10:59, which shows that it was actually on estimated time instead of actual server time. I believe there was actually about 20 minutes left in the session at this time.
Edited (1 time)