u/Froshure

This occurred to me recently on Trail Ridge road between Grand Lake and Estes Park, Colorado.

This could happen to you if you have all of the following:

1. Rear full fender.
2. Trailer with non inline wheels (so not a trailer with 1 wheel that leans with the bike).
3. Connection between bike and trailer that can intersect the bike's rear fender when the trailer is rotated.

If you have all of the above, here's ways to prevent this failure from happening:

1. ⁠My provisional solution is a nylon buckle strap (with a sufficient weight rating to support the fully loaded trailer) wrapped around my trailer's pull handle and bike's seat rails, then tightened so that the trailer arm can't reach the fender in case of a trailer roll over.
2. ⁠The ideal solution is to use a bike/trailer connection that can't intersect the rear wheel, such as one that connects between the seatpost and top of trailer, or use a trailer with inline wheel(s).

And here's ways to reduce the chance of this failure happening:

1. Reduce your trailer's tire pressure.
2. Look farther forward to see dangers (I definitely wasn't).
3. Avoid the shoulder, because debris tends to accumulate there.

"Mouse" as in computer controller, not animal.

Motorcycle is from Hirochi Outlaw mod

These pictures are from the Contagion project, made for and by the Vic's Modern Warfare mod team, and which would be a DayZ-like survival game, had it been finished. The project was abandoned in early 2022, leaving this 15k x 10k world—a product of 9 world designers and 2,000 hours of work—without a satisfying end. Its development was troubled; this world was the 3rd iteration, and even between the first and last things built on this world is significant skill progression, meaning a few-months-old sub-project became obsolete… in a cycle characteristic of large projects begun by novices.

More information about picture #12 (not important; just technical narration):

We were building this airport when the project was cancelled. Had it been completed, it would've represented a significant shift in the building process, as we were experimenting with using Google Earth photogrammetry data as the basis for our builds. It would've allowed for easier gradient coloring, and lessened the cognitive load of deciding "what should go here?", as we could simply reference the Google Earth location to see what's there, if we got that decision fatigue.

It was an immature technology, though, as visible in the picture: many colors were too noisy (structure walls, concrete floors), underrepresented (yellow paint on airplane roads), oversaturated with inappropriate blocks (yellow and green terracotta and concrete as grass at bottom-center of picture), and corrupted by photogrammetric shadows (shadowed building sides translated to darker and bluer blocks in Minecraft).

Correcting these problems with 2020's technology would've meant tweaking the colormap before importing the 3D model into Minecraft, limiting block types for different colors, and manual in-game fixing. But, with modern technology, I've wondered if, for example, a neural network could be trained to detect and fix these problems, such as using natural blocks for terrain and vegetation, building-appropriate blocks for man-made structures, and detecting then deleting shadows in the photogrammetric models.