Загрузка видео...

Не удалось загрузить видео

На главную

Rendering some of my previous work with Eevee Next! Very impressed with it so far, I simply loaded my old blend file and worked straight away! Also, the compositor can run on the GPU! exciting times ahead! This animation is based on the 240W USB-C charger from EPC #b3d...

19,249 просмотров • 2 лет назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

today was the first time i was genuinely impressed with what AI can do i recently decided to buy a whole FPV drone setup knowing basically nothing about the hardware side of it there's a pretty steep learning curve even just to set everything up properly: radios, RF protocols, flight controllers, ESCs, firmware, batteries, goggles, betaflight configs etc as someone that spends essentially 12h a day prompting agents to build software, it's actually pretty rare that i interact with AI on something where i have zero idea what's going on under the hood, and i never really used it for debugging a bunch of physical devices that all have to talk to each other i had codex + voice mode open for basically the entire setup. told it everything i bought, sent it some pics and then just started talking to it >what order do i set all this up in >how do i change this setting on the radio >which of these cables do i use >the drone is flashing pink wat mean >can you make this thing less insane to fly in my apartment and it was surprisingly seamless it would go find the manual for whatever specific thing i was holding, tell me exactly which buttons to press, what port to plug something into, what i should see if it worked etc then when i got to configuring the actual drone i had codex running on the computer it was plugged into, so it could inspect the config, back everything up, change settings, send usb reboot signals and check what happened the insane thing about voice mode is that youre literally hands on with the hardware and just telling codex what it should do, i literally never touched a thing on the computer besides starting voice mode if something doesn't work you tell it what happened and keep going a few hours of this and i had the radio, goggles, charger, batteries, drone firmware and betaflight all set up and had actually flown the thing the part that stuck with me is that i also understood what most of it was doing by the end, every time there was a term or tech i didnt understand id just ask to explain there is something absolutely magical about having proper real time personalized assistance, being able to dump a pile of unfamiliar hardware on your desk and have something figure out exactly what you own and walk through it with you in real time you become the missing physical link pressing the buttons i think spending all day using coding agents has actually made me pretty numb to AI progress. every new model is a bit better at some benchmark or can oneshot some task that the previous one couldn't and you just kinda adjust to it this felt different mostly because i had no existing knowledge to fall back on for the first time the jarvis comparison didn't feel cringe ai for coding and general computer tasks is cool and all but this feels a lot closer to the endgame anyone should be able to just ask any question about whats going on in their life and have realtime support i wonder if more hardware products will actually start exposing some sort of MCP or interface for agents to plug into thinking for example of how elevators in china are increasingly built with interfaces that let delivery robots call them directly instead of having to physically press a button we might actually start seeing hardware design shift from being purely human-interface-first to also being agent-interface-first buttons, screens and menus exist because humans need some way to tell machines what to do. agents don't necessarily need any of that if the hardware exposes an interface directly very curious which side closes the physical world gap first: humanoid robots that can operate hardware designed for humans, or hardware adapting so agents can operate it directly

ultra

18,096 просмотров • 16 дней назад

004/100 Buttons. A bit of the process on building an animation. When looking at a finished animation or in this example a finished button, it can look quite complex inside the CSS. But when building it, it’s more like a lot of simple steps, one after another. Here I had the idea to make some kind of text animation like the footer logo on the Osmo site. I try to add the base animation with no complex easing, for example transition: translate 0.4s ease. Starting with just moving the one text from bottom to top and the other text to top. Adding a stagger, play around with it. Searching for a way to make it more circular. On the research I found the sin() function inside CSS which can build a more smooth non linear curve for the stagger which creates this circular effect. And step by step adding more complexity like, different easing for hover/hover-out, opacity, 3D transform and more. I use also the sin() function to rotate the letters, so the middle ones are getting more rotated than the outer ones. Another thing which helps is to add a small delay on hover, for example 0.05s or 0.1s, you don’t really see the difference, but when you hover pretty fast on and out it doesn’t get that jumpy. I’m using here GSAP’s SplitText to split every char into spans. And then I’m adding a CSS index variable to every span, starting from the center. SplitText can provide CSS index variables, but you cannot tell it from which direction. For the sin() it’s also important to have a max length, so I add another CSS variable with the max char number on it. Crafting 100 Buttons with Osmo ⏳ Total time: 63h

Eduard Bodak

166,023 просмотров • 4 месяцев назад

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 просмотров • 4 месяцев назад