Panasonic’s Innovative Augmented-Reality HUD Could Be in Cars by 2024
caranddriver.com
caranddriver.com
It is very slow.
People feel discomfort when different "overlays" lag by as little as few tens of milliseconds.
People feel uncomfortable working with touchscreens because they feel "unnatural" when they push the button, and it only reacts, and plays animation half a second later.
What people say what feels most "fake" about touchscreens is stuttering, and lagginess.
I believe you really need to go to sub-millisecond levels of latency for it to feel "glued" to the real world.
I had a touchscreen project in the musical instrument space, with a pressure sensitive touchscreen, where button animation had to match the touchscreen pressure.
Even with all tricks, lag on Android was making it completely unusable, not to say Android's audio API is completely not suited for serious audio work. In the end we went bare metal with it.
The lowest latency we got was 18ms by using the touchscreen interrupt to set the sensor value as a pointer to bitmap image of a button animation frame.
Yet, some more experienced musicians said that it was still "felt off."
I'm thinking to go full FPGA next time I need to do any latency sensitive HMI with kinetic-screen interaction.
Just wanted to help clarify that 300ms means "delay", not refresh rate (FPS). We run our entire AI and AR at under 33 ms per frame, and we can get to about 60 FPS of optimized throughput. The 300ms of delay mostly comes from the hardware display process: it takes time for the camera to receives an image, and passes that image through many different pieces before getting to the processor that we can use, and then it takes again some time to be rendered. With that said 300ms is the upper-bound and typically the delay is less than that. Further, you may not have noticed but there's similar delays for iPhone AR games, as well as to all other AR headsets, and that delay is there just for the videos to display (no AR, no AI).
We also recognize that distraction is a risk, and therefore UI/UX design is highly important here. Ultimately, we believe that overlaying on a live view in a clean and effective way is better than people reading directions off of a synthetic 2D map on a different screen that takes your eyes completely away from the frontal view.
Definitely appreciate all the feedback and discussions though, we will continue to improve and do our best to deliver a product that people want!
- BTW we are totally hiring: software engineers, PMs, sales, AI/AR scientists, and more!
Watch "Hyperreality", if you haven't seen it, for where this leads.
No, ads exists mostly where people are not paying. Vast majority of paid products and subscription services are ad-free.
- Netflix has constant product placement in their show and show ad for their other show on their main page
- Amazon Prime Video show you an ad for other show when you start playing one
- A lot of "smart TV" have ad in their UI at this point
- Windows has try to force ad in the OS UI several time and comes with preloaded junk
- Most Android phone comes with preloaded junk (which is basically ad)
And the list goes on. Companies have noticed that you can start to put ad even in paying product and secure a stable source of income and get away with it.
Just like journalism.
If they haven't made phones that are cheaper if you agree to watch an ad once a day before using it - then the dynamics for cars would be even worse for that.
Edit: typos.
Like when I write email and some parts in bold, people tend to read only the bold ones.
I do the same when I'm riding a bike near an intersection and there's a car coming in the opposite direction.
Assuming the road isn't just a flat straight road all the time, there will be uphill and downhill drives. Turns, curves, and twists. All of which affect your FOV. The YouTube trailer didn't show the actual windshield, but a view recorded from a mounted camera.
I wonder how this will compare to a bad FPS gaming experience.
I imagine this will make you want to vomit faster than anything else you've experienced.
This is the way. HUDs are an absurdly awesome coolness and safety feature. I don't care about how the dashboard looks because I don't want to look away from the road! Seeing this is extremely impressive and I hope that we can get AR technology to see widespread adoption in cars ASAP. The fact that we have to wait until 2024 (and for us Toyota or Lexus drivers 2028-2030) is just embarrassing. Why isn't this coming in the next year?
Tesla's refuse to add them and the aftermarket options suck, so I can't buy one either which is extremely sad.
Don't block my windshield with your "helpful" alerts. I don't care, I can drive without them, that's how I (and millions of others) learned to drive.
I want a physical key.
I want the engine not to cut off when I'm stopped at a traffic light or stop sign.
I don't want more cameras, whether facing the occupants, or facing the road.
Cars are already "good enough", and have been for years. Why do we need to keep adding software and other janky "features" that create more failure points and more expensive repairs?
You can always get a 20 year old Toyota, and that will be more-or-less what you described. But if you want to buy a modern car and drive it on public roads, you have to abide by the rules.
Because I like them and I'll pay more for the car than you will. And there are more people like me.
Are there any cars where you can't turn it off? I thought the switch is pretty standard.
> I don't want more cameras
Why wouldn't you want a camera on the back? I get some other points, but this one is pure improvement of safety with no drawbacks I can think of.
The first time I saw HUD navigation was when playing Need For Speed 9. It'd be awesome if that becomes the reality.
Maybe only put up satnav directions. Like “take next turn right”. 3fps is enough for that.
But if you’re gonna draw lines and highlight cars and bicycles at 3 FPS you’re just gonna make everyone vomit in their own car.
I mean unless the HUD is in a helmet, then things like head position and driver's height will create rather large mismatches between what is the intended projection and actual road features, no?