- 564
- new mexico
- fissionproject
only problems i'm having is when PD servers have problems
Temp. server issues and what not
ugh.
Temp. server issues and what not
ugh.
Well..I just took down the remote to make a trade at reset, and before I fired remote back up I reset my Bob value to '0', since I'm only drawing from my alt accounts at the moment...fired it up and have a full 16 man field for the first race, with no server interruption...
But that raises a question...since I'm not borrowing Bobs from across the globe it seems to me I'm cutting out a myriad of connection issues others may be experiencing when dealing with service providers and servers on different continents.....
v.1.1.3 has been solid for 2 hours ...but, it is not filling all 16 driver slots (10, 11, even just 6) and only appears to be choosing drivers from about 4 or 5 friends out of 11.
I'm getting full fields, but noticing I'm getting 4 and 5 drivers from the same people, not a wider swath of friends. I don't remember it being like this with the previous version, but then again I hadn't used the widget a lot before the recent update.
Not sure if there is anything that can be done. If the user is allowed to select a max # of drivers from any one person it may lead to half full events.
For instance I'm hosting a race right now and it is full, 16 drivers, but only from 7 different profiles (mine included). That 7 is from a field of 55 (including me).
I'm getting the same sort of thing, the bob's loaded are usually from the same group of friends with a few less popular friends (according to the widgets selection of bob's) included every now and then.
Wishlist: An option perhaps to include only one driver from each friend, with double/triple selection from one friend only occuring if you dont have enough different friends with bob's available.
Not sure how hard this would be to implement but it would be a fantastic addition IMHO...I like to share the bob grinding love
Awesome tool regardless, keep up the great work!! 👍
I'm still considering it, but it's tricky because when Polyphony updates the events, they replace them all. So I need to figure out a way to not be dependent on the user's preferences in case there's a change.regarding your next update, any plans on making it possible to select which races to run (or which not to run)?
I've finally figured out how the payout scheme works for the remote races, and some races do pay a lot better than others. The max payout for the Nuerburgring, for example, is only $15,220, while the max payout for Le Sarthe is $23,490. Naturally, if you run this widget to make money, you'd be better off running more Le Sarthe, and less Nuerburgring. So having an option in the widget to tell it what to run (or what not to run), would be a very nice feature indeed. Would allow us to earn money even quicker, given the races all take about 20 minutes.
I'm still considering it, but it's tricky because when Polyphony updates the events, they replace them all. So I need to figure out a way to not be dependent on the user's preferences in case there's a change.
I believe the experience is more dependent upon how many places your driver overtakes during the course of the race If he starts out in 16th and ends in 4th, I think you earn more than if he starts in 12th and ends in 11th.
only problems i'm having is when PD servers have problems
I'm also having the problem where the 16 places won't be filled (right now it's running with only 9), although I have lots of available Bobs from around 15 friends...
I host on an alt account with few friends and seem to have MUCH better reliability.
I'm getting full fields, but noticing I'm getting 4 and 5 drivers from the same people, not a wider swath of friends.
I'd have to agree that this has nothing to do with not enough drivers being available, they're available, they're simply not picked up (or not picked up in time?).
It seems like it eventually rolls through all my friends, it just loads up races with limited people. Over several hours it seems like it evens out...
I dug around in Polyphony's own JS to try and find some debugging code that I could use in the Widget, and I did find an API call that lets me confirm which drivers are being reserved. One of my suspicions is that your own driver is not being reserved when the server says that it was. Another of my suspicions is that the time spent reserving drivers is either too fast or too slow and the server is either not able to keep up or is sitting around waiting on your connection and it gives up, respectively.it is not filling all 16 driver slots (10, 11, even just 6) and only appears to be choosing drivers from about 4 or 5 friends out of 11.
I dug around in Polyphony's own JS to try and find some debugging code that I could use in the Widget, and I did find an API call that lets me confirm which drivers are being reserved. One of my suspicions is that your own driver is not being reserved when the server says that it was. Another of my suspicions is that the time spent reserving drivers is either too fast or too slow and the server is either not able to keep up or is sitting around waiting on your connection and it gives up, respectively.
I've developed another debug version which helps me test both of these hypotheses. When you see a problem, copy the output, paste it into Pastebin, and PM me the link.
If no common patterns emerge, I will retrofit one of the 0.9 series with the new authentication code so I can get some readings there whichever version worked the best for people and try to find out why that version worked and the newer ones don't.
DCSemiWhat if some of your friends' bobs are already used by others? I mean, the friends you got on your friend list, these guys also have friends who can remote race and stuff...
Does she? Where exactly are you getting your information from then? (possibly a tad of bitterness speaking?)Aye, that might be her problem, she tends to delete people if they're not remoting within 2 hours of being added on psn.
Is 1.5 million (ave) per 24 hrs a small return to you?Small friends list = small returns from remote racing.
v.1.1.3 has been solid for 2 hours ...but, it is not filling all 16 driver slots (10, 11, even just 6) and only appears to be choosing drivers from about 4 or 5 friends out of 11.
Yes, I see your point, but I have just manually started a race where there were more than enough Bob's available for a full 16 driver race - this was only 25 minutes after the last widget-run race. I doubt that's just coincidence.
👍 For the record, my v.1.1.3 widget ran flawlessley last night. Not one 'Temporary Server Issue'. I'm sure all my friends - those who actually remote race back as opposed to ^others - will be very grateful too!For you, maybe.
I left my widget running at approx.1am last night. My last widget race was at approx.2:30am and it never ran again all night. Incidientally, the error was 'Temporary Server Issue'.
Since 10pm last night the widget has neded approx 20 minutes to reload a race...to what would I attribute this? Every kid in South Florida is gaming tonight severely impacting broadband usage....
I'm still of the mind that all these issues are partly, if not fully caused by both the Sony servers hiccuping and possibly Sony's attempts to make life difficult for widget use.
Yesterday I had widget errors, last night it ran flawlessly. For you it was the opposite; yesterday you were praising it, today you have problems. You live in the US, I live in the UK. There has to be a constant in all this and I think it's Sony.
This is on it's way: https://www.gtplanet.net/forum/showthread.php?p=5003677#post5003677It'd be nice if you can add the ability to block certain PSNs from being added to your list. Or even better, have it show preference to certain PSN users.
So the ones that race your Bobs get preference.
And the ones that don't return the favor get blocked.