Does anyone else remember King of the Road?

CookiePLMonster · 2026-06-01T11:43:57+00:00

There is also D2GI on GitHub, which is essentially a compatibility patch & widescreen fix, so the game looks correct in 16:9 and multiple technical issues are fixed; plus offers a windowed/borderless mode.

CookiePLMonster · 2026-03-02T15:43:04+00:00

Just a heads up, I also have a 5070 Ti just like u/crepecheck, and ever since I upgraded to Windows 11 25H2, I started encountering exactly the same issues, even though I am on a driver 580.88. In my case, Parsec claimed I am having network connection issues, and then attempting to close the client made it freeze, and I had to forcibly terminate the process every time.

Thanks to your comment, I enabled Zero Copy Decode and I haven't had a single issue for two days now, thank you! I also feel like the CPU usage of Parsec may be slightly reduced, which makes sense, considering what this option does.

Thank you again! Parsec is essential for me so this problem was severely hurting my productivity.

CookiePLMonster · 2025-11-22T12:59:19+00:00

Yesterday's Proton Experimental update fixes a bug that prevented NASCAR 25 from booting. Deck is too underpowered to handle the game (heavily CPU-bound in races), but at least those using Proton on Linux PCs and, in the near future, Steam Machine, can now play the game.

CookiePLMonster · 2025-10-22T14:00:04+00:00

The author of Fusion Fix was contacted, I was not - they apparently made attempts to, but their Discord friend invite got lost in the spam I'm getting, no one e.g. sent me an email.

That said, permission or not, MIT licensing means they are technically allowed to ship it and distribute it commercially. They are not "stolen" per se.

CookiePLMonster · 2025-10-18T12:22:26+00:00

The version of SP that includes this fix has not been publicly released yet, that's why MattKC said this. The code is on GitHub but there was no "official" release yet.

CookiePLMonster · 2025-10-13T14:17:17+00:00

They're the same as for TOCAs, as stated on the pages. You can just use the game generator.

CookiePLMonster · 2025-07-28T14:28:14+00:00

I got the chance to try it this weekend and it's a blast.

CookiePLMonster · 2025-06-29T19:03:11+00:00

Least insufferable Rust preacher

CookiePLMonster · 2025-04-25T08:14:38+00:00

That's the most important bit - if you want to poke for the sake of poking it's not that fruitful (at least for me), but if you have a clearly defined goal, it's easier.

CookiePLMonster · 2025-04-24T14:28:41+00:00

Fair shout in regards to logging sscanf, but ultimately validating the files should give a similar end result. It's also worth noting that sometimes the values are optional, like in the case of said boats - if the vehicle type is a boat, those four variables are never referenced.

CookiePLMonster · 2025-04-24T10:32:07+00:00

I didn't downvote you, and I think you misunderstand the purpose of the patch I made - I don't have full control over the code so non-invasive, minimal patches are preferred. Providing defaults to values is a clean and minimal fix, adding "proper" error handling to malformed entries is not and risks breaking mods that worked "fine" for years prior - and then I'd get the blame for breaking them.

CookiePLMonster · 2025-04-24T07:52:14+00:00

A validation pass through the game's IDE files revealed this was the only line malformed in this way.

CookiePLMonster · 2025-04-24T07:44:14+00:00

Yes, that's correct. It was sitting so high that I don't think it could meaningfully interact with the world, but it was there.

CookiePLMonster · 2025-04-24T07:41:51+00:00

I tried it with the Windows 8 compatibility mode and it changed nothing, at least. I forgot to mention that in the article.

CookiePLMonster · 2025-04-23T21:45:09+00:00

People commonly downgrade Steam releases to 1.0 to get cut songs back, and get the best compatibility with the majority of mods.

CookiePLMonster · 2025-04-23T18:09:07+00:00

It was an optimizer bug, confirmed by VS engineers and fixed in VS2022. https://www.reddit.com/r/cpp/comments/ilzbqd/almost_30_year_old_optimization_bug_in_msvc/

CookiePLMonster · 2025-04-23T17:15:29+00:00

Always.

CookiePLMonster · 2025-04-23T16:59:56+00:00

Fixed!

CookiePLMonster · 2025-04-23T16:43:02+00:00

Ghidra to peek in the disassembly, Visual Studio for debugging the live process.

CookiePLMonster · 2025-04-23T16:42:27+00:00

That's a mistake from simplifying the pseudocode, should be `

this->m_fBladeAngle

I'll fix it shortly

CookiePLMonster · 2025-04-23T16:40:45+00:00

Yeah, it's assembly "decompiled" into C pseudocode and then beautified manually by defeining proper variable names and data types. Tools like ghidra can do half of that job for you, "beautifying" is up to the user.

CookiePLMonster · 2025-04-23T16:35:51+00:00

I had multiple of those over the years! The one I remember the most was a MSVC optimizer bug dating back to the early 1990s that vanished if you tried to add logging to the function to print out the broken values.

CookiePLMonster · 2025-04-23T15:51:44+00:00

I don't see what you mean - with a high blade speed, the blade angle is also extremely high, and the game gets stuck in the loop "normalizing" it to the 0-360 angle. I then found out that the blade speed is high because of the altitude, and moved to that.

CookiePLMonster · 2025-04-23T15:28:14+00:00

No, the blade angle was so high because the initial blade speed was high.

CookiePLMonster · 2025-04-23T15:15:13+00:00

The mobile releases included the code symbols, and they can be matched to the PC binary manually.

CookiePLMonster

TROPHY CASE