Creepypasta SFM GLITCH

SFM Render Glitch
Hello. Lately I’ve been making LOADS of short SFMs, usually under a minute. Why are they always under a minute? I’ve been making them so short because if I make them too long, a really weird glitch happens, and the video becomes unplayable and corrupted. So one day, I decided to work on an SFM project that I’ve been putting off for a while now. Unlike all my projects so far, this one actually tells a story, and it is quite lengthy compared to my other ones. The concept was simple; the Engineer would keep building sentries, but they kept disappearing whenever he went to go get more materials. Eventually, the Engineer finds out that the Spy has been stealing the sentries and converting them to the other team. The engineer says “Now I’ve seen everything.” This alerts the spy and leads to a chase scene where the Engineer somehow avoids all the bullets the Spy shoots at him, and the Engineer is cornered. The spy walks up to him and fires his gun at the Engineer. Then it is revealed that it was all a dream, and everyone lives happily ever after. When I tried to render it to upload to YouTube though, that’s when weird things began happening. The rendering time took about half an hour, so I played Minecraft while I waited. While I was in the middle of making an upside down house (don’t even ask…) I heard the noise that SFM makes when it finishes rendering. I tried to open up the new file, named “Missing Sentries.avi” and the Video Player said either the format was not supported or it got corrupted. I figured I might as well try uploading it on YouTube to see what would happen. That might not have been the best idea ever. When I uploaded the video (which took a million forevers and a half…) the thumbnail looked weird. The hue was off so now the Engineer was purple, and so was everything else. The screen was also split in many different ways. Naturally, I went “WTF?” and clicked on the URL to the finished video. It showed a discolored Team Fortress 2 logo flashing and going all over the screen accompanied by an obnoxious loud buzz in the background. It cut to the outro, where text would pop up saying “Made with SFM” and the text would be knocked down by a giant SFM logo. That did happen, but the screen was split somewhat awkwardly, and the top left corner of the video was cut off. After that, it cut to the scene where the Engineer sees the Red Spy walking down stairs. The screen was split differently, with two screens at the top half, and one screen on the bottom half, almost kind of like a crappy 3-player split screen game. It cut to the part where the Engineer sees Red Spy converting his sentry to Red using a modified Sapper. This was much like the previous scene where the screen is divided into 3 parts, and the video was flickering a lot. It then cut to the chase scene, and the irritating buzz got louder and started fluctuating and occasionally sounding like fingernails on a chalkboard. It then cut to a short section where the Heavy (who was eating lunch) starts laughing at the engineer running like a coward. The buzz started sounding like if an old game crashed. It cut to the part where the Spy shoots the engineer, but this time the buzz got quieter and occasionally stopped for about a second before coming back on again. The Spy shot the engineer, and it cut to black. The Engineer woke up and left. It then cut to the Team Fortress 2 logo flashing different colors, but now the screen was split in two uneven halves. It showed the Source Filmmaker scene I described earlier, and the video repeated itself. This time, however, the buzz was now changing pitch very frequently, yet the change was subtle. I barely noticed it. The only other difference was that the screen was only 2 halves side by side, not up and down like it was before. At the end, it showed a purple team fortress 2 logo on both halves. Then the “Made with SFM” screen came up. The video then faded to black like normal. After viewing the video, my mind was full of WTFery. I decided to keep the video on my channel as proof that this actually happened.