omershapira

Shameless plug: Horizon (Before the name got saturated), a 4D third-person game https://youtu.be/R6qTi3TCM2U

This is peak 2008 internet, and I love it deeply. Thank you.

Meta: If I had to rank software features of an NLE when I was employed as an editor, key-to-photon (or click-to-sample, etc) latency would rank #1, far outpacing all other concerns. It's fundamental to the rhythm feel of the result, and prevents fatigue.

Avid bent over backwards to optimize for that in their software. I can't imagine cloud/remote editing being a good artist tool.

I really have to hand it to these companies for making these sensors. They're thin margin, not a sectorial revenue driver, but still fundamental to the industry in a "who else is going to do it?" sort of way.

Every once in a while an exec will see the first part of the sentence above as a cost optimization opportunity and will set this industry back by years. This is what happened to most Kinects and previous Realsense cameras. And yet they keep coming back, precisely because they are terrible standalone businesses.

> a paid service

It's a book you purchase. I've never had a book charge me a recurring fee, and this one is no exception.

This makes me wonder if in spite of all these years of education by play, Elementary Piagetian* education is still overlooking mental methods of arithmetic that musicians use. Musicians have an easy time understanding structure - and also knowing how to learn by repetition (to tell a student to repeat something is often a task in itself)!

* https://en.wikipedia.org/wiki/Piaget%27s_theory_of_cognitive...

The proprioception on the index finger while bending on guitar is worse for me than locking the ring finger and using the wrist to control the magnitude of the bend. Useless backfill-ass finger.

This is wonderful. Truly the spirit of the 2000s internet.

I wish designers helped modernize the looks. This needs to be well-used

Cinematic crossovers have gone too far

> Do you recall any specific browsing sessions during these times?(Required)

lol

* You can't google snippets on stackoverflow

* Packages are harder for divergent languages

* Momentum

Hard to come up with more words to explain it

> But if it works it would be very exciting for DRAM and NAND.

Japan back in control of DRAM, nature is healing

Every "Perception for VR" class I give focuses on understanding proprioception. Designers ignore it until they experience spatial planning just with proprioception:

• Start by closing your eyes and touching your nose. Why can you do that?

• Continue by trying to touch two fingers on opposite hands behind your head. Why can't you do that? (because your proprioceptors are saturated).

• Now, you can build an environment with post-it notes and a blindfold: https://omershapira.com/blog/2016/04/the-painful-introductio...

To those who use Unity currently:

• Has the engine improved in any capacity in the past 5 years for your usecase? (IL2CPP is the only example that comes to mind)

• Are workflows faster or more reliable?

• Has any AI tool become available for your projects? Weta Digital tools?

• Have you benefitted in any way from the company's efforts to penetrate the AAA market? I'm talking about DOTS and HDRP primarily.

I'm sorry but assuming the tooth fairy's gender exposes your bias. smh

I'm usually surprised when no-nonsense economic incentives fly under the radar nowadays. You'd expect this, much like subsidized education or any other workforce support utility, to just be a hot topic in a media landscape that looks to shame these incentives, but I guess the state it comes from is complicated to put in narrative.

Why are you this handsome. It's not fair

Layoffs always suck, and the things and people Epic are getting rid off will hurt everyone, but credit is due for allocating the budget to take care of everyone, including accelerating the vesting schedule.

The communication around the layoffs, the "why" and "what now" make sense. If you have to pivot, learn from this communique.

The one display I got takes about 2 seconds to cycle. You can make it shorter with partial redraws, but for my purposes, the cycle was the right thing to do.

To be fair:

1. His project does allow rendering any HTML: https://www.invisible-computers.com/programmable-e-paper-scr...

2. It is in stock. :) Raspberry Pi Zero 2 and the waveshare displays are in a bit of a stock crunch, and the frame I ended up mounting this in, along with the special flat USB cable, pushed the project cost to the same price. It's my own aEsTheTic tho.

The most fun part of these projects is seeing people quickly build ad-hoc renderers for E-Ink. Very quickly you find out you need render passes, dithering, debanding, etc.

Here's my weather E-Ink board (which consistently gives a faster result than waiting for the iOS weather app to fetch & render): https://github.com/OmerShapira/theres-some-weather-outside

This is a reminder that we can, in fact, have Nice Things – if there only were a market for Nice Things.

I'd love to have a decently integrated watch with low battery usage (and generally low stakes for wearing/replacing) which I can also agree with aesthetically. Bums me out that Sensorwatch [1] is the best we can do.

[1] https://www.sensorwatch.net

edit: Sensorwatch is amazing, but not an ecosystem (yet).

I think this is the biggest mental shift to make when considering OpenUSD.

It allows splitting the data representation from the render pipeline.

On the data side, OpenUSD can support BIM just fine:

• Can store the geo representation, will render as long is there is a plugin written to render it (for systems that don't, the geo is still available to query) • Can store additional information either on the same file, referenced in a different referenced file (ex.: In-wall pipe layouts can be referenced from the main construction file to keep it small) • Can 'layer' additional information and resolve conflicts according to a well-defined resolution method, allowing multiple authors.

OpenUSD has a plaintext encoding mode, which by convention gets saved as .usda. The standard OpenUSD SDK contains two command line utilities `usdcat` and `usdedit` to do plaintext editing, but most programs using the SDK have better editing functionality by directly using the C/Python SDK.

Brad was one of the first users of a program I was working on, which he used for his work at Sandia National Labs. He would send me frequent, detailed feedback - respectful and kind, inquiring about possible solutions he'd thought of. He even invited me to Sandia to give a talk together about these efforts [1]. I've never had a kinder customer.

[1] https://www.sandia.gov/xr/4th-annual-xr-conference/agenda/

I now keep a live reference collection. I'll make an effort to update it soon with your request :) https://omershapira.com/blog/2022/11/reference-collection/

This is one of maybe 10 articles that made me a decent low-level programmer when I got a job in computer graphics 10 years ago. Shockingly relevant (cache tradeoffs haven't grown significantly since core/lane/memory bandwidth considerations haven't changed in CPUs). I still regularly send this around to people getting started.

> You’re not an expert in your field, otherwise you wouldn’t be publishing in a blog, but writing papers and giving interviews

At least in the field I'm in (computer graphics), the penalty of publishing is months; blogposts (and patents) cost days. Papers have perverse incentives in style and fact presentation. Where do you prefer the knowledge ending up?