#cylinder tracking system

[trakaid4u]

Enhance Safety and Efficiency with Trakaid's Cylinder Tracking

A cylinder tracking system is an innovative solution designed to enhance the management and monitoring of gas cylinders within various industries, including hospitality, healthcare, and manufacturing. This system enables companies to efficiently track the location, status, and usage of their gas cylinders in real-time, significantly reducing the risk of loss and ensuring timely refills. By utilizing advanced technologies such as RFID (Radio-Frequency Identification) and IoT (Internet of Things), businesses can streamline their operations, improve inventory management, and ensure compliance with safety regulations. With a robust tracking system in place, organizations can optimize their resources and enhance overall operational efficiency.

At Trakaid, we specialize in providing state-of-the-art cylinder tracking systems that cater to the unique needs of each client. Our comprehensive solution includes intuitive software that allows users to monitor cylinders from anywhere, along with hardware components designed for durability and ease of use. With features such as automated alerts for low inventory and expiration dates, our system minimizes downtime and enhances safety measures. Trakaid is committed to delivering high-quality tracking solutions that empower businesses to manage their gas cylinders effectively, ensuring they can focus on their core operations without the hassle of tracking inventory manually. Experience the benefits of enhanced visibility and control with Trakaid’s innovative cylinder tracking system. Visit Now: https://www.trakaid.com

[rupasriymts]

[whirligig-girl]

(zoom in!)

Two double-headers on the Trans-Gooiw Railroad passing each other in the hills, dragging long freight trains behind them, during the early days of the Pan-Mellanus Oil Crisis.

More mellanoid trains: Guz's Model Garratt | Museum-piece carrying rocket parts | Advanced Steam Tank Engine | Guz's bigger model Garratt | Tram and Coal Mine loco sketches.

The diesel-hydraulic at the front of the foreground consist, already somewhat old and tired by this point, dates back to around the time period that steam engines were originally retired on Mellanus. It's not very fuel efficient as it is, and with the oil rations, diesels can not handle the trains on their own any longer.

For a few years now the railroads have been taking their steam engines out of mothballs and museums, as coal was comparatively dirt-cheap. Still though, the various maintenance and operational complexities of running steam locomotives resulted in a lot of losses for the railroads.

Pictured here behind the diesel is an early attempt at the Advanced Steam Engine concept, modifying a member of a very prolific and successful 2-8-0+0-8-2 Garratt class with a gas producer combustion system, more modern cylinders and valve gear, and entirely replacing the cab with an electronic control system (with the more diesel-like control stands moved to separate cabs on the tenders). The electronic control scheme allows for the steam engine to be connected to a diesel engine to be run as a multiple unit, cutting down operational costs. However, as a modified prototype, this locomotive lacks some of the other features which exemplified the Advanced Steam era, such as modular ashpans, computerized control, and precision engineering.

On the other track, moving the opposite direction, we see a double header of two steam locomotives, another 2-8-0+0-8-2 loaned from the Slaibsgloth Coal Mine Railroad, and a 2-10-2 'easy' type non-articulated loco leads the train. In this case, there is no electronic connection, so a crew of four mellanoid slimes is necessary to operate the train.

The eagle-eyed railway fans will notice that there are radiators for a dynamic brake on the diesel, yet the diesel is an electric. Diesel-electric dynamic brakes switch the traction motors into generators, and dump the electricity out as waste heat--but there's no traction motors on a hydraulic. So why the radiator fins? There's still a dynamic engine brake on the diesel-hydraulic, so it still needs to be able to dissipate heat, especially on the mountain routes.

WIP images follow:

[nabazakk75]

**The BAC Mono: A Singular Experience in Automotive Performance**

In a world dominated by multi-seat sports cars and luxury performance vehicles, the **BAC Mono** stands as an anomaly. With its singular, monocoque design and an almost obsessive focus on the driving experience, this British-made hypercar offers enthusiasts something entirely different—a car built for pure driving pleasure. The BAC Mono isn’t just a car; it’s a reminder of the connection between man, machine, and road.

### **A Brief Introduction to the BAC Mono**

Manufactured by **Briggs Automotive Company (BAC)**, the Mono is a single-seater, track-inspired sports car that blurs the lines between street-legal car and racing machine. Introduced in 2011, the BAC Mono has quickly gained a cult following among driving purists who appreciate its minimalistic design, extreme performance, and exhilarating driving dynamics. This car isn’t meant for daily commuting or family trips—it's built for those who crave an unfiltered, high-performance driving experience.

### **Performance That Rivals the Best**

At the heart of the BAC Mono is a **2.5-liter four-cylinder engine** that produces 305 horsepower. On paper, this might not sound like a massive number when compared to other supercars, but thanks to its incredibly lightweight construction (weighing just 540 kg or 1,190 pounds), the Mono has a power-to-weight ratio that rivals the most exotic cars on the planet.

The engine is paired with a **6-speed sequential gearbox** that allows for lightning-fast gear changes, contributing to the car's superb track performance. The Mono's 0-60 mph (0-100 km/h) time is a blistering **2.8 seconds**, while it can reach a top speed of 170 mph (274 km/h). These numbers, coupled with a fully independent suspension system and lightweight carbon-fiber bodywork, result in a vehicle that is agile, responsive, and remarkably stable at high speeds.

### **Design Focused on the Driver**

The **BAC Mono** is fundamentally designed around the idea of the "driver's car." The cabin is minimalist but functional, with a single racing seat at the center, surrounded by a digital dashboard and a steering wheel that places all critical information and controls at the driver’s fingertips. The design makes it clear that this car is all about the person behind the wheel.

With its fully enclosed cockpit, a low stance, and an open-wheel layout, the Mono feels more like a Formula 1 car than a typical road-going sports car. The carbon fiber body not only reduces weight but also provides exceptional strength and rigidity, allowing the car to tackle tight corners and high-speed straights with precision and confidence.

The car’s adjustable suspension system ensures that it can be fine-tuned for a variety of driving conditions, from smooth tarmac to the rigors of a race track. The open-wheel design, while visually striking, also serves a functional purpose: it improves airflow around the vehicle, contributing to both aerodynamics and cooling, crucial for the kind of high-performance driving the Mono is built for.

### **Precision Handling**

The steering of the BAC Mono is precise, quick, and offers an incredible level of feedback. With its **low center of gravity**, the car feels glued to the road, providing a sense of control and responsiveness that is hard to find in many other vehicles. The Mono’s suspension system and high-performance tires ensure that it delivers an incredibly stable ride, whether you're taking tight corners or pushing it to its limits on a race track.

