Title: Glitch?
Description: Fatigue points and destination
Stinky - November 19, 2008 12:26 AM (GMT)
Me and 1 of my drivers are having problems with our fatigue points - he was at 0, went up to 5 but it said 10.....several times a similiar thing has happened to me - from 7 to 10 or 8 to 10 and once from 8 to 6. He went from Jacksonville to New Orleans, then back to Jacksonville, then was going back to New Orleans but wound up in Charlotte...... Is this a glitch? He's the only one of my drivers who has said this was happening. It's been happening over a week to me but I didn't say anything because I thought I just didn't see the numbers right. Can anything be done to correct this?
100 Trucker - November 19, 2008 12:47 AM (GMT)
| QUOTE (Stinky @ Nov 19 2008, 12:26 AM) |
| Me and 1 of my drivers are having problems with our fatigue points - he was at 0, went up to 5 but it said 10.....several times a similiar thing has happened to me - from 7 to 10 or 8 to 10 and once from 8 to 6. He went from Jacksonville to New Orleans, then back to Jacksonville, then was going back to New Orleans but wound up in Charlotte...... Is this a glitch? He's the only one of my drivers who has said this was happening. It's been happening over a week to me but I didn't say anything because I thought I just didn't see the numbers right. Can anything be done to correct this? |
maybe a glitch :explosion: i dont know but i remember this happend to someone else
Mr Bear - November 19, 2008 01:01 AM (GMT)
| QUOTE (Stinky @ Nov 18 2008, 07:26 PM) |
| Me and 1 of my drivers are having problems with our fatigue points - he was at 0, went up to 5 but it said 10.....several times a similiar thing has happened to me - from 7 to 10 or 8 to 10 and once from 8 to 6. He went from Jacksonville to New Orleans, then back to Jacksonville, then was going back to New Orleans but wound up in Charlotte...... Is this a glitch? He's the only one of my drivers who has said this was happening. It's been happening over a week to me but I didn't say anything because I thought I just didn't see the numbers right. Can anything be done to correct this? |
Holy Crap! Talk about weirdness! Wow I would be pissed if that happened to me.
-Mr Bear
100 Trucker - November 19, 2008 01:03 AM (GMT)
| QUOTE (Mr Bear @ Nov 19 2008, 01:01 AM) |
| QUOTE (Stinky @ Nov 18 2008, 07:26 PM) | | Me and 1 of my drivers are having problems with our fatigue points - he was at 0, went up to 5 but it said 10.....several times a similiar thing has happened to me - from 7 to 10 or 8 to 10 and once from 8 to 6. He went from Jacksonville to New Orleans, then back to Jacksonville, then was going back to New Orleans but wound up in Charlotte...... Is this a glitch? He's the only one of my drivers who has said this was happening. It's been happening over a week to me but I didn't say anything because I thought I just didn't see the numbers right. Can anything be done to correct this? |
Holy Crap! Talk about weirdness! Wow I would be pissed if that happened to me.
-Mr Bear
|
Yea i KNow i would be throwing the eggs at my truck
100 Trucker - November 19, 2008 02:23 AM (GMT)
| QUOTE (Mr Bear @ Nov 19 2008, 01:01 AM) |
| QUOTE (Stinky @ Nov 18 2008, 07:26 PM) | | Me and 1 of my drivers are having problems with our fatigue points - he was at 0, went up to 5 but it said 10.....several times a similiar thing has happened to me - from 7 to 10 or 8 to 10 and once from 8 to 6. He went from Jacksonville to New Orleans, then back to Jacksonville, then was going back to New Orleans but wound up in Charlotte...... Is this a glitch? He's the only one of my drivers who has said this was happening. It's been happening over a week to me but I didn't say anything because I thought I just didn't see the numbers right. Can anything be done to correct this? |
Holy Crap! Talk about weirdness! Wow I would be pissed if that happened to me.
-Mr Bear
|
try to get a screen shot on it next time :)
War Man - November 19, 2008 02:49 AM (GMT)
The thing about winding up in Charlotte- most likely not a glitch. He probably accidently went to the wrong city. I am not sure about the fatigue thing, though.
-WarMan v2
Stinky - November 19, 2008 07:22 AM (GMT)
| QUOTE (Stinky @ Nov 18 2008, 07:26 PM) |
| Me and 1 of my drivers are having problems with our fatigue points - he was at 0, went up to 5 but it said 10.....several times a similiar thing has happened to me - from 7 to 10 or 8 to 10 and once from 8 to 6. He went from Jacksonville to New Orleans, then back to Jacksonville, then was going back to New Orleans but wound up in Charlotte...... Is this a glitch? He's the only one of my drivers who has said this was happening. It's been happening over a week to me but I didn't say anything because I thought I just didn't see the numbers right. Can anything be done to correct this? |
Can someone tell me how to get in touch with an admin?? This is getting really bad and nothing's been done yet so I guess this is the wrong place to report such a glitch. I just was at 7 - bought 2 fatigue points - took me to 5 - clicked to 10 - went to check the ledger and dispatch view of my company - we've been having problems with the truck's condition NOT increasing when the drivers purchased items that are supposed to raise the condition - several are having THAT problem.....anyway, I went back to my driver to check my truck's condition and my fatigue points are at 12!!!!
Somebody please correct this glitch.
jefffan24 - November 19, 2008 11:26 AM (GMT)
When you buy something to raise your trucks condition you have to repair the truck in order to get its benefits.
Stinky - November 19, 2008 05:55 PM (GMT)
| QUOTE (jefffan24 @ Nov 19 2008, 06:26 AM) |
| When you buy something to raise your trucks condition you have to repair the truck in order to get its benefits. |
They do repair - some several times while in route - we're a new company and most are on their 2nd or 3rd trucks. So it isn't that. And about the guy going to Charlotte --- I checked my dispatch page and he's doing the route he's supposed to be doing ( Jacksonville/New Orleans), I go to bed, first thing when I get up I check my company and he's coming back from Charlotte. Not possible without a glitch - not enough actual hours.
jefffan24 - November 19, 2008 06:11 PM (GMT)
Well first off they are not in the greatest trucks, they are going to lose condition fast...
Secondly the Charlotte thing, it looks like it only happened once and now its fixed he's heading to new orleans
As for the Charlotte thing...its odd b/c look at the arrival times for 2 of his routes...
When he "supposedly headed to charlotte" -
[Departed Date] 11/18/2008 8:39:30 AM
[Expected Arrival] 11/19/2008 4:48:05 AM
When he "supposedly arrived to Charlotte and was leaving for new orleans" -
[Departed Date] 11/18/2008 8:44:46 AM
[Expected Arrival] 11/19/2008 4:53:20 AM
There is only like a 5 min difference and there is 770 miles in between Charlotte and New Orleans
I can not explain that one :P Maybe a glitch.
Stinky - November 19, 2008 06:53 PM (GMT)
So who deals with glitches? I haven't heard from an admin. I sent 'admin' here a PM last night - he opened it this morning at 10:32 AM. Who else can I get in touch with to fix this and where else can I post to get whomever's attention that's supposed to fix this? I must be doing it wrong. There's definitely a glitch and it definitely needs fixing.
jefffan24 - November 19, 2008 07:11 PM (GMT)
When he gets on the forums he will look into it.
Deano - November 19, 2008 09:07 PM (GMT)
| QUOTE (jefffan24 @ Nov 19 2008, 06:11 PM) |
Well first off they are not in the greatest trucks, they are going to lose condition fast...
Secondly the Charlotte thing, it looks like it only happened once and now its fixed he's heading to new orleans
As for the Charlotte thing...its odd b/c look at the arrival times for 2 of his routes...
When he "supposedly headed to charlotte" - [Departed Date] 11/18/2008 8:39:30 AM [Expected Arrival] 11/19/2008 4:48:05 AM
When he "supposedly arrived to Charlotte and was leaving for new orleans" - [Departed Date] 11/18/2008 8:44:46 AM [Expected Arrival] 11/19/2008 4:53:20 AM
There is only like a 5 min difference and there is 770 miles in between Charlotte and New Orleans
I can not explain that one :P Maybe a glitch. |
If he was at 0fp when leaving for charlotte, 770 miles is easily done in 5 mins by using the quick rest. It would only take just over a 64mph average to do the run in 12 legs, being in the south the weather should've been ok and I guess he managed it in 11 legs, average of 70mph.
jefffan24 - November 19, 2008 09:55 PM (GMT)
But how did he at Leave from from the first and second one within 5 min of each other (same day) and arrive withing 5 min of each other on the same day????
Thats what I'm talking about look at the dates and times
Knockoff Norman - November 19, 2008 11:52 PM (GMT)
Expected arrival is just the time the load becomes late, not when the driver actually arrived. The only times you need to look at are the depart times. As the late time is calculated from the start time the two sets have to be the same timeframe apart given that the routes are between the same two cities.
Also your sig is wrong. 35% Fuel + Fuel discount is equivalent to 41.5% as 3.5% of the discount effectively goes to the company.
The discount takes 10% off the price of fuel, the company then pays for 35% of the remaining 90% and the driver pays for 65% of the 90%.
jefffan24 - November 20, 2008 12:32 AM (GMT)
Stinky - November 20, 2008 12:35 AM (GMT)
This is what he wrote after it happened, "Twice today I went from a level 0 to exhausted with very few clicks of the next leg button. I was on my way back from Jacksonville last night, and the next morning I find myself in Charlotte NC."
Also, I check where all my drivers are before I go to bed every night and he was on the route I had told him to run = New Orleans/Jacksonville = in route - not at either city. The next morning he was going from Charlotte to New Orleans. Doesn't matter whether a driver could get from anywhere to Charlotte in 12 clicks or 10 or 20.....he had not been on all night and his driver was on a different route than the one he had started before he went to bed. And he was maxed out on fatigue points when he went to bed - between New Orleans and Jacksonville.
dmw devil - November 20, 2008 02:59 AM (GMT)
I'm tempted to ask about what browser is in use and if there's something amiss in the cache.
Stinky - November 20, 2008 06:53 AM (GMT)
| QUOTE (dmw devil @ Nov 19 2008, 09:59 PM) |
| I'm tempted to ask about what browser is in use and if there's something amiss in the cache. |
I use IeE- whatever the latest one is - and what could be wrong in my cache? I'll ask 2stroke what browser he uses. I have a program I run every day to get rid of spy cookies. But I've had that for and long time. Nothing has changed on my pc in the last 2 weeks.
Knockoff Norman - November 20, 2008 05:53 PM (GMT)
If you refresh the page whilst in route you'll drive another leg. In addition to this I've seen reports of browsers (usually IE) randomly start refreshing pages automatically without being asked to. If your driver has had a dodgy internet connection and hit refresh a couple of times or has a browser that's playing up it's quite possible to click next leg a few times and suddenly realise you're at 10FP already once you see the red warning sign come up on screen.
As for the wrong route bug are you sure he didn't accidentally choose the wrong city (Charlotte being in the ring of cities next to Jacksonville) and only realise his mistake when he came back to the game? Looking at his routes the departure time fits in pretty well with all his other departure times so it's not like he's started at a time he couldn't be online. Also how did you check what route he was on? Did you view his driver specifically or just use the dispatch screen? I know the dispatch screen lags behind with regards to the FP level shown but does it ever also lag behind with the route columns? What game time was it when you checked? Maybe your driver started the Charlotte routes after you had gone to bed?
Sorry if I sound skeptical but a bug that makes you drive from one city to another and back again sounds pretty unlikely.