kanetw

8 ms·

31.
by kanetw 4y ago
Typo. We'll fix it i7-1265U and Wi-Fi 6E is correct.
32.
by kanetw 4y ago
I'm not fundamentally against ARM. But ARM in the VR world is Qualcomm, and they both didn't want to deal with us + their support for regular old Linux is (AFAIK) nonexistent. Apart from that, x86 is IMO just easier to adopt. I wo
33.
by kanetw 4y ago
The Quest Pro wasn't announced when they subpoenaed us.
34.
by kanetw 4y ago
A sour attitude definitely wasn't intended. Meta has some misleading marketing and we wanted to correct that. Apart from that we're just comparing our products, as the Quest Pro (unlike the Quest 2) does indeed intrude on our nich
35.
by kanetw 4y ago
This is our (SimulaVR's) vision, basically. Our target is to have pixel density/optical quality and comfort good enough to work comfortably. The pixel density is there (and better than quest pro), and we just need to finish the co
36.
by kanetw 4y ago
There's no fundamental reason it can't be decompiled. Vivado uses white-box crypto for their IP keys, and they're all over the Chinese internet. No one in the West will publicly mention touching them, for good reason. In Chin
37.
by kanetw 4y ago
Prescription inserts (we're working with vendors on this) are possible, and the focus distance of our headset (and most headsets, I think) is in that region.
38.
by kanetw 4y ago
Yeah, I agree. I distinctly remember open source becoming more corporate as the years got by, and corporate becoming more open source aligned.
39.
by kanetw 4y ago
Yeah, Immersed popped up alongside us. A big reason of why we went the hardware route (as an originally pure software product) was that the existing hardware was not good enough. Having worked with the prototype headset, I can fairly confid
40.
by kanetw 4y ago
We made our weekly blog post about it (because it's worth talking about, IMO) and someone else posted it on HN. It blew up and we're responding to comments as necessary. We're letting our legal counsel handle the actual detai
41.
by kanetw 4y ago
Responding to any legal request without legal counsel is a good way to fuck yourself up. There's no "just do x" unless you enjoy playing with fire.
42.
by kanetw 4y ago
We ran it past them and they ok'd it. We as a company are fundamentally very open. It is quite literally a core facet of our business, and that includes not just the technical parts. Of course there's stuff that's internal, b
43.
by kanetw 4y ago
Hiring a lawyer was the first thing we did. For the rest, I'd gladly do this if we had the funds to do so. We don't. Plus, we as a company are (maybe excessively) open. Of course we're going to get involved in legal proceedin
44.
by kanetw 4y ago
Yep. It's easily going to be in the 5 digits.
45.
by kanetw 4y ago
We aren't throwing a hissy fit lol. We're just stating the facts and are working with our lawyers to resolve this.
46.
by kanetw 4y ago
It's a bit tooting my own horn but when I first put on the prototype it was really satisfying. Incredibly crisp.
47.
by kanetw 4y ago
First thing we did was get a lawyer.
48.
by kanetw 4y ago
Yeah, of course, it's a tough space to be in. Just saying that we need to carve out a niche where Meta can't compete vs try to fight Meta head on.
49.
by kanetw 4y ago
We're going to absorb the legal expenditures as part of our overall expenses, but you can crowdfund us by preordering a headset :)
50.
by kanetw 4y ago
Of course anything Meta does is a bit worrisome. I just don't think we're in the same niche-- IMO Meta is fundamentally built on data collection, and VR is just a side effect. Unless Meta decides to abandon that, I think we'l
51.
by kanetw 4y ago
We already have standing legal counsel. George made it sound like we're just now seeking a lawyer, but we already reviewed our policies etc in the past.
52.
by kanetw 4y ago
I know 1 person who got SARS-CoV-2 twice, unvaccinated. And another who had it thrice, also unvaxxed.
53.
by kanetw 4y ago
It's a significantly different segment than the Quest or Valve Index-- somewhere in between a Varjo and a Valve Index. With better economies of scale, we would be able to drop the price more/introduce more segmentation. As is we j
54.
by kanetw 4y ago
PCIe gen4+ compliance testing and debugging
55.
by kanetw 4y ago
I'm just talking about end devices here (source/sink).
56.
by kanetw 4y ago
Yeah, it always gives you default power. It's just such a low amount that I kinda forgot. Sometimes it's just fine to yolo it, but it adds to the confusion-- "I plugged in my device and it doesn't work??"
57.
by kanetw 4y ago
A compliant USB-C source will not provide more than 5V/3A without PD negotiation period, and is only guaranteed to provide default USB power. So if you can potentially draw more, you need to check whether it's allowed.
58.
by kanetw 4y ago
Yeah, that's about the only thing you can do without ICs. 500mA max, high-speed lanes unused.
59.
by kanetw 4y ago
Without CC line sensing, you don't know how much current you're allowed to draw. Screenshot from the standard: https://i.kane.cx/EI4HtM Specifically, the sink has to detect vRd to determine how much current it can
60.
by kanetw 4y ago
I'm considering TBT3/4 for our VR headset's tethered mode. It's a bit of a pain to implement, but the data rate is worth it. For reference, we need 2-4 lanes of DP HBR3 (depending on compression) + PCIe Gen3x4 for the ca

More ›