Driving the Mono is a visceral experience. The car is designed to be felt as much as it is driven. With every input, you feel the direct connection between the car and the road. Its lightweight nature and finely tuned handling make it an absolute joy to drive, especially in track conditions where its true potential can be unleashed.

### **Exclusivity and Customization**

BAC takes the idea of exclusivity to heart. Each Mono is built to order, with the company offering a range of customization options to ensure that each car is unique to its owner. Whether it’s bespoke paintwork, interior finishes, or specialized performance components, the Mono is made to reflect the personality and preferences of its driver.

Additionally, BAC offers a "Mono Track Pack" option for those who want to take the performance up a notch. This package includes enhancements like track-focused tires, additional aerodynamic elements, and lighter materials that further reduce the car's weight, pushing it even closer to the performance characteristics of a full-blown race car.

### **A Thrilling Driving Experience**

The BAC Mono is more than just an amazing feat of engineering; it’s about the **experience**. This car is not meant to be a comfortable, cushioned ride. Instead, it’s about immersion, about feeling every twist in the road and every shift in the gear lever. There are no distractions—no radio, no luxury features—just a focused, raw connection with the driving experience. It’s an experience that only those who have had the privilege of driving the Mono can fully appreciate.

### **Conclusion: A Driver's Dream**

The BAC Mono is a car that represents the purest form of driving. While most hypercars focus on speed, luxury, or technology, the Mono prioritizes one thing above all: an unadulterated driving experience. Every aspect of the car is engineered with the singular purpose of delivering the most thrilling, responsive, and dynamic performance possible.

For those who value the art of driving, the **BAC Mono** is a dream come true. It's not a car for everyone, but for those who crave the purest connection between man and machine, it offers an experience that few vehicles can match. In a world where the line between road car and race car continues to blur, the BAC Mono stands out as a reminder of the joy of driving in its most unrefined, exhilarating form.

[literallymechanical]

How do they keep up the fuel input into a fusion reactor? And how do they get the specified fuel mix into the reaction area if it’s sealed?

Oh that is a very good question! So, yes, the vacuum vessel is sealed, but there are plenty of vacuum passthroughs and other equipment that sticks into the torus. In this case, fuel is added to the fusion plasma in a couple of ways: the old-school method where it is "puffed" in as a gas, or as is more common now, it is fired in at extremely high velocity as frozen pellets of hydrogen isotopes.

Here is how the frozen pellet injectors are set up on DIII-D, in San Diego. Some are fired directly at the midplane at extremely high speeds (like, 1000 m/s (over 2000 mph!)), whereas some take a more circuitous, slower route – you get better fuel penetration when launching from the inner wall of the torus, even with slower pellets. This is done with a burst of pressurized light gas, usually hydrogen.

Here's a 1.8 mm diameter deuterium pellet bursting into plasma as it is launched from the midplane of ASDEX-Upgrade at 800 meters per second (1800 miles per hour):

pchooo

However, traditional gas-pressurized systems have a problem with a slow rate of fire (tens of Hz) and introducing potentially unwanted gas from the launcher. How to solve these problems?

ASDEX-Upgrade in Germany has pioneered a new method of rapid pellet launch: extrude a cylinder of frozen fuel into a centrifuge, which slices off pellets and launches them into the reactor! No pressurized gas needed. This iteration can do it at 70 Hz, but future centrifuges could go much faster.

Pellet injectors have more uses than just fueling! These are the nozzles of a "shattered pellet injector," also in ASDEX-Upgrade.

Rather than launch a tiny pellet of fuel, these have a sharp angle at the end that shatters a giant pellet (3 or 4 cm wide) of frozen heavy gasses (neon, argon, etc) and/or deuterium just before it enters the plasma. The sudden burst of fragments will do all sorts of funky things, like stop the fusion plasma dead in its tracks. This is an important way to mitigate disruptions that might damage the reactor.

For a very thorough overview of pellet injection technology, check out this paper out of Oak Ridge National Lab. They are one of the leading pellet injection research labs, and their launchers are installed in tokamaks all over the world:

[stigblomqvists]

INSIGHT

In the 80s, Group B had a vast collection of automotive beasts from different car manufacturing companies. One of these companies included Peugeot, where their 205 T16 simply rocketed through tracks. This Peugeot in particular, model 205 T16, absolutely dominated rallies within the golden age that was Group B. The 205 T16 technically was the most successful car in Group B with its 16 victories out of 26 starts and lastly 2 world championships to its name.

NOTABLE DRIVERS

1. Juha Kankkunen 🇫🇮 2. Ari Vatanen 🇫🇮 3. Timo Salonen 🇫🇮 ENGINE SPECS

Cylinders: L4 Displacement: 1775cm^3 Power: 200HP [at precisely 6750RPM] Fuel System: Turbocharged Multipoint Injection Fuel: Petrol

PERFORMANCE SPECS

Top Speed: 130mph [209km/h] 0-60mph: 6s

TRANSMISSION SPECS

Drive Type: AWD Gearbox: 5-speed manual

[theramblingsofadork]

None of the boys on the Starpoint Squad have a professional background in engineering or chemistry, so when Starline tells them not to eat in the lab or while constructing the robot, they don’t take him very seriously.

This results in him flipping his lid (reasonably so) when he finds them doing just that, despite his warnings.

They do meekly apologize when they learn there is actually a real, scientific reasoning behind his words, and it's not just because he's being a stick in the mud.

Goes to show, Starline’s not the only one to get a slice of humble pie during the competition! XD

Accompanying fanfic below the cut!

vvvvvv

📘📙 Fanfic: A Slice of Humble Pie

Accompanying Music Track: World Trigger - 12/30

Starline stopped dead in his tracks the moment he stepped into the room. The platypus’ eyes widened when he saw Charge, Hex, and Lug standing around a table in the center.

Munching on cookies and cinnamon covered churros as they worked on the robot’s response system to Cello’s chemical mix.

Rivet immediately saw the problem too and clicked her tongue, green eyes shifting to the doctor besides her as his fists tightened at his sides. “Oh boy...” She managed to get out before Starline’s patience utterly cracked.

“GENTLEMEN!!” He exploded at the group, all of whom immediately looked up and froze like they had been caught with their hands in the cookie jar. (Ironic, because of what they were snacking on.) “WHAT DID I SAY ABOUT EATING AROUND THE EQUIPMENT?!”

The three stared at him blankly before Hex slowly crunched down on the cookie still in his mouth to reply, “Um… not to do it?” He squeaked.

“And yet, here you are, going against my very clear instructions and making an absolute mess!” Starline exclaimed angrily before he stomped over to them with balled fists. “Did it not occur to you—“ He yoinked the cookies away from Charge. “—That I had a very good reason—“ He plucked away Hex’s next. “—For telling you all not to eat in here?!”

