If you know of anyone else with similarly high B-Spec credits, please get them in touch with me as I'd like to compare notes.Some people (not me, unfortunately) are just shy of $40 Million.
I suppose you could write a browser extension or a Greasemonkey script to automate races... But I see no significant benefit to doing that.
If you know of anyone else with similarly high B-Spec credits, please get them in touch with me as I'd like to compare notes.
And I should hit 40M in the BoB in the next few days.
To begin with, having more than 4 posts would help
I suppose you could write a browser extension or a Greasemonkey script to automate races... But I see no significant benefit to doing that.
Actually, I see one benefit from a browser extension. It would probably work with Linux.
So Yonis, any update on a new version release??
.I assume you mean driver selection. I still don't know yet, but I'll give another status update.
Right now, as you saw in the YouTube video I posted a few pages back, I've hooked up the UI for rearranging friends and drivers. I've also started work on the backend for saving all your settings made in that window, and I've also implemented the setting which automatically reciprocates racing for friends who use your drivers.
Next up is adding the always/sometimes/never use groups to the list and saving settings.
Now this is whack....
I start the widget this morning....just checked 1 hour later and I'm on the same race and same point in the race every time I check...it's Groundhog Day....
This happened to me during server maintainence. There are a couple of procedures that may fix it.
I am too! I've never, ever seen this issue on 1.1.3 on my computer at home. I have one theory as to why it doesn't work which I'm testing with someone right now, which is that 0.9.1 reserves drivers differently from 1.1.3; 0.9.1 waits for a few seconds between fetching a driver list and reserving drivers, because it fetches every single driver list from every single friend before reserving drivers. 1.1.3 acts more human-like in that it fetches a friend's driver list, immediately reserves drivers, and then fetches another list if it needs more drivers. But this means that the delay that's present in 0.9.1 is gone. So this debugging version adds a delay which gets progressively longer each time it fails to start a race, to see if a delay has any weight at all in this matter. You can change the delay to any arbitrary number of seconds by typing CONFIG.delay = 10; into the debug window, where 10 is the number of seconds — You can change that to any number (just don't try to set it to anything below 1 or above 25).I had 1.1.3 running for all night, no races started, reloaded a few times today, no race started.
Now tried the 0.9.1 with new authentication, it started a race right away.
I'm confused...
The Widget currently doesn't cache any data. Right now it just fetches your friends list when it first launches — if your list changes later, you need to reload it for now (as you did).Where does the grinder widget cache input (mac version)? I ask because I un-friended someone on my ps3, but the grinder is still running drivers from that user. Very strange because I logged in the remote racing site, the un-friend does not show up, but his drivers are able to participate in my races via the grinder.
The API sent the Widget the ID of a race that isn't your own. It's a known problem for which I have a workaround built into the Widget, but it takes a few minutes for the API to send us the correct B-Spec monitor ID.I closed the widget, re-opened it, and a race showed up that wasn't even mine, with drivers/users who are complete strangers. Closed the widget again and re-opened and they went away. I get the feeling that the remote racing api is not doing much checking on session ids.
only one bob will join races, what are iam doing wroong ?💡
Just one question, what happens if I have to shut down my PC while it's halfway through a race?
In my testing, 14 seconds fails, 14.25 seconds works.I am too! I've never, ever seen this issue on 1.1.3 on my computer at home. I have one theory as to why it doesn't work which I'm testing with someone right now, which is that 0.9.1 reserves drivers differently from 1.1.3; 0.9.1 waits for a few seconds between fetching a driver list and reserving drivers, because it fetches every single driver list from every single friend before reserving drivers. 1.1.3 acts more human-like in that it fetches a friend's driver list, immediately reserves drivers, and then fetches another list if it needs more drivers. But this means that the delay that's present in 0.9.1 is gone. So this debugging version adds a delay which gets progressively longer each time it fails to start a race, to see if a delay has any weight at all in this matter. You can change the delay to any arbitrary number of seconds by typing CONFIG.delay = 10; into the debug window, where 10 is the number of seconds You can change that to any number (just don't try to set it to anything below 1 or above 25).
The Widget currently doesn't cache any data. Right now it just fetches your friends list when it first launches if your list changes later, you need to reload it for now (as you did).
The API sent the Widget the ID of a race that isn't your own. It's a known problem for which I have a workaround built into the Widget, but it takes a few minutes for the API to send us the correct B-Spec monitor ID.
It went away in about 30 minutes, must have been a sync issue on the PD side of things...The Widget currently doesn't cache any data. Right now it just fetches your friends list when it first launches if your list changes later, you need to reload it for now (as you did).
size="12"color="#FFFFFF" />
I noticed a slight bug in GT5.kon, line 212, needs a space after size="12":
Code:size="12"color="#FFFFFF" />
You can change the delay to any arbitrary number of seconds by typing CONFIG.delay = 10; into the debug window, where 10 is the number of seconds — You can change that to any number (just don't try to set it to anything below 1 or above 25).