Hey, your GeDoSaTo addition to the DS2 page is all in excellent form and fully according to editing guidelines, but have a question: is it really needed for the page? Isn't it made redundant by the Video table's Vsync note already referring to this https://www.pcgamingwiki.com/wiki/Glossary:Vertical_sync_(Vsync)#Override_vertical_sync_.28Vsync.29_behavior glossary page with plenty of good solutions? Especially with you mentioning "GeDoSaTo Tool may occasionally fail to work as intended. When that happens, simply restart the game for the vsync to take effect", might it not be better to maybe remove the GeDoSaTo addition to refer people to the solutions on the glossary page? Because especially the Nvidia/AMD Control panel instructions there are probably far preferable above using GeDoSaTo right?... and easier for users to apply... Does GeDoSaTo have any advantages above these glossary-mentioned ones? Just let me know what you think :)
Topic on User talk:Hondamatic
Hi there!
I'm sorry, I'm new to editing Wikis so I've no idea what the 'protocol' is or how PCGW works in general. In fact, this is the first time I've made a 'major' edit in a Wiki page, and it took me a while to figure out all the ins and outs! In the end it was mostly certainly worth it, and I look forward to contributing more in the future.
In any case, the reason I added GeDoSaTo tool is because I've an RX570 and for some reason or another, the driver level vsync is broken on AMD Polaris. I'm not entirely sure why but it sure looks like I'm not the only one.
Come to think of it, even my older R7-260X had problems forcing driver level vsync. The only option that seems to work on my 570 is the EnhancedSync which, as you may already know, introduce motion judder and all sort of issues (I've a non-FreeSync monitor).
It took me ages to find a method to finally run Dead Space 2 at 60FPS with proper frame pacing / vsync and I just felt like more people should know about it. I most certainly didn't, even though I consider myself a hardcore PC enthusiast!
And while the tool indeed has its share of quirks, it works brilliantly for the most part, aside from the initial hiccup. I'm not sure what causes it. It might very well be just me facing these issues.
Anyhow, I hope that explained why I made those edits! However, feel free to take it down or modify it as you may see fit. No hard feelings, whatsoever! I absolutely understand where you're coming from.
Cheers.
"I'm sorry, I'm new to editing Wikis so I've no idea what the 'protocol' is or how PCGW works in general." Well, I didn't know this, but then have to say again that your first edit was regarding content fully in-line with PCGW editing guidelines from what I can see :) Nice to see a new editor putting in the works to look at examples or editing guidelines to make some good first real edits :) If you perhaps have the time, would you want to test and let me know if any of these solutions at the linked glossary page (https://www.pcgamingwiki.com/wiki/Glossary:Vertical_sync_(Vsync)#Vendor_agnostic_solution) works as good or even better than your added GeDoSaTo solution? (apart from Special K and dgvoodoo as those are more hacky solutions) What troubles did you encounter with AMD driver level Vsync as you said and pointed out here (see https://www.pcgamingwiki.com/wiki/Glossary:Vertical_sync_(Vsync)#AMD)? I assume you have the latest GPU driver version?