He reached to grab the churro away from Lug, but the bulldog knit his brows together and quickly held it up out of Starline’s reach in defiance. The platypus merely gave him an unamused deadpan before a portal activated over his head, allowing Starline to easily take it from him.

The bulldog sputtered at his now empty hand and at being outsmarted, before growling deeply as the doctor continued by without so much as a second glance. “Grrrh… Well MAYBE we just thought you were being a big ole, grumpy stickler! I paid for that, you know!!”

“Well then, maybe next time, you’ll heed my words,” Starline stated with an over the shoulder frown as he crossed over to the nearest trash can to dump the confiscated goods into it.

“I don’t get what the big deal is, doc,” Charge said as he frowned and rested on his elbow on the counter.

“Clearly.” The platypus’s tone was practically dripping with sarcasm.

“…Look, I get the whole liquids thing for obvious reasons, but is food really THAT much of a problem?”

“Yes, it is. And quite frankly, I’m surprised I even have to be saying that!” Starline exclaimed before the bag of cookies made a particularly loud ‘cur-chunk!’ as it hit the bottom of the cylinder.

Starline then spun to face them again, crossing his arms like a disappointed parent. “I understand that none of you have ever had formal training in a professional setting like this… but even so! I expected you to have SOME common sense!“

“Hey! You calling us dumb or something?!” Lug complained as he leaned atop the counter.

Starline sighed dramatically and pushed his fingers into his ivory bangs. “Your words, not mine, Lug.”

“HUHHH??”

“Regardless! Since it seems that merely believing the words of a professional isn’t enough for you, I suppose I have no other choice than to make it perfectly clear why we mustn’t eat in here.”

Gazing out to the annoyed faces watching him, Starline began to explain. “Contrary to what you all might think of me, I tell you this NOT because I am a stickler and want you all to starve. But rather because ingesting food or drink in a setting like this poses a very real and very dangerous health hazard! Not to mention it could potentially mess with the reliability of our tech!”

“‘Health hazard?’ ‘Mess up reliability?’” Lug squinted suspiciously, not buying a word of it. “How?”

Starline motioned to Charge, whose ears flattened at being singled out. “For example: Charge is currently handling the concoction Cello made, testing if the fluid is potent enough for what we need to operate the hydraulics system, is that correct?”

Charge nodded and picked up the capped glass container with the glowing blue liquid inside. “Yeah. Cello wasn't sure how concentrated it needed to be, so I’m adding it little by little to get the proper dosage. But I’m keeping it covered so it doesn’t spill and no crumbs can get inside!” He gave the bottle a little shake, causing the liquid to noisily slosh against the sides.

“A measly effort at best to prevent incident,” Starline scoffed dismissively, which earned an immediate frown. “By handling the chemicals, then eating and sharing your food with the others immediately afterwards, you’re running the risk of making yourself and the group quite sick from cross contamination!”

Charge’s grumpy attitude and expression almost immediately dropped when the realization of what he said clicked. The lemon colored cat meekly set the concoction back down on the table and dropped his gaze with it. “…Ah,” he mumbled quietly.

Starline then turned to Hex and Lug. “And you two! Even if you’re not handling the chemicals, you’re still getting crumbs everywhere! And no matter how tidy you may try to be, they’re still going to end up getting into the ports and components of whatever you’re trying to build! Which, in the long run, can and will affect connection integrity, and potentially cause a multitude of other problems down the line!”

“Oh.” Both bulldog and rat too shrank down like wet, burlap sacks in embarrassment.

“That.. might actually explain some problems I ran into back home…” Hex mumbled, scratching at a tuft of purple fur as he recalled his favorite robot struggling to work properly after a few tests. He had snacked quite a bit around that one as well. Namely, pretzels and granola bars.

Starline huffed out a breath, pleased to hear their arguments silenced, though he was still feeling flummoxed. “Do you understand now why I was so insistent on this? One careless misstep, and our chances of winning the competition could be over before we even get the chance to show them all what we’re capable of.“

He sighed and pushed up his glasses as he pinched the bridge of his bill. “Honestly, I get being hungry on the job, but if you feel as though you MUST feast so badly, then please, for the sake of everyone here, do us all a favor and take it to the cafeteria where that stuff belongs!!”

The boys went silent, and Starline took that as a sign of their understanding. “Thank you!”

With that seemingly now settled, the platypus huffed from his long winded speech, feeling the twinge of a headache coming on. “…Augh.. Now if you’ll excuse me, I need to get some air… I expect this place to be spotless when I come back, do I make myself clear?”

“Yes, Starline,” The three boys somewhat mutedly murmured in unison.

“Good.” The platypus shut his eyes and headed for the door, brushing past Rivet who hadn’t said a single word the entire time. “Honestly, the things I put up with...” he grumbled to himself as he walked out.

The room was deathly silent as the door closed shut behind him. Then Rivet shifted her gaze over to the group. Before she could even so much as breathe in their direction, Charge held up a hand. “Don’t say anything, sis.”

Rivet shrugged nonchalantly. “I wasn’t going to...” She paused for a long moment, then added, “…He is right though, you know.”

Charge groaned in response like he knew she was going to do that and grit his teeth. “I—!! Realize that! Ugh… Now, anyways.” He rolled his eyes sideways and slunk down.

“I didn’t mean to make him so upset…” Hex murmured softly, quietly picking at the hard plastic on his tablet. “I just didn’t want to fall behind on our tasks…”

“Augh, no, don’t blame yourself, Hex,” Lug groaned, rubbing his face with a gloved mitt. “We’re the older ones here. You were just following our example... Technically we should be the ones who are responsible..”

“Says the one who, up until a minute ago, was the most eager out of all of us to defy the doc’s instructions,” Charge pointed out.

Lug start, completely caught off guard. “WHA—! Yeah, okay, well— MAYBE I realize I was being petty… But it’s not exactly like you were any better!!” He then exclaimed.

“Yeah alright, you got me there.” Charge gave a small, sheepish chuckle. “I can admit I was wrong too…”

“Look, I’m sure you all didn’t mean any harm by it,” Rivet encouraged them. “But maybe from now on, just trust what he says when it comes to things like this, yeah? It’s clear to me that this competition is really important to him.” She chuckled weakly. “Otherwise, he.. probably would have kicked us to the curb about a week ago…”

The lavender cat then moved to join them at the table so she could lean back against it. “Yeah, he can be a bit arrogant, and… he’s a little rough around the edges at times. But I think he IS trying his best to work with us despite his pride. So… maybe we can do a bit more to work with him too, yeah?”

The room was quiet for a moment, then Charge nodded, seeing her point. “..I hate it when you make sense... You’re right! I guess it isn’t in our best interest to pull a him by ignoring his request.”

