Topic on User talk:Mrtnptrs

Mod was added back to page, although still not fully determined if the Gsync issue is really there or not...

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.....