Singapore 🇸🇬
Joined October 2021
- Tweets11.3K
- Following7.2K
- Followers3.7K
- Likes71.6K
Brian Chew retweeted
Imagine having an assistant working on your game’s animations while you build the game with Codex.
That’s my current workflow for Echoes Below:
- Codex helps code the game engine and gameplay.
- Tripo generates the 3D assets.
- Dots helps edit and animate those assets in Blender.
Right now, Sherly, my Dot, is working on the character’s movement and bow animation. I can watch her Blender session and give feedback while working on the code with Codex.
Still a work in progress, but I’m loving this workflow for making a game.
Let’s see how it turns out.
ALT Sherly's view-only Blender session showing the new untextured elf rogue holding a bow, still a work in progress.
ALT Sherly chat next to the Tripo elf rogue character standing with a bow, arms out.
ALT Four frames of the old green-hooded character. The old ranged animation is shown last, not the new bow work.
This is the breakdown I wanted to see. Doodle to Godot, and you can tell exactly what each tool is doing.
My Echoes Below flow matches the first half. Reference image in Codex, then Tripo for the 3D model and texture. The elf Fighter's sword used P2.0 Smart Mesh in Quad mode with a 2K texture, exported as FBX and GLB, and the shield went through the same flow.
The second half is where we split. You rig and animate in Blender with Claude. I let Tripo assemble the equipped fighter first, and it came back with 55 joints instead of the original 65. So my next step looks like yours, a proper Blender pass on the original rig.
After that I check idle, slash and walk frame by frame. A sword clipping through the head on a slash is the kind of bug that only shows up once the character moves.
Saving this for when I start the Blender part.
ALT Codex reference image of a green and gold shield with a leaf emblem
ALT The textured 3D shield generated in Tripo Studio from the reference image
recommended reading
A detailed report of the October 21st security attack
blog.railway.com/p/incident-…
1
2
625
Brian Chew retweeted
It's been a busy last few weeks, but our community never stops! We've had local hosts gather people globally pretty much every day. 😄
Here's what is coming up this week:
Mon, 9 Nov
🇯🇵 Nagoya
🇸🇰 Bratislava
Wed, 11 Nov
🇪🇨 Machala
🇬🇧 Cambridge
🇸🇪 Stockholm
🇲🇽 Monterrey
Thu, 12 Nov
🇳🇿 Christchurch
🇦🇺 Adelaide
Fri, 13 Nov
🇦🇺 Sydney
🇩🇪 Frankfurt
Sat, 14 Nov
🇦🇺 Sydney
🇲🇾 Kuala Lumpur (Kajang)
🇻🇳 Hanoi
🇲🇦 Marrakech
Sun, 15 Nov
🇮🇩 Jakarta
🇮🇱 Tel Aviv
Find an event near you → luma.com/codex-community
Huge thanks to our Codex Ambassadors for bringing their communities together. 🫶
Brian Chew retweeted
had a lot of fun playing with @LottieFiles this week.
used it to add more personality to the peek logo, and a bit of sass to the app. as a consumer app founder, that kind of attitude in the product makes a huge difference.
here's how i did it 👇
Brian Chew retweeted
Dots can now control many machines in addition to its own little cloud computer that we provide by default.
Brian Chew retweeted
🧵 OpenAI Build in Public Thread 🧵
I know it’s crazy, I'm building a prompting system out of my @OpenAIDevs @OpenAI merch from dev day.
Hard to believe last Sunday was the DevDay hackathon in London, and last Tuesday was DevDay itself. I wanted to turn that energy into something real.
Also good to bump into a few folks @reach_vb @paw_lean @Andy_AJT @embirico @thsottiaux @romainhuet
Here's what I'm working on 👇
FYI : Using lots of MCUs from @seeedstudio and extracting items from previous hackathon stuff I have already - I.e I extracted the button from my AirPods to power the
First prototype (Black OpenAI dot) .
Brian Chew retweeted
commercial flying has only been around for 112 years.
i was looking out the window thinking: people figured out how to do this.
how fucking crazy is that.
and yet most of us barely look up from our phones while flying.
human ingenuity got us here, and it got us to AI.
where will human ingenuity + AI take us?