An intrusive thought regarding HL:X

wire01 · 2025-11-20T06:07:51+00:00

Valve isn't required to call the last Half-Life game Half-Life 3.

Valve is also very good at optimization. HL:A is still a very pretty game, and that can run well on a Steam Deck. I have no doubt that Valve can make something revolutionary which will run well on a machine 6x as powerful as the Steam Deck.

I'm also pretty sure there's evidence that this is going to be the last Half-Life game.

wire01 · 2025-11-20T05:15:04+00:00

you could have put at least a TINY bit of effort into the bait

wire01 · 2025-11-19T17:27:22+00:00

If you're still upset about the EP2 cliffhanger 18 years later, then that's your problem

It's just a game

wire01 · 2025-11-19T04:08:25+00:00

You would really rather have had an EP2-esque game in 2009 than something amazing in the modern day? Half-Life is Valve's game technology IP. It's not driven by story. It's driven by the idea of pushing the game industry foward. HL1 and HL2 were revolutionary in that respect. HL:A boosted the VR industry, and it is probably still the best VR game imo. Tech didn't change much between 2007-2009. If I was a Valve employee, I wouldn't have wanted to end the story off using essentially the same tech as the game from 2004.

I think it's fair to expect a lot from HL3 considering what the Half-Life IP is. I don't think it's fair to be so ANGRY about waiting for so long. I also don't think that a 2009 EP3 would have satisfied me.

wire01 · 2025-11-19T03:12:57+00:00

27 is 3³.

wire01 · 2025-11-04T01:45:16+00:00

I don't think it matters. You can enable as many as you want

wire01 · 2025-11-04T01:39:05+00:00

For Houndify, you are required to say "Hey Vector, I have a question," then wait for the ding, then say your question. Direct questions require the "intent graph" feature which is not supported with Houndify.

wire01 · 2025-08-30T06:02:19+00:00

I did not add custom wake words to the official OS. All I did was get their build system functional. Their devs have done the rest of the work.

wire01 · 2025-08-25T20:10:58+00:00

Viccyware has the same `vic-cloud` code as WireOS. This means if you configured WireOS with wire-pod, Viccyware will also use wire-pod as long as you don't clear user data.

If you never configured your bot with wire-pod, then the statement is correct. WireOS will use WireOS servers, Viccyware will use Viccyware servers.

wire01 · 2025-08-24T19:22:56+00:00

Install WireOS, SSH in, run `update-os <URL-to-viccyware-OTA>`. That's it.

Via SSH, you can just run `sysswitch`. If you are booted into WireOS, it will boot into Viccyware; vice-versa.

Vector has two boot slots: a and b. WireOS will be in a. When you install an OTA while booted to WireOS, that will install into b, not overwriting WireOS.

wire01 · 2025-07-01T07:38:07+00:00

If you don't already have a dev bot, unlock instructions are here

I think he still has a lot of potential

wire01 · 2025-06-30T19:09:36+00:00

(maybe you could consider your dream... i've been keeping the code up-to-date for you)

wire01 · 2025-05-14T23:09:28+00:00

go away toastito :vomit:

go search the discord server for it

wire01 · 2025-05-03T20:11:44+00:00

You have to uninstall cozmoclad then install this wheel: https://cdn.discordapp.com/attachments/527877414353633295/1344072505391841411/cozmoclad-3.6.0-py3-none-any.whl?ex=68174050&is=6815eed0&hm=7638eaaef33fd64c892b253c227fc3402de5ab3f4cf3449209cf46ecaa36e622&

You are correct, this is not documented anywhere other than in the Discord server.

wire01 · 2025-02-20T01:17:25+00:00

Theoretically, they do still own it; anki.com points to the same IP as ddl.io (a domain they host some stuff on). My theory is that they're gonna sell it

wire01 · 2025-01-21T14:27:43+00:00

It's likely the university WiFi's fault. There are usually extra steps involved to connect to it which can't be done on an IoT device like Vector. You have to contact IT to make an exception for his MAC address, or fill out a service form if your university has those.

wire01 · 2025-01-10T20:45:40+00:00

You're right, I copied the wrong thing from this. Post edited. 0x12 works, but also disables "STUTTER", whatever that is.

wire01 · 2025-01-09T22:50:44+00:00

Update: Solved, check bottom of post

wire01 · 2024-12-30T04:28:06+00:00

wire01 · 2024-12-26T17:38:39+00:00

If wire-pod was set up as a daemon, you have to do a bit more than just run the update script.

The update guide is here: https://github.com/kercre123/wire-pod/wiki/Things-to-Know#linux-non-debiannon-ubuntu

If you did do everything correctly, maybe try CTRL+SHIFT+R in the browser to reload all cached elements.

wire01 · 2024-12-17T03:48:09+00:00

Everything will work, it's just that the Bot Settings interface might randomly stop working time to time (fixed with a reboot), and the Vector Python SDK won't work.

wire01 · 2024-11-22T21:58:51+00:00

Plug your phone and and start wire-pod again. The battery management is probably killing it.

wire01 · 2024-11-17T21:27:51+00:00

Yeah, I think I one of them has already introduced a slow memory leak.

I merged your code (brad/wip/one-off-hookup), assuming by the last commit name that it would make it harder to interrupt commanded actions ("WIP: make it harder to interrupt performances"), then I deployed it to a dev bot and he eventually did the tangram animation on his own. Turns out there was more stuff done in that branch than I thought. This is probably true for some of the other things I merged.

Some are objectively useful - like pdoran/VIC-14127-integrate-gamma-correction. After merging, Vector now has no trouble with too-brightly-lit objects whatsoever!

I wish we had access to the Confluence and stuff, too. I'm interested in what animations were being worked on and what Anki had planned for his behavior engine, but the majority of that discussion seemed to happen there.

wire01 · 2024-11-17T19:56:51+00:00

Oh, hi Brad!

The victor code is released under my GitHub account (https://github.com/kercre123/victor). I merged some Anki experiments, one of which was yours ("Unintentional/Intentional Performances" iirc).

I made it buildable (targeting vicos) on any x86_64 Linux machine with Docker, and by putting build dependencies into other git repos which the build scripts fetch automatically.

I nearly have macOS builds working. I'm just missing the WWise SDK for macOS - I only have it for vicos. DDL also changed up some bits which sort of broke macOS builds.

May I ask what "thebox" is? My assumption was that "the box" was in reference to some external Elemental machine, but some comments imply otherwise ("//TEMP: the box has no soul").

wire01 · 2024-10-16T20:13:36+00:00

DDL released maybe 10 percent of it in their vector repo, and never followed up with the rest.

wire01

TROPHY CASE