Lug grumbled and put a hand on his neck in bashfulness. “Mm.. yeah… Especially when at the end of the day, he just seems to be looking out for our wellbeing.” The bulldog glanced over at the trash can where their treats now lay discarded.

“We’ll apologize then when he gets back,” Hex stated, holding up his determined little fists. “Let him know we do appreciate him! And that we’ll try even harder from now on to be the best teammates he could ask for!”

Charge sighed and sunk further down into his hand. “Yeah, I guess you’re right. Even if he’s going to lord it over our heads for a while…”

“Better than him staying quiet and letting you accidentally poison yourselves, right?” Rivet flashed them a smile and pushed off the table to retrieve a roll of paper towels from one of the nearby counters. As she passed them to head to her own work station, she bumped it against Lug’s chest.

Lug accepted it and blinked at the roll, turning it over in his hands. “Yeah, you’re right about that,” he stated, before sighing and ripping off a square of it. “All right then.. come on guys! Let’s get this place cleaned up like the doc instructed.”

The coder and bio-electric kinetic nodded, and the three got to work on cleaning while Rivet sat down to resume work on her part of the project.

When Starline would eventually return to the group ten minutes later, their work area would be just as he expected it to be.

Bright, clean, and sparkling, with not a single crumb or drop of chemical concoction in sight. ✨

[dinocanid]

Our System Overview

(Preface: our system is highly metaphysical, in every single aspect, so that's the context everything's written in)

I've gotten a few requests over the months to write out how our system works, but I could never get around to it since it's hard to articulate. I'm attempting to do that today, but I'm encouraging you (the reader) to send asks if something is confusing since I acknowledge that some things might not be clear still. And of course, this is all our personal experience! Everything is different for everyone.

Members (and visitors)

One thing you'll probably see a lot in the rest of the post is "members" and "visitors". Everyone that's considered a member lives in the system; while they can venture out, they are bound to the system and for one reason or another can't just walk out forever to live somewhere else. Everyone that's a visitor doesn't live in the system, they exist elsewhere in whatever universe they came from and can leave whenever they please. Regardless, they're all under the "headmate" umbrella.

Our members (besides myself) include:

Amorphous (Ammy)

Drom

Gaster

And all of or visitors include:

Sans (from our timeline, not the canon one)

Several of his AU selves (there's a reason for this, it's just. A whole thing we're trying to get sorted)

Coincidentally, all of our members are spirits/dead in some sense of the word, while all of the visitors are still alive in their respective places.

Headmates That Are Also Kintypes (IE: the case with Ammy and Drom)

Often times when I'm talking about experiences relating to my dragon or dromaeosaurus kintypes, I'm using "the plural I". The reason for this is because due to some reincarnation shenanigans we are both each other and separate at the same time. They're both my past lives, and so one example is that when I was a dragon I was Amorphous (I'm not a "piece" of her or anything like that). When I'm feeling dragon-y that's not because of her doing anything, it's because my behavior and whatnot from the time I was a dragon is popping up. Duplication may or may not be the right word.

A good way to think about it is that both her and Drom are like "snapshots" of those lives, and each snapshot stacked with the next one. So Ammy was following Drom around as a headmate, and now they're both following me around.

How We Operate

At the time of writing, everyone both has their own individuality and are able to function independent from myself. There is no single thread of thought, everyone is doing their own thing at all times. How does my brain keep track of all that? It doesn't. Everyone is able to autonomously think and act in the headspace even if I'm not paying attention to them, but even so, I do have to say that it takes up a lot of processing power. Unless I'm asleep, my brain is regularly firing all cylinders like a laptop trying to run a heavily modded copy of The Sims. It's not uncommon for me to get headaches from system-related things. If someone new enters the system (visitors included) then I will get a headache even attempting to communicate with them. It usually takes a couple weeks for my brain to get used to it and for that effect to stop happening every time.

While I'm the main one seeing through the perspective of the body's eyes, everyone else not in front is capable of having multiple perspective. They can either have the view through the eyes psychically beamed into their heads (what happens by default), or they can go to the fronting room and see through the screen in there. They're also aware of all the other senses like smell, touch, and taste. These are all things they can opt in and out of at any time if they choose to. We don't all have access to the same thoughts though. Everyone can tell what I'm thinking (they have to since that's how we communicate), but I don't know what they're thinking about at any point in time unless they tell me (much like a separate-bodied person).

Although we aren't currently able to switch, we are currently practicing and most guides are hard to follow since it assumes that all of what's described above is not the case. Rather than there being "the body (who is the host) + everyone else", for us it's "the body + the host + everyone else". So a guide that details how to change a stream of consciousness (often described as "the I") is a bit hard to follow when we each have our own individual stream. And guides that describe "becoming the host" don't help either because the host isn't the body in our case. I'm the host because I'm the original occupant of the body, but I metaphysically exist independent of it with another form entirely. So reading guides on switching is a huge mess of "ok what do you mean because that is not how we work, what are we supposed to do exactly?".

The Headspace

Our default headspace is the void, which is a whole bunch of black nothing aside from the couch, lamp, and coffee table (and those are relatively new additions). If you've seen this post, that's basically the entirety of all that's in there. Even though it's virtually endless in all directions, the best way to think about it is that it's metaphorically in a bubble. In a very convoluted way, Gaster is a part of the void in a literal sense, so he has decent control over it (he could just meld down and be a disembodied voice if he really wanted to, less energy). He can keep our system's "bubble" of the void closed to prevent visitors from coming in, and can temporarily make "rooms" that's like being in a void on your own.

The void headspace also has the fronting room, which does look like an actual room but doesn't function for what it was made for. So as of right now it is a room you can stand in if you don't want to stand somewhere else, and that's about it (Drom likes to paint in there lol). It's unclear if the fronting room is connected to the void or its own thing. The door that goes out of the room leads into the void, but how you get to the fronting room from the void is a bit fuzzy. Sometimes the room is just freestanding in the distance and sometimes it isn't. My only guess is that it "loads/unloads" based on if someone is entering or exiting the room, so if someone's not currently going through the door then after a few moments it'll just poof if you're outside of it.

Another completely separate headspace we use regularly is a canyon area that has things like Drom's fishing pond, a forest, and a house. Unlike the void though, it cannot sustain itself and I have to actively "manifest" it so-to-speak, which takes a lot of mental energy and can result in headaches if done for too long. When I stop manifesting it the headspace reverts to the default void, so using another headspace is an event we usually have to plan for a specific block of time.

[autotopic]

