peterept

This is great.

But when I read the headline I was kind of hoping it might be a home arcade machine that also let me watch other people playing (ala’twitch) but then also allow me to join the game (or even take it over).

Oh yes at the time I ordered a sheet but it didn’t align with my display panel. I should try that again.

I got excited about this a few years ago when I was into digital pinball. I built an open source project called Phonemote using an iPhone to track eyes and relay telemetry over WiFi/BT and a plugin for FuturePinball.

However the result wasn’t that useful because we humans have 2 eyes.

The 3d effect is very compelling if you close/cover one eye.

But that becomes annoying quickly.

The best results I had was sneering a little hair gel in the center of my left eye glassses. Then it felt like I was using 2 eyes but really my right eye was seeing the pinball table clearly and fooling my brain.

Back in the day of LAN parties Descent was our favorite game.

Auto-pilot is not on all Teslas as it was a paid upgrade til mid-2019. My M3 does not have auto-pilot!

To avoid memory allocations, and if you can modify the source string in place, then an alternative is to return std::vector<char*> and modify the string to replace the separators with '\0'.

Of course, as that post suggests, use reserve() to encourage having the vector itself as optimal as possible. (In my strsplit call I pass it in as optional so each caller can optimize it).

Cardboard SDK is already stereo vision.

Looking at tech specs there is no touch controls. Input is either by using CV hand tracking or sending motion controls from an Apple Watch. Basically they are using Apples SDK for everything.

Wouldn’t the SDK be the same as Google Cardboard but disabling the distortion and mirroring the output?

Use ARKit/ARCore for tracking.

A few lines of code and you are all set.

Same happened to me!

I developed NewtFTP because wireless cards were just starting to appear, the PM100D cellular cards and the early 802.11 WiFi. FTP was the most popular way at that time to distribute application packages and files.

It felt like living in the future walking down the street in ‘96 with my newton and accessing the internet!

I was worried about that too - because I loved the (apparent) simplicity of using Apple maps from my phone... until I actually got the Tesla and found voice navigation is way easier and flawless. (And in the very occasional situation I have an address on my phone now I can just share it to the Tesla). I don’t miss CarPlay (at least for the features I used).

I run a multiplayer VR team platform where we run a copy of Unity3d on the linux cloud server and load the the same Unity Asset Bundle on the server as the clients ("The current world"). I chose this method because:

(1) it followed the Unity3d documented approach using UNET server and client architecture (2) it meant we get to simulate the entire scene on the server (physics, meshes, networked objects, etc)

We boot the instances on demand when a team wants to meet in VR.

Sounds like Unity's new T&C's means this architecture is dead in the water.. unless Authorized by Unity3d. :-(