TechyMagThings

RC planes are a lot of fun, and the bigger the better! [Ramy RC] has built the world’s biggest RC A380.

At 29 ft (8.83 m) long, with a 32 foot (9.75 m) wingspan, and weighing 800 lb (362 kg), this 1/8 scale jumbo jet is not your typical model. The fuselage is built from CNC cut EPS foam layed up with fiberglass on the outside and carbon fiber inside. The wings have a combination of carbon, aluminum, foam, and wood components to handle the aerodynamic loads.

The attention to detail is wild. Instead of painting the windows, each one is an actual hole in the plane with a 3D printed window frame and acrylic window. You can actually see one falling out of the plane in the video below. An Airbus mechanic in the comments even notes the landing gear door order of operations are identical to the real thing.

If [Ramy] looks familiar, perhaps you remember his previous A380 build? Much like the 747, the full size A380 is no longer in production, but they can run on cooking oil while they’re still flying.

YouTube streaming typically involves a camera with an HDMI output, a USB3 HDMI digitiser, and a suitably beefy PC to run it all. It’s quite a process, and for [Coreymillia], more complex than it needs to be. He’s come up with something simpler, a dedicated self-contained streaming rig using a Raspberry Pi 4.

As you might expect it uses the Raspberry Pi HQ camera at the optical end, but it’s the software surrounding it that transforms it from a mere camera into a streaming rig. There’s a web based user interface, but perhaps more interesting are the companion dashboard peripherals. A Raspberry Pi or an ESP32 Cheap Yellow Display can both serve as a small in-view dashboard and controller.

We know from experience that a stream can be a difficult thing to get right even with high-end hardware, and we’re interested to see this standalone device allowing , we hope, an easier way to do it. If you’re a streamer we’re guessing you’ll be taking a closer look. Even so, this is surprisingly, not the simplest Raspberry Pi based streaming device we’ve seen.

Swift is a relatively modern program language, appearing in 2014 as a replacement for Objective-C. Since then, it’s become a popular solution for programming apps across Apple platforms. That led [Yeo Kheng Meng] to a simple yet fun idea—porting Swift to the oldest Apple platform of all.

Yes, [Yeo] managed to build a development environment for Swift that targets the Apple II platform. Not just one machine, either—everything from the original Apple II up to the IIe and a little beyond. Now, the Apple II is very different from modern Macs and iPhones and the like, having debuted in 1977 with a 1 MHz 6502 CPU and a minuscule 4 KB of RAM. But that doesn’t mean you can’t use a modern language to develop for it!

[Yeo] does a great job of explaining how it all works, and how Claude Code and GPT 5.5 Codex were used to help piece things together. The compiler is set up to spit out bytecode that’s executed by a virtual machine running on the 6502. The target was to allow the setup to work on a standard 1977 Apple II from the factory, which would allow it to then run on subsequent models without issue. However, there is a small note— [Yeo]’s implementation requires the RAM to have been upgraded to 48 KB.

We love seeing modern stuff ported to the Apple II. This Portal port was a particular highlight.

The recently released Valve Steam Machine is that it uses a custom, non-standard PCB and non-standard power supply. This fact apparently has irked some people who decided that it makes perfect sense to try and cram a Mini-ITX board, Small Form Factor (SFF) PSU and full-sized discrete GPU into an enclosure of the same size. Cue the SFF Mini-ITX Steam Machine Case project by [3DCatt] over at Printables.

This is apparently a project done in cooperation with AMD’s [Jacob Terkelsen], who showed off the 3D printed case stuffed full with the aforementioned parts, which includes a GeForce RTX 5060 GPU. Of note is that the Valve Steam Machine uses a different cooling configuration as it has both the CPU and GPU on the same PCB. These share the same massive heatsink, as can be seen in e.g. the [Gamers Nexus] teardown video.

For this angular imitation machine it would have been nice to use a blower-style GPU, to exhaust the hot air rather than dump it all into the case. This is also an issue that was raised by [Jacob], with more ventilation added to mitigate the issue. What the overall performance will be compared to regular compact Mini-ITX cases remains to be seen, but if you really want to live the Steam Machine life and have some parts kicking around along with a 3D printer, it might be worth a shot.

