B-Spec Grinder 2.5.2: Automate Remote Races

  • Thread starter yonis
  • 4,266 comments
  • 562,479 views
Anybody having server issues, use the Ireland one. I'm guessing the reason why I never had any problem with the widget is that this server is probably quieter than the others.
 
Mine ran flawlessly all yesterday and last evening. I went to bed at 3AM. The last race run before something went wrong ended at 3:10AM. I wish I could figure out what is going on. Every night I leave this thing running and every night I get booted from the server in the 3AM - 5AM window. I had the debugger running, but when I enlarged the window it was blank and stayed blank.

I thought maybe sleep mode was the issue, but yesterday I purposely let the computer go into sleep mode (for 2 hours no less) and had no issues.
 
1.1.3 (w/new dubugging window) and has been running fine all 16 slots continue to be filled...cant wait for to be able to select Yonis' drivers to always be in use...Great app once again (tip'd hat)
 
Mine has been running flawlessly all day, great app, I saw somewhere someone had posted what events got the best credits/xp. Is it possible if you could make it so it raced those ones only, since most people are only using this app to make more money.

Otherwise great work with the widget, loving it, the next update idea looks amazing.

Edit: I have had another awsome idea, could you implement a think saying what position you are in, (kinda like the lap counter).
 
Last edited:
Mine has been running flawlessly all day, great app, I saw somewhere someone had posted what events got the best credits/xp. Is it possible if you could make it so it raced those ones only, since most people are only using this app to make more money.

Otherwise great work with the widget, loving it, the next update idea looks amazing.

Edit: I have had another awsome idea, could you implement a think saying what position you are in, (kinda like the lap counter).

Lighted helmet shows your position. Moving the cursor over the helmets shows who is driving and what they are driving. Move cursor over the credits and it will give your driver credit breakdown.
 
Lighted helmet shows your position. Moving the cursor over the helmets shows who is driving and what they are driving. Move cursor over the credits and it will give your driver credit breakdown.

Wow I never knew that, I thought it was just random to make it look nice.

Awesome.
 
It's probably not possible but well: is there any option to set a preferred race? I'd like to use the Le Mans race only.
 
It's probably not possible but well: is there any option to set a preferred race? I'd like to use the Le Mans race only.

I'm sure it is possible but to be honest this would be wayyyyyy down the list of things to do. Besides, PD will probably change the races again in a month or so and the coding would get all messed up again.
 
Unfortuntely, although the widget - v.1.1.3 - is working this evening for me personally, it's not selecting a full 16 drivers which is a shame. Still, it's working which is the main thing.

Yonnis - running new debug version for you.
 
I'm sure it is possible but to be honest this would be wayyyyyy down the list of things to do. Besides, PD will probably change the races again in a month or so and the coding would get all messed up again.

True - it might be possible to pull the track names from the server and add them to a drop-down menu, tho. I don't have the necessary insight but depending on how the widget is starting the race, it might be possible.

Then again, not too important since all long distance races have more or less the same payout, I guess.
 
getting temporary server issue sporadically. Been restarting the widget pretty regularly.

If I just let it go and cycle on its own, eventually it will successfully start a race, but at a rate of about 1 per hour instead of every 20 mins.
 
I've analyzed the issue that prevents the use of the Widget.

The issue is that when the Widget is reserving drivers, the server responds with a "200 OK" response code, which should mean that everything is OK. However, later on, when the Widget attempts to book a race, it turns out that the server hadn't reserved any drivers, as verified through a few debugging reports. A similar but less common version of this bug is that the server will reserve the drivers and even verify that they've been reserved, but it still won't allow us to start the race. I am adding a test to version 1.5 which will check for this problem.

One forum member graciously allowed me to access his account so I could try to see the issue firsthand, and attempt to see how the official Remote Race page coped with that error. Alas, 14 perfect races later, I gave up trying to reproduce the problem there.

I'm estimating that the Widget has around 1,200 active users. Based upon the number of people who are posting in this thread that they have this issue, I'm concluding that, though serious, the problem affects a small subset of users. And even then, it only appears to be sporadic. Due to the nature of the bug being server-based, there is not much I can do to fix it, either.

Some users have stated that one of the versions in the 0.9 series was the most reliable for them. I can retrofit the most stable version in that series with the new authentication code in the hopes that it will work better for you, but I won't be able to add the new driver selection feature into it. [EDIT: Done, here's the link...]

If you are affected by this bug and you've sponsored development, I'd be happy to refund your money — send me a PM with the PayPal email address you donated with and I'll get that processed for you.
 
