hey man i am glad i find you your guide is awesome and well detailed but i have problem you write in your guide about unlocking fps by editing in game files like sim -1 i already have it and cap 59 fps but how ? i have micosuttering in most wanted 2005 and i want your solution to help me my pc specs- procesor amd ryzen 5 4500u-6 cores 8 gb ram and integraded graphics card amd radeon i saw on youtube some guy making guide to unlock fps it s slightly help me but i have still issues with the game i even if i make everything on low settings it s same i want everything on high without problem i know it s old game but still i would love to get your help and fix this problem so thx for reading and sorry for my english it s not my primary languge :D so you can ask whatever you want if you have problem to understand what i write
User talk:Mrtnptrs
PCGW pages are maintained by a large community group, so the PCGW Most Wanted page is not "my guide", but a large collaborative effort; sorry, wanted to give credit where credit is due haha. But I would have quite some questions in return to help you most optimally, but it would require many messages back-and-forth here, so maybe PCGW Discord would be easier?: https://discord.gg/KDfrTZ8 Would post your question in the #game-troubleshooting channel there, just tag me (@mrtnptrs) and I can help you more easily and efficiently + others can jump in if they also have some ideas.
And don't worry regarding language barrier haha, I understand you and when I don't, I'm sure to annoy you with many questions :P
https://www.pcgamingwiki.com/w/index.php?title=Need_for_Speed:_Most_Wanted&oldid=1352056
Why someone would use 1.2 demo executable in retail version?
1) Because it's fully functional in retail version
2) Because it's 100% clean (made by EA)
3) Because some people are paranoid on installing any cracks on their system
4) Because non-DRM executable is the only way of playing the game on modern systems -
5) None form of SafeDisk loader/injector or mini-image works on modern systems as an alternative
6) Not everybody uses 1.3 version
Also, I don't remind myself any written rule here allowing you to delete information just because it's without reference, but I kindly ask pointing me out to the right place if I'm wrong.
Last but not least, can I know the reason why a part of your article cleanup here:
https://www.pcgamingwiki.com/w/index.php?title=Need_for_Speed:_Most_Wanted&diff=1352053&oldid=1347347
was deleting 44kHz music replacement?
Something didn't work for you? Didn't sound good? Or maybe installation was too convoluted? Or maybe you didn't fully followed the instruction? Please let me know.
Regarding the first issue; it was totally not clear to me at the time that the demo executable could be used because of it not having DRM. Without that information it looked quite strange to me at the time. I will then thus place it back in a few days if you haven't already done so yourself beforehand :) I should just have placed a dubious note instead so someone like you could have explained the matter. Regarding the 44Khz music replacement fix; I don't fully remember... ok, read back from here https://www.pcgamingwiki.com/w/index.php?title=Need_for_Speed:_Most_Wanted&diff=1352053&oldid=1347347 I removed it because the other fixes suggested that it wasn't even needed and as the other fixes were much simpler, it seemed to me better at the time to remove it and keep the simpler fixes intact. But honestly indeed should have just kept the fix in, so will place that one back too in a few days if you haven't beaten me to the punch. Sorry, I made those edits 3.5 months back and have learned a lot regarding editing since; I simply removed too much info in the past sometimes for not good enough reasons where I thus shouldn't have and just should have placed a dubious note or citation request to clear things up. Honestly tried to clean up the page a whole lot and sadly some collateral damage occurred due to some possible errors in judgement on my part. Thanks for pointing these out.
If you have doubts on any other edits I made at the time on this NFS: MW page, feel free to mention them here too. Also, if you beat me to the punch in placing the info back, feel free to add some external or user references to make sure that nobody else makes the same mistakes as I do.
Will try to look into this tomorrow or the day after, please message here if you haven't beaten me to the punch already and I haven't added it yet in three days as I then likely have forgotten.
I followed a link claiming the Atomic Heart page had a fix for mouse acceleration, but no such fix was on the page. You had removed it, with the following reasoning:
"Again, mouse acceleration fix already included on the UE4 glossary page linked below the video table.... + FOV fix already linked to in the video table. Thus removing both fixes. Additionally, please read the editing guidelines as they are not really conform those... :) Feel free to ask us any questions on the talk page or our Discord :)"
Removing what I'm sure many would consider an "Essential Improvement" because it can be found half-way down a different page, only linked in a footnote at the bottom of the unrelated "Video" section, while the page's only mention of mouse acceleration simply notes, "Forced on by default, with no way in-game to disable it.", is so ludicrous that I made an account just to complain about it. Before entirely removing any mention of a fix from a game's page, please consider whether a visitor to the site will have any chance of learning about and locating that fix.
Those mentions should be removed as stated already: those fixes are already included on the UE4 glossary page linked to under the Video table. This has been agreed upon and discussed many times in our Discord. Please go there to dispute this decision if you disagree.
I don't disagree that the instructions for generic fixes shouldn't be duplicated on each game page. If the instructions had been replaced with a link to the appropriate section of the UE4 glossary page, or a link added in the Input section, there would be no duplication and no harm done. But entirely removing any mention of the fix, on the basis that it can be found on a separate page with no apparent relation to the issue, unnecessarily obscures the existence of that fix. I couldn't find the policy you seem to be referencing in the editing guide, but I'm sure it's intended to improve the consistency of fixes without making them harder to find.
To be frank, the way you're treating this feels almost malicious, as if you're twisting the rules to remove information just because you can. I hope that's not the case.
(And to be clear, I'm aware that this particular fix turned out to be a placebo, making this specific case moot, but I'm still concerned that important fixes for other games could be similarly "hidden" where visitors won't find them)
"To be frank, the way you're treating this feels almost malicious, as if you're twisting the rules to remove information just because you can. I hope that's not the case." Please see our Discord group discussion. Not trying to be malicious, vicious or anything, was just trying to follow the PCGW way of working as done so far. See our Discord for the discussion about this and more detailed explanation :)
Discussion was btw done at one point at 3 places at the same time, hence I kept my answer here a bit short, sorry if that made me sound blunt or anything :)
After discussion here and on Discord: ok, links to UE4 glossary page fixes can sometimes stay when "false" values doesn't already produce a note pointing to the UE4 glossary page. However, adding fixes clearly already covered as a whole on the UE4 glossary page literally as a 1:1 copy is still not liked and will still be in the future removed when noticed.
I get your reasoning: "Move note to proper place + cleanup of unsourced fixes (last fix sounds sketchy)"
There is no source except my personal experience and a video I made to document it, https://www.youtube.com/watch?v=5j4u4cRnXKg. I'm not sure how PCGW's policy is regarding sourcing, but I saw that often some steam forum post is considered as sufficient. My hope was that a trustworthy veteran user would reproduce the issue, or I could just link the video in the notes.
This is the edit you are referring to: https://www.pcgamingwiki.com/w/index.php?title=Doom_Eternal&diff=1360115&oldid=1360114 I removed it indeed because it is a significant claim that was unsourced and I could not find easy info about it. That video showed it indeed was an issue at that time, but as it is a two year old video and many GPU and game-updates have released since, it doesn't really represent the status of this issue today in my opinion. So, my questions to you are: what are your systems' hardware specifications (CPU and GPU most importantly), have you fully updated your GPU driver (not from OEM, but from GPU manufacturer's site) and are you running the game thus using your dedicated GPU? Just asking this to rule out this performance issue being actually caused by something at your side :) Also, what is your experience regarding performance numbers between async computer on vs. off when using V-sync?
Btw, also removed that bit because of it was not according to PCGW guidelines: usage of "you", essentially lists two workarounds in one and first part of the description should actually be a note inside the fixbox (thus it missing the "|fix="). Also indeed because it misses a ref, if you can reproduce it, you could easily then add yourself as a user-reference ("checked by user") and list in its comment what your findings are in more detail. Because it was not according PCGW guidelines and looked a bit sketchy, I thus chose to remove it as it only made it look more sketchy. But if we quickly rule out something at your side, we should indeed place it back :)
" [...], it doesn't really represent the status of this issue today in my opinion. " I retested it with the up-to-date WHQL driver 22.11.2 and Doom patch 6.66 rev2 and the issue unfortunately persists: imgur.com/a/Je2HsNi
" what are your systems' hardware specifications (CPU and GPU most importantly), have you fully updated your GPU driver (not from OEM, but from GPU manufacturer's site) and are you running the game thus using your dedicated GPU? " The Doom Eternal performance overlay is unique in that it displays all this information in the video (except the CPU which is of non concern in id-tech 7). In short: Ryzen3700X/RX580, Yes, Yes.
" Just asking this to rule out this performance issue being actually caused by something at your side :) " That's the main reason I hoped other users would reproduce the issue. My suspicion is that it is a driver/architecture related issue. Polaris GPUs get the most recent vulkan drivers, but often have questionable support of newer vulkan_extensions (at least according to some emulation developers). If someone tests it with a GCN5/RDNA/Nvidia card, I would expect to see different results.
" Also, what is your experience regarding performance numbers between async computer on vs. off when using V-sync? " The video should illustrate that, but I also noted the numbers in the description.
" Btw, also removed that bit because of it was not according to PCGW guidelines: usage of "you", essentially lists two workarounds in one and first part of the description should actually be a note inside the fixbox (thus it missing the "|fix="). " The fix is using triple buffer Vsync in combination with Async instead of regular Vsync. But yes, the form could have been more concise and formal.
" Also indeed because it misses a ref, if you can reproduce it, you could easily then add yourself as a user-reference ("checked by user") and list in its comment what your findings are in more detail. " Sorry, I'm not that familiar with the PCGW structure. I just clicked edit and tried to replicate the form of the already existing entries. My few contributions are limited to problem-solving of niche problems in mostly older titles I figured out for myself and try to share. I guess your aim and that of the site is more a documentation/preservation approach, which is admirable.
Because PCGW is not only about documentation and preservation, but of course mainly just about fixing games. But tried to clean up some pages in the past as they contained an excessive amount of sketchy fixes and this one got likely caught in the crossfire. So, would be okay if, with previous feedback, you would place this issue back, but if you feel hesistant or such would it be okay if I added this issue back with proper layout and everything and then use your images on imgur as the reference? But again, feel free to place it back yourself; I can always afterwards provide some extra feedback to also aid you in improving your future edits. :)
Ok, a new attempt was made. https://www.pcgamingwiki.com/wiki/Doom_Eternal#Various_performance_issues
The new set of images is cropped and includes marks for better readability. I also tested all four V-sync variants Doom Eternal offers.
Corrective suggestions are welcomed.
The corrections that should have been made were so small, that I made them myself, tell me if you think anything should get changed :)
I see, the fix takes center-stage and then gets elaborated further inside the fix box. Looks good to me.
Great, if you have any suggestions, feel free to tell me. Will soon receive a new computer and will then test this game on there if I think of it. Will be Nvidia hardware.
Hello Mrtnptrs, when you reverted my controller support for Hitman Blood Money, you said, "Newly added mod, according to the added notes, causes more issues compared to the original one, thus reverting it", no, it has less issues than the original one, that's why i added it. There is no broken Menu formatting anymore, there is no loading messages referring to "the PS2 Memory card" anymore and entering the "Control" menu don't crashes the game anymore aswell, I even deleted those old notes referring to these issues when I edited the section, to show that there is much less problem with my fixed version of the controller support.
Ok, this is very weird; sorry, I was totally wrong. The "diffs" of the made edits seem to have confused me majorly, making me think the notes were added instead of removed. Sorry for this. I will undo my undos. Thanks for the keen critical eye, don't know exactly how this happened.
No problems ! Thank you Mrtnptrs
Oh, another proper fix removed by gatekeepr Mrtnptrs? No way, I'm shocked! haha :)
"Gatekeeper"? Please leave your distasteful salty remarks somewhere else please. This topic is completely unrelated to your mod. Hijacking it is not really nice. Also, this was literally an accident caused by some unclear diffs, as already explained. The discussion surrounding your mod was a whole different thing....
not sure how to do it correctly but you go the folder where the game is stored, look for a file called settings.ini and open it with notepad, there's a line called "mouse= ###" you can change that value higher than what the in-game allows, and set it to read only after changing the values
Doing that only changes the mouse sensitivity value beyond what the in-game setting allows. The strong negative mouse acceleration sadly can't be disabled.
hence it's a workaround
it's a lot more playable than before
theoretically if you set it high enough...
Then maybe mention that it is a workaround and around what amount it should be set/that it worked for you. And thus mention that it only changes the mouse sensitivity setting and not the negative mouse acceleration itself. Then it could maybe be added again? What do you think @Jigen123?
I am the person who published the fix about the world area being completely dark for the player. I posted it for other Players that might have the issue but couldn't find a fix for it. You also stated it is sketchy that lowering the settings will fix it. But I found about this method when trying to find a fix for the error on my own and could only find this video with a reddit post linked in the description.
It was hard to check your added fix as it missed any references/citations towards that Reddit post or video. But there are still more points why I think it now shouldn't be added to the page; the linked Reddit post suggests this only happens while using DXVK. DXVK isn't officially supported on Windows, so if a game doesn't have major known performance issues, they shouldn't be added to PCGW pages. If on AMD, did you update your graphics driver and if that didn't help just try this fix for Mesa drivers?: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3036#note_598704 Also, video only suggests to change volumetric fog section and only shows a black square issue, so it is a total question for me why your added issue also mentions a "World area is completely dark" issue and suggesting to adjust Ambient Occlusion setting too. Not to be rude, but did you perform testing on this yourself? Because it feels a bit like you just found a fix on Reddit and just put it on PCGW quickly without testing haha, but I assume that isn't true? :)
> Because it feels a bit like you just found a fix on Reddit and just put it on PCGW quickly without testing haha, but I assume that isn't true? :)
No I did not. As this fix did not worked for me in the first place, so thats why I tried to change every setting in the graphic options to see which one works. And I found out which one worked for me, so I added it to PCGW for people that might also have this issue to have a fix ready. So its hard to add a reference when I found a fix that worked. So I find that the remove of the fix was a bit rude, as this might be a chance for people that could also have that issue, to find and use the fix for it.
Well, your fix is just changing two settings values to another, which is not ideal and sounds sketchy. You provided a source only in this talk page topic which did not fix your issue (so can't be used as a reference), so you tried things yourself without adding yourself as a ref with an explanation (or adding it in the commit message) of why it helps and your current configuration. Also, you didn't answer my questions regarding DXVK and AMD... What OS are you running this on? Because again, if DXVK is used, it is a DXVK-only issue and shouldn't be added to a page of a game with no known huge performance problems.
And for me being rude: I found your fix sketchy (just two settings changed, likely that in reality only one changed setting worked around your issue, large chance game itself isn't the cause etc.) and without reference or explanation given anywhere. I also couldn't find you on our Discord server. In such cases I often revert the edit with extensive feedback and asking to discuss it first so it can be placed back possibly in a much improved form. And btw, not to be rude, but your "fix" is not really a fix, but a workaround. Issue from what I see might be caused by DXVK or an outdated driver, but as you didn't answer my questions related to that yet.... I can't determine this.
About the question what OS I'm running. My specs are these:
Windows 10 Pro GTX 1050Ti (Driver version 31.0.15.2225 according to the device manager) AMD Ryzen 5 3600XT 16GB RAM 3200MHz
Also yes you couldn't find me on the Discord because first I didn't knew that one existed and second that I don't like like to be on many Discord servers that I rarely would visit as I find the website already useful enough for me.
Again, are you using DXVK or any wrapper. Please answer all my questions.
I thought my answer that I use Windows 10 might be obvious enough that I don't use any wrapper. As with Windows 10 I can natively start the game.
Btw, that looks like to be a very outdated GPU driver. Please update it from the Nvidia website, will most likely fix your issue.
I always use "NVCleanstall" to install my drivers update as I don't like the bloated "Geforce Experience" software.
Ok, cannot determine from this if you fully updated your GPU driver or not of course.... Please, when someone asks something or asks you to do something, please be clear about it and not leave things so free for interpretation. Did you make any further modifications to the game like mods, tweaks etc.? Please answer fully or I'm gonna stop with this tango....
After I bought the game I installed the game and started it right away. I have not made any further modifications to the game via mods or anything like that. Cause Saints Row The Third Remastered should be played without mods in my opinion. And I noticed the issued when I was proceeding through the gameplay, I first ignored the issue but it became much more annoying, which made me try and search for an fix for the issue. As stated I could only find the YouTube video where someone was using a wrapper for it. But I play the game completely native. I'm still running with the GPU driver version which I stated and only made changes in the settings that I wrote in my fix to get rid of the issues.
Again, asked you if you've updated your GPU drivers as I said that from the driver version you provided, it looked outdated, thus that you should update to likely fix your issue. So, really the last time: can you please update your GPU driver to the latest version (527.56, https://www.nvidia.com/download/driverResults.aspx/197460/en-us/ , My GTX 1070 reports this driver as 31.0.15.2756 in device manager) and report to me if this fixes your issues with the black squares and darker world. If you can't, don't or are very vague again, I can't verify if its actually your GPU driver being outdated here and thus then we cannot proceed.
At the time of your comment his driver (as he mentioned: 522.25) wasn't even two months old. How is that "very outdated"? Especially if talking about a game from almost 3 years ago. Thank god you were here to put him and his fix in his place haha :)
Please stop hijacking old topics I started. This is starting to feel like harassment specifically at me because of my decision to temporarily pull your DS3 mod pending discussion and is already placed back, so....
Because of your reason to respond to this, I'm sadly not going into details...
You deleted my edits regarding the "DS3 Proper PC Experience Mod". Let me address your points:
1) "just a mod-pack basically of fixes already on this page"
It's not a collection of fixes. Most of the fixes on this page don't even work with the latest version anymore (e.g. No Intro, FOV) or don't work together (e.g. G-Sync only works in fullscreen in DS3, but the FPS mod only works in windowed mode). Also, some of the mods only work in the Steam version of the game. This is a single file you drop into your game folder and you're done, no fiddling around or trying hours to make stuff work (e.g. G-Sync).
2) "(see credits on nexusmods)"
You must've misunderstood this section. This gives credit to the people that found out what memory regions or logic the game used to achieve its effects. Built upon their previously shared knowledge, new and better fixes were created here. Just because you learned how to fix car engines from a book you've read, does not mean you copied the book author's work.
3) "misses warnings that individual fixes have on this page regarding disadvantages"
Which one? There's only an issue with increased FOV mentioned on here. The same warning is on the Nexus Mods page, but could've been added as well.
4) "fix was added twice instead of referencing to itself one of the two times"
Not exactly sure what you mean should've been done instead.
5) "ref that was used is lacking (should also contain a user-name or website-ref)"
I feel like Nexus Mods has all the info needed? Why create multiple pages? Single point of truth.
6) "seems like individual tweaks can't be turned off"
The only thing you cannot turn off is the No Intro mod. Everything else can (see description on Nexus Mods page) or is applied when needed (e.g. no black bars on ultrawide monitors). The "DS3DebugFps tool" which is mentioned on the page is also silently removing the intro screen, which cannot be turned off.
A lot of work was put into this to fix this game for PC gaming once and for all and with basically one click. Please don't gatekeep this.
I'll look into this somewhen today, but only thing I'll say so far in general: a mod containing a collection of fixes/enhancements that individual fixes already contains is in general not well-liked. But maybe in this case it could be, I'll look into it. But wanted to say I'm not just gatekeeping it for no reason or for fun haha, so don't worry :) Thanks for the detailed arguments you brought up btw :)
Ok, here we go:
1 and 2. Sorry, I meant it contained fixes for issues similar to fixes for issues already on the page. So, not the exact same fixes maybe, but fixes that overlap in the issues they fix. You are absolutely certain that the No intro mod, indeed not updated after June of this year and the FOV mods (all 3 options) are not working anymore with the latest Steam release? Btw, Proper PC Experience Mod literally says in the credits that it contains the FOV patch from Altimor, which is referenced on the PCGW page in that FOV section. If during testing you encounter a mod absolutely not working on a clean install and when installed individually of course, feel free to remove it with of course naming the reason of removal in the "summary" line. Not that you would do that, but of course should be avoided to remove individual working fixes to replace it with a larger mod.
3. Yeah, would always be better to mention negative points and warnings on the PCGW page too, so people don't have to look through many pages to make a decision regarding which solution they want to apply. Also would be nice to mention its incompatibility with specific mods, like Souls Unsqueezed (I know it overlaps maybe, but if that feature of the mod is turned off, are you sure it is still incompatible? Bit biblical for the mod then to remove the other one automatically right?).
4. You literally added the same fixbox with identical content. See Manhunt page for multiple examples how to reference a previous made fixbox/section in-article. This reduces the amount of overlapping information on pages and decreases maintenance work on pages.
5. The mod page for a mod itself is not a reliable reference of course as the maker of a mod is of course never fully objective about his or her own work. A citation would be nice to confirm it indeed working: like a forum post of people confirming it working (in the form of <ref>{{Refurl|url=|title=|date=2022-12-28}}</ref>) or just a user-reference, like you (in the form of <ref>{{Refcheck|user=Mrtnptrs|date=2022-12-28|comment=}}</ref>). Is also a bit of the standard way of working on PCGW.
6. Ok, was not really clear to me honestly when reading the description page. Also, don't see the DS3DebugFps tool referenced anywhere on that page (anymore)... But could be because it was recently updated/edited...
7. My extra bonus-point haha: Gsync fix looks a bit like a scam to me as it should still work if people enable Gsync to work with windowed applications too, which can be easily done in the Nvidia Graphics panel. Or what does this mod then specifically fix regarding Gsync, which is normally totally not handled by the game itself, but by the graphics driver?
8. Also regarding your first point: are you sure some existing fixes on the PCGW page are incompatible? Because as said in point 7, Gsync "fix" shouldn't be needed. Why don't the other mods then not work together properly?
I'll try to keep it short:
Yes the above mentioned fixes don't work with the latest version anymore on a fresh install.
G-Sync doesn't trigger for borderless for this game, only for fullscreen. Enabling "window mode" for G-Sync in the NVCPL, causes the game and menu to run at unsteady 1-10fps. This is confirmed on a fresh install of DS3, latest Nvidia drivers, and a 30-series GPU.
"in the credits that it contains the FOV patch from Altimor" - "patch" as in "algorithm" for calculating the FOV in-game, not the das3fov tool.
The redundant fixboxes can be reduced down to one I guess, the one under "Essential Fixes" maybe?
As for references, the Nexusmods page has comments where users say it's working. I guess I'd have to wait for some reddit post of people talking about it to add it? I feel like the Nexusmods comments are good enough for a user to decide if it's worth installing, I could be wrong though. Speaking of, the citation [4] regarding the negative effects of FOV widening just links to the Souls Unsqueezed Steam page, where nothing related to the issue can be found?
Dude, wtf? I also just noticed YOU removed my fixes for Red Dead Redemption 2 and Doom Eternal a few months ago. I'm not too invested in Doom Eternal so whatever but Red Dead Redemption 2:
https://www.pcgamingwiki.com/w/index.php?title=Red_Dead_Redemption_2&oldid=1287251
"Removing this bit [...] clearly shows a DLSS sharpening slider being available"
The whole point of these mods was the sliders weren't working properly (0 often did not mean "disabled", just the least intensity) or sliders were not available at all. As you can see here, the slider is useless in RDR2:
reddit; /r/nvidia/comments/s94c0n/tool_to_properly_disable_dlss_sharpening_and/inmg6yn/ (won't let me link here, but check first comment)
"Auto-exposure is a feature by the game and not really an issue right"
What? Why are you removing stuff from the PCGamingWiki if you don't know what it's even doing? DLSS wants the engine to provide exposure values with every frame. If the engine can't do it, the developer is supposed to enable "Auto-exposure" in DLSS, so DLSS can try to calculate its own exposure values for each frame. Guess what? Rockstar neither enabled Auto-exposure nor provides the exposure values. Besides, the Nexusmods page allows to download two version of the mod, one with the Auto-exposure fix and one without.
"Dude, wtf? I also just noticed YOU removed my fixes for Red Dead Redemption 2 and Doom Eternal a few months ago." Please keep being respectful as I am to you.... I'm only trying to keep pages clean of sketchy, outdated and unsourced fixes. Many, especially older game pages, sadly suffer from this. Clearly state my motivation for this when doing it and everyone is free to object and discuss it of course. So, please stay nice ok?
Nevermind, confused you with another user, so removed the content of this specific message
"G-Sync doesn't trigger for borderless for this game, only for fullscreen. Enabling "window mode" for G-Sync in the NVCPL, causes the game and menu to run at unsteady 1-10fps. This is confirmed on a fresh install of DS3, latest Nvidia drivers, and a 30-series GPU." This is really really unusual as Gsync should never be able to interfere with a game in this way and have never seen it causing performance issues. Are you sure you have any overlays or tools that could interfere with the game disabled/closed?
""patch" as in "algorithm" for calculating the FOV in-game, not the das3fov tool." How do you know this for sure exactly? The page is really not conclusive about that. You are the uploader of that mod then right?
"The redundant fixboxes can be reduced down to one I guess, the one under "Essential Fixes" maybe?" If/when a fix gets added and would be mentioned multiple times on one page, it is preferred to display the most top one in full and later on thus only reference it with a fixbox only containing and in-article link to the full version. If the fix is indeed essential, then the full version should be in Essential fixes yeah.
"What? Why are you removing stuff from the PCGamingWiki if you don't know what it's even doing? DLSS wants the engine to provide exposure values with every frame. If the engine can't do it, the developer is supposed to enable "Auto-exposure" in DLSS, so DLSS can try to calculate its own exposure values for each frame. Guess what? Rockstar neither enabled Auto-exposure nor provides the exposure values." Ok, may have then not properly understood this, sorry. Thought I checked it correctly. Luckily others can correct me if I make any mistakes. Did a lot of cleanups a while back, so a mistake can always slip through. But thanks for the feedback :)
"The whole point of these mods was the sliders weren't working properly (0 often did not mean "disabled", just the least intensity) or sliders were not available at all. As you can see here, the slider is useless in RDR2:" Did not know this I think and wasn't aware of the sharpening actually not getting fully disabled... If I remember correctly, this wasn't in the notes of the fix either, which it then should have been. Could you add that then to the sharpening and auto exposure fix you added back to the page with this source?
"As for references, the Nexusmods page has comments where users say it's working. I guess I'd have to wait for some reddit post of people talking about it to add it?" When you can't find a non-modpage reference, but you tested it, you can always add yourself as a reference as I previously suggested.....
Hopefully I covered it all as we were now also talking about RDR2...
I apologize if I appeared rude, I just saw you removed a bunch of my stuff from more than just DS3.
I've added a note about the slider at 0 still causing haloing in RDR2. Feel free to improve its wording or move the entire box.
Back to DS3/G-Sync: Yes, there were no overlays. The "windowed" G-Sync option has been very buggy for a long long time, I'm not too surprised it didn't correctly work in this game.
FOV: Yes, I'm the author.
Can I add the single fixbox then? You can polish it afterwards however you see fit.
"I just saw you removed a bunch of my stuff from more than just DS3." As previously stated, I worked on quite some pages, so I likely have at least some overlap with like 70% of contributors here haha.
"I've added a note about the slider at 0 still causing haloing in RDR2. Feel free to improve its wording or move the entire box." Yeah, I saw, improved wording a tiny little bit.
"Back to DS3/G-Sync: Yes, there were no overlays. The "windowed" G-Sync option has been very buggy for a long long time, I'm not too surprised it didn't correctly work in this game."
To my knowledge it works just fine lately with all games, I encounter no issues with it enabled. Ok if I maybe ask other users on the PCGW-Discord for a second opinion? Just to verify this really strange issue is really there.
But can you still argument which existing fixes on the DS3 PCGW-page are incompatible with each other and why and which ones completely do not work with the latest release on Steam? (apart from the Gsync fix as that one is still a bit up in the air)
Feel free to ask whoever you want on Discord.
For this game, even the author of SpecialK/Souls Unsqueezed says to use fullscreen instead of borderless for G-Sync:
github dot com /Kaldaien/SoulsUnsqueezed/releases/tag/sus_060 (very bottom)
In contrast, the DS3DebugFPS to unlock FPS does not work in fullscreen:
nexusmods dot com /darksouls3/mods/614?tab=description
"For this mod to work properly, you must play in windowed mode which is why I have forced the game to run in a borderless window [...]"
So it's one or the other.
The No Intro mod doesn't work with the latest version on Steam. If I remember correctly neither does das3fov for increasing FOV (and required to be launched on every restart of the game anyway, just like all the other CET "suggestions"). Souls Unsqueezed only works with the Steam version, if I remember correctly. Ultrawide requires the user to install a hex editor first and the linked article only tells them what to insert if their resolution is 2560x1080 or 3440x1440, but these are not the only ultrawide resolutions out there. And so on... So much pain instead of literally just dropping one file into your game folder and be done with everything.
Anyway, do what you want, I don't wanna discuss this anymore because I feel like we're doing circles here. I'm adding a single fixbox and you can edit it however you want or delete it if you feel it's useless. I like PCGW and it's always the first resource I open before buying/starting a new game. That's why I wanna "give back". People on Reddit message me almost every day requesting to fix some game, especially whenever a new game drops. If it takes _this_ much effort to add a fix to a 7 year old game's article, I'll definitely take this into consideration when deciding to do another game. Obviously I will let my reasons known. I understand trying the keep the quality of the articles up but this is ridiculous.
I've already asked on the Discord about it and will let you know when I have an answer.
"If it takes _this_ much effort to add a fix to a 7 year old game's article, I'll definitely take this into consideration when deciding to do another game. Obviously I will let my reasons known. I understand trying the keep the quality of the articles up but this is ridiculous." I understand your frustration, but have some question-marks regarding the Gsync thing, thus wanted a second-opinion on the matter from someone else than the maker of the fix him/herself and just asked some questions..... I was intending thus to get feedback first from others for confirmation before placing it back.... I'm reverting it for now till I get confirmation from a second opinion that it works (some of the people on PCGW have a bit more tech-knowledge than your run-off-the-mill nexus mods user :) ) and a confirmation of the Gsync issue as that still sounds weird to me haha.
Btw, if I get no answer there after asking repeatedly, I'll place it back anyways, so no worries about it staying in limbo forever :)
So why remove it now and not once you heard back? Surely after 4 days someone on your Discord replied to you after "asking repeatedly".
FYI: nexusmods dot com /darksouls3/mods/?BH=7
It's been out for just a few days and already has way more downloads than any other mod in the past 30 days. It's also leading in endorsements. Tell me again how this mod is redundant and unneeded? haha :)
Already provided my reasoning, but indeed asked multiple times in the Discord with no answer, thus was indeed planning on adding it back today (as I promised I would do if hearing nothing back), which you've already done as I can see. Will let you know if anything would ever change....
Also, never said it was really redundant or unneeded..... Also, see PCGW Discord #Articles channel for me indeed asking it repeatedly if you don't believe me. Thus, because of the lack of answers there, I would have placed your mod back anyways.....
Hi, Mrtnptrs.
I'm writing regarding your particular edit below:
https://www.pcgamingwiki.com/w/index.php?title=Grand_Theft_Auto_IV&diff=1281577&oldid=1281571
"RGL-fix removed: source did mention updating it, but did not fix problem. "Infinite loading loop" removed as fix under it doesn't even mention it. Removed settings guides. Removed Steam Overlay-fix (doesn't make sense)"
I kindly ask you to have nothing against its restoration in the section below DXVK, slightly changed and renamed as:
"Framerate drops associated with too high details on not modern hardware"
I understand the section is completely irrelevant on such CPUs like i7-13700KF, but it's very useful and tested on configurations with old Core2Quads and Phenom II X4 to maintain 60 FPS on even RGL versions of the game.
It's also a good alternative for people with older GPUs which doesn't support DXVK as performance fix/workaround (no Vulkan support). I only slightly expanded the section made by someone else at some point, and I can confirm it works and someone did a good job on this.
Regards
Uh... Next time, could we use the GTAIV's Talk Page instead of a user's one? I'll try to read the whole conversation and share my thoughts about the suggestions that were shared. 😅
Uhhhh, removed and refactored some notes in the DXVK section together with someone else to reduce bloat on the page. So, if you have good information to add, feel free to do so. It was just that saying "lower this setting to this to improve performance" was also removed by me because it is quite basic for almost all games; lowering draw distance improves performance for example.
"Framerate drops associated with too high details on not modern hardware" This is thus in my opinion also kinda standard; too high settings result in framerate problems. Please don't assume I'm disregarding this because I have a more modern PC, has nothing to do with that; I tried to look at it from an objective perspective and if it was too standard or not.
So, feel free to add whatever you want and if needed, it can always be discussed further :) Just my opinion would be to avoid to name things that are basically applicable to every game, like lowering draw distance can improve performance....
I absolutely got your point.
Although, especially on game launch, some high values were considered experimental to the extent they were unplayable and can be tasking even to this day due to legendary poor optimization of the game, so let's better leave people aware of the issue.
Yeah, higher values make it even worse, but even on lower settings, this game runs quite bad. It is also thus just in general very poorly optimized with lots of stuttering. I'll ask some others with more experience regarding GTA IV and if they find your changes ok, you won't hear a peep from me :)
@Deton24
While it may be very helpful, that sort of information is better kept in a personal tweak guide, not in the game article. I think you and mrtnptrs should probably try to reach a definitive consensus for that sort of stuff in the wiki with senior editors or perhaps moderation. You can always create a forum thread about the game and keep the information there too.
@Deton24 I share Markie's opinion here honestly. Although your additions are good and very well-intended, I would vote for replacing your additions with a mention in the introduction like "The game is notorious for poor performance (especially on higher settings, but also on lower settings) and frame-pacing issues, even on high-end systems. Lowering settings is strongly advised." The mentioned command line options by you are in my opinion also quite minor and are very lower-end hardware specific and most likely won't contribute even on those systems much to performance. What do you think about this proposition.
Moving the section to the discussion page with a link at the top of the GTA IV wiki with your note is an even better solution, indeed. Nobody will have writing permissions on discussion page, but comments will remain open. I see you've just moved key points to introduction, so it's moved there.
Yep. Sounds good to me too.
Think that is a good solution, nice :)
I'm not using dev build or pirated copy. LOL I'm on game pass. And it's a well known issue at this point.
https://thenerdstash.com/how-to-enable-vsync-in-atomic-heart/ https://primagames.com/tips/how-to-enable-vsync-in-atomic-heart https://www.distractify.com/p/how-to-turn-on-vsync-atomic-heart https://www.youtube.com/watch?v=kTcp5NaWics https://sirusgaming.com/atomic-heart-vsync-not-working-fix/ https://www.reddit.com/r/atomicheart/comments/117p0l8/how_to_enable_vsync/
etc. etc. Whatever.
The workarounds mentioned above don't work anymore since today's update btw. Only way to fix it now is to force VSync via driver software. I thought it's worth mentioning on a PC gaming wiki.
Why the F?! This is the weirdest issue I've seen.... Sorry, gonna undo my undo. Keep me posted if an upcoming update fixes your issue.
Yea, what the F. Big screen tearing and no VSync. :-) Thanks Don't know what the commonality is here, it's happening on both AMD and Nvidia.
Btw, on the internet, they suggested the Vsync option is just totally broken, but sources on it are a bit vague, so.... But also, the game hasn't had an update in three days.... So there was no update released today or yesterday. See: https://steamdb.info/app/668580/depots/
I strongly suspect somehow a specific setting in the driver control panel of these users is causing the game to do this, thus that the game has a bug not being able to handle a certain case or something. Guess we'll see haha
Don't know, I played yesterday evening, and today when I launched it, it downloaded a 19.7GB patch on game pass and since then the workaround doesn't work anymore. I have a relatively fresh Win11 and never touched any setting in the Nvidia control panel, today was the first time I opened it since installing Windows.
Oh, it was on Game Pass.... I checked the Steam version and that had no update. Very likely then that it is an issue with the Game Pass version. Ok if I add you as a user source?
I added you as the source haha, feel free to undo my edit if you don't want that :)
Also weird that the Game Pass version gets updated while the Steam release doesn't.
Can you still reproduce this issue as of the latest 1.3.5.0 patch (version of Steam, don't know what it is on Gamepass)?