Launched a century ago, the Bugatti Type 35 didn’t just make a single impact—it revolutionized the racing world with its innovative design and engineering. The car became legendary not only for its initial capabilities when it debuted in 1924 but also for the continuous improvements Bugatti implemented throughout its production. Ettore Bugatti was one of the first automobile manufacturers to grasp the marketing potential of winning races on Europe’s renowned circuits and road tracks, which brought considerable publicity to his brand. Confident as he was in the capabilities of his new car, even Bugatti could not have predicted that the Type 35 would become the most successful race car in history, achieving 2,500 victories during its active racing career.

The first Type 35, released in 1924, was equipped with a 1,991cc eight-cylinder engine, delivering 90 PS in race trim. By early 1926, Bugatti had increased the engine size to 2,262cc for the Type 35T, named after the famous Targa Florio road race in Italy, which it won, with two smaller-engined Type 35s finishing close behind. Despite this success, Ettore Bugatti realized that to stay ahead of the competition, he needed more than just increased engine displacement. He knew that the future of performance lay in forced induction, even though he was initially not a fan of superchargers, which were seen as inefficient at the time.

“It’s no secret Ettore Bugatti preferred naturally aspirated engines and was not an early enthusiast of supercharging due to its perceived inefficiency,” says Luigi Galli, Specialist for Heritage and Certification at Bugatti. “However, what’s less well known is that Bugatti was forward-thinking about the potential of forced induction, experimenting with superchargers even before the Type 35 debuted at its first race in Lyon in August 1924. In fact, Bugatti applied for French patent number 576.182 on January 22, 1924, for a ‘Compresseur ou pompe à palettes,’ a rotary vane supercharger design that could provide extra power on demand by forcing pressurized air into the carburetor. If Bugatti was going to use a supercharger, he was determined to innovate in his own way.”

As a result, Ettore Bugatti, alongside the Italian engineer Edmond Moglia, developed a unique three-rotor Roots-type supercharger, differing from the common two-rotor designs of the time. This supercharger was strategically mounted on the engine’s offside, which allowed it to warm up more quickly and improve overall engine cooling—a principle that remains relevant in modern engine design. The Type 35TC, where “TC” stands for Targa Compressor, was introduced in late 1926. It evolved into the Type 35B in 1927, featuring a larger radiator and cowling, known as the ‘Miramas’ design, which enhanced cooling capabilities. This configuration enabled the Type 35B to produce up to 130 PS, achieving speeds over 205 km/h (150 mph).

By late 1930, further refinements led to what many consider the ultimate version of the Type 35B. This final iteration featured a twin-cam, two-valve-per-cylinder engine, a twin fuel filler cap, improved suspension, wheels, brakes, and tires, as well as a lower-mounted supercharger relief valve. Bugatti’s relentless pursuit of perfection extended to optimizing every element of the combustion system, from sculpted pistons and cylinder heads to the use of aviation-grade fuel, which boosted the output to 140 PS.

Today, at Bugatti’s atelier in Molsheim, each Bugatti model is hand-assembled with the same meticulous attention to detail that Ettore Bugatti applied to the Type 35. A century later, Bugatti’s engineers and designers continue to push the boundaries of automotive excellence, upholding a legacy of innovation and performance that began with the groundbreaking Type 35.

[dovescheck]

TRANSCRIBED THIS!

DD 000 RRR SSS 000 SSS D D 0 0 0 0 R R SS 0 0 SS DD 000 000 R R SSS 000 SSS disk /dev/sdb: 120.0GB. 120034123776 bytes 75 heads, 63 sectors/track, 49617 cylinders, total 23441648 sectors Unit - sectors of 1 - 512 - 512 bytes Sector size [logical/physical]: 512 bytes / 512 bytes I/0 disk [minimum/optional]: 521 bytes / 512 bytes Disk identifier: 0x00000000

Device boot Start End Blocks Id System /dev/sdbi 2048 23441647 117219800 83 Doors05

Command: [? for help]: ? Command action a toggle a bootable flag b edit bsd disklabel c toggle the dos compatible file d delete a partition l list known partition types m print this window n add a new partition o add a new DDS partition table p print partition table q quit without saving changes s create a new empty disklabel t take a gander at earth u change display/entry units v verify the partition table w write table to disk and exit x exit functionality [l33t IT nerds only]

SRCHLIST "PRGR(or PRGM) CORE CORRUPTION" [EXECUTING] . . . . [100%]

DISPLAY RESULTS: -> ACCELSYS [PRGR HANG] . . . [RESOLVED] -> BOOTKERNEL [PRGR HANG] . . . [RESOLVED] -> ABSOLV [ERR] ---> TERMINATE [REBOOT] ---> SYSFAILSAFE [DISABLED] ---> SYSSELFDESTRUCT [DISABLED] ---> PGRMREPORT [DISABLED] ----> PRGMDIAGN [DISABLED] . . . [FATAL ERROR]

[sweet7simple]

Terms and definitions that you can maybe apply to your fan works

I don't know anything about computer or mechanical engineering (it's very funny to me that I am in the Transformers fandom and I don't even care about cars), but I do care about improving my writing. I have gathered a list of terms that sound very sciencey and applicable to mechs, some from Martha Wells's "Murderbot Diaries," some from fanfiction/fandom (shout-out to the Crime in Crystals series by Aard_Rinn and Baebeyza, they wrote Transformers better than any Transformers comic/TV show did), and a lot from just surfing through Google and going, "well, what the hell is this? Okay, but what the hell is THAT?".

Also, as I was writing this post, I ended up getting sucked into this article:

And this really bloated my already long list of terms. Very easy to read if you want to glance it over yourself.

It's not an exhaustive list and who knows if it will be useful to you - but maybe you can reblog with your own add-ons of terms and definitions you think make a Transformers fan work just that much better.

The list is below the cut:

100% CPU Load - CPU is fully occupied with too many processors/applications/drivers/operations - not necessarily synonymous with an overload.

Actuators* - A device that causes a machine or other device to operate (Ex: a computerized unit instructs the actuator how to move the tires on a vehicle); create linear and rotary movement (Ex: A hydraulic actuator on a valve will move that valve in response to a sensor/signal); Linear actuators "move a piston back and forth inside a cylinder to build pressure and 'actuate', or complete an action".

* Think of actuators as devices that help produce linear motion and motors as devices that help produce rotational movement. Hence, some consider actuators as a type of motor. But a motor is not a type of actuator (jhfoster.com).

Alternator - Converts mechanical energy to electrical energy with an alternating current. The stator and rotor inside the alternator work as magnets and rotate to generate the alternating current. Then the alternating current (AC) is transformed into a direct current (DC) that charges the battery.

Archive (Archive files) - used to collect multiple data files together into a single file for easier portability and storage, or simply to compress files to use less storage space.

