@HarryCincy@wlmsears@Turbinetraveler Have the app assign everyone an order number. You are 17, go find 16 and 18 in the 1-30 group that just got called up first. Don't make them think about seat letters/rows, etc. Just tell them exactly where to stand and charge a fee for those who break the flow.
@AZELZY@wlmsears@Turbinetraveler Charge em extra for boarding together, or for messing up the order. If people want to slow things down, let them pay and let the airline collect on it. People would get over the co-dependency or pay.
Big numbers assigned in the app on the boarding pass screen. Not seat numbers, but 1-100 or whatever assigned based on how the algorithm wants you to board accounting for empty seats, people not checked in yet, etc. I have a big ass 17 on my screen, I need to find 16 and 18 and get between them, or I am denied boarding until the end and charged a fee of $20.
People would figure it out really quickly.
@Bonzombiekitty@wlmsears@Turbinetraveler If you show up to the scanner out of order, you get denied entry and charged a fee of $20, back of the line to try again.
At boarding based on who is checked in, assign numbers in large font on the screens. First group is 1-30, put yourself in order or if you show up to the gate out of order you go to back of line/get a $20 fee applied to card on file.
Nobody has to think or plan other than "I'm number 17, I need to get between the person with the giant 16 on his screen and the person with the giant 18 on his screen.
So charge anyone who wants to board together $20 extra per ticket to do so. Filters out those who don't really need to and just prefer it slightly. Gives the airline extra money for those who require it and keeps the disruptions to a minimum. Not impossible to do this in blocks/groups, just don't want too many.
@flyastroapple@Turbinetraveler So charge anyone who wants to board together $20 extra per ticket to do so. Filters out those who don't really need to and just prefer it slightly.
@rhensing All Teslas in Colorado at least have had this issue on all V14s for 3 months now. Ignores the GPS all across the state. Seems like an underlying/hidden construction/road closure map is outdated because it will do it on all of the same exact turns. I have a post thread about it.
@TitaniumTomP@Fidelity Yeah everyone had to do this everywhere. Instructions were pretty clear. I got screwed because @CharlesSchwab put the order on my tiny IRA instead of investing account so I got 0/1400. But I found out because I logged on to confirm last night like everyone.
@bradsferguson@LimitingThe 1/155 robinhood, 0/1400 Schwab because they put the order on my tiny IRA account instead of investment account and couldn’t fix it.
I ended up taking it to service. They said it's a known issue. Still they cleaned the camera (new squeaks, yay).
While they had it, I got a loaner X, which was amazing! But same exact issues in the same exact places - something is wrong with the internal FSD maps.
14.3.3 didn't fix it either - my streaks are 1-2 miles on 80 mile trips the whole way 😆
v14.3.2 did not fix the issue -- the first 5 turns indicated by the GPS were ignored or performed in opposition to the directions. I have booked an appointment for service, but the soonest was well over a week out and they marked it as a camera clean... I have checked the cameras, they are fine, and there are no indicators saying the front camera needs to be cleaned. But just to be sure I cleaned the windshield and retested -- no luck.
@Rebellionaire@bradsferguson So by letting this information out, aren't you giving large firms a heads up that they should request more shares than they actually want so that when we all get 50% of the request, they still get 100%?
@grok@Oilwayne0830@SawyerMerritt It's clear that he is steering a wheel. We know for a fact that a majority of the cybercabs we see on the roads have temporary steering wheels for testing new areas.
v14.3.2 did not fix the issue -- the first 5 turns indicated by the GPS were ignored or performed in opposition to the directions. I have booked an appointment for service, but the soonest was well over a week out and they marked it as a camera clean... I have checked the cameras, they are fine, and there are no indicators saying the front camera needs to be cleaned. But just to be sure I cleaned the windshield and retested -- no luck.
Something is very wrong with my FSD on my Model Y. For the last couple of months it has been taking some turns up to a mile too early, or in some parts of town/the state, it will just act like the road is closed and try to take *every single* right or left turn it can.
For miles.
On major roads and interstates.
Or drive right past where the GPS says to turn without trying to take it or change lanes at all from the center lane.
I miss 1/3rd of exits on the highway. And again it’s not even close. It’s as if the car is purposely choosing not to take my exit.
Sometimes it says it’s 15 MPH on the interstate and sometimes it says it’s 75 MPH on in town 45 MPH roads, so I’m assume it’s a bad map update?
I have been using FSD since 10.2 or so. Literally 4.5 years. So it’s not a rookie mistake kind of deal. And I’m not talking a weird edge case turn — I’m talking about the entire state of Colorado.
V14 was amazing. And then one day it wasn’t working at all. For nearly 2 months FSD has been unusable. I was at over 99% use on my stats for thousands of miles… and now it’s not even worth turning on for more than a straight mile at a time.
I tried steering wheel reboot. Tried full car reboot. Tried camera calibration. Tried calling Tesla, both AI assistant and human. Asked for fresh map or FSD install. Was told no, to schedule an appointment to bring it in. Haven’t really had the time to do that yet and was hoping for V14.3 to maybe come down the pipe and save me, but that seems to be a slow rollout.
I guess my point is… how can the car/Tesla not tell something is wrong and either self correct or call for help? How could we ever trust a robotaxi that reports perfect condition, and then drives me to the wrong side of town, ignoring the GPS entirely for miles and miles?
I’ve sent hundreds and hundreds of voice notes. Surely they should flag users with that many issues for manual observation?
v14.3.2 did not fix the issue -- the first 5 turns indicated by the GPS were ignored or performed in opposition to the directions.
I have booked an appointment for service, but the soonest was well over a week out and they marked it as a camera clean...
I have checked the cameras, they are fine, and there are no indicators saying the front camera needs to be cleaned. But just to be sure I cleaned the windshield and retested -- no luck.
Something is very wrong with my FSD on my Model Y. For the last couple of months it has been taking some turns up to a mile too early, or in some parts of town/the state, it will just act like the road is closed and try to take *every single* right or left turn it can.
For miles.
On major roads and interstates.
Or drive right past where the GPS says to turn without trying to take it or change lanes at all from the center lane.
I miss 1/3rd of exits on the highway. And again it’s not even close. It’s as if the car is purposely choosing not to take my exit.
Sometimes it says it’s 15 MPH on the interstate and sometimes it says it’s 75 MPH on in town 45 MPH roads, so I’m assume it’s a bad map update?
I have been using FSD since 10.2 or so. Literally 4.5 years. So it’s not a rookie mistake kind of deal. And I’m not talking a weird edge case turn — I’m talking about the entire state of Colorado.
V14 was amazing. And then one day it wasn’t working at all. For nearly 2 months FSD has been unusable. I was at over 99% use on my stats for thousands of miles… and now it’s not even worth turning on for more than a straight mile at a time.
I tried steering wheel reboot. Tried full car reboot. Tried camera calibration. Tried calling Tesla, both AI assistant and human. Asked for fresh map or FSD install. Was told no, to schedule an appointment to bring it in. Haven’t really had the time to do that yet and was hoping for V14.3 to maybe come down the pipe and save me, but that seems to be a slow rollout.
I guess my point is… how can the car/Tesla not tell something is wrong and either self correct or call for help? How could we ever trust a robotaxi that reports perfect condition, and then drives me to the wrong side of town, ignoring the GPS entirely for miles and miles?
I’ve sent hundreds and hundreds of voice notes. Surely they should flag users with that many issues for manual observation?