Thornskade
TF2 Direct Hit Gameplay – Annotation Removal Reupload
updated
Originally in my mind I was going to make the water rise so high that the tip of the mountain were just a small island surrounded by a giant ocean. But I soon realized at the speed the water was moving, that would have taken many hours. So this has to suffice
28:13 I'm done, water has settled, final overview
3:15 2023 version of TF2
There's a glitch in TF2 where hugging certain walls draws your shadow on the opposite side of the wall, effectively giving other players a wallhack against you. What's interesting about this is that this glitch has existed since 2007 but has become worse over time. While you could be seen through walls, it was only while hugging a wall and simultaneously moving toward its direction. So the wallhack was at least very brief, in that sense. However in modern TF2, your shadow is always visible even when you're standing still. It is also bigger and can be seen from further away. Overall it's a much bigger problem than it used to be.
github.com/ThatOneDuder710/skin.Blades
If your screen supports HDR, a small "HDR" icon shows on the cogwheel. Many phones have HDR, but fewer TVs and monitors do. You probably know if you have one.
If you don't, the video shows converted to SD quality from the HDR output, which looks a bit different than if the game was recorded in its default SD output. You may compare with other video uploads of this game's cutscenes in SD quality.
Just like with my last test with the N. Sane Trilogy, the recording turned out to be imperfect. As last time, even though the game ran at a high framerate (over 100 fps), the video recording frequently falls back to 30 fps. This time it's much worse, as it looks like there's a fairly consistent stutter. Instead of short periods of 30 fps, the video switches between 60 fps and 30 fps in short bursts.
I still don't know why this happens, whether it's a memory constraint resulting from recording at 1440p with a high bitrate. Perhaps the best way to record HDR is to lower the bitrate and limit the video to 1080p, at least depending on your hardware. Maybe an RTX 2070 Super is not good enough to record at a perfect 60 fps in 1440p and HDR.
If your screen supports HDR, a small "HDR" icon shows on the cogwheel. Many phones have HDR, but fewer TVs and monitors do. You probably know if you have one.
If you don't, the video shows converted to SD quality from the HDR output, which looks a bit different than if the game was recorded in its default SD output. You may compare with other video uploads of this game's cutscenes in SD quality.
Another weird thing that happened is that some short parts of the video fall back to 30 fps, even though the game was running at 150+ fps and recorded at 60 fps. This may suggest a limitation with HDR recording, perhaps memory constraints, where the Nvidia software needs to scale back in order to not run out of Vram or something? Or perhaps it just wasn't able to process as many HDR frames in time? I really don't know, but if anyone does, please enlighten me :-)
I bet everyone did this
Equip either the Paladin charm or the "parry to get HP" charm, whatever that is called. Start the King Dice fight on normal difficulty and make sure the second bonus heart is on field 6, which is the horse race fight. You may have to restart a few times until the second heart is on 6.
Beat whichever boss the first heart is on, which should be trivial, but remember you can't take any damage for the achievement.
Once you enter the horse race fight, don't attack. The horse spawns an infinite amount of presents for you to parry the pink horseshoe. The only thing you really need to pay attention to are the racers at the bottom. If the racer is a ghost, it will jump up and you need to avoid it.
Technically, you don't need to parry horseshoes as often as I did since parrying the dice also counts, but I lost count on my parries. After you beat the horse you need to get the final bonus heart and after that the achievement should be yours.
Recently I found out it was because Zurg wasn't supposed to move as fast as he did, which made it impossible for me to hit him. The programmers tied Zurg's movement speed to your CPU speed – obviously not a very future-proof thing to do. My computer's processor was too fast and thus Zurg was always out of reach before I could even blink.
With this knowledge I installed Toy Story 2 on PCem, emulating an appropriate processor, determined to finally play through the game 21 years later, and this is the clip of me finally beating Zurg. For once, I wasn't stuck on something because I was a dumb kid; it was actually the game's fault.
The blade log cycles are random, the fire crate cycles are random, the cannonball cycles at least seem random, sometimes the blade logs let you clip through them while sliding and sometimes not, sometimes Crash does a bellyflop after landing on a crate while wearing Aku, sometimes you're able to do a second slide while in mid-air and sometimes you're not, sometimes a slide spin uses your normal tall hitbox to hit crates above you and sometimes it doesn't, sometimes crates on top of a stack you spin into bounce up and sometimes they don't... all of these (seemingly) random things make the time trials way too frustrating to try and beat. I at least can't find any rhyme or reason to these occurances but perhaps there's something I'm missing and pros can actually accurately influence all of these things. But either way it's a tad too ludicrous.
I tried beating my own time to get a full run recorded but haven't yet. I spent like 30 minutes just to get this time which isn't even anywhere near world record so I'm kinda pissed about it.
Initially I was somewhat confident that I could beat this deathless as it started relatively easy but disaster quickly ensued with over 50 deaths in the end. At least I got all 1006 boxes and both gems.
I really like this in concept and this game's mechanics could absolutely work as an open-world game à la Twinsanity. However either something about this implementation is kinda wonky or I'm just bad at it (it's probably both), but I very often found myself unable to judge my position in 3D space. The yellow circle doesn't help as much as you'd think, especially not when it's just way below the actual height you're operating in over certain gaps. In that case, it can actually be misleading as I sometimes thought I was already past a crate. Perhaps if we were able to zoom in the camera a little to get a better sense of perspective. Or try a VR mod, haha. (Seriously though, VR really mitigates distance judging issues in 3D games) Plus, the level design is a little unfair. Aside from hidden nitro crates under piles of other crates, the box jumping parts have these fire crates planted everywhere and the timing is very hard to judge so far ahead in time. Sometimes it seems you can't help but take a hit.
Also, the spin slide in general I just don't understand. Its visual reach is much wider than the actual hitbox so I don't know yet where I need to position myself to either hit or not hit crates. All of this is very frustrating. Oh well.
(Most phones and monitors use 60 Hz displays. You benefit from high refresh rates with most gaming monitors and gaming phones.)
i feel liek die
Non-German peeps should enable subtitles
except VAT
The way these eggs bounce makes it virtually impossible to get through certain geometry like those tubes, so I opted to find a different way. And succeeded =)
––– Background values –––
00 – Manhattan
01 – Medieval
02 – Sports
03 – Construction
04 – Cheese Moon
05 – Warzone
06 – Default Gradient
07 – Arctic
08 – Hawaii
09 – Hell
0A – Jungle
0B – London
0C – Space
0D – Puzzle
0E – Forts
0F – Time
10 – Retro Hell
11 – Arabian
12 – Prehistoric
13 – Wild West
14 – Golf
youtu.be/pzuigUslK9I
---- Video Credits ----
Title cards: Viacom, altered in Photoshop
Font: "SpongeBoy me Bob" by EyeOfTheLioness
dafont.com/spongeboy-me-bob.font
Countdown timer animation by Luiz-Jorge-Artista
pixabay.com/de/users/Luiz-Jorge-Artista-2114853/?utm_source=link-attribution&utm_medium=referral&utm_campaign=image&utm_content=3469
---- Description ----
This is just a gameplay video and there's no proper tutorial, but for now I will give you as much info as possible
THINGS YOU NEED (to download):
Unreal Engine 4 Unlocker
Parsec
Steam Big Picture Mode/Steam Input (to make Player 2 more playable with a controller config as well as to change the controller enumeration)
Optional: Build 1.0 of the game (if you wish to change characters on the fly, Player 1 only)
TUTORIALS AND DOWNLOAD LINKS:
Cards from the video (if you don't want to pause):
pastebin.com/b02k7fRV
Download Unreal Engine 4 Unlocker:
framedsc.github.io/GeneralGuides/universal_ue4_consoleunlocker.htm
Download Parsec:
parsecgaming.com
Download Steam:
store.steampowered.com
Controller Config Screenshots:
imgur.com/a/FeGGEdC
Level names:
pastebin.com/z07PQYuB
How to downgrade your games on Steam:
Follow this guide: https://knockout.chat/thread/10205/1 and afterwards follow this one: steamcommunity.com/sharedfiles/filedetails/?id=1985923465
---- Timestamps ----
0:00 Intro
8:42 It Begins - Jellyfish Fields
1:23:24 Downtown Bikini Bottom
2:13:38 Goo Lagoon
https://openfortress.fun/
https://openfortress.fun/
https://openfortress.fun/
https://openfortress.fun/
Why did no one tell me that Kritzkrieg is awesome?
Real funny situation.
CPU: AMD Ryzen 5 3600X 6-Core Processor
Arbeitsspeicher: 16 GB RAM (15.95 GB RAM verwendbar)
Aktuelle Auflösung: 1920 x 1080, 144Hz
Betriebssystem:
CPU: AMD Ryzen 5 3600X 6-Core Processor
Arbeitsspeicher: 16 GB RAM (15.95 GB RAM verwendbar)
Aktuelle Auflösung: 1920 x 1080, 144Hz
Betriebssystem:
CPU: AMD Ryzen 5 3600X 6-Core Processor
Arbeitsspeicher: 16 GB RAM (15.95 GB RAM verwendbar)
Aktuelle Auflösung: 1920 x 1080, 144Hz
Betriebssystem:
CPU: AMD Ryzen 5 3600X 6-Core Processor
Arbeitsspeicher: 16 GB RAM (15.95 GB RAM verwendbar)
Aktuelle Auflösung: 1920 x 1080, 144Hz
Betriebssystem:
steamcommunity.com/sharedfiles/filedetails/?id=2004584868
CPU: AMD Ryzen 5 3600X 6-Core Processor
Arbeitsspeicher: 16 GB RAM (15.95 GB RAM verwendbar)
Aktuelle Auflösung: 1920 x 1080, 144Hz
Betriebssystem:
CPU: AMD Ryzen 5 3600X 6-Core Processor
Arbeitsspeicher: 16 GB RAM (15.95 GB RAM verwendbar)
Aktuelle Auflösung: 1920 x 1080, 144Hz
Betriebssystem:
I guess here's another video then to show that yes, Crash also did slide off regular platforms in the original game, just like in the remake.
youtu.be/VTiywh5k0Jw


