You could say that this isn’t very alarming

windows.h without NOMINMAX be like

“hippity hoppity words min and max are my property”

Similarly how SilentPatch and the WidescreenFix fixes various bugs and adds improvements, mine does as well.

As a matter of fact, I used to maintain ThirteenAG’s WFP for NFS. Now I’m focused on my own thing mostly. (Forked it off of it but barely any of the code is left lol)

It’s called NFS-MultiFix. (I made one ages ago in 2017 for ProStreet but I’m reviving the project now).

It’s a going to basically be an all-in-one thing. So, from basic things like a widescreen fix, to the added ability to change resolutions of environment maps and shadows, fixing clipped/popin shadows in Undercover, fixing crashes, fixing some crap gameplay features, resizable windowed mode, etc. Basically, making it a version of the game that it deserves to be on PC.

It’s a genuinely pretty massive set of fixes spanning over 80 cpp/hpp files with about 500 lines of code on average. I made sure to optimize every nitty-gritty and I ended up with a smaller DLL size than the average widescreen fix while adding so many more features.

I also have a design rule in place - it must do its best effort to work in every possible version of the game without crashing. This includes demo versions of the same games. (This sadly doesn’t count DRM but nothing I can do about that)

That being said, I am currently focused on ProStreet (as I’m also the main coder in Team Pepega for the Pepega Mod) and I hope to make a release within the next year. It should be available for every Black Box NFS on PC (except The Run and World)

If you wanna check out what I made so far, check out the Reformed mod for Undercover. I made an exclusive release for those guys because frankly, Undercover is the worst one out of the bunch (in terms of code).

Silent is a real cool dude. I’ve interacted with him directly and he’s always been helpful.

I assume the code was closed only because it was a bit of a hodge podge he had to clean up. (Well, that and the GTA modding scene is a bit, uh, toxic, to say the least)

I’m currently in a similar position for Black Box NFS games. It’s taken me over a year so far and I’m still not fully satisfied to release anything because there’s so much code to span over 6 (similar, but different) games.

I probably misremembered something then, 390xx it is then.

But whatever it may be it is in the AUR 100%.

It’s very good.

Basically, there is one maintainer in the AUR (the name escapes me, jonathon I think it was?) who applies the necessary patches to the old NVIDIA drivers to make them run with a modern Linux kernel.

Of course, there won’t be any Wayland support, but the experience is acceptable as long as you temper your expectations in terms of graphics API support. (No vulkan sadly)

I hadn’t used it myself but I know a person who does and loves it. iGPU handles Wayland stuff while the NVIDIA is there for the heavy lifting in Xorg.

Unironically, the best bet for them is nvidia 540xx drivers on the AUR with an LTS kernel.

Chart

There go my hopes and dreams of IRL Solid Vision system and duel disks…

One day, it will happen with MR.

RIP Black Box Games

(I’m a NFS fan but also a fan of Black Box)

The way I did it is by trying to solve more and more advanced problems with simpler tools/features, then looking at more advanced features and seeing where they could be applied to make the problem solving simpler. Rinse and repeat.

An easy example that I can remember is making arrays that dynamically expand. I started with the barebones malloc and worked out how to use std::vector (and other list types) in its place.

Understanding that concept is, what I believe, to be the foundation of learning programming.

I’m no pro whatsoever, but using this method really helps me pick up and learn new languages.

Oh you mean Android Studio automagically “updating” your versions so that your build breaks and you spent 3 hours figuring out what just happened without you even touching anything?

Yeah I meant don’t use joycons lol

Pro Controller at the very least. CTR is a game that should be played with a dpad for steering. You can use the analog inputs but some more advanced tricks (such as tight steering) will require a solid dpad.

I’d recommend getting a proper controller for it. CTR is a dpad and shoulder button masher.

Any Black Box made Need for Speed.

(Currently busy fixing Pro Street, so many bugs…)

C++ is at least backwards compatible (for 99% of code anyway, yes I know about some features being removed, but that’s an exception and not the rule).

Yes but, in practice some of these things don’t matter much at all. At that point you’re looking at the performance stack a bit too deeply.

Look at the bigger picture. For example - an RTX 4090 can perform about as well on PCIe 3.0 as it does on 4.0 in most tasks that you’d likely use it for.

You don’t have to care about some of these things as much as you used to before. Sometimes you can get too deep into hunting the best version of your system before you realize that it really doesn’t make that much of a difference.

To top it off, what matters at the end of the day js this - people generally don’t care about graphics anymore!

Even if you end up with graphics that are worse than a console, you still have:

• an option to upgrade later
• options to configure graphics (generally games actually optimize themselves pretty well nowadays)
• an open platform to do things the way you want

PS5 Pro makes absolutely no sense to me.

AAAAAAAAAAAAAAAAAAAAAAAA

It’s just their ego showing through.

It basically now comes down to the current devs depending on new Rust devs for anything that interacts with Rust code.

They could just work together with Rust devs to solve any issues (API for example).

But their ego doesn’t allow for it. They want to do everything by themselves because that’s how it always was (up until now).

Sure, you could say it’s more efficient to work on things alone for some people, and I’d agree here, but realistically that’s not going to matter because the most interactivity that exists (at the moment) between Rust and C in Linux is… the API. Something that they touch up on once in a while. Once it’s solid enough, they don’t have to touch it anymore at all.

This is a completely new challenge that the Linux devs are facing now after a new language has been introduced. It was tried before, but now it’s been approved. The only person they should be mad at is Linus, not the Rust devs.