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.

Topic on User talk:Mrtnptrs

Deleted Contribution to Saints Row: The Third Remastered page

16
Summary by Mrtnptrs

User stopped responding after repeatedly asking the same question that wasn't answered. Still, because the fix already looked very sketchy, it was removed and the severe doubts raised in this discussion makes that probably a good thing.

Nullyuki (talkcontribs)

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.

https://youtu.be/FWfCj5O4lkM

Mrtnptrs (talkcontribs)

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? :)

Nullyuki (talkcontribs)

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

Mrtnptrs (talkcontribs)

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.

Mrtnptrs (talkcontribs)

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.

Nullyuki (talkcontribs)

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.

Mrtnptrs (talkcontribs)

Again, are you using DXVK or any wrapper. Please answer all my questions.

Nullyuki (talkcontribs)

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.

Mrtnptrs (talkcontribs)

Btw, that looks like to be a very outdated GPU driver. Please update it from the Nvidia website, will most likely fix your issue.

Nullyuki (talkcontribs)

I always use "NVCleanstall" to install my drivers update as I don't like the bloated "Geforce Experience" software.

Mrtnptrs (talkcontribs)

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

Nullyuki (talkcontribs)

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.

Mrtnptrs (talkcontribs)

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.

Potatogamer (talkcontribs)

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 :)

Mrtnptrs (talkcontribs)

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

Mrtnptrs (talkcontribs)

Because of your reason to respond to this, I'm sadly not going into details...