When people start ranting about AI, you can be sure a few things are going to come up during the two-minutes hate: job loss, higher power bills, the neverending tide of low-effort slop, and wasting precious freshwater. Well, NVIDIA wants to take away that last one, beacause the all-water cooled Ruben architecture won’t need any evaporative cooling— coolant can stay in a closed loop, and never needs to be cooled below 45 C, or 113 F.

This sort of coolant loop should be familiar to anyone who has ever built a water-cooled PC or PlayStation: there’s a glycol-water mix, water blocks, and a radiator to reject heat to the environment. NVIDIA doesn’t mention if their new servers come with RGB lighting, but we’d like to imagine it’s an option. The big difference — aside from the rainbow LEDs– between a Ruben server and your old gaming rig is that in these racks, everything is on a waterblock. If there’s a chip on the motherboard generating heat, it’s getting rid of it into the same cooling water. Cooling water, that we have to emphasize, needs only be cooler than the chips themselves: in this case, they’re talking 45 C on the cold side, and 55 C headed out of the racks. (That’s 113 F to 131 F for all the bald eagles reading this.)

Given the required temperature drop is so modest, there’s no need for the evaporative chillers that have given AI data centers such a bad name in water conservation circles. Just like in a water-cooled PC, ambient-temperature air running over dry heat exchangers– also known as big honkin’ radiators–is able to handle the cooling, so no water is lost. Since everything is on waterblocks, there’s no need for cooling air, either, and the server farms need only be air conditioned to the degree required to make them comfortable to work in.

If you think NVIDIA is making this change because they suddenly care about water conservation, think again. The press release makes their motivations very clear: cooling costs money, and running this hot saves a lot of it. We’re talking four mil US a year for a 50 MW hyperscaler. One might suspect that this sort of thermal regime could limit the lifetime of the hard-working NPUs, but since they’ll be obsolete in a few years anyway, that’s not likely a big concern, especially not for NVIDIA.

We’ve actually seen hotter fluids used to cool computers before– coffee, for one. Water cooling also isn’t new in the data center world; we took a look at it a few years back. Things are clearly heating up now, though.

Recently [Bits und Bolts] found himself in a bit of a pickle, when on boot his PC would complain about a connected USB device drawing too much power, before shutting down again. After unplugging various USB devices, the problem was narrowed down to an Elgato Cam Link 4K video capture device.

Some prodding and poking around with a thermal camera on the disassembled device while powered showed that an onboard IC had sprung a power leak. Sadly, even asking nicely, Elgato support wasn’t going to provide board-level repair help, so this was left as an exercise to the owner.

Although the markings on the chip didn’t offer much help, it turns out that this is a more common issue, with a convenient repair guide by [Uldis Melderis] identifying the part as the TI TLV62585 buck regulator.

After purchasing a couple of spares, the defective IC could then be replaced. Following this a quick test showing decidedly less angry electrons. From there it was a matter of reassembling the device in its plastic case and seeing whether the PC was happier with the now hopefully fixed device, which fortunately turned out to be the case.

Any such analysis and repair obviously raises a number of questions, such as why these buck regulators are dying, and why you’re supposed to just toss out a $100 device instead of doing a repair involving a $0.20 part and a few minutes with a hot air gun.

[Dominic Buchstaller] wanted a neat, tidy entryway keypad that actually looked good. Prime goals were something slim, wireless, and with no visible screws. Dependency on the cloud was also a no-go. With few ready-to-go options available on the market, he set about whipping up his own.

The heart of the build is an ESP32-C6 microcontroller devboard. This device has the benefit of including Zigbee communication functionality baked right into the chip. It’s hooked up to an MPR121 capacitive touch controller, which allows different segments of the touchpad PCB to act as capacitive buttons for numerical entry. The number labels are directly printed on the PCB solder mask, so there’s no overlay or other label required on top. Power is courtesy of a 1300 mAh lithium-polymer cell which gives a useful lifespan of six months between recharges. A simple 3D-printed case holds everything together and completes the clean and simple look. [Dominic] notes that it’s possible to also use the device via Matter or Thread without a lot of changes, as the ESP32-C6 can easily handle those protocols, too.

If you’re looking for a cheap, handsome keypad for your Home Assistant setup or similar, you might find this useful. We’ve explored DIY keypad entry systems before, too. If you’ve come up with some other creative way to get into your house, car, or bank vault, be sure to notify us via the tipsline.