Why I keep running into this same issue with highlight reels
Most people trying to work with Crossing Gameplay Highlights Part 1 run into the same wall: the game's internal replay system doesn't always sync with external recording software, and you end up with stuttered footage or missing sections that make the whole thing unwatchable. I spent about three weeks figuring out the right pipeline because the documentation for this game is practically nonexistent, and the community threads are mostly from 2019 when the engine was different. The first thing you need to understand is that this isn't a standard game clip system. The highlight engine captures data separately from the video stream, which means you're dealing with two file types that need to be merged. NVIDIA ShadowPlay won't touch this properly, and OBS has the same problem unless you route the capture through a specific method. Here's what actually works. Run the game in windowed borderless mode at exactly 1920x1080. Don't overscale, don't use ultrawide resolutions even if your monitor supports it. Open OBS and add a Window Capture source, but do NOT use the "capture cursor" option. That adds a two-frame delay that breaks sync with the highlight metadata. Set your encoding to x264 with a preset of veryfast and a bitrate of 8000 kbps. The game's own replay system runs at 60fps, and if your recording bitrate is too low, you'll get compression artifacts that show up as ghosting during fast movement sequences. This usually takes about 45 minutes for a full match highlight reel to render out.
I hit a specific edge case last month that took me forever to solve. When the highlight system was processing long sequences, my recordings would randomly drop frames in the middle, creating a jump cut that made the footage unusable. The workaround was adding a null soft filter in OBS that effectively forces the encoder to flush its buffer at regular intervals. In the custom output section, I added -force_key_frames expr:gte(t,n_forced*2) to the x264 options. This didn't fix the root cause, which appears to be the game engine's interaction with the Windows DWM, but it eliminated the frame drops entirely. The tradeoff is a slightly larger file size, roughly 15 to 20 percent bigger, but that's a fair exchange.
The metadata problem nobody talks about
When you export from the in-game highlight system, you get a .rec file and a .json metadata file. Most people delete the json thinking it's useless, but it's actually what tells the video player where the action beats are. Without it, you're just watching a raw recording with no markers. I've seen people spend hours editing footage manually because they didn't realize the metadata file existed. The json contains timestamps, player positions, damage events, and ability cooldown states. If you're building any kind of automated pipeline for processing these highlights, you parse that json first. It saves you from having to scrub through footage looking for key moments. A basic Python script using the json library and FFmpeg can slice out individual highlight clips in about 10 seconds per clip, compared to the manual process which takes roughly 5 minutes per clip. One counter-intuitive thing I learned the hard way: lower resolution captures actually produce better looking highlights than higher ones for this particular game. The rendering engine uses a lot of post-processing effects like bloom and depth of field. When you capture at 1440p or 4K, those effects get downscaled and they look muddy. Capturing at 1080p keeps the effects crisp because you're not introducing additional interpolation artifacts. This was completely opposite to what I expected coming from other games.
Get the Full Details
What this system can't do
Be realistic about what you're working with here. The highlight system only captures the last 5 minutes by default, and the maximum stretch is 15 minutes if you manually activate the extended buffer. You cannot go back in time and pull footage from earlier in a match that you didn't have the buffer active for. I wasted an entire evening trying to find a workaround for this and found nothing. The game simply doesn't keep that data. Another limitation is that the highlight system doesn't capture voice chat audio. If you need audio commentary synced with your clips, you have to record that separately and align it manually in your editor. Two tracks to manage instead of one. This is a known issue and has been for over a year with no signs of a fix from the developers. If your goal is just to share cool moments with friends, the basic OBS setup I described earlier will get you there without much trouble. If you're trying to build a content creation pipeline around this, you're going to spend a lot of time on the metadata parsing and sync workarounds. There are community tools that automate some of this, but they break every time the game gets a patch, so budget time for maintenance.
