EQAA is not external and is classified as 16xQ in game when in engine it is using AMD's EQAA, as for other notes yes i accidentally replaced NVIDIA notes, apologies.
User talk:Markie
I didn't know that, thank you, and it's fine. The AA options should be listed and described as presented in-game, so if it uses EQAA instead of CSAA with an AMD GPU just add that without the "8f16x", and perhaps add "(Nvidia)" and "(AMD)" after each AA type so it's clear it might change. Now that you mention it I remember some games from that era did differ in AA offering depending on your GPU vendor, Counter-Strike: Source was one of them, probably some other Valve/Source games too.
Hello, I noticed that you had added a line to the page for Sonic Generations saying that unlocking the framerate leads to negative gameplay impacts and was wondering if you had an explanation on how to unlock the framerate for the game.
I don't know how to unlock it. But it would probably cause some serious gameplay issues since even capping it to 30 FPS does that. The game must run at 60 FPS.
The wiki is currently very frequently being targeted by spam bots, you really should remove your email seeing as you are easily asking for your account to be targeted and filled with annoying spam emails.
It's your choice tho.
Thank you!
Helllloooooo, regarding the Doom 2016 Scanline issue, could you add yourself maybe as a source and mention that you still saw it in 2021, far after post-launch updates ended? Because every message in the source I provided are all from far before post-launch updates ended and couldn't find more recent info on whether the issue was still happening or not....
We never run out of thingies here right? :P
Judging by the News section of the game in the Steam Community, the last major update (6.66) was in July 2017. There was another update in March 2018 but it only added Razer Chroma support. I have found a thread specifically about the issue in question that was posted after these updates, detailing it and confirming it was never fixed, and replaced the reference link with it.
Nice job! Couldn't find it, but good that you did :)
In your latest commit from today on this page you now tell people this: "change the values related to the postfx_tonemap_filmic_a setting to 0.220 0.000" Why two values for one (set of) parameters? :P Error?
This post was hidden by Markie (history)
Each of the settings that have been mentioned include two values. You're supposed to set the first value for this setting in particular to 0.220 ignore that line, no value on it has to be changed. Just an oversight while editing.
Ah, if you could make that more obvious which value is for which parameter, then that would make it easier for users yeah :)
What? It's already clear. If you look at the setting in the actual file while editing it there's no room for mistake with how it's written.
Ok, nevermind then, I'll assume it's all fully correct then. Currently don't have it installed, might check it sometime.
There are no older topics