OCULUS QUEST GESTURE RECOGNITION DEMO: "FINGER GUNS"
https://github.com/mcclure/lovr-oculus-mobile/tree/lovr-oculus-mobile-hand
When I "trim" videos in Quicktime Player and upload them to Mastodon, once they arrive on Mastodon I find several seconds preceding the "start" that have somehow been reattached to the video despite me having trimmed it off
I assume this has something to do with keyframes but I don't know what to do about it
SECOND TEST, OCULUS QUEST HAND-TRACKING SYSTEM WIRED IN TO HTTPS://LOVR.ORG ENGINE. COLORFUL FINGER TRAILS
Hi there if you are in America I suggest you ASAP contact your congressperson and ask them to oppose the CASE act, a weird copyright bill being voted on tomorrow
EFF:
https://twitter.com/EFF/status/1186324235557335040
Verge article:
https://www.theverge.com/2019/7/23/20703742/case-act-copyright-office-online-designers-congress-bill
Short version: Now in addition to normal courts plus the DMCA there'd be this new weird copyright quasi-court. By my read if notice is served and you don't respond within 60 days you could get hit with a $15,000 fine as default judgement. Sounds really easy to abuse.
Today I am excited about:
LÖVR is a open source, VR game engine made by Bjorn Swenson. As of today version 0.13 is released:
And, of specific interest to me, this is the first version to officially support Oculus Quest!
https://lovr.org/docs/Getting_Started_(Android)
LÖVR is the basis for the commercial game I've been making for the last year and a half. I maintain LÖVR's Oculus Mobile port, plus this repo (forked from my game) of helper classes and tools:
Hey I don't usually announce streams on Mastodon but starting RIGHT THIS SECOND me, and Miguel who made They Bleed Pixels, and Christine who made Digital and Analogue, and our friend Parrish are gonna be streaming Nintendo's bizarre five screen game experiment Four Swords Adventures and I'm excite. We'll have a GBA cam. U should watch, using the Internet https://twitch.tv/spookysquidgames
Update: It's now been explained to me I misread the meaning of "OP-IMM" in this table, and actually RISC-V intentionally defines 0x0 to be an illegal instruction (for safety—so if you execute uninitialized memory you know immediately) and NOP is actually 0x13. (OP-IMM is 0x10, ORed with 0x3, the code for "standard 32-bit instruction space".)
This makes sense, but part of me is sad NOP is so arbitrary. It would have been so cool if they'd found an excuse to make 0x0 be illegal and 0x1 be NOP.
glitch girl