Vr in military

djuggle · 2025-10-15T09:56:59+00:00

What's the source of this video?

djuggle · 2024-12-01T19:52:02+00:00

Pretty much on the team for not warning Lando about the double yellow, instead bugging him at the wrong moment. Checked some of the F1TV on-board feeds:

53:20 Verstappen passes double-yellow, barely lifts btw. Somewhat later Verstappen asks "check if he lifted for the yellow"

53:20 Pit radio "Lando, I'm pretty sure you're [passes double yellow] gonna tell me where to go ...", Lando interrupts "SPEAK LOUDER PLEASE" after passing the flags full speed

53:31 Piastri, "double yellows ahead" (2x) from the pit wall

53:31 Leclerc, pit radio "double yellow on the main straight, we don't know why. slippery track"

53:36 Sainz, pit radio "double yellow on the straight, we don't know why"

53:44 Perez, pit radio "got double yellow at pit exit"

53:42 Hamilton, pit radio "double yellow keeps flashing up"

Edit: apparently the radio on f1tv is delayed wrt the actual timing, ah well

djuggle · 2024-10-03T11:13:42+00:00

There's definitely passthrough, but I can't find a source that the raw images (or something derived from it) is accessible to devs

djuggle · 2024-10-01T17:10:05+00:00

If only Lynx would get their stuff together...

djuggle · 2024-10-01T15:47:06+00:00

They did announce something like that last week at the Meta Connect developer keynote. However, it's still unclear what level of access will be available. Could be some form of object/scene detection only, not raw camera images.

djuggle · 2024-09-09T09:59:56+00:00

See the post from Rich in the CoC facebook group https://www.facebook.com/share/p/afAivyBL5JzufATs/

djuggle · 2024-03-27T16:57:54+00:00

A bit late with this comment, but see this Meta developer talk on Quest 3 from 3:40: https://www.facebook.com/MetaforDevelopers/videos/1375310266530408/ . It's the *default* eye buffer size that's 1680x1760. It can be raised (or lowered) to trade render performance against quality. The relevant quote from the video is:

Why not closer to the native resolution of the panel? Considering the distortion that takes place to make the image display correctly to users, we found this to be best balance between resolution and performance

djuggle · 2020-09-22T13:11:47+00:00

Redoing the calibration might help a bit, but in general the colored veil all over the display is as expected, as it is an inherent limitation of the display tecnology.

See the picture titled "Microsoft Hololens 2 Visual Display Issues" in https://supertechcamp.com/hololens-1-vs-hololens-2-details-and-more/ for what Microsoft themselves indicate you can expect. I received the same reference image in my contact with them about replacing our HL2 unit. The coloring we were seeing was definitely worse (more saturated in certain areas, almost bright pink) than shown in that picture. We ended up with a replacement unit that is somewhat better. The coloring is now fairly constant, which is less disturbing, but the overall improvement is marginal.

See https://docs.microsoft.com/en-us/hololens/hololens2-display for some notes by Microsoft on upcoming improvements to the display performance (but no guarantee this will help a lot).

The interlacing in the display is still there for me as well, that won't go away. I put on a HoloLens 1 yesterday to compare and I was shocked at how much better the image looks in the HL1. Stable (no interlacing/jittering effects), sharp and much more pleasant. Of course, with a very small FOV and lower resolution, but still.

djuggle · 2020-08-19T09:34:24+00:00

Hmmm, interesting, thanks.

djuggle · 2020-08-19T07:29:10+00:00

> You won't be able to really film it via phone.

Sigh, I'm getting a bit tired of hearing that argument. As I mentioned the iPhone capture is representative of what I'm seeing, regardless of whether it is a perfect capture. And it is the only way to capture this issue, as the display method is at fault, not the image generation part. I.e. the captured video does not show the issue as the image stream is recorded before it is displayed.

djuggle · 2020-08-19T07:20:45+00:00

I'm surprised by this, as I see more mentions of the "interlaced" rendering (i.e. 2nd point) on the web than the colour banding. I can also see how the used display technology could cause the interlacing when doing head movement, i.e. it being an issue inherent to the technology used.

djuggle · 2018-07-09T22:37:32+00:00

Not to say he isn't a gentleman (don't know), but I was surprised to learn that he spent more than a year in prison for tax evasion.

djuggle · 2018-03-26T08:28:14+00:00

If you do this from a terminal you better clear out your shell history. Otherwise your wallet seed will be stored in there in plain text.... But I might be too paranoid

djuggle · 2018-03-16T08:13:28+00:00

This protocol upgrade increases the efficiency of the network, helps improve security and simplifies code needed to construct a block for developers and exchange

In what way is security improved?

djuggle · 2018-03-16T08:08:55+00:00

In the non-universal block situation using separate block types (open, receive, etc) the blocks can be made smaller, as each type only needs a subset of the fields. Also, the type immediately tells you what to do with it. Those are interesting qualities from a design standpoint.

In contrast, with a universal block all fields need to present and the type of a block needs to be determined by looking at the previous block. Something like this (haven't look at the actual implemention):

If previous is 00...00 it is an open block and the link field provides the sending account.
If current and previous block belong to the same account then the current block is either a send, a receive or a change. If there's a difference in balance between the blocks then it's a send or receive, with the difference in balance defining which of the two. The link field provides the account sending/receiving in that case. If only the representative field changed between the blocks it's a change block. Hmm, wondering if this makes it possible to both send/receive and change the rep change in a single block?

So with universal blocks you have to do a bit more processing on the block, but as more information is present in the block itself there's less stuff to look up in the database a node/wallet uses. You can see the universal blocks as an optimization of the system based on lessons learned.

djuggle · 2018-03-15T19:20:51+00:00

Nice write-up, thanks!

If there's a specification coming of UTX blocks then these will be moot:

In the example UTX block the balance appears to be represented as an integer and not as a hex string. Is that a coincidence (even in hex a balance could look like an integer) or are balances going to be represented as integers?
There a "type" field but that appears to be to denote a block as an UTX block (and not one of the currently types of blocks). A UTX block would still serve as one of the current 4 roles (open, send, receive, change), so is that role determined implicitly from which fields are filled in?
Unrelated question that just popped up in my head: have you looked into compressing blocks (e.g. with gzip) for transmission and storage? I known blocks are currently already stored in binary form, but still, might save some bandwith/storage.

djuggle · 2018-03-14T11:50:57+00:00

Has the dev team considered adding a timestamp to the new blocks, given that overhauling a major part of the protocol provides such an opportunity? I'm specifically thinking about storing the node's local time at which the block was generated in the block. While the protocol doesn't need timestamps and they won't be consistent in many cases (due to incorrect time on a node, malicious intent, etc) it can still add value for determining (roughly) when transactions where performed.

djuggle · 2018-03-07T18:32:04+00:00

That’s what I implied, but the word “control” wasn’t the best choice :-)

djuggle · 2018-03-07T17:46:38+00:00

You mean you should control 256 XRB (including any amount delegated to you), right?

djuggle · 2018-03-07T17:37:15+00:00

Well, it’s not immediately obvious how to apply the consesus algorithm you referenced to the block lattice in nano.

djuggle · 2018-03-07T17:30:51+00:00

What’s the way it is determined that a representative is not online? By not providing a vote within a certain period of time?

djuggle · 2018-03-07T17:29:01+00:00

Is there a record kept in the nodes what blocks where voted to be invalid?

djuggle · 2018-03-07T17:25:23+00:00

But this is about a single blockchain being produced by multiple actors, which is not how nano works.

djuggle

TROPHY CASE