Last edited:
I've had almost no trouble with v1.1.3. I always run the debug window to see what it has done, and very little problems so far, much less than previous versions.

So no, I don't want my money back :sly:

Any idea when we can expect friend selection though?
 
he Yonis maybe it would be nice to see what time the race started.
so you can see its not stuck or having issues or still working properly.

as i noticed that most people use the debug mode for that. (me to)

but the site works better to,... witch make the app. work flawless.
but I'm still checking the times to make sure its running ok.
 
Very good of you to offer refunds Yonis but personally, I really don't think that's necessary.
v.1.1.3 has worked for me without any connection issues over the last few night and I think a good, stable connection is much more important than a full 16 driver selection for, of course, without the connection there'd be no race anyway.

I'm happy to sacrifice a few drivers per race for an always-connecting widget. I'd also rather have the option of allowing some drivers permanently while others can perhaps be ommited from selection, so personally, I look forward to your next version. I would also be happy to give the v.1.5 widget a try, so you may at least get some debug info from it.

Many thanks for all your efforts.
 
I've analyzed the issue that prevents the use of the Widget.

The issue is that when the Widget is reserving drivers, the server responds with a "200 OK" response code, which should mean that everything is OK. However, later on, when the Widget attempts to book a race, it turns out that the server hadn't reserved any drivers, as verified through a few debugging reports. A similar but less common version of this bug is that the server will reserve the drivers and even verify that they've been reserved, but it still won't allow us to start the race. I am adding a test to version 1.5 which will check for this problem.

One forum member graciously allowed me to access his account so I could try to see the issue firsthand, and attempt to see how the official Remote Race page coped with that error. Alas, 14 perfect races later, I gave up trying to reproduce the problem there.

I'm estimating that the Widget has around 1,200 active users. Based upon the number of people who are posting in this thread that they have this issue, I'm concluding that, though serious, the problem affects a small subset of users. And even then, it only appears to be sporadic. Due to the nature of the bug being server-based, there is not much I can do to fix it, either.

Some users have stated that one of the versions in the 0.9 series was the most reliable for them. I can retrofit the most stable version in that series with the new authentication code in the hopes that it will work better for you, but I won't be able to add the new driver selection feature into it.

If you are affected by this bug and you've sponsored development, I'd be happy to refund your money — send me a PM with the PayPal email address you donated with and I'll get that processed for you.

Is it better to let the widget try and restart it's self, or should I do it manually, when this issue shows up?
 
Hi guys, first I want to thank yonis for his fantastic work. I'm using the widget, didn't have any problem but I notice that Uk server fill the races with more drivers than others. I only tried the servers from US, Spain and UK, and the last is by far the best. I live in Spain by the way, don't know if that has anything to do. I hope it helps.
 
Looks like I hobbled through the night....20 minute load, 20 minute race, 20 minute load....Sarthe is being ignored completely.....makes sense as I'm sure it's getting the most pressure...

Will close and restart everything this morning and report back later....

EDIT: OK...just ran three races in a row, 2 full, 1 with 10 drivers... I saw Bongo's post about allowing third party cookies and that fixed my conflict with logging in to GT website.....
 
Last edited:
Really having trouble with the latest version, didn't have any issues with older versions. I think it may have run 1-2 races before getting the temporary server issue each time I've tried to run it. Once it gets the server issue, I don't think it starts another race, as far as I can tell. Any help would be appreciated, I'm guessing the problem is something on my end.:ill:

As a last resort, I have started a remote race right from gran-turismo.com US and then I started the widget, just to see if it will continue with starting another race... looks like the widget started another race. Hope this works and it continues to start races.:nervous:

Well, that didn't work either, back to the temporary server issue. Sending the log your way yonis.
 
Last edited:
i haven't had any issues whatsoever with the last 2 - 3 new widgets, can't say why tho :)
 
i just got an error popup.

B-Spec Grinder

!!!!! PLEASE REPORT THIS ERROR ON THE GTP FORUMS. !!!!!

The server redirected the Widget to a hostname outside of its security sandbox. The full URL it was told to go to is:

$redirect_url.replace('signout/','')

Please report where the Widget was told to go, and which stage it was at in the process. After you close this message, you will be notified of a security violation.
 
Lots of Temporary Server Issue's here tonight too - various country servers - v.1.1.3

EDIT:
Managed to find a decent server and al is well here.
 
Last edited:
hey guys, no problems today either

but i'm wondering how to bring up the debug window

how do i do this?

When the Yahoo widget software is running - not Yonis' grinder - hold CTRL and SHIFT, then right-click the Yahoo widgets icon in the taskbar. Select Debug Mode.
 
Back