Hayden Toppeross

Volumetric Capture guy, VR/AR creator, Ancient Greek nerdist

[Hayden Toppeross @wundercog]

I made this tool for my own use and now I'm releasing it on the mac app store for post production nerds everywhere. Its a timecode calculator and rushes logging tool.

Feature requests and feedback welcome!

https://t.co/c0JK608jug
#PostChat, #FilmTwitter, #DaVinciResolve

[Dyerbolical Horror (☥𝐃𝐁) @DyerbolicalDB]

Anyone else?

[Lee @osgamer74]

If you had this Lord of the Rings poster on your wall in the 80’s, you are my people

- Jimmy Cauty (1976)

[Hawklorddragon @cimerians]

'Sailor on the Seas of Fate' by Richard Hescox
#fantasyart #Elric

[Tim Curry @NotTheTimCurry]

I’m finally ready to tell the world about my private life. This has taken a lot of courage and a lot of thought. But here we go. https://t.co/MrkhxmiZPZ

[MechCanuck 🤖 🔧 @JessieTweeting]

VR/MR developers are so fixated on building the next “killer” VR game that they’re missing the biggest opportunity - education.

Give us VR YouTube.

I want to learn the basics of woodworking, glass blowing, electronics, 3D printing, house repair/construction… @MetaQuestVR

[Eric S. Raymond @esrtweet]

Earlier today I listened to a friend comment that modern systems have longer keystroke-to-screen latency than an Apple IIe. He meant it as a complaint about bloat and sloppiness.

He's not entirely wrong. But much of that lag is a cost we have paid for flexibility and modularity, and those qualities are worth something.

The software stack under an application running in X on a modern Linux is doing a lot more things than the Apple IIe did; it has to be split into more layers just so the layers will be maintainable. and each joint between those layers introduces latency.

Have we undervalued latency? Are there too many joints? Maybe. On the other hand, human beings are slow creatures. In discussions like this I always bear in mind Jef Raskin's finding that 0.17 seconds is a magic number with respect to the minimum response time of the eye-hand-brain loop.

Human beings can do repetitive actions like drumming on shorter time scales than 0.17s, but not considered and planned actions.

0.17 seconds is a lot of time with respect to any one joint, any one latency hit in the interaction stack. The problem comes when there are many layers and designers aren't aware of how much of that budget the parts of the stack they're not paying attention to are already using.

Of course there's a coordination problem here. In the open-source world, the OS, X, the desktop environment, and the application all typically belong to different dev groups. They're not all reporting to somebody who can notice that aggregate latency is a problem and kick their asses about it. And the problem is worsened by the fact that whole-stack latency is difficult to measure.

However. There is a realistic design rule each layer could adopt that would fix the problem and get the entire keystroke-to-screen time under the Raskin threshold - an equal, measurable constraint on everybody. That is this:

If your layer introduces worst-case keystroke-in-to-keystroke-out latency of more than 0.03 seconds, you're being a bad neighbor to the rest of the application stack and should fix that.

With modern hardware this should be quite achievable. Could be we're already there - but we won't know until we measure.

[Science girl @sciencegirl]

Invisible mending of a knitted item

📹 alexandrabrinck
https://t.co/NM7k9tWoyq

[Tsarathustra @tsarnick]

Demis Hassabis says AlphaFold enabled a billion years worth of research to be done in one year and the goal is to simulate virtual cells so that experiments can be performed in silico

[Sabine Hossenfelder @skdh]

I don't understand why this nonsense ever spread so far or why anyone is taking it seriously, but if you need someone to say it's all nonsense, here we go: it's all nonsense.

https://t.co/zHhWEharZb

[RTÉ @rte]

✨🎵 “I searched for my spark and I found it” ✨🎵

Cruinniú na nÓg, Europe’s only national free day of creativity for young people is back, with over 1,000 free activities, taking place on Saturday, June 15. 🎉

#CruinniuNaNog - an initiative of @creativeirl, supported by @rte

[Hayden Toppeross @wundercog]

@cyanworlds @MetaQuestVR Shut up and take my money (again)

[Cyan Worlds @cyanworlds]

Today's the day for a BIG platform announcement:

We're THRILLED to bring Riven to life in GLORIOUS VR on the Meta Quest 2 & Meta Quest 3! 😎✨

Click to see more @MetaQuestVR images ➡️
https://t.co/mPz5xsHZEg

[Marcel @MarcelD505]

Ok so people already cracked the rabbit R1 and found out its android. People dumped the apk and i got it working (with root and a few mods) on a standard ass phone lmaoo

[GingasVR @gingasvr]

The people getting mad at Ai mods for Skyrim and Fallout have no ground to stand on imo.

1) the normal vanilla dialogue for Bethesda games are complete nonsensical trash, the stories are basic and predictable. The only exception is Fallout:NV which was Not made by Bethesda. At least the Ai dialogue makes the game semi interesting

2) people seem to think it’s “taking away jobs” from VAs. These are 10+ year old games with mods made by the community in their free time.. and releasing it for free, nobody is making any $ from the Ai mods 🤦‍♀️

3) saying “it’s trash doesn’t add anything” is objectively false. You can ask NPCs for directions, how their day is going, what they think of another NPC, how to do quests etc. it literally adds so much life to the game it’s scary

#vr #ai

[Massimo @Rainmaker1973]

Drone light painting

[📹 theliamman]
https://t.co/RICMNTc7w5

[Neal Stephenson @nealstephenson]

Polostan, my new novel, is coming out October 15. It’s the first book in a new series I’m calling Bomb Light. More info to come as we get closer, but for now: https://t.co/0tNxyBuNmr  @wmmorrowbooks

[John Carmack @ID_AA_Carmack]

Meta Horizon OS

Meta already sells the Quest systems basically at production cost, and just ignores the development costs, so don’t expect this to result in cheaper VR headsets from other companies with Quest equivalent capabilities. Even if the other companies have greater efficiency, they can’t compete with that.

What it CAN do is enable a variety of high end “boutique” headsets, as you get with Varjo / Pimax / Bigscreen on SteamVR. Push on resolution, push on field of view, push on comfort. You could drive the Apple displays from Quest silicon. You could make a headset for people with extremely wide or narrow IPD or unusual head / face shapes. You could add crazy cooling systems and overclock everything. All with full app compatibility, but at higher price points. That would be great!

This brings with it a tension, because Meta as a company, as well as the individual engineers, want the shine of making industry leading high-end gear. If Meta cedes those “simple scaling” axes to other headset developers, they will be left leaning in with novel new hardware systems from the research pipeline for their high end systems, which is going to lead to poor decisions.

VR is held back more by software than hardware. This initiative will be a drag on software development at Meta. Unquestionably. Preparing the entire system for sharing, then maintaining good communication and trying not to break your partners will steal the focus of key developers that would be better spent improving the system. It is tempting to think this is just a matter of increasing the budget, but that is not the way it works in practice – sharing the system with partners is not a cost that can be cleanly factored out.

Just allowing partner access to the full OS build for standard Quest hardware could be done very cheaply, and would open up a lot of specialty applications and location based entertainment systems, but that would be a much lower key announcement.