Arithmetic Log Unit (ALU) - the part of a central processing unit that carries out arithmetic and logic operations on the operands in computer instruction words. In some processors, the ALU is divided into two units: an arithmetic unit (AU) and a logic unit (LU).

Augment - Make something greater; increase.

Auxiliary Battery - Designed to run as a backup to the starting battery and provide power to some essential equipment like engine start/stop and other systems that require power while the engine is off to put less strain on the main battery and alternator.

Bandwidth - A measurement indicating the maximum capacity of a wired or wireless communications link to transmit data over a network connection in a given amount of time.

Behavioral Coding - A term used in Martha Wells' Murderbot Diaries; essential, code for behaviors.

Branch Instructions - Use programming elements like if-statements, for-loops, and return-statements; used to interrupt the program execution and switch to a different part of the code.

Branch Predictors - Track the status of previous branches to learn whether or not an upcoming branch is likely to be taken or not.

Buffer - A region of memory used to store data temporarily while it is being moved from one place to another.

Cathodes vs Anodes - Cathodes are the positive electrode while the anode is the negative electrode; electrons flow from the anode to the cathode and this creates the flow of electric charge in a battery or electrochemical cell.

Catastrophic Failure - Complete, sudden and unexpected breakdown in a machine, indicating improper maintenance.

Central Processing Unit (CPU) - Primary component of a computer that acts as its "control center"; complex set of circuitry that runs the machine's operating systems and apps; the brains of the computer. * Components: Instruction Set Architecture (ISA), Control Unit (CU), Datapath, Instruction Cycle, Registers, Combinational Logic, the Arithmetic Logic Unit (ALU), etc...

Clock - Determines how many instructions a CPU can process per second; increasing its frequency through overclocking will make instructions run faster, but will increase power consumption and heat output.

Combustion Chambers - An enclosed space in which combustion takes place, such as an engine; jet engines also have combustion chambers.

Condition Codes - Extra bits kept by a processor that summarize the results of an operation and that affect the execution of later instructions.

Control Bus - Manages the communication between the computer's CPU and its other components.

Control Unit (CU) - Manages the execution of instructions and coordinates data flow within the CPU and between other computer components.

Cybermetal - Element native to Cybertron and Cybertron alone.

Datapath - The path where data flows as it is processed; receives input, processes it, and sends it out to the right place when done processing; datapaths are told how to operate by the CU; depending on instructions, a datapath can route signals to different components, turn on and off different parts of itself, and monitor the state of the CPU.

Diagnostic and Data Repair Sequence - Term used in Martha Wells' Murderbot Diaries; exactly what it sounds like.

Diode - A semiconductor device with two terminals (a cathode and an anode), typically allowing the flow of current in one direction only.

Discrete Circuit vs Integrated Circuit- Single device with a single function (ex: Transistor, diode) vs Devices with multiple functional elements on one chip (ex: Memories, microprocessor IC and Logic IC).

Drivers - A set of files that help software (digital components, such as Microsoft Office) interface/work with hardware (physical components, such as a keyboard); allows an operating system and a device to communicate.

Electromagnetic (EM) Field - A combination of invisible electric and magnetic fields of force; used in fandom by mechs to broadcast emotions to others.

Flags - A value that acts as a signal for a function or process. The value of the flag is used to determine the next step of a program; flags are often binary flags which contain a boolean value (true or false).

Full Authority Digital Engine Control (FADEC) - Consists of an electronic control unit (ECU) and related accessors that control aircraft engine performances.

Gestation Tank - Used in mech pregnancies, you can pry it from my cold, dead hands.

Heads Up Display (HUD) - A part of the user interface that visually conveys information to the player during gameplay.

Heat Spreader - Often used in computer processors to prevent them from overheating during operation; transfers energy as heat from a hotter source to a colder heat sink or heat exchanger.

HUB - A device that connects multiple computers and devices to a local area network (LAN).

Inductive Charging - How I imagine berths work; wireless power transfer (ex: Wireless charger or charging pad used for phones).

Instruction Cycle - Also known as fetch-decode-execute cycle; basic operation performed by a CPU to execute an instruction; consists of several steps, each of which performs a specific function in the execution of the instruction.

Instruction Set Architecture (ISA) - The figurative blueprint for how the CPU operates and how all the internal systems interact with each other (I think of it like a blueprint for the brain).

Irising - Term used in fanfiction (specifically the Crime in Crystals series) to describe the action of the of the spark chamber opening ("The Talk", chapter 6, my absolute favorite chapter out of the entire series). I just really liked how the word sounded in that context.

Life Codes - "For those of us who were forged, Primus, through Vector Sigma, generated a pulse wave. Each one a data-saturated life code faster than thought, brighter than light, racing across Cybertron, sowing sparks..." (~Tyrest/Solomus, Volume 5 of More Than Meets the Eye)

Memory Hierarchy - Represents the relationship between caches, RAM, and main storage; when a CPU receives a memory instruction for a piece of data that it doesn't yet have locally in its registers, it will go down the memory hierarchy until it finds it.

Levels: L1 cache (usually smallest and fastest), L2 cache, L3 cache, RAM, and then main storage (usually biggest and slowest); available space and latency (delay) increase from one level to the next

Depending on the multi-core (a core is usually synonymous with a CPU) system, each core will have its own private L1 cache, share an L2 with one other core, and share an L3 with more or more cores.

Motors* - Any power unit that generates motion; electric motors work by converting electrical energy into mechanical energy... when this happens within a magnetic field, a force is generated which causes shaft rotation.

Multitasking Operating System - Allows users to run multiple programs and tasks almost simultaneously without losing data; manage system resources (such as computer memory and input/output devices), allocate resources, enable multiple users, and eliminate long wait times for program execution.

Network - A set of computers sharing resources located on or provided by network nodes. Computers use common communication protocols over digital interconnections to communicate with each other.

Network Feed - The continuously updating stream of content that users encounter on networking platforms.

Neural Network - A type of machine learning process that uses interconnected nodes (like neurons) to teach computers to process data in a way similar to the human brain; a form of deep learning that can help computers learn from their mistakes and improve their time.

Nimbus - A luminous cloud or a halo surrounding a supernatural being or a saint; has been used in fanfiction synonymously or in junction with the corona of the spark.

Nodes - A connection point between devices that allows data to be sent and received between them.

Oil Sump/Oil Pan - Don't forget to change your mech's oil.

Out-Of-Order Execution - A paradigm used to minimize downtime while waiting for other instructions to finish; allows a CPU to choose the most timely instructions to execute out of an instruction queue.

