Czech RepublicThey're still broken in small games too, like Excitebots: Trick Racing.
To me it looks like it's related to fall/impact damage
This is the video in question: https://gamerdvr.com/gamer/demonic5andwich/video/172371717
The game is playable on Steam Deck and Linux via proton. I recommend adding these as platforms. (I play on Linux)
Hi, I've thought about running this game.
When does the timer start/stop?
@PunchSh0t to answer your question; "All Tracks" has been changed to "All Races".
Yes, for the B-Rank category, you can run all of the races in regular excite, and then run diamond nebula in super excite or mirror excite.
For the S-Rank category, you are confinted to Super Excite and Mirror Excite only.
@kagetaro we already have an excite discord: https://discord.com/invite/hFbTa78qsB
I do think a change in moderation is needed if these issues aren't resolved soon. There are runs on the board with incorrect times, and some that don't even qualify for the category they were submitted in.
For example: https://www.speedrun.com/excite_truck/run/y9lqj2vy is not completed in super excite https://www.speedrun.com/excite_truck/run/ywdojl3z has incorrect time due to crashes
There has also been no response to the timer bug: https://www.speedrun.com/excite_truck/thread/pavf4
Additionally, individual level runs can't even add their time correctly because we can't submit time in milliseconds. I brought this up a month ago: https://www.speedrun.com/excite_truck/thread/ibwxc
All of the IL runs on the board need to be fixed because of these issues. I'm willing to do this. This game has the same issues with the in game timer as Excitebots, which I am a moderator of.
Edit: I've contacted @OddPandemonium on discord about the issues we're having and am waiting for a response.
@OddPandemonium the time on this run and the S rank one is 3:06.2 due to the crash at timestamp 3:04 in the video.
The in game timer slows down when the game enters slow-mo mode and no longer reflects real time.
@OddPandemonium This does not meet the requirements for an S rank run. Super Excite mode is required. This run was done in regular Excite.
I agree with kagetaro about adding a 'Excite Race - Excite - B Rank' category and 'Excite Race - Excite - S Rank' like we have in Excitebots.
It would be nice to use variables like in excitebots to have runs that require all B rank and runs that require all S rank runs.
It would be nice to get some input from other runners in order to build a consensus to add milliseconds to the board.
The fact that the in game timer for individual runs goes to deciseconds, and that crashing bugs the in-game timer and makes runs have to be frame timed in order to be accurately timed makes this pretty important.
Can we please add milliseconds to the leaderboard? The in game timer measures up to deciseconds.
Hello, I'm writing this on behalf of the moderation team of Excitebots: Trick Racing ( @esoterics, @TopStar, @Gamebuster1990 ).
On February 2, 2020, an issue was discovered with our game's in-game timer. After crashing, the slow-motion effect of the game also slows down the timer, causing it to be out of sync with real time.
I.E. Crashing makes your run appear faster than it actually is.
Today, we have discovered that this effect is even more pronounced in Excite Truck, because it takes more time to get out of slow-motion (you have to press 2 repeatedly, instead of shaking the wii remote like in Excitebots).
Link to youtube video:
As you can see, excite truck thinks the above run is 14 seconds faster than it actually is.
This bug only occurs if the runner crashes, in all other instances, the timer remains accurate.
Also another thing to note: We're not sure about Excite Truck, but in ExciteBots, sometimes crashing is faster than not crashing even when taking this into account, so we didn't ban runs with crashes.
Because of this, we frame time every run where the runner has crashed. Of course, how you choose to handle this bug is up to you.
Sincerely, The Excitebots moderation team
Excitebots: Trick Racing
The WR history graph for IL runs in Excitebots is still broken months after I filed a bug report. I even looked through the code and specifically pointed out what could be wrong. I even submitted it through the old feedback form (https://docs.google.com/forms/d/e/1FAIpQLSf6G5kHeooo1K11C8WMREf69P_Pv3X4i5DKOjLtUCcDSTreNQ/viewform), and never got a response, not even a "we recognize you have submitted an issue".
Now you've locked the feedback thread and site bug threads, so now there isn't even a real place for users to talk and/or look for these things. It doesn't matter if you don't use it, being able to read about the suggestions and issues people are having with the site adds a layer of transparency. All that locking the threads does is make it harder to discuss issues and improvements with the site.
My third major reason for leaving: the way you have implemented advertisements is stupid, lazy, dangerous, and insecure.
The advertisements are ugly and don't fit the theme, and they shift elements of the page so they're inconsistent between reloads, or they load right before you're about to click on something, and the content you were about to click gets shifted down, which makes you click on it.
ADVERTISEMENTS ARE ON THE LOGIN PAGE. WHERE YOU ENTER YOUR PASSWORD. THIS IS EXTREMELY BAD PRACTICE! DON'T EVER, EVER DO THIS! I'm not going to bother wasting my time for this, so I'll give you the benefit of the doubt and say they're running in a sandboxed iframe. Even if they are running in a sandboxed frame, all it takes is one exploit found to escape the sandbox, and everyone's login info is stolen.
It was already bad enough having the twitch stream and twitter feeds on the login page, but at least you (and twitch) control what code is run there. Having the possibility of just anyone run whatever code they want on the login page is just inexcusable. You shouldn't have any third party scripts running on the login page, period. https://security.stackexchange.com/questions/214784/can-ads-on-a-page-read-my-password
I will not support a company that is so blatantly incompetent, with my content.
The reason why the history graph for IL records breaks is because some of the datasets are undefined.
Specifically in the updateDatasets() function, it tries to get the length of a undefined dataset.
I don't know if it's valid for dataset to be undefined. If it can be undefined under normal circumstances, then a simple !== undefined check should suffice...
If the dataset should never be undefined in the first place... well then obviously you're having a different issue.
I have a stacktrace here if it helps: https://pastebin.com/8ZejjQuc
Just a friendly reminder that the statistics page for IL runs are still broken: https://www.speedrun.com/the_site/thread/o7k5n
I didn't post it in the correct thread last time so here it is :)
My apologies, I'll use that thread next time.
I suspect it may be trying to load some of the data from the Full Game Leaderboards instead of the Individual Level Leaderboards, as clicking on runs seems to only take me to Full Game runs, and never any IL runs, even when clicking on an IL run.
