Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.
Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.
Not editable
Content is available under Creative Commons Attribution Non-Commercial Share Alike unless otherwise noted.
It's 100% fact that AA is "hackable" with an Nvidia GPU in this game. But you have to add the game's .exe to Nvidia's C&C:Renegade profile as an absolute application path because the executable that actually *runs* when playing the game is called "game.exe". Which is a common issue. Or else it won't work. www.imgsli.com/OTEzNA and here's the visual proof showing so.
Denying people that knowledge doesn't seem fair because the average person probably doesn't realize this.
And here's another higher resolution screenshot showing 8xMSAA working fine. u.cubeupload.com/MrBonk/Game2019120515410497.png
Because GPU based overrides are better handled through the glossary page, as that way is basically applicable to all games. The link to the glossary page is automatically populated when set to "false".
The "hackable" state has historically been limited to other forms of AA overrides, either engine-based or third-party ways.
I feel it's more relevant to have it on the game page so people don't have to go hunting for the information. Because they may not even be aware or know they can do it with that specific game. That's why they go to the game page in the first place. And unless they somehow end up on the page for my AA compatibility document for Nvidia GPUs (Not something I think you'd easily stumble upon really) or find the relevant thread on Guru3D. It'd be really easy to miss.
"Hackable" in my mind means being able to by means outside of the game itself. Because the majority of games either don't have any AA at all, or are not going to have any way at all to force it through some kind of config tweak. I'd certainly think that a driver level hack that needs compatibility flags set on a per profile basis that aren't exposed by the vendor's own program to be third party related. (Because the driver is intercepting and forcing things)
I respect your rules and will keep it in mind in the future. But it seems like a missed opportunity to keep information on a game by game basis easily visible. Sorry for the trouble.
Here's a relevant forum thread that goes more into why having generic solutions as "hackable" is more problematic than it is helpful: https://community.pcgamingwiki.com/topic/4485-anisotropic-filtering-and-anti-aliasing/