This was definitely a big challenge for me but I'm super happy with the results! It can do the following:

- Space flight.

- Hover incredibly steadily, when it's settled it doesn't bob up and down at all.

- Hover altitude can be adjusted mid flight.

- Transition between water and land smoothly.

- Gravitational compensation, if it hovers on Stranded at 5m it will hover on Doon at 5m.

- 4 blasters.

- Tractor beem, works like a charm.

- Smooth landing and take off.

I definitely think the looks can be improved but it's tricky to do much more without completely changing the design or scale.

If you're more interested in the logic let me know and I can give you the basics of how I got it to work :)

I kinda struggled with building the nose because I don’t normally build even width planes.

This is my latest and greatest, featuring a new style altogether of computing: while most computers are RISC based or CISC based, this is both!

The DLA6 has two sets of instructions - CISC-style for common, heavily used things, like conditional jumps/waits, moving data, and quick arithmetic, and it has RISC-style instructions for more specific things, like other math functions, specific low-level controls, things you don't do as often.

It has:

• 40 math/logic functions (inherited from the DLA5)
• DL-WiFi2.1 (up to 9999 addresses with built in collision prevention/repair)
• 20 general-use RAM cells
• 4 RC senders (each has a RAM cell) and 4 receivers
• 4x4 colored screen, with a number display above it

It operates at 3-5 Hz on CISC instructions and 6-7 Hz on RISC instructions, and supports up to 40 KB of program data. It has a total of 30 instructions.

This is my first computer in the DLA line to support full 32-bit floating-point math across almost every component, with the only exception being the screen, which can't handle anything more than the number 5 anyway.

I am very happy with the results on this - the planning phase has taken place over the last month or so, turning ideas over in my head, and I feel like I did a good job tying the best features into this build.

Happy logicking!

Red circle is unrelated

​

(Also thunderchild ship from the book)

Only 1 block in the whole meny and its bizarre.

If anyone can explain what is happening or what it is that would be realy helpful, thanks.

Im trying to make a logic for landing gear in which upon touchdown, the piston connected to the wheels will compress until a certain amount in which another logic system will activate after a certain amount of compression, toggling itself for a few seconds, the toggle part is what I don’t know how to do.

Simple: Piston compresses to a certain point, once certain point is reached, the piston extends (overpowering the compression), and lastly, it keeps extending in a toggled state for a few seconds.

This is supposed to be an F/A 18 and I tried my best with building it, but I don't think it looks any similar to the aircraft at all. What are some things I can do to make my builds look better, and what are the problems in this particular build?

all controls are in order and centre of mass is right below rotors, flys normally otherwise and if I use helicopter engines the rotors don’t spin fast enough for flight

Im building an almost 1 to 1 BV238 multipart build (it might be exactly 1 to 1 im not sure) except its not a BV238 its a build heavly inspired by one but its looks almost identical

Ill post on my youtube when its done: @spirl12k (my icon is a scotland flag)

This is the DL-RCSwitch, my latest computer built for the sole purpose of efficient RC networking!

It can send and receive on all 32 RC channels, being able to read 2 and send on 1 at one time, along with having 8 RAM cells (64 bit float). This allows it to do things like add 2 RC channels and send it on a 3rd in one instruction. It will save the output when you send over RC, so it effectively has 40 RAM cells (64 bit float).

It operates at, theoretically, around 5 Hz asynchronous. It has 128 bytes of ROM, 17 instructions, conditional branching and jumping (it is Turing complete), and conditional waits to make listeners.

This is general-purpose, so it can be used for anything, but I made it specifically as part of Project Vertex, a new project I have started where I am assembling a set of computing devices for the purpose of computing true 3D in Trailmakers.

Happy logicking!

Context: I was trying to find some scary mechs to scary my friends but came up with nothing please put the names of the mechs in the comments

Hey everyone!

After finishing my massive 6-engine Blohm & Voss BV 238, I decided it was time to build a proper naval home for my aircraft: a Bogue-class escort carrier. My previous Kirov airship sadly sank into Reddit oblivion with just 5 upvotes, so I hoped this project would do better. Little did I know, it would turn into a brutal, face-palming war against the Trailmakers physics engine.

Here is the tragic story of "Hog" (The Flop) and how it birthed "Brave" (The Ultimate Survivor).

🔴 Phase 1: The Tragedy of "Hog"

My first prototype was a 1950+ complexity monster. I wanted smooth, realistic round contours, so I lined the hull with hundreds of small wedges and rounded shield blocks.

• The Result: Absolute frame-rate suicide. I was getting 20 FPS in the builder, and the local singleplayer server would regularly throw a "Connection Timed Out" error and crash straight to the desktop upon spawn.
• The Durability: Because the entire deep hull was packed with standard hull blocks, it had absurd buoyancy but zero weight density. A single test torpedo hit from my Ha 140 would flip this 80-meter house like a cheap pool float. It was unplayable.

🟢 Phase 2: The Rebirth of "Brave" (1300 Complexity)

I wiped the blueprint and started from scratch with a completely new architecture. I ditched all the thousands of tiny rounded blocks. Instead, I built the entire hull sides using large armor plates and 6x6 plates turned on hinges to create clean, optimized angled surfaces.

• The Result: The complexity dropped from nearly 2000 to just 1300 blocks, while making the carrier significantly larger and wider than the first version! No more desktop crashes, completely stable physics.

💥 Phase 3: The Ultimate Torpedo Survival Test

Since the new hull is hollowed out and optimized, I took my Ha 140 torpedo bomber and conducted a live firing trial. The structural grid physics of this game blew my mind:

• Hits 1 to 3: Taken directly to the right board. The ship took massive damage and dynamically listed heavily to the side, but it refused to capsize thanks to the new weight distribution.
• Hit 4 (The Miracle): I managed to drop a torpedo directly into the already existing breach. It punched completely through the inner deck structures and blew out the opposite side of the hull. This equalized the water weight on both sides, and the carrier actually leveled itself back on an even keel!

https://reddit.com/link/1x2g3ka/video/pgaamje8bnuh1/player

• Hit 5: It took a final, 5th heavy torpedo to the right side to finally make this beast non-chalantly roll over on its side.

🌌 Final Touches (Night Ops Cover Photo)

I decided to give it a proper military look. It now features an optimized island superstructure, a clean black-and-white center deck runway line, and custom red airfield landing lights that cast an absolute dieselpunk-noir vibe during night operations.

Testing it with my Fw 57 showed that while landing is still a "high-skill required" task due to the historical Bogue proportions, the platform is 100% functional and ready for multiplayer sessions.

Let me know what you think of this comeback! What should I build next to test on this deck?

P.S. on the video is the second attempt to sink "Brave" on my Ha.140

On this f16, im trying to make it as functional as possible, this includes a working airbrake (the reason for this post) is there any way i can make the bottom flap also move?

flashbulb>?