Overload - Orgasm; an electrical overload occurs when too much electricity passes through a circuit, exceeding its capacity; an information overload is when a system receives more input than it can process, or a state of being overwhelmed by the amount of data presented for processing.

Pedes - Feet

Pipelining - A technique used in computer architecture that allows a processor to execute multiple instructions simultaneously, improving overall performance.

Processing Capacity - The ability and speed of a processor, and how many operations it can carry out in a given amount of time.

Program Counter - A special register in a computer processor that contains the memory address (location) of the next program instruction to be executed.

Programmable Nanobots/Nanites - Cybertronian microbots programmed to do work at the molecular level; used popularly for surface healing and pigment in mechs.

Protected Storage - Provides applications with an interface to store user data that must be kept secure or free from modification; a storage method; a function in mainframe hardware.

Protoform - Formed of an ultra-dense liquid metal and are extremely hard to damage; the most basic Cybertronian form of raw, free-flowing living metal; first stage of Cybertronian life cycle

To create a Cybertronian, you need the protoform, the life-giving spark, and alt-form information.

Register - A type of computer memory built directly into the processor or CPU that is used to store and manipulate data during the execution of instructions.

Ex: "When you run a .exe on Windows... the code for that program is moved into memory and the CPU is told what address the first instruction starts at. The CPU always maintains an internal register that holds the memory location of the next instruction to be executed [the Program Counter]"...

Resource Allocations - The process of identifying and assigning available resources to a task or project to support objectives.

Risk Assessment - Focus on identifying the threats facing your information systems, networks, and data and assessing the potential consequences should these adverse events occur.

Routine - A component of a software application that performs a specific task (ex: Saving a file).

Servomechanism - A powered mechanism producing motion or force at a higher level of energy than the input level (ex: In the brakes and steering of large motor vehicles) especially where feedback is employed to make the control automatic.

Servos - Hands

Shellcode - A small piece of executable code used as a payload, built to exploit vulnerabilities in a system or carry out malicious commands. The name comes from the fact that the shellcode usually starts a command shell which allows the attacker to control the compromised machine.

Semiconductor - A material used in electrical circuits and components that partially conduct electricity.

Semiconductor materials include silicon, germanium, and selenium.

Struts - Bones; A rod or bar forming part of a framework and designed to resist compression.

System/System Unit (in computers) - A setup that consists of both hardware and software components organized to perform complex operations/The core of your computer where all the processing happens.

Task Specific Accelerator - Circuits designed to perform one small task as fast as possible (ex: Encription, media encoding & machine learning).

Teek - Used in Transformers fandom in conjunction with EM Fields; when a mech "teeks" another mech's field, they are feeling the emotions that mech is broadcasting.

Transistor - Enables a computer to follow instructions to calculate, compare and copy data.

Universal Serial Bus (USB) - A standard plug-and-play interface that allows computers and peripheral devices to connect with each other, transfer data, and share a power source; allows data exchange and delivery of power between many types of electronics; plug-and-play interface is also a type of sexual activity used in fandom.

Warren - Used to refer to a group of minibots with their own social hierarchy and culture (Seriously, read the Crime in Crystals series, it's better than canon).

[trakaid4u]

Trakaid's Cylinder Tracking System: Streamlining Operations

A cylinder tracking system is a vital solution for industries that manage gas cylinders, ensuring accurate tracking, monitoring, and management throughout the supply chain. This system helps prevent losses, improves safety, and ensures compliance with industry regulations. By utilizing barcodes, RFID tags, or GPS technologies, companies can track each cylinder's movement, maintenance, and usage history in real time. The system not only optimizes inventory management but also enhances safety by ensuring that only certified and inspected cylinders are in circulation, reducing the risks associated with faulty equipment.

Trakaid offers an advanced cylinder tracking system designed to streamline operations and improve efficiency. Their solution integrates cutting-edge technologies, providing detailed data on cylinder location, status, and usage patterns. This enables companies to reduce operational costs, minimize human errors, and improve overall supply chain transparency. Trakaid's system is particularly beneficial for gas suppliers, as it helps manage cylinder fleets efficiently while maintaining regulatory compliance. With real-time data and insights, businesses can enhance customer service by ensuring timely deliveries and preventing stock shortages. Visit Now: https://www.trakaid.com

[hasbr0mniverse]

G.I. Joe Battlefront 1985 - Vehicle: Mauler M.B.T. Tank (Manned Battle Tank) - Two-man armored tank with track turning, removable turbine engine and smoke grenade launcher.

Technical Specifications:

• 12 Cylinder Twin-Supercharged Diesel lEngine: 1800 Horsepower; Road Speed: 62 MPH; Range: 500 Miles.

• DX-Z Series II Digital Ballistics Computer.

• Holographic Image-Display Targeting
System.

• MXZ 125MM "Earthquake" Cannon.

[gurradesu]

Starting out on Godot: Part Two, Tower Defence

Tower Defence. Tower Defense. We love different spellings.

For this part I needed a way to communicate between components, or nodes, to enable loading from one mode to another. I have a hub (see previous post), now I need to get from there to my level with a tower defence.

To do this I had to implement the signal system so my root node, the game manager, can unload the hub area and load in the Tower Defence area.

My implementation here is pretty clunky and could be refactored easily. But at least it worked. And now I can move from here:

to here:

Now the above screen is actually jumping ahead a little bit, but that's fine. I made a very basic level scene in Blender by using the shape tool to score grooves into a plane - that's the path - and made some trees and rocks with primitive shapes to make some fauna. I also made some hexagonal plinths to place defenders on. I kept it very basic and simple for now as this was for prototyping.

Once I had a system to change scenes and update cameras I could work on implementing the basics of a Tower Defence. The most standard components are 1) Enemies, 2) A path for enemies to travel, 3) Defenders and 4) An area for defenders to be placed.

Godot has me covered here, and strangely enough to implement the mechanics of the path there is whole ready made node structure for it. The Path node, and the Path Follow node:

The path nodes let me set up the nodes that the enemies will walk along, and the path follow node lets me attach the enemy units to them as children so that they can more along the path and carry out any other actions they may want. And very quickly, I have this:

After this all I had left to implement was the defenders who can track which enemies are in range for their attacks by using sphere or cylinder colliders. And in no time at all - after a lot of bug fixing due to messing up my code - I had this:

A working tower defence prototype. A "Game" in the loosest sense possible as it wasn't particularly interactive.

But slap on some materials, and a text tutorial, and you can technically call this a game. Voila!

[spacetimewithstuartgary]

Hera burns towards Mars

ESA's Hera mission has completed the first critical maneuver on its journey to the Didymos binary asteroid system since launch on 7 October.

On 23 October, Hera fired its three orbital control thrusters for 100 minutes, kicking off its first deep-space maneuver and changing its velocity by approximately 146 m/s. A second burn on 6 November lasted 13 minutes with the aim of providing an additional boost of around 20 m/s.

Together, these burns have put Hera on a trajectory that will enable a gravity assist at Mars in March 2025.

"Deep-space maneuvers are often split into parts," explains Sylvain Lodiot, Hera Spacecraft Operations Manager. "The first, larger burn does most of the work. Then, after precisely measuring the spacecraft's trajectory, we use the second, smaller burn to correct any inaccuracy and provide the rest of the required boost."

The maneuver followed three successful test burns performed in the weeks after launch by Hera's control team at ESA's European Space Operations Center (ESOC) in Germany.

The team used the Agency's deep space radio dishes in Spain, Argentina and Australia to track Hera during the maneuver and to precisely measure its velocity before and after each burn.

"We are now analyzing Hera's new trajectory following the second burn," says Francesco Castellini from ESOC's Flight Dynamics team, the mathematical experts that keep ESA missions across the solar system on track.

"It appears to have gone very well. We will execute a much smaller correction maneuver of a few tens of cm/s on 21 November to fine-tune the trajectory for the upcoming Mars flyby."

Mars lends a hand

Hera is on a two-year journey to the Didymos binary asteroid system, where it will analyze the results of humankind's first asteroid deflection experiment.

The recent deep-space maneuver was carefully calculated to line Hera up for a gravity assist in March 2025 that will shorten the travel time to Didymos.

"We are very fortunate that Mars is in the right place at the right time to lend a hand to Hera," says Pablo Muñoz from ESOC's Mission Analysis team, who planned Hera's journey.

"This enabled us to design a trajectory that uses the gravity of Mars to accelerate Hera towards Didymos, offering substantial fuel savings to the mission and allowing Hera to arrive at the asteroids months earlier than would otherwise be possible."

Hera will also use the Mars flyby for some opportunistic science. The ESA teams have designed a trajectory that will see the spacecraft fly past Deimos at a distance of just 300 km before passing Mars itself, offering a rare chance to study this small and mysterious martian moon.

Hera will then carry out a second deep space maneuver in February 2026 before a sequence of rendezvous maneuvers from October to December 2026 brings it into proximity of the asteroids.

At Didymos, Hera will begin its mission to answer questions such as: How and why do binary asteroid systems form? When NASA's DART mission impacted Didymos's moonlet Dimorphos in 2022, did it leave a crater, or did it reshape the entire asteroid? What is Dimorphos's internal structure?

Asteroid community gathers at ESOC

It's a busy time for ESA's asteroid teams. October saw the launch of the Agency's first asteroid mission, Hera, and the start of work on its second asteroid mission, the proposed Ramses mission to asteroid Apophis.

Meanwhile, ESA's Near-Earth Object Coordination Center has continued discovering, tracking and analyzing new asteroids from the ground and recently helped to identify the tenth asteroid ever discovered prior to Earth impact.

Next week, a team from the Agency's Planetary Defense Office will meet with experts from around Europe and beyond at ESOC in Germany to discuss how to more accurately measure the size of potentially hazardous near-Earth asteroids.

TOP IMAGE: Hera's Propulsion Module incorporates its propellant tanks—housed within a central titanium cylinder, the 'backbone' of the spacecraft—along with piping and thrusters, which will have the job of hauling the mission across deep space for more than two years, then to maneuver around Dimorphos and Didymos. This module was mated with Hera's Core Module at OHB Bremen to complete the spacecraft structure. Credit: OHB

LOWER IMAGE: Lutetia at closest approach. Credit: ESA 2010 MPS for OSIRIS Team MPS/UPD/LAM/IAA/RSSD/INTA/UPM/DASP/IDA

[transingthoseformers]

Minimus loves his brother, he does, he should be–he is thrilled that Dominus is alive, is here, is slipping so seamlessly into the crew's social circles without any sturggle, because Dominus never struggles.

He also has not left the Ultra Magnus suit even in his private quarters since the DJD arrived. He allowed Rodimus, relievingly eager to work for once, to finish their integration with Rung and instead focused on work.

Yes, work is good.

Like keeping track of Megatron, who is clearly up to something. Hiding in his quarters and missing his shift.

Yes, behavior Ultra Magnus (he is going to be Ultra Magnus right now because Minimus feels inadequate in the face of Dominus's miraculous return as, of course, Dominus would miraculously return to a hero's welcome and Rewind II's welcome which is something he is also not dealing with) can focus on.

Megatron meanwhile has semi-genuinely actually converted–he doesn't deal well with his belief system being turned on its head either and can only handle it in the most extreme way possible–and is dealing with Ravage choosing now to reveal himself because he knows Megatron did not summon one of his "worst mistakes" (Ravage's words as Ravage was never quiet on his opinion of the DJD and Phase Sixers) and Megatron's reaction to it has convinced Ravage he's probably not Shadowplayed and needs a friend.

(Even if said friend is currently furious at him.)

So Ultra Magnus walks in on Ravage–the top Dcepticon spy–on Megatron's bed which looks incredibly incriminating.

Ravage makes the executive decision to knock him out by frying his nervous system and in the process triggers the opening to the Magnus Armor revealing to both of them that Ultra Magnus is a smaller bot inside a bigger suit.

When Minimus wakes up he is feeling very exposed but Megatron and Ravage are very respectfully averting their eyes because Minimus's form and designation are his own business and it was an accident.

Which makes him feel something.

There is a loud private argument and a la the first episode of The Good Place Megatron convinces Minimus that if he finds him lacking then to persuade him of the benefits of an Autobot become his mentor and do the probationary period himself. If he feels that Megatron truly is insincere by the end then Megatron, ignoring Ravage's hissing, swears he will remove the badge himself. Megatron does this by dramatically dropping to his knee and grabbing Minimus's hand like they are romantic leads in a period drama.

Minimus, not going full cylinders, agrees to give Megatron Autobot Lessons instead of pushing for extradition because he may be having a small moment inside himself about proving he can do this which is something his brother never accomplished.

(Minimus's insecurities aren't being handled great.)

Those private lessons in Megatron's quarters with Ravage supervising begin.

(MiniMegs Part 2)

Mini and Megan are just absolutely saying "Mmm fuck that, fuck the ouside world" seperately and absolutely focusing on the bullshit between them which is adorable

Ravage broke his cover just to ask Megatron if he did what he thought he just did (which he didn't do)

Ravage both chose the worst at the best timing, pistachio man has been revealed to having been secretly a pistachio and is honored the other two tried to be respectful.

So that's adorable as hell, Meggsie asking for Minimus to tutor him in How To Be An Autobot: remedial classes, awwwwww